Adam Winer wrote:
Re: what happens if the number of tags change from one request
to the next: this is why JSF tags inside of c:if are required to have
an explicitly set ID (think this is stated explicitly in the JSF spec).
This whole mess is why I proposed JspIdConsumer for JSP 2.1,
which lets
Sounds like it is a bug, though that's a very quick impression
without serious thought.
Re: what happens if the number of tags change from one request
to the next: this is why JSF tags inside of c:if are required to have
an explicitly set ID (think this is stated explicitly in the JSF spec).
Thi
Does anyone have any comment on whether this is a bug or not:
>
> As you can see UIComponentTag.doEndTag calls internalRelease(). But
> strangely, members _id, _rendered and _binding are cleared only in
> release(), not internalRelease(). Maybe that's a bug?
>
Hi Travis,
Thanks for your response.
Yes, it looks to me like on the first visit to the view, the ids are
generated via that getOrCreateUniqueId method (which calls
UIViewRoot.createUniqueId). That id is then stored persistently in the
component. But on the second view, how does the 3rd anony
I believe the id's are generated at the time the component is
instantiated which seems to occur in UIComponentTag.findComponent().
The corresponding code is:
//Child
String id = getOrCreateUniqueId(context);
_componentInstance = parent.findComponent(id);
if (_componentInst
Hi,
As part of my investigations of
http://issues.apache.org/jira/browse/MYFACES-856
I have found that I need to understand how a UIComponentTag finds its
corresponding component.
When a JSP page is processed, each time a jsf tag is encountered a
UIComponentTag instance is created, initiali
