|
Replies:
6
-
Last Post:
Mar 17, 2009 7:43 AM
by: Felipe Gaúcho
|
|
|
|
|
|
|
Properties resource ? is it a good idea ?
Posted:
Mar 17, 2009 2:54 AM
|
|
|
do we have a "properties resource" in Glassfish ?
if not, is it a good idea ?
as we have JDBC, JMS and JavaMail resources, why not to have a
Property resource ? a place where to write all configuration params
shared by applications ?
--
Please help to test this application:
http://fgaucho.dyndns.org:8080/cejug-classifieds-richfaces
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net
|
|
|
|
|
|
|
RE: Properties resource ? is it a good idea ?
Posted:
Mar 17, 2009 6:06 AM
in response to: Felipe Gaúcho
|
|
|
There is nothing like that because the Java EE way to store configuration params is to put them in the ejb-jar.xml file. The core idea of this originally was that all configuration is to be stored in a directory service (like ActiveDirectory, OpenLDAP etc) so administrators can modify the configuration easily with any LDAP- or JNDI-aware tool (or the native tools / GUIs of the directory vendor), while the value found in ejb-jar.xml will be just the defaults. Unfortunately it seems as if no server vendor supports this, at least officially. This some kind of strange, because in the Windows world for example, it is pretty usual to store anything in the AD...
> as we have JDBC, JMS and JavaMail resources, why not to have a
> Property resource ? a place where to write all configuration params
> shared by applications ?
|
|
|
|
|
|
|
|
|
Re: Properties resource ? is it a good idea ?
Posted:
Mar 17, 2009 6:10 AM
in response to: Markus Karg
|
|
|
the classical example is the key for encryption.. where to put it ??
ejb-jar.xml is not a good idea unless all your developers can have
access to the password..
if I have Properties resources - perhaps also with encrypted features
- the admin can manage a few secret password and other installation
values without any relationship with the packaged artifacts.. just an
idea...... actuall a day-by-day missed feature..
On Tue, Mar 17, 2009 at 2:06 PM, Markus Karg <karg@quipsy.de> wrote:
> There is nothing like that because the Java EE way to store configuration params is to put them in the ejb-jar.xml file. The core idea of this originally was that all configuration is to be stored in a directory service (like ActiveDirectory, OpenLDAP etc) so administrators can modify the configuration easily with any LDAP- or JNDI-aware tool (or the native tools / GUIs of the directory vendor), while the value found in ejb-jar.xml will be just the defaults. Unfortunately it seems as if no server vendor supports this, at least officially. This some kind of strange, because in the Windows world for example, it is pretty usual to store anything in the AD...
>
>> as we have JDBC, JMS and JavaMail resources, why not to have a
>> Property resource ? a place where to write all configuration params
>> shared by applications ?
>
--
Please help to test this application:
http://fgaucho.dyndns.org:8080/cejug-classifieds-richfaces
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net
|
|
|
|
|
|
|
|
|
RE: Re: Properties resource ? is it a good idea ?
Posted:
Mar 17, 2009 6:48 AM
in response to: Felipe Gaúcho
|
|
|
Why not putting it into a directory server and use JNDI to look it up?
> -----Original Message-----
> From: Felipe Gaúcho [mailto:fgaucho@gmail.com]
> Sent: Dienstag, 17. März 2009 14:10
> To: users@glassfish.dev.java.net
> Subject: Re: Properties resource ? is it a good idea ?
>
> the classical example is the key for encryption.. where to put it ??
>
> ejb-jar.xml is not a good idea unless all your developers can have
> access to the password..
>
> if I have Properties resources - perhaps also with encrypted features
> - the admin can manage a few secret password and other installation
> values without any relationship with the packaged artifacts.. just an
> idea...... actuall a day-by-day missed feature..
>
> On Tue, Mar 17, 2009 at 2:06 PM, Markus Karg <karg@quipsy.de> wrote:
> > There is nothing like that because the Java EE way to store
> configuration params is to put them in the ejb-jar.xml file. The core
> idea of this originally was that all configuration is to be stored in a
> directory service (like ActiveDirectory, OpenLDAP etc) so
> administrators can modify the configuration easily with any LDAP- or
> JNDI-aware tool (or the native tools / GUIs of the directory vendor),
> while the value found in ejb-jar.xml will be just the defaults.
> Unfortunately it seems as if no server vendor supports this, at least
> officially. This some kind of strange, because in the Windows world for
> example, it is pretty usual to store anything in the AD...
> >
> >> as we have JDBC, JMS and JavaMail resources, why not to have a
> >> Property resource ? a place where to write all configuration params
> >> shared by applications ?
> >
>
>
>
> --
>
> Please help to test this application:
> http://fgaucho.dyndns.org:8080/cejug-classifieds-richfaces
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
|
|
|
|
|
|
|
|
|
Re: Re: Properties resource ? is it a good idea ?
Posted:
Mar 17, 2009 7:09 AM
in response to: Markus Karg
|
|
|
because I miss all admin console features and JMX features, etc..
the same question apply to JDBC resources.. why not to put the JDBC
connection properties in a file somewhere and load it.. 
it is so robust and easy to configure things through the console..
that I tend to imagine the properties resources as a good thing..
On Tue, Mar 17, 2009 at 2:48 PM, Markus Karg <karg@quipsy.de> wrote:
> Why not putting it into a directory server and use JNDI to look it up?
>
>
>> -----Original Message-----
>> From: Felipe Gaúcho [mailto:fgaucho@gmail.com]
>> Sent: Dienstag, 17. März 2009 14:10
>> To: users@glassfish.dev.java.net
>> Subject: Re: Properties resource ? is it a good idea ?
>>
>> the classical example is the key for encryption.. where to put it ??
>>
>> ejb-jar.xml is not a good idea unless all your developers can have
>> access to the password..
>>
>> if I have Properties resources - perhaps also with encrypted features
>> - the admin can manage a few secret password and other installation
>> values without any relationship with the packaged artifacts.. just an
>> idea...... actuall a day-by-day missed feature..
>>
>> On Tue, Mar 17, 2009 at 2:06 PM, Markus Karg <karg@quipsy.de> wrote:
>> > There is nothing like that because the Java EE way to store
>> configuration params is to put them in the ejb-jar.xml file. The core
>> idea of this originally was that all configuration is to be stored in a
>> directory service (like ActiveDirectory, OpenLDAP etc) so
>> administrators can modify the configuration easily with any LDAP- or
>> JNDI-aware tool (or the native tools / GUIs of the directory vendor),
>> while the value found in ejb-jar.xml will be just the defaults.
>> Unfortunately it seems as if no server vendor supports this, at least
>> officially. This some kind of strange, because in the Windows world for
>> example, it is pretty usual to store anything in the AD...
>> >
>> >> as we have JDBC, JMS and JavaMail resources, why not to have a
>> >> Property resource ? a place where to write all configuration params
>> >> shared by applications ?
>> >
>>
>>
>>
>> --
>>
>> Please help to test this application:
>> http://fgaucho.dyndns.org:8080/cejug-classifieds-richfaces
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
>> For additional commands, e-mail: users-help@glassfish.dev.java.net
>
>
--
Please help to test this application:
http://fgaucho.dyndns.org:8080/cejug-classifieds-richfaces
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net
|
|
|
|
|
|
|
|
|
Re: Re: Properties resource ? is it a good idea ?
Posted:
Mar 17, 2009 7:35 AM
in response to: Felipe Gaúcho
|
|
|
1) JDBC resources configuration can be specified using a xml file and
loaded
http://blogs.sun.com/JagadishPrasath/entry/jdbc_connection_pool_templates_glassfish
2) For properties resource, it is proposed for v3 :
http://wiki.glassfish.java.net/Wiki.jsp?page=GFV3JDBCOnePager#section-GFV3JDBCOnePager-4.1.7BuiltInFactoriesForCustomResources
Thanks,
-Jagadish
On Tue, 2009-03-17 at 15:09 +0100, Felipe Gaúcho wrote:
> because I miss all admin console features and JMX features, etc..
>
> the same question apply to JDBC resources.. why not to put the JDBC
> connection properties in a file somewhere and load it..
>
> it is so robust and easy to configure things through the console..
> that I tend to imagine the properties resources as a good thing..
>
>
>
> On Tue, Mar 17, 2009 at 2:48 PM, Markus Karg <karg@quipsy.de> wrote:
> > Why not putting it into a directory server and use JNDI to look it up?
> >
> >
> >> -----Original Message-----
> >> From: Felipe Gaúcho [mailto:fgaucho@gmail.com]
> >> Sent: Dienstag, 17. März 2009 14:10
> >> To: users@glassfish.dev.java.net
> >> Subject: Re: Properties resource ? is it a good idea ?
> >>
> >> the classical example is the key for encryption.. where to put it ??
> >>
> >> ejb-jar.xml is not a good idea unless all your developers can have
> >> access to the password..
> >>
> >> if I have Properties resources - perhaps also with encrypted features
> >> - the admin can manage a few secret password and other installation
> >> values without any relationship with the packaged artifacts.. just an
> >> idea...... actuall a day-by-day missed feature..
> >>
> >> On Tue, Mar 17, 2009 at 2:06 PM, Markus Karg <karg@quipsy.de> wrote:
> >> > There is nothing like that because the Java EE way to store
> >> configuration params is to put them in the ejb-jar.xml file. The core
> >> idea of this originally was that all configuration is to be stored in a
> >> directory service (like ActiveDirectory, OpenLDAP etc) so
> >> administrators can modify the configuration easily with any LDAP- or
> >> JNDI-aware tool (or the native tools / GUIs of the directory vendor),
> >> while the value found in ejb-jar.xml will be just the defaults.
> >> Unfortunately it seems as if no server vendor supports this, at least
> >> officially. This some kind of strange, because in the Windows world for
> >> example, it is pretty usual to store anything in the AD...
> >> >
> >> >> as we have JDBC, JMS and JavaMail resources, why not to have a
> >> >> Property resource ? a place where to write all configuration params
> >> >> shared by applications ?
> >> >
> >>
> >>
> >>
> >> --
> >>
> >> Please help to test this application:
> >> http://fgaucho.dyndns.org:8080/cejug-classifieds-richfaces
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> >> For additional commands, e-mail: users-help@glassfish.dev.java.net
> >
> >
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net
|
|
|
|
|
|
|
|
|
Re: Re: Properties resource ? is it a good idea ?
Posted:
Mar 17, 2009 7:43 AM
in response to: Jagadish Prasat...
|
|
|
> 2) For properties resource, it is proposed for v3 :
wow, great !
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net
|
|
|
|
|
java.net RSS
