performance - EJB3 - Session Bean calling method of another bean interface -


I have a little question ... I find a difference in local reach between access to a method which is only remote Is declared in a Bean's interface and not in the local interface ...

Does the Interface Declaration (Remote or Local) method determine the Access Protocol? Or does the Eugene Container understand that both beans are running the same JVM? What is a big performance difference? Do you have any source about it?

BR

Laurent

I make sure I would suggest testing it on your EJB container.

It has been said that, according to the spec, (Section 3.2.3) @ Remote Interface should use the pass-value parameter, whereas @ locally-context parameter passes

< P> This means that if both clients and @Remote Bean are on the same JVM, then the parameter is an overhead of the copy.

It also means that all @mammot parameters must be serial jub.


Comments

Popular posts from this blog

c# - ListView onScroll event -

PHP - get image from byte array -

Linux Terminal Problem with Non-Canonical Terminal I/O app -