Local beans should be accessible cross-application about ejb-spec

[glassfishrobot]

Reported by reza_rahman

[glassfishrobot]

paulusbenedictus said:
I don't know how this feature could work properly. When dealing with local beans, the client holds onto the actual bean instance – unlike a proxy for remote interfaces. If a local bean is shared across applications, how can the hosting application ever undeploy/redeploy it?

[glassfishrobot]

@arjantijms said:
Paul, for local beans the client gets a proxy as well and not the actual bean reference. This is needed so the container can do things like start a transaction and call an interceptor. A major difference between a local and remote proxy is that the former doesn't serialize method arguments and return values, while the latter does, but they are thus both proxies.

Or did you mean something else?

[glassfishrobot]

paulusbenedictus said:
My apologies! Arjan, I didn't know local beans were proxied; thought that was exclusive to remote beans. Thanks for the information.

[glassfishrobot]

wolfc said:
How would you want to deal with class loading? Especially the arguments of methods.

To keep pass-by-reference semantics they must come from the the same class loader.

This becomes especially interesting once you undeploy (/ redeploy) the app containing those classes.

[glassfishrobot]

Was assigned to mvatkina

[glassfishrobot]

This issue was imported from java.net JIRA EJB_SPEC-22