Template files that change will be picked up, as long as they are on the file system, not packaged in a JAR. This may happen when the servlet container "explodes" the WAR file as part of deployment. It is not dependent on production mode.
On Wed, Sep 9, 2009 at 10:40 PM, Kalle Korhonen <kalle.o.korho...@gmail.com>wrote: > The templates need to be on the classpath. It's completely up to you > whether you want to keep them in a jar, war, ear or as plain files in > the file system. However, I don't think changes in the templates would > be picked up unless you run in non-production mode. > > Kalle > > > On Wed, Sep 9, 2009 at 10:20 PM, Angelo Chen<angelochen...@yahoo.com.hk> > wrote: > > > > Hi, > > I'd like to update the templates for component in the live server, but it > is > > always stored in: > > > > myapp/ROOT/WEB-INF/lib/myapp.jar > > > > is there a way not to include those tml in the jar file? Thanks, > > > > Angelo > > > > -- > > View this message in context: > http://www.nabble.com/t5%3A-templates-used-for-component-tp25377468p25377468.html > > Sent from the Tapestry - User mailing list archive at Nabble.com. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast!
