Javier,
Thanks for the nice piece of code, but it still doesn't solve the problem if
the EJB vendor requires initial context properties beyond just the factory
name and url. That's the core of the problem. There appears to be no spec
on how vendor's implement JNDI interfaces to their servers.
-Ron
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Javier Borrajo
> Sent: Wednesday, October 20, 1999 11:58 AM
> To: [EMAIL PROTECTED]
> Subject: Re: EJB client context
>
>
> >> Ron Yust wrote:
> >> 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....
>
> You may find this code useful...
>
> Regards
>
> Javier Borrajo
>
>
===========================================================================
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".
