-
1. Nesting h:dataTable (Can't be done?)
I removed the inner <h:dataTable> and this now allows the outer <h:dataTable> to work properly when previously it was not.
So it seems you CAN NOT nest <h:dataTables>.
Although no error messages of any kind are displayed (c'mon how about some error messages). After setting breakpoints in the setters, I found only one set of datatable's setters were being called.
When I had the nested tables, the inner datatable setters were called but not the outer datatable. When I removed the inner datatable, the outer datatable setters then got called.
This means, I now have to construct another web page for the inner <h:dataTable>. I can't say that I'm really excited about doing this.
Has anybody worked with nested <h:datatables> and got it working.
If so can you please......................
reply with some code that I can look at. -
2. Re: Embededding <h:dataTable> within <h:dataTable>
I think the problem is to do with runtime vs. compiletime components (so nested datatables won't work). It should work inside a c:forEach or the like.
-
3. Re: Embededding <h:dataTable> within <h:dataTable>
I actually got the inner and outer <h:dataTable> to work together.
After spending quite a bit of time disecting the code line by line,
it turns out that the rendered attribute was the root of the problems.ex. rendered= "#{scsSectionDefinition.allowCriteria == 'Y'}"
Some of the edit fields include a rendered attribute. Once I removed
the rendered attribute, everything works fine. All data is submitted an set properly in the @DataModel component.
Now I'm just really baffled why does removing the rendered attributes fix my code. Not to mention I really need to have the rendered attribute for some instances.