Tapestry pages aren't compiled, as they don't use JSPs. However, there
is a lot of run-time injection. To aid in performance, Tapestry uses
pooling. The first time a page is rendered, it's a lot slower than
subsequent requests.
I haven't explored if there's a way to initialize a pool at startup.
Erik? Howard? ...?
[EMAIL PROTECTED] wrote:
Hi @all,
I'm just reading the book "Tapestry in Action".
I really like the concepts of Tapestry and I like to think to get rid of the
JSPs ;-)
And I like the idea to configure my pages and components in order to reduce the
amount of code.
But I'm missing something: Can I also precompile the Tapestry files (Templates,
Pages, ...) like JSP files ?
I mean you can put a lot of OGNL-code or refer to JAVA-methods in the
templates, so there should be way to check for errors before
deploying an application and testing at runtime.
Thanks & Regards
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
