from the nightly docs at 
http://tapestry.formos.com/nightly/tapestry5/tapestry-core/

Tapestry now differentiates between development mode and production mode, primarily in how it reports runtime exceptions. It defaults to production mode.

guess there must be a switch for this...

cheers
harald



Chris Lewis schrieb:
I love puns :-).

This indeed would be a useful feature, if somehow T5 had a notion of execution phases, or whatever they might be called. You could easily build this into your application in a somewhat rigid manner with a service that reads your prop file and provides access to that setting (or insulated the logic with method like Application#isInDevelopment). A more sophisticated implementation could run autonomously and even add/update parts of pages/components without them knowing about it. That of course would be a bit more involved..

chris


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to