well - it depends on what your packaing looks like. 1) if you have an ear and inside that ear you put the ejb jars, the jsps (inside a war) and whatever else you want in there, then you can just hot-deploy the entire ear all you want and not encounter this issue.
2) you can extract the interfaces (Remote Home, Remote) into a seperate jar file from the EJB impl class (so you've now got 2 jar files). if you do this, then as long as you don't add any methods to the interfaces, you can modify the EJB impl class all you want and redeploy w/o having to touch the jsp files. if you add a method to the interfaces, then you're only option is to either restart the server or "touch" all the deployed packages that reference the EJB interface that just changed. it will probably be easier to just restart the server if you have more then 1 or 2 deployment archives referencing the EJB. if you are going to be adding more methods to the interface, and you know what the method names, params, return types, etc will be up front, then just stub them out in the impl class - that way you'll reduce the number of times for a server restart b/c only the impl class is changing. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3834474#3834474 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3834474 ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
