On Tue, Jul 27, 2010 at 8:05 AM, Christophe Cordenier <christophe.corden...@gmail.com> wrote: > 2010/7/27 Kalle Korhonen <kalle.o.korho...@gmail.com> >> Very good, that's what I thought. Makes sense now why calling it in >> PageResponseRender may not necessarily be the right place but there >> doesn't seem to be a lot of wiggle room for this case. Well I trust >> you to figure out something better than I could :) >> > To be complete, my opinion is that you should set it in your API since you > are doing something specific for multiple Tapestry version support, my worry > is that in your case you depend on the API to do so...
Sorry, not sure if I follow. Regardless of the multiple Tapestry version support, I can certainly fix it in the library myself now but are saying that the general case (what if the exception page has a form) is invalid? One could just claim it's a limitation of the framework but why? Kalle --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
