Actually it's a feature! Problem is:
- you can't know which client id was generated by a component
- you can't assume that client id = component id (think loops, e.t.c.)
- the component cannot really know its client id unless it actually
renders itself.
- only form components support client id.
So, the best bet is to check out the generated id and use that...
Sam Gendler wrote:
I was trying to update a tacos:Table component with an AjaxForm and it
was always failing to update. Looking at the html, I could see that
the html id of the table was 'tableACamp.tableSection' even though the
jwcid of the table was just 'tableACamp.' As a result, it was failing
to update. Changing the id in updateComponents from 'tableACamp' to
'tableACamp.tableSection' did fix the problem, although I don't reall
understand why, since I would have expected the server side code to
fail to re-render the table, since it would have the wrong id.
Regardless, it did work, but I suspect that there is a bug in there
somewhere, possibly with tacos:table. Any thoughts?
--sam
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat
certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd_______________________________________________
Tacos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tacos-devel
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
Tacos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tacos-devel
