Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Date: Wed, 7 Mar 2012 15:20:59 +0000 (UTC)
From: "Stan Zapryanov (Created) (JIRA)" <dev@myfaces.apache.org>
To: dev@myfaces.apache.org
Message-ID: 
 <645779169.34378.1331133659989.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (TOMAHAWK-1612) Children of h:form within
 t:panelGroup still get rendered even though their parent (h:form) has
 rendered=false
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Children of h:form within t:panelGroup still get rendered even though their parent (h:form) has rendered=false
--------------------------------------------------------------------------------------------------------------

                 Key: TOMAHAWK-1612
                 URL: https://issues.apache.org/jira/browse/TOMAHAWK-1612
             Project: MyFaces Tomahawk
          Issue Type: Bug
          Components: Html Tag
    Affects Versions: 1.1.11
         Environment: Tomahawk20-1.1.11 and MyFaces 2.1.6  (Tomcat7, Java6)
            Reporter: Stan Zapryanov


Children of h:form with rendered="false" do get rendered (but should not) IF  h:form is placed within t:panelGroup
If t:panelGroup in the example below is changed to h:panelGroup, then everything works correctly (h:form children don't get rendered).

Example demonstrating the bug:

<t:panelGrid>
<t:panelGroup>
<h:form id="testForm" rendered="false">
	Stuff inside form should not show but this line shows
</h:form>
</t:panelGroup>
</t:panelGrid>


I did some debugging and it seems to me that the bug is coming from the following change made from Tomahawk20-1.1.10  to Tomahawk20-1.1.11 
In class: org.apache.myfaces.shared_tomahawk.renderkit.RendererUtils
Method:    public static void renderChild(FacesContext facesContext, UIComponent child)     throws IOException
The following lines were removed:

530   if (!child.isRendered()) 
531    {  
532           return; 
533     } 

There might be other places where this change could be causing problems/bugs.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira