I suspect strongly that you're right when you say a full manual republish is required.
In order for the changes to become apparent, JBoss will need to be told a new module or group of class files is available. It will then need to dump references to the old classes and load the new ones. I can't imagine any way in which changes such as that can be viewed without jboss reloading the classes. The only exception I can think of would be if the IDE was merely emulating or pretending to be the actual app-server and the changes weren't "live" on the server but were shown as projections as to how it will look once on the server. If anyone has any idea as to how JBoss could make redeployment faster, or more targeted to the specific changes, I'll be sure to take note of that and try to add it into the IDE's debugging and redeployment features, but until I hear about that, I'm pretty sure a full redeploy is required for module changes. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3949983#3949983 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3949983 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
