The main complication is that the Ejb3Deployer is processing an ear deployment unit for
essentially no reason. In the past I guess this is what was creating the root ejb3
DeploymentUnit to be able to resolve nested ejbs, but this is handled by other deployers.
Its also still doing too much processing that prepares for annotation scanning that is
also done elsewhere. At some point this needs to be overhauled. For now I have just
corrected the check for a nested/scoped ejb jar and the seam booking testcase is running.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157158#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...