[ http://issues.apache.org/jira/browse/MYFACES-436?page=comments#action_12319694 ]
Martin Marinschek commented on MYFACES-436: ------------------------------------------- Ok, I just applied your patch. Thanks a lot for fixing this for us! regards, Martin > ResponseWriter with null argment fro componentForElement > -------------------------------------------------------- > > Key: MYFACES-436 > URL: http://issues.apache.org/jira/browse/MYFACES-436 > Project: MyFaces > Type: Improvement > Components: Tomahawk > Versions: 1.0.9 beta > Reporter: Frank Ye > Assignee: Martin Marinschek > Fix For: Nightly Build > Attachments: myfaces-1.0.9.zip, share_r239274_patch.txt, src.tgz, > tomahakw_r239274_patch.txt > > In some instances of the MyFaces custom components, the > startElement(..) > is called with a null componentForElement. > This causes a problem for the integration of MyFaces' custom components > with some 3rd-party ResponseWriters. > See JSF 1.1 specification: > Section 6.4 of the JSF specification states that the > ResponseWriter.startElement(String name, UIComponent > componentForElement) > method allows a null argument for the componentForElement parameter "to > indicate that the element has no corresponding component". > The specification goes on to state that "the prescence of this > parameter > allows tools to provide their own implementation of > ResponseWriter". > For example: > Pass in a component reference to the startElement method on the > ResponseWriter. E.g. if your UIComponent is a PanelGrid, and you want to > emit <table><tr><td>... you would use writer.startElement("table", > gridpanel); > writer.startElement("tr", gridpanel); > writer.startElement("td", gridpanel); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
