perfect thanks!
On Tue, Aug 19, 2008 at 4:09 PM, Robert Zeigler <[EMAIL PROTECTED]> wrote:
> ah... Sorry...
> Change:
> beginRender
> to
> afterRender
>
> in the ensureid mixin.
>
> Alternatively, you might be able to get away with writing ensureid as a
> "@MixinAfter".
>
> The problem is exactly
ah... Sorry...
Change:
beginRender
to
afterRender
in the ensureid mixin.
Alternatively, you might be able to get away with writing ensureid as
a "@MixinAfter".
The problem is exactly what tapestry is saying: the component hasn't
been rendered yet (the component's beginRender hasn't been ca
That gets me much closer, I changed my tml to look like this
...
${product.name}
but now I'm getting the following exception.
org.apache.tapestry5.ioc.internal.util.TapestryException: Client id
for product/List:details is not available as it did not render yet (or
Check out the second comment by HLS:
"Or, here's a better idea; an id should only be generated if
getClientId() is invoked, at which point the id attribute of the
element may be set. Dynamic updates to the DOM are a great thing. "
That's the behavior that ended up getting implemented.
You s
Weird. According to TAPESTRY-2294 the value should be uniqued via
RenderSupport...
-Filip
On 2008-08-19 17:42, Mark Horn wrote:
hhmm... that is a problem as my links are in a loop. so they used to
be remove, remove_0, etc. if I set id="remove" then all links have
the id of 'remove' which does
hhmm... that is a problem as my links are in a loop. so they used to
be remove, remove_0, etc. if I set id="remove" then all links have
the id of 'remove' which does not work for my tests ether.
Any other ideas?
On Tue, Aug 19, 2008 at 11:32 AM, Mark Horn <[EMAIL PROTECTED]> wrote:
> right.. how
right.. how did I miss that. thanks!
On Tue, Aug 19, 2008 at 11:27 AM, Filip S. Adamsen <[EMAIL PROTECTED]> wrote:
> Hi,
>
> As far as I can tell from the issue you linked to, you need to bind the id
> (not t:id) parameter of the link.
>
> -Filip
>
> On 2008-08-19 17:11, Mark Horn wrote:
>>
>> I j
Hi,
As far as I can tell from the issue you linked to, you need to bind the
id (not t:id) parameter of the link.
-Filip
On 2008-08-19 17:11, Mark Horn wrote:
I just updated to Tapestry 5.0.14 from 5.0.11 and have run into an
issue with using PageTester to test ActionLinks as shown here
http:
