Hi, I am not sure, but looking in the EJB spec (draft version), for two
times it specifically forbid the optimized EJB calls made in JBoss. Citing
the draft:
<quote>
The enterprise bean�s remote home and remote interfaces are remote
interfaces in the Java RMI sense.
The Container must ensure the Java RMI argument passing semantics.
Non-remote objects must be
passed by value across these interfaces.
Specifically, the EJB Container is not allowed to pass objects by reference
on inter-enterprise bean invocations
of methods on the enterprise bean�s remote home and remote interface 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.
EJB 2.0 entity beans and session beans support local and local home
interfaces. The arguments of the
methods of these interfaces are passed by reference, and the local clients
of such beans must be collocated
in the same JVM. Such beans must be coded to assume that the state of any
Java object that is
passed as an argument or result is shared by caller and callee.
</quote>
> -----Mensaje original-----
> De: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]En nombre de Scott
> M Stark
> Enviado el: mi�rcoles, 19 de septiembre de 2001 1:29
> Para: [EMAIL PROTECTED]
> Asunto: [JBoss-dev] Optimized EJB calls in catalina
>
>
> I looked at integrating the catalina final release with integrated
> security and JNDI and I find that everything works except for optimized
> EJB calls. This occurs for wars that include the EJB interfaces in their
> classes directory. This has been required for wars with JSP pages that
> access EJBs. I have not tested the catalina version of jasper to see if
> this is still required.
>
> The reason EJB calls are not optimized for this scenario is that the
> web container class loader loads classes in WEB-INF/classes before
> asking its parent class loader. This seems to be consistent with the
> 2.3 servlet spec if "container-wide library JARs" is taken to mean
> jars accessible by the container parent class loaders.
>
> If the EJB interfaces are not in the war then call optimization works as
> before.
>
> <servlet-2.3-fcs spec>
> SRV.9.7.2 Web Application Classloader
>
> The classloader that a container uses to load a servlet in a WAR
> must allow
> the
>
> developer to load any resources contained in library JARs within the WAR
>
> following normal J2SE semantics using getResource. It must not
> allow theWAR
> to
>
> override J2SE or Java servlet API classes. It is further recommended that
> the loader
>
> not allow servlets in theWAR access to the web container's implementation
> classes.
>
> It is recommended also that the application class loader be implemented so
>
> that classes and resources packaged within the WAR are loaded in
> preference
> to
>
> classes and resources residing in container-wide library JARs.
>
> </servlet-2.3-fcs spec>
>
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
