Hi,
One solution could be to let tapestry handle id attribute as before and
instead use a unique class as your own identifier.
Best regards
Mats
Daniel Henze skrev 2010-10-28 00:17:
Hi there,
I have two actionlinks with different t:id, but still Tapestry sets a
unique id at the end and therefore caters the actionlink useless:
instead of <a id="addToFavorites" zone="messageOutput" href="..."> I
do get <a id="addToFavorites-12befc24b12" zone="messageOutput"
href="...">.
It's worth mentioning that after refreshing the page I do get the
desired result (non uniquified id) and therefore all working well. How
to control this behaviour and stop Tapestry from setting the id?
Best regards
Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
