> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Gautam Borah
> Coming back to my original point, IMHO the Local Interfaces should not be
> exposed through JNDI names, as they are not available in the network(They
> are not remote, nor serializable). These interfaces should be accessed
> through only by the <ejb-local-ref> and the Container should be able to
> resolve this at the deployment time. *Having two JNDI names for the same
> bean !!* , specification is not very much clear about this issue
> and is very much debatable.
Good points. The compromise WLS 6.1 adopted for now is to bind the local
home in the JNDI tree but not make it serializable, so it can't be looked up
from a remote client.
Probably not the best solution but it obeys the principle of least surprise.
Any suggestions to improve it will be very welcome.
--
Cedric
===========================================================================
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".
