Ian McCallion wrote:
> The point is that as well as portability, the INTENT of J2EE is that each EJB's
>context
> can be different so as to permit, for example, a production and a test version of the
> same EJB to automatically access production or test resources and to enable beans to
>be
> moved about from machine to machine without affecting their clients.
For what it's worth, we've also used InitialContexts to avoid using a
vendor-specific API. It's similar to the way JDBC drivers are used. But
instead of doing Class.forName(), etc to register an implementation of a
standard interface, as with JDBC, we use InitialContexts to achieve the
same result. The nice thing about it is that you not only avoid
importing a certain vendor's package (com.foo.*), but it's a great way
to use the same InitialContext API to create a local object, to create
an RMI server, or to lookup a remote RMI server. And it works fine on
both the client-side, the server-side, and in standalone client
applications.
cheers,
david
--
David Sims [EMAIL PROTECTED]
Sims Computing, Inc. www.simscomputing.com
===========================================================================
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".
