Yes, this is one example of Spec-defined logic that I'd like performed by
jboss-metadata (not a deployer responsible for populating JBossSessionMetadata).
Another example is:
@RemoteHome
| public interface RemoteHome extends EJBHome{
|
| public RemoteInterface1 create();
|
| public RemoteInterface2 create2();
|
| }
The above example defines 2 EJB2.x Remote interfaces, even though they're not
explicitly marked as such anywhere.
That's EJBTHREE-1127, defined by:
"EJB3 Core Specification 3.6.2.1" wrote : The return type of a create method on
the remote home interface is the session bean's remote interface.
Currently this is being handled (improperly?) by Proxy generation code. Metadata
doesn't access the ClassLoader for the Container, so I don't see a way to handle
this there now. Ideas?
S,
ALR
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151223#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...