>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.
It is true you cannot have 100% portable EJB clients.
There are ways to mitigate the problem, as that code shows.
Anyway EJB clients are "more" portable than what you get
with any other server-side component framework.
Regards
Javier
===========================================================================
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".
