[MYFACES-3293] REGRESSION: 2.0.5->2.0.6: RendererUtils.renderChild no longer checks isRendered

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.6, 2.0.7
• Fix Version/s: 2.0.8, 2.1.2
• Assignee: Leonardo Uribe
• Reporter: Kennard Consulting
• Created: 29/Aug/11 06:16
• Updated: 29/Aug/11 21:06
• Resolved: 29/Aug/11 17:31

Description

Hi guys,

Thanks for all the work you do on MyFaces. It is such a robust JSF implementation.

There appears to have been a regression between 2.0.5 and 2.0.6/2.0.7? Specifically, RendererUtils.renderChild no longer does an 'upfront' check of whether a UIComponent is rendered or not. This logic appears flawed if the UIComponent does not render its own children (the default in Renderer.getRendersChildren)?

First, encodeBegin/encodeEnd for the UIComponent will skip (the default in UIComponentBase.encodeBegin). But encodeChildren for the UIComponent will not get called (because getRendersChildren is false), so the UIComponent has no opportunity to prevent rendering of its children. Instead RendererUtils will invoke encodeBegin/encodeEnd on each child directly. So if a rendered component is nested inside a non-rendered component, it will still appear.

Surely there is an implication that even if I elect not to render my own children (i.e. I let JSF handle it), they should not get rendered if I myself am not rendered?

I enclose a small project that demonstrates the issue. Hopefully it is sufficient to debug. If not I can try and untangle it from Metawidget.

Issue Links

• is duplicated by: MYFACES-3146 ui:fragment (ComponentRef) is responsible for rendering its child components
• is duplicated by: MYFACES-3239 ui:fragment ignores rendered attribute if nested in h:dataTable or h:panelGroup