In Tapestry terms, you need to reset the Tapestry cache of templates and specifications, which is easy enough to do. The hard part is any changed classes in WEB-INF/classes. Those are hard to pick up ... out of the web application's control. This is a worse problem as we transition to annotations and away from XML. Free yourself from JSP thinking. With moderate effort; storing templates and specs on the file system is the default, but not an absolute. You can certainly get this kind of data out of a database. And if your new modules are just re-arrainging and re-configuring existing fragments, then your in even better shape. -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind
Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com <http://howardlewisship.com/> _____ From: edward earley [mailto:[EMAIL PROTECTED] Sent: Thursday, June 30, 2005 8:43 AM To: [EMAIL PROTECTED] Subject: question about tapestry hi howard, i have a bit of an advanced question in re tapestry and web frameworks in general. since tapestry seems to be a bit more of a pardigm shift for web app frameworks, i thought that you & the tapestry developers might find this interesting.... sorry to intrude. does tapestry have the abilty to hot deploy 'sub-components' of a web app? say for a web app -tomcat ---webapps -------mywebapp ------------module1 ------------module2 ------------module3 ------------WEB-INF .... needed: the ability to redeploy module3 while the entire webapp is running. do you see what i mean? if you or the tapestry developers have ever seen something like this, than please let me know. otherwise, if i write it myself, i can always donate it to tapestry if you all are interested in something like this. it would not be tapestry specific although, would work for any old web app. thx
