Except for the jboss-ejb3-ext-api project https://github.com/jbossejb3/jboss-ejb3-ext-api which provides JBoss EJB3 specific annotations (as of now), rest of the EJB3 integration code *all* lies within the AS7 code base. That means that the jboss-ejb3 code that was used in previous versions of AS is no longer used for AS7. Some of the reusable classes have been moved back to the AS7 codebase.
Viacheslav Krot wrote:
I want to use IsLocalInterceptor in order to do calls by reference if EJB is located in same JVM as the client.
That interceptor and other similar AOP interceptors are no longer applicable for AS7.
Thank you for replay.
Maybe you could suggest me how to archive my goal in other way: I'm porting a EJB2 application from weblogic. Many EJBs there are configured with option enable-call-by-reference, it means that if bean resides in same JVM, even if it is reached via removed interface, there will be no serialization overhead and everything will be passed by reference.
I'm not concerned about performance overhead of serialization, but guys that wrote that app maybe relied on that feature and made changes to objects that were passed as parameters to EJB method. If it is the case, serialization will break the code behavior.
Is there a way to archive this in JBoss7?
Thank you. This is just what I was looking for.