Well this question should be addressed to Jesse On 7/25/07, #Cyrille37# <[EMAIL PROTECTED]> wrote:
Andrea Chiumenti a écrit : > ciao, > the fact is that tapestry uses the form form['componentname'] , so > for > Tapestry name is sufficient to specify ur id u should use > id="clientId:yourComponentId". But why the shortest way jwcid="[EMAIL PROTECTED]" does not create a html element with a id="myCompId" ? Perhaps there are not same ids : clientId <> tapestryId ? Is that right ? cyrille > > Hope this helps. > > kiuma > > On 7/25/07, #Cyrille37# <[EMAIL PROTECTED]> wrote: >> >> Hello >> I'm writing my first "complex" component : GroupableCheckbox (not same >> behaviors as CheckboxGroup). >> >> The question is about the component id. To define the id of the >> component I think to use the text before the @ in the jwcid but it does >> work, I had to add an id attribute : >> >> does not write my defined id : >> <input jwcid="[EMAIL PROTECTED]/GroupableCheckbox" value="L1" /> >> render is : >> <input type="checkbox" name="checkbox" checked="checked" >> id="checkbox" /> >> >> does works : >> <input id="ckL1" jwcid="@MyComps/GroupableCheckbox" value="L2" /> >> render is : >> <input type="checkbox" name="ckL1" checked="checked" id="ckL1" /> >> >> >> What the reason ? The theory ? >> Thanks for your explanation. >> cyrille >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
