The exception is happening during state saving. All the rendered attributes are irrelevant for this tree recursion because the whole component tree needs to be saved. When state saving hits the PanelSeries, it has some logic to reset the rowIndex to -1, which should be ok, but that code eventually hits some work-around code we put in for ICE-4066 that looks like some kind of hack to solve another problem. In fact it's likely that if we remove the work-around and test for the regression it'll be ok now because of other code changes since then. Anyways that work-around has a side-effect of testing the rendered property on its parents, which causes the exception.

Should combine the issue reported in ICE-4066 with any fixes for this issue to have one complete solution.

This is actually not caused by the rendered attribute, but by the value attribute. There is an exception in the value getter method, triggered by reference to loginBean.getNumConcepts(), which in turn triggers a chain of exception handling code that ultimately loops back to a test for the rendered attribute, which triggers another exception. All very twisted.

Found the simplest fix involving the way CustomComponentUtils.isAncestorRendered() is used. It is used by UISeries only and so should have no side effects. (It was also once used by PanelTabSet but later that change was backed out. Probably it caused the same issues back then.)

Now if ancestor is not rendered, then neither value nor rendered attribute should give exceptions.

Revision: 25201

Modified : /icefaces2/trunk/icefaces/compat/components/src/main/java/com/icesoft/faces/component/panelseries/UISeries.java

Revision: 25202

Modified : /icefaces2/branches/icefaces-2.0.x-maintenance/icefaces/compat/components/src/main/java/com/icesoft/faces/component/panelseries/UISeries.java