One issue that showed up in JBCTS-717 was metadata that looked like xml input but was
missing the required mapped name. This is metadata being generated from the deployment
annotations. I added logic similar to what existed for the @Resource processing for known
types like UserTransaction and ORB. I suppose this logic should be in the
ReferenceMetaDataResolverDeployer.
We are also doing duplicate annotation processing, so how that gets dropped from the ejb3
container needs to be discussed.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109520#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...