Example 1: try to use an input-field in your data-table, and look at the output of the <h:messages> - the messages won't indicate the row of the component in the dataTable - they can't, due to this problem.
Example 2: try to use the new AJAX-form components (which rely on the usage of find-component heavily) in a dataTable. regards, Martin On 1/20/06, Simon Kitching <[EMAIL PROTECTED]> wrote: > On Fri, 2006-01-20 at 11:57 +0100, Martin Marinschek wrote: > > Hi *, > > > > I am having the following problem: > > > > whenever I use dataTables > > > > - and use messages alongside, or AJAX, or other stuff using findComponent - > > > > I have the problem that I can't work with the components that are > > children of the dataTables if I call a findComponent. Of course - I > > won't find the correct component instance, due to the generated id and > > the things the dataTable is doing to set the context of the current > > row. > > > > I've been thinking of a solution to this problem, and the only > > solution that has come to my mind is to get rid of findComponent for > > such things - and create an "executeOnComponent" method, which can be > > implemented by all components doing special things with their > > children. > > > > I believe that components are too much of a black box for > > findComponent ever to work at all - what's your impression? > > > > Thoughts? feedback? Better ideas ;) ? > > I've found findComponent very useful (once I figured out what it does; > the sun-provided documenation really sucked). > > Of course I've never had the need for a component to "find" another > component that is nested inside a table. > > I don't understand your "executeOnComponent" suggestion. Could you give > an example? > > Regards, > > Simon > > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
