Hmmm, you do raise a valid issue. I searched the entire EJB 2.0 spec for
various usages of "scope", but was not able to find a definition of what is
meant by "local scope" which is used so often in the spec. I am too, very
interested in these implications.
Most likely that "local scope" means in the same ejb-jar.xml descriptor
(although the spec does mention something about local running in the same
JVM, but nothing about classloaders). This implies that the only client
that can use a local-view is another Entity bean deployed in the same
ejb-jar.xml. Meaning, that a "local" web client is not possible, since it
will be deployed using a different descriptor.
This kinda limits the "local" view, but then again, that's why it is called
"local" right?
-AP_
-----Original Message-----
From: A mailing list for Enterprise JavaBeans development
[mailto:[EMAIL PROTECTED]]On Behalf Of Daniel OConnor
Sent: Monday, April 30, 2001 7:35 AM
To: [EMAIL PROTECTED]
Subject: EJB 2.0: local interfaces and classloaders
Version two of the proposed final draft for EJB 2.0 introduces the
concept of local interfaces, which use pass-by-reference
semantics. These local interfaces are required to be co-located in
the same JVM as their clients (obviously). However, apparently
local interfaces can be located in a different deployment unit from
their client--or can anyone point to something in the specification
which contradicts this?
It seems to me that this introduces an implementation issue. If
multiple deployment units are deployed into the same JVM,
wouldn't they have different class loaders? This would be the most
obvious way to implement features such as hot deploy and
configurable Java security, anyway. But interface and value-object
(e.g. view object) instances passed by reference across class
loaders would result in a ClassCastException, wouldn't they?
I'm guessing I'm missing something obvious...
===========================================================================
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".
===========================================================================
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".
