Hi!
Another variant is to have an object on JNDI or RMINaming which contains
properties needed for you object and just lookup it and use. The only
property you will need is where to get the object.
You can also initialize settengs from plain text read from some URL.
The problem is that it is unspecified if how you can add object to JNDI
namespace before use of any related object. I think that we maybe need
something like "EJB Service deployment descriptor" for protable way
of doing things like this.
Constantine
Rickard �berg wrote:
>
> Hey
>
> Bob Pecor wrote:
> > I understand that I could manually put the info I want in a number
> > of places but that is not an implementation-independent
> > approach: if I change vendors I must change the hard-coded
> > info. I would rather "discover" the info dynamically at class
> > initialization time.
>
> I understand, and agree. A workaround would be to create a number of
> properties-files which contains the various info for the servers that
> the EJB:s could be deployed with. Upon runtime you could try them out in
> sequence to determine which is the right one. (ugly ugly ugly, but might
> actually work and requires less work than manual hardcoding).
>
> /Rickard
>
> --
> Rickard �berg
>
> Computer Science student@LiTH
> @home: +46 13 177937
> Email: [EMAIL PROTECTED]
> Homepage: http://www-und.ida.liu.se/~ricob684
>
> ===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
