(moved from jboss-user)
Rickard Oberg wrote:
>
> >Rickard �berg wrote:
> >
> >> Pretty much, yes. When you say optimized, you do mean calls between
> >> beans in same jar, right?
> >
> >No, I mean calls from inVM client (tomcat)
> >
> >This test is a simple session bean, deployed twice: once with
> >Optimized=true, once with Optimized=false. A servlet (deployed with
> >EmbeddedTomcat, inVM, classloader integration) calls the 2 beans. (the
> >test is in the contrib module, tomcat directory).
> >
> >Results should be better with the optimized bean, they were until
> >recently.
> >
> >It seems the last checks you added prevent the optimization to work in
> >this case (servlet->ejb).
>
> Hm...yeah, that's true. The parent check is not enough, I realize that now.
> Any suggestions on improvement? Should we check parent of parent too..or?
Hi,
I don't know, but the approach you took when you did the changes was "in
the case of different jars (external ejb-ref), optimization is not
possible, so don't allow it".
Why would you think of "in the case of different jars, make optimization
possible (ie merge, or whatever, the classloaders, during deployment)"?
Would it be difficult/dangerous?
It would be more efficient:
- optimized calls
- no checks necessary in JRMPCI (see the embedded tomcat test, they seem
to take some time)
Sebastien
