H. de Paula Figueiredo [mailto:thiag...@gmail.com]
Sent: Friday, August 07, 2009 3:50 PM
To: Tapestry users
Subject: Re: Possible render problem/bug
Em Fri, 07 Aug 2009 10:47:29 -0300, Sebastian Hennebrueder
escreveu:
> I found this work around as well but this would require a second ev
Em Fri, 07 Aug 2009 10:47:29 -0300, Sebastian Hennebrueder
escreveu:
I found this work around as well but this would require a second event
listener method.
You can use @OnEvent("action") in that case.
But I suppose that the ids need to be unique on the Tapestry component
tree, so the f
I found this work around as well but this would require a second event
listener method.
But I suppose that the ids need to be unique on the Tapestry component
tree, so the fact that the id is unique on the rendered result is not
relevant. As a consequence, I will need the second event listener
Yes, rename one to link1 and the other to link2
On Fri, Aug 7, 2009 at 8:30 AM, Howard Lewis Ship wrote:
> You have t:id="link" on two different components. That is not allowed.
>
> On Fri, Aug 7, 2009 at 4:06 AM, Sebastian
> Hennebrueder wrote:
>> The following snippet in a page template leads t
You have t:id="link" on two different components. That is not allowed.
On Fri, Aug 7, 2009 at 4:06 AM, Sebastian
Hennebrueder wrote:
> The following snippet in a page template leads to the exception
>
> # java.lang.RuntimeException
> Exception assembling root component of page Navigation: Exceptio
The following snippet in a page template leads to the exception
# java.lang.RuntimeException
Exception assembling root component of page Navigation: Exception
assembling embedded component 'link' (of type
org.apache.tapestry5.corelib.components.ActionLink, within Navigation):
Component Navigat
