[ http://issues.apache.org/jira/browse/MYFACES-69?page=all ]
Martin Marinschek closed MYFACES-69:
------------------------------------
Assign To: sean schofield
> clientId should be determined in HtmlRendererUtils (during encoding)
> --------------------------------------------------------------------
>
> Key: MYFACES-69
> URL: http://issues.apache.org/jira/browse/MYFACES-69
> Project: MyFaces
> Type: Improvement
> Reporter: sean schofield
> Assignee: sean schofield
> Priority: Minor
>
> When attempting to decode the request parameters, it seems as though all of
> the Html-based renderers use HtmlRendererUtils to determine the clientId of
> the component. That id is then used to see if there is a submitted value
> that is intended for the component.
> It would be nice if the clientId could be determined through
> HtmlRendererUtils during the *encode* process as well. Currently it is being
> done through the individual renderer classes. An example would be
> HtmlTextRendererBase which gets the clientId directly from the component.
> It would be nice if we could rely on a common static method in
> HtmlRenderUtils to determine the client id attribute (the HTML attribute, not
> the clientId used by the component tree). This change would make it easier
> for future ehancements that would allow for a user specified value for this
> attribute.
--
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
