The easiest workaround is to build the table yourself. Essentially
the datatable just provides a built-in looping mechanism for your
data. However, if you built a component programmatically (using the
"binding" attribute) you can assemble a table however you want.
Here's an example:
<h:panelGrid binding="#{myBean.myGrid}" />
Then, inside your myBean:
public HtmlPanelGrid getMyGrid()
{
HtmlPanelGrid myGrid = new HtmlPanelGrid();
for (Iterator i = m_nestedOuterBeans.iterator(); i.hasNext();)
{
NestedOuterBean outer = (NestedOuterBean) i.next();
HtmlPanelGrid myInnerGrid = new HtmlPanelGrid();
for (Iterator j = outer.getInnerBeans().iterator(); j.hasNext();)
{
// add some components to myInnerGrid using
// myInnerGrid.getChildren().add(UICompoent);
}
myGrid.getChildren().add(myInnerGrid);
}
return myGrid;
}
Your getter method will only be called the first time JSF builds the
view for the page, so you if you have changes to make to the content
while you're on the page, you''ll want to retain a reference to the
grid.
On Sun, 13 Feb 2005 21:29:52 +0100, Slawek <[EMAIL PROTECTED]> wrote:
> this is my first mail so be lenient for a newbee;)
>
> i know that there is a bug with inner datatables...
> but some importand part of my project rely on nesting datatables and
> deadline is closing:/
> so i would ask if there is somme "plan" to fix it (and when) or do i have
> to walkaround it somehow (scriptlet and nested loops or sth - i dont know
> how many rows inner table has) ?
>
> thanks for great job u doing!
>
> Slawek
>
--
-Heath Borders-Wing
[EMAIL PROTECTED]
