T5: Problem with Decoding of Activation Parameters

Hi, we have the following problem with Tapestry 5: In onActivate methods, the parameter array always seems to be decoded once too often. That means that correctly encoded parameters in URLs will result in broken parameters in the onActivate method. Only double-encoded URLs result in correct pa

Re: t:type="loop" problem

Hi Leon, On Sunday 16 September 2007 18:41:07 Leon Derks wrote: > I have a problem with the t:type="loop" component in my Menu Component > > [...] > Every categoryId is 1. (and it generates to much tags). > [...] > This is what is in Menu.html > > > >context="${category.id}">${catego

Re: t:type="loop" problem

quite non-intuitive in a loop, which has irked me for > > some time, and I'm beginning to consider it a bug. It's also one > > reason I still value the Any component. > > > > I'll log a JIRA. > > > > Cheers, > > Nick. > > > > Michael G

Re: t:type="loop" problem

the solution to this problem is just not to do that. Cheers, Michael > On 9/17/07, Michael Gottschalk <[EMAIL PROTECTED]> wrote: > > On Monday 17 September 2007 08:42:46 Davor Hrg wrote: > > > I had no problem using expansions in a loop, (T5.0.5) > > > > > &g

T5: Custom 404 Page

Hi, we have the following problem with our tapestry5 application: We already have a custom ExceptionReport page which is displayed when an exception is thrown in the application. However, when the user enters a non-existing page name, the exception page is not shown, but the standard tomcat 404

T5: Problem with browser cache

Hi, I have problems with my web application using Tapestry 5 when the back/forward buttons of the browser are used. The internal page state seems to be out of sync with the actual state in the browser then. I get strange behaviour and exceptions in some cases. I'll give an example: I have a pa

Re: T5: Problem with browser cache

On Thursday 21 June 2007 17:41:21 Michael Gottschalk wrote: > I have problems with my web application using Tapestry 5 when the > back/forward buttons of the browser are used. The internal page state seems > to be out of sync with the actual state in the browser then. I get strange > b

T5 XHTML strict conformance

Hi, I have some questions in addition to the issue with non-well-formed XML generation. In order to be XHTML strict compliant, some standard components also need to be changed in tapestry 5, I think. Should I open bug reports for all problems I find? Or is XHTML strict conformance not currentl