Dunno actually. My build script has done that for the last 2 years I guess and it has always worked. The APP-INF/lib/classes.jar contains all classes I need in the nested deployed jars. So in fact, the nested .jar (and also .war that I did not mention) only contain the deployment descriptors for the session beans.
I have made some progress since... had a typo in a setter method of one of the properties of the resource adapter. I discovered that when I used the same structure as the examples (i.e. not use nested deployment). Currently, the app deploys but I cannot see my MDB connecting to the resource adapter, although I have logging in the activtion method. Rudi. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3913243#3913243 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3913243 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
