Dan, (& Richard)
a normal jndi lookup of an EJB from another EJB
*may not* guarantee that the lookup will return
a reference to an EJB in the same container as
the caller (or lookuper ;) . this can happen when
when you've clustered your ejb server and lookups
return references based on load balancing/round
robin algorithms - unless you've used ejb links/references
I could go into some detail here, but for a slightly
more detailed explanation - you could refer to
page 20 - 'EJB Design Patterns' by yours truly at
http://www.borland.com/appserver/papers
Richard does bring up an interesting point - on
how to convert between remote/local interfaces.
On another note, I am actually wondering about
the real world benefits of local interfaces - as
quite a few ejb vendors (mostly with a corba
infrastructure i might add) detect & optimize
co-located calls. of course - i can see some
advantages - like local interfaces for entity beans
but the same could be accomplished by
- having the facade pattern (session wrap entity)
and making session beans the only point of
access for clients.
- having T attribute "Mandatory" for entity beans
preventing clients from calling EBs directly (unless
clients start up a transaction which should anyways
be discouraged)
- not distributing entity bean classes/stubs to client
side application developers
-krish
> Hi Richard,
>
> What's the disadvantage of using the existing JNDI lookup
> mechanism?
>
> -Dan
===========================================================================
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".
