You are correct that obtaining the InitialContext requires different
parameters depending on the EJB container you are using, but the process of
obtaining this context is the same. Portability is achieved by placing the
vendor specific parameters in a properties file that is external to your
application.
jim
----- Original Message -----
From: Ron Yust <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, October 20, 1999 10:19 AM
Subject: EJB client context
> I'm setting up an EJB client application that would support different EJB
> servers. I've discovered that the clients could have different methods
for
> obtaining a JNDI context for each server depending on the EJB vendor.
> Doesn't this decrease the portability of EJB if I have to modify client
code
> for each installation? I was hoping that it would be as simple as coding
> Context.INITIAL_CONTEXT_FACTORY and Context.PROVIDER_URL properties for
each
> vendor (which could be supplied as client startup properties) and then
> obtaining a InitialContext.
>
> Am I missing something? Has anyone gotten around this and developed a
> generic way for clients to obtain the server context? Thanks.
>
> Ron Yust
> Director of Information Services
> Empire District Electric Co.
> (417) 625-5126 voice
> (417) 625-5155 fax
>
>
>
===========================================================================
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".
