You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Simon Kitching (JIRA)" <de...@myfaces.apache.org> on 2005/12/12 00:39:09 UTC

[jira] Commented: (MYFACES-769) configurable IDs used for rendering

    [ http://issues.apache.org/jira/browse/MYFACES-769?page=comments#action_12360168 ] 

Simon Kitching commented on MYFACES-769:
----------------------------------------

Please provide more details.

Is this problem specific to portlets, or does it affect traditional JSF apps too?

By "same code is used to generate a component tree" do you mean java code is used to create the components?
If so, that code is responsible for creating and setting unique ids on each component.

Or do you mean that the same JSP fragment is included into a page more than once, and the included fragment has defined explicit ids for the components using the "id" attribute? If so, wrapping the included component in an f:subview should ensure unique ids.

> configurable IDs used for rendering
> -----------------------------------
>
>          Key: MYFACES-769
>          URL: http://issues.apache.org/jira/browse/MYFACES-769
>      Project: MyFaces
>         Type: Improvement
>     Reporter: Dave Brondsema

>
> If the same code is used ot generated a component tree for more than one part of a webpage, the rendered IDs are the same and functionality is broken (javascript needs unique IDs).
> An example of when this happens is when as portlet uses JSF for rendering.  If the portlet is used more than once on a single page (e.g. an RSS reader) all the IDs are the same.
> Thus we need a way to have more configurable (perhaps random) IDs when rendered.

-- 
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