So you are saying that for every tag that is rendered for a certain
component the component needs to be passed?
My impression was that this parameter was only to be set for like the
main tag of this component, in this case the table component.
If that is necessary, this will be a major change in the sources. Are
you going to open a jira-issue on this?
regards,
Martin
On 8/19/05, Frank Ye <[EMAIL PROTECTED]> wrote:
> Hello,
>
>
> 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);
>
>
>
> Any comments?
>
>
> thanks,
>
> Frank
>
>
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Trainings in English and German
