That's vaguely the approach I'm hoping to persue. It gets complicated, with multiple templates per component (localized templates) and the way in which specification data (from XML) gets interweaved with HTML template and even annotations.
Say you have a component Foo with a template and an XML: specification file. Any change to either the template or the XML requires invalidating any page or components that uses the Foo component, recursively. To do it right requires a smarter object pool as well, since if at the moment of invalidation, there are affected pages checked out of the pool, it will be necessary to recognize and discard those pages when detached from their request cycles. On 8/26/05, Kent Tong <[EMAIL PROTECTED]> wrote: > Hi, > > It seems that to support hot-deploying of html templates based > on timestamps, the required changes are localized in a single > class: TemplateSourceImpl. Instead of returning a ComponentTemplate > from various template locating methods, they may return a Resource > instead. Then one can get an URL from the Resource, open a > connection and get the last modified time. > > Do you think this approach will work? > > -- > Author of an e-Book for learning Tapestry (http://www.agileskills2.org/EWDT) > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
