I rearranged my deployment a bit and solved the datasource error, but now my EJBs fail to deploy with a similar problem. I suspect that I'm not deploying my classes correctly.
My EAR consists of three common jars - two ejb jars - and a war. I declared everything in application.xml as either a "java" module, an "ejb" module or a "web" module. I'm operating under the assumption that the ejb and web modules ought to be able to access all the classes in the java modules - is this correct assuming an isolated deployment strategy? If not, would packaging copies of all the common jars into each EJB and WAR be the recommended approach? I had thought that it was possible to share these classes even with a strict classloader. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3920596#3920596 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3920596 ------------------------------------------------------- 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://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
