Em Thu, 24 Sep 2009 11:28:09 -0300, Vangel V. Ajanovski <a...@ii.edu.mk>
escreveu:
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:
http://wiki.apache.org/tapestry/Tapstry5First_project_with_Tapestry5%2C_Spring_and_Hibernate
So the changes in the DAO or Manager classes are not reflected without
reloading the application.
Tapestry class reloading only works for the classes it controls: pages,
components and mixins. But it is a huge productivity boost anyway. :)
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 ...
But the live class reloading can still be used in development, while not
being used in production.
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
