How to get Tapestry to eagerly create the components/pages

[Patrick Moore <pm...@yahoo.com>]

Hi there --

How do I get Tapestry to eagerly parse all component and page files so that in
production I know that there are no bad pages or components caused by, for
example, out-of-date template files? 

I would also like a cluster to be able to share the results of the parsing so
only one vm would actually do the parsiong on a given template, the other vms
would get the result just like they would get any other object shared across a
cluster. 

Ideas?

-Pat

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org