yu_robin <[EMAIL PROTECTED]> writes:
>For compatibility, I suggest that you should not use this "feature" in WLG,
>whether all ejbs live in one JVM or not is not mandatory in specification.
This WebLogic "feature" is unfortunately defaulted to on with WebLogic
5.1 at least - a rather dangerous default IMHO.
It is also actually illegal under the new EJB 2.0 specification.
Section 23.2.7 (my emphasis added) :
The enterprise bean's home and remote interfaces are remote interfaces
for Java RMI.
The Container must ensure the semantics for passing arguments conform to
Java RMI.
** Non-remote objects must be passed by value. **
Specifically, the EJB Container is ** not allowed to ** pass non-remote
objects by reference on inter-EJB invocations when the calling and
called enterprise beans are collocated in the same JVM.
Doing so could result in the multiple beans sharing the state of a Java
object, which would break the enterprise bean's semantics.
----------------------------------------------------------------------
| Orbware Ltd http://www.orbware.com/ |
| --- Enterprise technology for the "real world" --- |
| Try the OrCAS EJB server -- Completely free for development use. |
----------------------------------------------------------------------
===========================================================================
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".
