myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Brondsema (JIRA)" <>
Subject [jira] Commented: (MYFACES-769) configurable IDs used for rendering
Date Tue, 13 Dec 2005 00:46:46 GMT
    [ ] 

Dave Brondsema commented on MYFACES-769:

Okay.  If my portlet does this:

<f:subview id="foo">
  <!-- all my components -->

And I use that portlet twice on one page, both instances of the portlet are using "foo" prefixes
which doesn't help.   (All lifecycle phases run fine since each instance is executed independently
of the other, but the portal aggregates the HTML of instance 1, the HTML of instance 2, and
some of its own HTML which makes forms and javascript not work)

I'd like to do something like this

<f:subview id="foo#{bean.random}">
  <!-- all my components -->

or (where render-id is a new attribute used only when rendering components):

<f:subview id="foo" render-id="foo#{bean.random}">
  <!-- all my components -->

> configurable IDs used for rendering
> -----------------------------------
>          Key: MYFACES-769
>          URL:
>      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:
For more information on JIRA, see:

View raw message