On 24.09.2009 15:39, Thiago H. de Paula Figueiredo wrote:
http://www.zeroturnaround.com/blog/java-ee-container-redeploy-restart-turnaround-report/Hi, I would really like to have live class reloading but it doesn't work for all classes because I use the pattern with Spring and Hibernate described at:It makes one very compelling reason to use Tapestry 5: live class reloading avoids almost most redeploys related to the web tier. :)
http://wiki.apache.org/tapestry/Tapstry5First_project_with_Tapestry5%2C_Spring_and_HibernateSo the changes in the DAO or Manager classes are not reflected without reloading the application.
And that is for development, for deployment I have a bigger problem because it is under Tomcat 6 which is behind AJP fronted by MS IIS. And if the application is packaged from maven as a WAR, then all the classes are inside packed in a JAR, which Tomcat extracts in a temporary place and sometimes is not refreshed even if you bring a newer WAR. So I have to stop the application, clean the WAR, clean the extracted folders, clean the temp and work folders ...
smime.p7s
Description: S/MIME Cryptographic Signature
