Yes, please. It caused a lot of problems when running Tapestry in OSGi where a bundle can be reloaded at runtime.
On Tue, Feb 15, 2011 at 12:29 AM, Howard Lewis Ship <[email protected]>wrote: > I'm starting to wonder whether Tapestry should, in production mode, > not even check for file changes. All the related code could be > converted to no-ops and placeholders, and the portion of the code that > even has to decide when to check for file changes could be removed. > > -- > 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! > > (971) 678-5210 > http://howardlewisship.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Best regards, Igor Drobiazko http://tapestry5.de
