I ended up finding out what was wrong... I had deployed the ejbjar and war seperately so they did not have the same classloader. One way to work around this is change tomcat to use the jboss classloader, but that mucks up other things.
I ended up deploying my ejbjar and war into an ear, this didn't help either! I made a third jar which contained the interfaces which both ejb and war used, and then I made the manifest from the ejbjar and war include the common interfaces into its classpath. I did have a problem with forgetting that my highest interface extended the apache abstractlogenabled interface, and I needed to include that in the manifest too. Now it's all working sweet though. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3937810#3937810 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3937810 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
