Does anybody knows why my application context (in tomcat) gets fully reloaded after I change a simple Action class? I mean, if I change a "if" condition and build the application in the MyEclipse, all the application gets reloaded, and I have to wait almost 80 seconds to it do all the work... My framework uses Spring+Struts+Hibernate.
Action classes, like servlets are multi-threaded classes that remain resident in memory as long as the application is running. I'm guessing that somehow MyEclipse recognizes that when you change an Action, it won't become effective unless you restart the web application, so it restarts the application.
Thanks Merrill, but in another project that uses only Struts+Hibernate this Action classes works perfectly! Just like updating a jsp page, the reload is NOT reloaded but the class source is.
Does anybody knows a good solution to develop java code in projects that takes long time to reload the context? It's so boring and counter-productive having to wait for 80-90 seconds every time I modify an Action class.