jaikiran, Okay I believe I have located the problem. I have not opened a JIRA yet because this may well be spec, though it seems a strange spec to me (and certainly different from JBoss 4.2.3).
Basically: the presence of an <app.ear>/<ejbs.jar>/META-INF/ejb-jar.xml file, even an empty one, short-circuits the annotation-based detection completely. I have put together a little example here: http://kennardconsulting.com/tmp/avant-ss-app.zip You will need to extract it into the deploy/ folder of a fresh JBoss 5.1.0.GA installation. You will find it deploys okay (it errors if you don't give it a -ds.xml, but that's okay) but it has the JBMETA-4 warning and does not set up the JNDI. But if you go in and delete the ejb-jar.xml then it detects the bean via the annotations. This may be intentional. But in 4.2.3 you could specify some beans in your ejb-jar.xml and leave the annotation processing to find the rest. In particular, you could configure some beans with <env-entry>'s and the like without having to specify every bean. So has this changed deliberately? And is there a way to revert to the old behaviour? Richard. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237646#4237646 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237646 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
