AFAICS, if an EJB2 session bean is defined in the ejb-jar.xml version 3 then the EJB3 deployer creates the EJB3 container with the EJB2 client view for the bean.
Is this really how it is supposed to work?
Looking at the test I suspect the setSessionContext(...) is not called on the instance when it is created. Even though I see the Resource annotation is added for the method in the Ejb3DescriptorHandler. Or maybe it doesn't get there or the injection is not performed...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145570#4145570
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145570
According to this thread http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145455#4145455 Ejb3Deployment is going to disappear. Any meta data retrieval should be delegated to JBossMetaData instead.
How do we retrieve arbitrary annotation meta data in this case?
Before EJB3 offered something like getAnnotation(Class c), which allowed me to pull any meta data regardless if it's derived from a deployment descriptor or an annotation.
How do projects add annotation based meta data to the meta data project? I.e. WS defines @EndpointConfig. Does this mean I need to add parsing of that information to the MD project and release it before I can use it? Or is there a more generic way to access annotation based meta data?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145492#4145492
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145492
"heiko.braun(a)jboss.com" wrote : I don't get it. How is an intermediate deployer different from what we already do to Ejb3Deployment? Those interfaces just specify our requirements towards EJB3 meta data. If I am going to put another deployer in between, I still need to work on Ejb3Deployment.
Ejb3Deployment won't be there anymore, you need to work on JBossMetaData. To get that you need to create a deployer which has as input:
addInput(MergedJBossMetaDataDeployer.EJB_MERGED_ATTACHMENT_NAME);
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145455#4145455
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145455