At deployment, Tapestry expects that the application is packaged as a WAR. It caches every specification and template that it reads.
During development, you can force Tapestry to clear its cache on demand (using the Inspector), or you can run in a cache-disabled stated. Redeploying a WAR in Tapestry is the same as redeploying any other type of application; existing user sessions may or may not be invalidated, depending on the servlet container implementation. IF you really needs this kind of functionality, you can deploy as an exploded-WAR (in most systems). You can then force Tapestry to discard its cache. -- [EMAIL PROTECTED] http://tapestry.sf.net > Hello! > > What happens if I modify a html template or .jwc file? Will Tapestry reload it? > If I would have a running site, could I update it without restarting the > application (and so kicking out current users) ? > > Thanks, > Norbi > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
