Hi,
a few days ago implications of local clients pass-by-reference and
classloaders were discussed and one possible solution that was mentioned
were application level classloaders. However, I cannot find a statement in
the spec requiring local clients to be in the same application. 5.3 only
states they have to be collocated in the same VM. Doesn't this make
container implementation rather messy from the classloader perspective?
Wouldn't it make sense to limit local clients to the same application? I
think by far the most common use case for local clients is the web tier of
an app accessing the ejb service layer. How many people have their web
tiers in different apps than their service layer and still need the tight
coupling of a local client view?
Just thinking about how container implementors would deal with the
situation when local ejbs are accessed across application boundaries makes
me shudder. Am I missing something?
Regards,
Robert
(-) Robert Kr�ger
(-) SIGNAL 7 Gesellschaft f�r Informationstechnologie mbH
(-) Br�der-Knau�-Str. 79 - 64285 Darmstadt,
(-) Tel: 06151 665401, Fax: 06151 665373
(-) [EMAIL PROTECTED], www.signal7.de
===========================================================================
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".
