When you redeploy the client classes (interfaces) in the EJB deployment get unloaded from the JVM and then reloaded. However, the WAR is using the old reference it has, which no longer matches the client class references as they have changed in the reload.
You could try bouncing (forcing a redeploy) of the WAR after you deploy a new EJB. You can do this by 'touching' the WAR or otherwise changing the date on the WAR file, assuming it is a packed WAR. Otherwise for an unpacked WAR, you just need to 'touch' the WEB-INF/web.xml to force JBoss to redeploy the WAR. You can also try packing the client classes for the EJB in the WAR. It might save you from having to bounce the WAR. You might need to also set Java 2 Classloading compliance to false in the Tomcat/Jetty deployment descriptor - jboss-service.xml. YMMV. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3830845#3830845 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3830845 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
