Problem solved... Of course, I was the stupid one, not JBoss... Having separate projects for EJB and WEB, my ejb deployment script was including by mistake the web compiled classes. I tested and deployed the EJB module 3 days ago and not touching it since, so it was normal the web classes to be the old ones... Although, when I open the application in browser, shouldn't the classes called be the ones in the WAR and not the ones in the ejb JAR? Anyway, everything is working now.
The problem with the hot code replace still remains. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3832303#3832303 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3832303 ------------------------------------------------------- This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek For a limited time only, get FREE Ground shipping on all orders of $35 or more. Hurry up and shop folks, this offer expires April 30th! http://www.thinkgeek.com/freeshipping/?cpg=12297 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
