IComponent.getClientId() or IComponent.getId() getClientId() is only relevant "in context"...ie calling it inside a For loop would be good.
On 11/2/06, Roberto Ramírez Vique <[EMAIL PROTECTED]> wrote:
Hello! I want to use something that I supose tapestry already made for me. I'll try to explain because probably some of you have, or have had this question, and probably the answer to my question is that this is not possible or shouldn't be done, but I'm not sure. I want to use the tapestry generated Id's. I have seen that in tapestry, when an element is inside a For component (supose we have a TextField with id= name), and this element is part of a dynamic form, is generated with a different id in each loop, this Id use to be like: tapestryIdName_X (where X is the index in the loop, or the index-1). I want to know if is possible to use the clientId that I've debugged and saw that is the correct one. I would like to use this id in two situations, one just to know the id of a TextField and the other to know the Id of my own component. Thanks you, -- Robert Ramírez Vique Computer Science Engineer
-- Jesse Kuhnert Tapestry/Dojo/(and a dash of TestNG), team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
