You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by SiSi'mon <s_...@purpleblade.net> on 2007/05/23 18:16:00 UTC
Started using Myfaces 1.1.5 and every page is broken (duplicate ID
in the faces tree Component)
We are getting errors on nearly every page now that we are using MyFaces
1.1.5. All seem to point to a duplicate ID problem but checking the xHTML
there is no duplicate ID. This seems to be generated or something.
Something seems quite mucked up. any ideas?
---
SEVERE: Error Rendering View[/web/Information.xhtml]
java.lang.IllegalStateException: Client-id : _id81 is duplicated in the
faces tree. Component : idListForm:idPopupDataTable:_id81, path:
{Component-Path : [C
---
--
View this message in context: http://www.nabble.com/Started-using-Myfaces-1.1.5-and-every-page-is-broken-%28duplicate-ID-in-the-faces-tree-Component%29-tf3805053.html#a10767409
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: Started using Myfaces 1.1.5 and every page is broken (duplicate
ID in the faces tree Component)
Posted by Werner Punz <we...@gmail.com>.
SiSi'mon schrieb:
> I have read a lot on "component binding" but still do not understand under
> the hood (in low level object/class terms) what it is. We do have some
> beans that are session scoped.
>
A the component binding is basically the code representation of
the tag in the page you have bound to...
the binding itself is just an attribute which gets assigned the
component itself if set.
You then can use it on the code side to influence its behavior, which
child components you have etc... pretty much everything.
It really depends on your programmingmodel... most of the times you do
not do it because it is easier just to set the values, but a model like...
public String doMyAction() {
textField1.setValue("hello world");
//textField1 is a binding to a h:inputText component
return "done";
}
is possible, this looks very familiar like the programming model
approached by classical rich client ui frameworks where you alter
various aspects of the component on code level.
And this approach is used for instance by the Netbeans Visual Web
Plugin.
> In the xhtml page that is failing, the word "binding" is never used. The
> backing beans used in the page are request scoped but we do have a user
> object that is session scoped which every page uses I believe.
>
such an object should be no problem... unless the user object has some
componen bindings in there....
It is kind of hard to nail down, can you post an error log maybe?
Re: Started using Myfaces 1.1.5 and every page is broken (duplicate
ID in the faces tree Component)
Posted by SiSi'mon <s_...@purpleblade.net>.
I have read a lot on "component binding" but still do not understand under
the hood (in low level object/class terms) what it is. We do have some
beans that are session scoped.
In the xhtml page that is failing, the word "binding" is never used. The
backing beans used in the page are request scoped but we do have a user
object that is session scoped which every page uses I believe.
thanks
Andrew Robinson-5 wrote:
>
> Are you by any chance using component binding with beans that are
> session scoped?
>
> On 5/23/07, SiSi'mon <s_...@purpleblade.net> wrote:
>>
>> We are getting errors on nearly every page now that we are using MyFaces
>> 1.1.5. All seem to point to a duplicate ID problem but checking the
>> xHTML
>> there is no duplicate ID. This seems to be generated or something.
>>
>> Something seems quite mucked up. any ideas?
>>
>> ---
>>
>> SEVERE: Error Rendering View[/web/Information.xhtml]
>> java.lang.IllegalStateException: Client-id : _id81 is duplicated in the
>> faces tree. Component : idListForm:idPopupDataTable:_id81, path:
>> {Component-Path : [C
>>
>> ---
>> --
>> View this message in context:
>> http://www.nabble.com/Started-using-Myfaces-1.1.5-and-every-page-is-broken-%28duplicate-ID-in-the-faces-tree-Component%29-tf3805053.html#a10767409
>> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Started-using-Myfaces-1.1.5-and-every-page-is-broken-%28duplicate-ID-in-the-faces-tree-Component%29-tf3805053.html#a10768604
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: Started using Myfaces 1.1.5 and every page is broken (duplicate ID in the faces tree Component)
Posted by Andrew Robinson <an...@gmail.com>.
Are you by any chance using component binding with beans that are
session scoped?
On 5/23/07, SiSi'mon <s_...@purpleblade.net> wrote:
>
> We are getting errors on nearly every page now that we are using MyFaces
> 1.1.5. All seem to point to a duplicate ID problem but checking the xHTML
> there is no duplicate ID. This seems to be generated or something.
>
> Something seems quite mucked up. any ideas?
>
> ---
>
> SEVERE: Error Rendering View[/web/Information.xhtml]
> java.lang.IllegalStateException: Client-id : _id81 is duplicated in the
> faces tree. Component : idListForm:idPopupDataTable:_id81, path:
> {Component-Path : [C
>
> ---
> --
> View this message in context: http://www.nabble.com/Started-using-Myfaces-1.1.5-and-every-page-is-broken-%28duplicate-ID-in-the-faces-tree-Component%29-tf3805053.html#a10767409
> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>
>
RE: Started using Myfaces 1.1.5 and every page is broken (duplicate
ID in the faces tree Component)
Posted by SiSi'mon <s_...@purpleblade.net>.
No, we are on Tomcat.
thanks
Si'mon
mario.buonopane wrote:
>
> Are you working on IBM RAD or WAS?
>
> -----Original Message-----
> From: SiSi'mon [mailto:s_simon@purpleblade.net]
> Sent: 23 maggio 2007 18.16
> To: users@myfaces.apache.org
> Subject: Started using Myfaces 1.1.5 and every page is broken (duplicate
> ID in the faces tree Component)
>
>
> We are getting errors on nearly every page now that we are using MyFaces
> 1.1.5. All seem to point to a duplicate ID problem but checking the
> xHTML
> there is no duplicate ID. This seems to be generated or something.
>
> Something seems quite mucked up. any ideas?
>
> ---
>
> SEVERE: Error Rendering View[/web/Information.xhtml]
> java.lang.IllegalStateException: Client-id : _id81 is duplicated in the
> faces tree. Component : idListForm:idPopupDataTable:_id81, path:
> {Component-Path : [C
>
> ---
> --
> View this message in context:
> http://www.nabble.com/Started-using-Myfaces-1.1.5-and-every-page-is-brok
> en-%28duplicate-ID-in-the-faces-tree-Component%29-tf3805053.html#a107674
> 09
> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>
>
>
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise private information. If you have
> received it in error, please notify the sender immediately and delete the
> original. Any other use of the email by you is prohibited.
>
>
--
View this message in context: http://www.nabble.com/Started-using-Myfaces-1.1.5-and-every-page-is-broken-%28duplicate-ID-in-the-faces-tree-Component%29-tf3805053.html#a10768422
Sent from the MyFaces - Users mailing list archive at Nabble.com.
RE: Started using Myfaces 1.1.5 and every page is broken (duplicate ID in the faces tree Component)
Posted by ma...@accenture.com.
Are you working on IBM RAD or WAS?
-----Original Message-----
From: SiSi'mon [mailto:s_simon@purpleblade.net]
Sent: 23 maggio 2007 18.16
To: users@myfaces.apache.org
Subject: Started using Myfaces 1.1.5 and every page is broken (duplicate
ID in the faces tree Component)
We are getting errors on nearly every page now that we are using MyFaces
1.1.5. All seem to point to a duplicate ID problem but checking the
xHTML
there is no duplicate ID. This seems to be generated or something.
Something seems quite mucked up. any ideas?
---
SEVERE: Error Rendering View[/web/Information.xhtml]
java.lang.IllegalStateException: Client-id : _id81 is duplicated in the
faces tree. Component : idListForm:idPopupDataTable:_id81, path:
{Component-Path : [C
---
--
View this message in context:
http://www.nabble.com/Started-using-Myfaces-1.1.5-and-every-page-is-brok
en-%28duplicate-ID-in-the-faces-tree-Component%29-tf3805053.html#a107674
09
Sent from the MyFaces - Users mailing list archive at Nabble.com.
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
Re: Started using Myfaces 1.1.5 and every page is broken (duplicate ID in the faces tree Component)
Posted by Andrew Robinson <an...@gmail.com>.
> I am not sure what a session scoped component binding is.
A backing bean that is session scoped that has a property that is used
for component binding.
When using component binding (<ns:component binding="#{...}">), that
value should NEVER be persisted longer than that lifecycle and
rendering of the page.
The reason why this is a common cause of duplicate ID errors is that
a component's ID must be unique per naming container. Common naming
containers are data tables, ui:repeat (facelets), subView, and form.
When a component is bound to a value binding the code works as
follows:
- get the value binding
- see if the value is null
- if null, create the component and then set the value binding to this
new component value
- if not null, insert this component into the component tree (return the value)
Therefore, if you have a component that is bound with no ID, it will
get a generated ID that is unique only for that UIViewRoot component.
If you use that component again in a different view, the ID is not
guaranteed be unique as the new view may (and will in MyFaces)
generate that same ID over again. Thus giving you a duplicate ID
error.
Re: Started using Myfaces 1.1.5 and every page is broken (duplicate ID in the faces tree Component)
Posted by Helmut Swaczinna <sw...@wlp-systems.de>.
Yes, I mean a session scoped backing bean which helds a component binding. I
got the
"duplicate ID in the faces tree Component" message in a foreach loop. The
loop was in a
container component which had a binding to a session scoped bean.
Helmut
----- Original Message -----
From: "SiSi'mon" <s_...@purpleblade.net>
To: <us...@myfaces.apache.org>
Sent: Wednesday, May 23, 2007 7:07 PM
Subject: Re: Started using Myfaces 1.1.5 and every page is broken (duplicate
ID in the faces tree Component)
>
> I am not sure what a session scoped component binding is.
>
> do you mean a session scoped backing bean? We are using Spring IOC to
> manage the backing beans and only have one that is session scoped.
>
> thanks
>
> Si'mon
>
>
> Helmut Swaczinna wrote:
>>
>> Hi,
>>
>> after switching to myFaces 1.1.5 I had many problems in my pages also.
>> Code
>> that worked with 1.1.4 didn't
>> work with 1.1.5. I found out that all problems had the same cause: a
>> session
>> scoped compoment binding.
>> After removing this evering works fine. But the question is, why worked
>> the
>> session scoped compoment binding
>> with 1.1.4? What is the corrent behavior?
>>
>> Regards
>> Helmut
>>
>> ----- Original Message -----
>> From: "SiSi'mon" <s_...@purpleblade.net>
>> To: <us...@myfaces.apache.org>
>> Sent: Wednesday, May 23, 2007 6:16 PM
>> Subject: Started using Myfaces 1.1.5 and every page is broken (duplicate
>> ID
>> in the faces tree Component)
>>
>>
>>>
>>> We are getting errors on nearly every page now that we are using MyFaces
>>> 1.1.5. All seem to point to a duplicate ID problem but checking the
>>> xHTML
>>> there is no duplicate ID. This seems to be generated or something.
>>>
>>> Something seems quite mucked up. any ideas?
>>>
>>> ---
>>>
>>> SEVERE: Error Rendering View[/web/Information.xhtml]
>>> java.lang.IllegalStateException: Client-id : _id81 is duplicated in the
>>> faces tree. Component : idListForm:idPopupDataTable:_id81, path:
>>> {Component-Path : [C
>>>
>>> ---
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Started-using-Myfaces-1.1.5-and-every-page-is-broken-%28duplicate-ID-in-the-faces-tree-Component%29-tf3805053.html#a10767409
>>> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>>
>>
>
> --
> View this message in context:
> http://www.nabble.com/Started-using-Myfaces-1.1.5-and-every-page-is-broken-%28duplicate-ID-in-the-faces-tree-Component%29-tf3805053.html#a10768421
> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>
>
Re: Started using Myfaces 1.1.5 and every page is broken (duplicate
ID in the faces tree Component)
Posted by Werner Punz <we...@gmail.com>.
SiSi'mon schrieb:
> I am not sure what a session scoped component binding is.
>
> do you mean a session scoped backing bean? We are using Spring IOC to
> manage the backing beans and only have one that is session scoped.
>
> thanks
>
> Si'mon
>
>
Well following, if you have referenced this bean into something like:
<component binding="#{sessionbeanbean.bindingattribute}" /> and this
bean is session scoped or even worse application scoped in spring then
you run into this problem.
You can however since you use spring anyway and if you do not want to
omit the session scope of your bean make the binding request scoped
nevertheless.
Spring 2 has the aop:scoped proxy mechanism, which you can use to wrap a
request scoped proxy once the session scoped bean references your
binding object around it.
Which means a contstruct like that:
<component
binding="#{sessionbeanbean.componentbindingholder.bindingattribute}" />
can work even if the bean is session scoped if the
componentbindingholder is request scoped and has the aop:proxy construct
around it.
(Sorry for going so deeply into spring)
what this means is following:
<bean id="componentbindingholder" scope="request">
<aop:scoped-proxy />
</bean>
<bean id="sessionbean" scope="session" class="....">
<property name="componentbindingholder"
ref="componentbindingholder" />
</bean>
what happens now is
that both beans are ioc glued together but, the contents of the
componentbindingholder is dropped at every request, while its proxy
shell stays the same the entire session.
Sorry for digging in so deep into spring, but this stuff is pure genious
and definitely a good way to avoid the session scoped component binding
problem. (It is a must have if you start to work with conversation based
frameworks)
Werner
Re: Started using Myfaces 1.1.5 and every page is broken (duplicate
ID in the faces tree Component)
Posted by SiSi'mon <s_...@purpleblade.net>.
I am not sure what a session scoped component binding is.
do you mean a session scoped backing bean? We are using Spring IOC to
manage the backing beans and only have one that is session scoped.
thanks
Si'mon
Helmut Swaczinna wrote:
>
> Hi,
>
> after switching to myFaces 1.1.5 I had many problems in my pages also.
> Code
> that worked with 1.1.4 didn't
> work with 1.1.5. I found out that all problems had the same cause: a
> session
> scoped compoment binding.
> After removing this evering works fine. But the question is, why worked
> the
> session scoped compoment binding
> with 1.1.4? What is the corrent behavior?
>
> Regards
> Helmut
>
> ----- Original Message -----
> From: "SiSi'mon" <s_...@purpleblade.net>
> To: <us...@myfaces.apache.org>
> Sent: Wednesday, May 23, 2007 6:16 PM
> Subject: Started using Myfaces 1.1.5 and every page is broken (duplicate
> ID
> in the faces tree Component)
>
>
>>
>> We are getting errors on nearly every page now that we are using MyFaces
>> 1.1.5. All seem to point to a duplicate ID problem but checking the
>> xHTML
>> there is no duplicate ID. This seems to be generated or something.
>>
>> Something seems quite mucked up. any ideas?
>>
>> ---
>>
>> SEVERE: Error Rendering View[/web/Information.xhtml]
>> java.lang.IllegalStateException: Client-id : _id81 is duplicated in the
>> faces tree. Component : idListForm:idPopupDataTable:_id81, path:
>> {Component-Path : [C
>>
>> ---
>> --
>> View this message in context:
>> http://www.nabble.com/Started-using-Myfaces-1.1.5-and-every-page-is-broken-%28duplicate-ID-in-the-faces-tree-Component%29-tf3805053.html#a10767409
>> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>>
>>
>
>
>
>
--
View this message in context: http://www.nabble.com/Started-using-Myfaces-1.1.5-and-every-page-is-broken-%28duplicate-ID-in-the-faces-tree-Component%29-tf3805053.html#a10768421
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: Started using Myfaces 1.1.5 and every page is broken (duplicate
ID in the faces tree Component)
Posted by Werner Punz <we...@gmail.com>.
Helmut Swaczinna schrieb:
> Hi,
>
> after switching to myFaces 1.1.5 I had many problems in my pages also.
> Code that worked with 1.1.4 didn't
> work with 1.1.5. I found out that all problems had the same cause: a
> session scoped compoment binding.
> After removing this evering works fine. But the question is, why worked
> the session scoped compoment binding
> with 1.1.4? What is the corrent behavior?
>
Good question... why it worked in 1.1.4 that a session scoped component
binding throws a lot of errors can be expected...
So I assume 1.1.5 behaves correctly.
Since components are request centric, they have to be also request
centric in their bindings.
You still can bind components to session scoped objects, springs
aop:proxy for instance would allow this.
Re: Started using Myfaces 1.1.5 and every page is broken (duplicate ID in the faces tree Component)
Posted by Helmut Swaczinna <sw...@wlp-systems.de>.
Hi,
after switching to myFaces 1.1.5 I had many problems in my pages also. Code
that worked with 1.1.4 didn't
work with 1.1.5. I found out that all problems had the same cause: a session
scoped compoment binding.
After removing this evering works fine. But the question is, why worked the
session scoped compoment binding
with 1.1.4? What is the corrent behavior?
Regards
Helmut
----- Original Message -----
From: "SiSi'mon" <s_...@purpleblade.net>
To: <us...@myfaces.apache.org>
Sent: Wednesday, May 23, 2007 6:16 PM
Subject: Started using Myfaces 1.1.5 and every page is broken (duplicate ID
in the faces tree Component)
>
> We are getting errors on nearly every page now that we are using MyFaces
> 1.1.5. All seem to point to a duplicate ID problem but checking the xHTML
> there is no duplicate ID. This seems to be generated or something.
>
> Something seems quite mucked up. any ideas?
>
> ---
>
> SEVERE: Error Rendering View[/web/Information.xhtml]
> java.lang.IllegalStateException: Client-id : _id81 is duplicated in the
> faces tree. Component : idListForm:idPopupDataTable:_id81, path:
> {Component-Path : [C
>
> ---
> --
> View this message in context:
> http://www.nabble.com/Started-using-Myfaces-1.1.5-and-every-page-is-broken-%28duplicate-ID-in-the-faces-tree-Component%29-tf3805053.html#a10767409
> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>
>
Re: Started using Myfaces 1.1.5 and every page is broken (duplicate
ID in the faces tree Component)
Posted by David Delbecq <de...@oma.be>.
According to the error message you posted, not, all your components have
defined ids:
faces tree. Component : idListForm:idPopupDataTable:_id81, path:
_id81 is an automatically generated id, use when no specific id was
provided. Also, as asked, please provide the xhtml code, it's nearly
impossible to continue to help you without it. And, check your use of
c:forEach tag, it's content gets duplicated for each iteration in the
component tree.
En l'instant précis du 24/05/07 18:24, SiSi'mon s'exprimait en ces termes:
> all includes and all components have an ID where it is permissable. The
> thing is that there was no problem with 1.1.4 but there is with 1.1.5 and
> everyone seems to be having a problem with it so I see a lot of people
> rolling back because 1.1.5 is utterly useless.
>
> thanks
>
>
>
>
>
> Andrew Robinson-5 wrote:
>
>> Could you post some of the XHTML code? Also the full error from the
>> duplicate component ID may be helpful. That component path should
>> directly indicate which component is getting the error (it is in a
>> dataTable, and doesn't have an ID assigned to it).
>>
>> Also if you are using facelets includes, you have to make sure that
>> IDs are unique for the entire component tree, not just the include. So
>> if you have:
>>
>> <ui:include src="a.xhtml" />
>> <ui:include src="b.xhtml" />
>>
>> the component IDs in a and b have to be unique.
>>
>> Since you are having an issue with an auto-generated ID in a data
>> table, I'm inclined to think it is a component binding issue though.
>>
>> On 5/23/07, SiSi'mon <s_...@purpleblade.net> wrote:
>>
>>> Thanks, I am not quite sure I understand everything in the article. We
>>> have
>>> ID's on every component in the xhtml.
>>>
>>> Not sure how to implement the suggestion for not using session scoped
>>> beans.
>>>
>>>
>>> Si'mon
>>>
>>>
>>> David Delbecq-2 wrote:
>>>
>>>> Since you seem to be using facelets:
>>>>
>>>>
>>>>
>>> http://wiki.java.net/bin/view/Projects/FaceletsFAQ#I_m_getting_Duplicate_ID_Errors
>>>
>>>> SiSi'mon a écrit :
>>>>
>>>>> We are getting errors on nearly every page now that we are using
>>>>>
>>> MyFaces
>>>
>>>>> 1.1.5. All seem to point to a duplicate ID problem but checking the
>>>>> xHTML
>>>>> there is no duplicate ID. This seems to be generated or something.
>>>>>
>>>>> Something seems quite mucked up. any ideas?
>>>>>
>>>>> ---
>>>>>
>>>>> SEVERE: Error Rendering View[/web/Information.xhtml]
>>>>> java.lang.IllegalStateException: Client-id : _id81 is duplicated in
>>>>>
>>> the
>>>
>>>>> faces tree. Component : idListForm:idPopupDataTable:_id81, path:
>>>>> {Component-Path : [C
>>>>>
>>>>> ---
>>>>>
>>>>>
>>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Started-using-Myfaces-1.1.5-and-every-page-is-broken-%28duplicate-ID-in-the-faces-tree-Component%29-tf3805053.html#a10771395
>>> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>>>
>>>
>>>
>>
>
>
Re: Started using Myfaces 1.1.5 and every page is broken (duplicate ID in the faces tree Component)
Posted by Alexander Wallace <aw...@rwmotloc.com>.
If i recall correctly the current tomahawk bridge to be able to use
tomahawk in portlets doesn't work with 1.5... Has this been changed?
On May 24, 2007, at 11:47 AM, Andrew Robinson wrote:
>> everyone seems to be having a problem with it so I see a lot of
>> people
>> rolling back because 1.1.5 is utterly useless.
>
> 1.1.4 had quite a few bugs. 1.1.5 is much more aligned with the JSF
> specification. The bugs that people are having with 1.1.5 are usually
> are due to them relying on bugs in the 1.1.4 implementation that have
> been fixed. Therefore, the problem isn't with 1.1.5, but with peoples
> code (code that used to work in 1.1.4 shouldn't have). I have been
> using 1.1.5 for a while now with a lot of code on top of it, and
> although I did have to tweak some of our code, the upgrade from 1.1.4
> to 1.1.5 wasn't that hard (mostly our problems were due to the select
> items change).
>
> As for your problem:
> From your stack, the component that is getting the error does NOT have
> an ID assigned. That is why I asked you to provide the XHTML code that
> is failing.
>
> Please stop bashing myfaces without good specific issues. You will
> find that no one will want to help you if this continues. Also please,
> when someone asks you to provide more information, do so. We are
> trying to help you out, but without your cooperation we cannot. We
> don't have your code and it is often hard to troubleshoot someone
> else's issues through a mailing list.
>
Re: Started using Myfaces 1.1.5 and every page is broken (duplicate ID in the faces tree Component)
Posted by Andrew Robinson <an...@gmail.com>.
> everyone seems to be having a problem with it so I see a lot of people
> rolling back because 1.1.5 is utterly useless.
1.1.4 had quite a few bugs. 1.1.5 is much more aligned with the JSF
specification. The bugs that people are having with 1.1.5 are usually
are due to them relying on bugs in the 1.1.4 implementation that have
been fixed. Therefore, the problem isn't with 1.1.5, but with peoples
code (code that used to work in 1.1.4 shouldn't have). I have been
using 1.1.5 for a while now with a lot of code on top of it, and
although I did have to tweak some of our code, the upgrade from 1.1.4
to 1.1.5 wasn't that hard (mostly our problems were due to the select
items change).
As for your problem:
>From your stack, the component that is getting the error does NOT have
an ID assigned. That is why I asked you to provide the XHTML code that
is failing.
Please stop bashing myfaces without good specific issues. You will
find that no one will want to help you if this continues. Also please,
when someone asks you to provide more information, do so. We are
trying to help you out, but without your cooperation we cannot. We
don't have your code and it is often hard to troubleshoot someone
else's issues through a mailing list.
Re: Started using Myfaces 1.1.5 and every page is broken (duplicate
ID in the faces tree Component)
Posted by SiSi'mon <s_...@purpleblade.net>.
all includes and all components have an ID where it is permissable. The
thing is that there was no problem with 1.1.4 but there is with 1.1.5 and
everyone seems to be having a problem with it so I see a lot of people
rolling back because 1.1.5 is utterly useless.
thanks
Andrew Robinson-5 wrote:
>
> Could you post some of the XHTML code? Also the full error from the
> duplicate component ID may be helpful. That component path should
> directly indicate which component is getting the error (it is in a
> dataTable, and doesn't have an ID assigned to it).
>
> Also if you are using facelets includes, you have to make sure that
> IDs are unique for the entire component tree, not just the include. So
> if you have:
>
> <ui:include src="a.xhtml" />
> <ui:include src="b.xhtml" />
>
> the component IDs in a and b have to be unique.
>
> Since you are having an issue with an auto-generated ID in a data
> table, I'm inclined to think it is a component binding issue though.
>
> On 5/23/07, SiSi'mon <s_...@purpleblade.net> wrote:
>>
>> Thanks, I am not quite sure I understand everything in the article. We
>> have
>> ID's on every component in the xhtml.
>>
>> Not sure how to implement the suggestion for not using session scoped
>> beans.
>>
>>
>> Si'mon
>>
>>
>> David Delbecq-2 wrote:
>> >
>> > Since you seem to be using facelets:
>> >
>> >
>> http://wiki.java.net/bin/view/Projects/FaceletsFAQ#I_m_getting_Duplicate_ID_Errors
>> >
>> > SiSi'mon a écrit :
>> >> We are getting errors on nearly every page now that we are using
>> MyFaces
>> >> 1.1.5. All seem to point to a duplicate ID problem but checking the
>> >> xHTML
>> >> there is no duplicate ID. This seems to be generated or something.
>> >>
>> >> Something seems quite mucked up. any ideas?
>> >>
>> >> ---
>> >>
>> >> SEVERE: Error Rendering View[/web/Information.xhtml]
>> >> java.lang.IllegalStateException: Client-id : _id81 is duplicated in
>> the
>> >> faces tree. Component : idListForm:idPopupDataTable:_id81, path:
>> >> {Component-Path : [C
>> >>
>> >> ---
>> >>
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Started-using-Myfaces-1.1.5-and-every-page-is-broken-%28duplicate-ID-in-the-faces-tree-Component%29-tf3805053.html#a10771395
>> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Started-using-Myfaces-1.1.5-and-every-page-is-broken-%28duplicate-ID-in-the-faces-tree-Component%29-tf3805053.html#a10787654
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: Started using Myfaces 1.1.5 and every page is broken (duplicate ID in the faces tree Component)
Posted by Andrew Robinson <an...@gmail.com>.
Could you post some of the XHTML code? Also the full error from the
duplicate component ID may be helpful. That component path should
directly indicate which component is getting the error (it is in a
dataTable, and doesn't have an ID assigned to it).
Also if you are using facelets includes, you have to make sure that
IDs are unique for the entire component tree, not just the include. So
if you have:
<ui:include src="a.xhtml" />
<ui:include src="b.xhtml" />
the component IDs in a and b have to be unique.
Since you are having an issue with an auto-generated ID in a data
table, I'm inclined to think it is a component binding issue though.
On 5/23/07, SiSi'mon <s_...@purpleblade.net> wrote:
>
> Thanks, I am not quite sure I understand everything in the article. We have
> ID's on every component in the xhtml.
>
> Not sure how to implement the suggestion for not using session scoped beans.
>
>
> Si'mon
>
>
> David Delbecq-2 wrote:
> >
> > Since you seem to be using facelets:
> >
> > http://wiki.java.net/bin/view/Projects/FaceletsFAQ#I_m_getting_Duplicate_ID_Errors
> >
> > SiSi'mon a écrit :
> >> We are getting errors on nearly every page now that we are using MyFaces
> >> 1.1.5. All seem to point to a duplicate ID problem but checking the
> >> xHTML
> >> there is no duplicate ID. This seems to be generated or something.
> >>
> >> Something seems quite mucked up. any ideas?
> >>
> >> ---
> >>
> >> SEVERE: Error Rendering View[/web/Information.xhtml]
> >> java.lang.IllegalStateException: Client-id : _id81 is duplicated in the
> >> faces tree. Component : idListForm:idPopupDataTable:_id81, path:
> >> {Component-Path : [C
> >>
> >> ---
> >>
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Started-using-Myfaces-1.1.5-and-every-page-is-broken-%28duplicate-ID-in-the-faces-tree-Component%29-tf3805053.html#a10771395
> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>
>
Re: Started using Myfaces 1.1.5 and every page is broken (duplicate
ID in the faces tree Component)
Posted by SiSi'mon <s_...@purpleblade.net>.
Thanks, I am not quite sure I understand everything in the article. We have
ID's on every component in the xhtml.
Not sure how to implement the suggestion for not using session scoped beans.
Si'mon
David Delbecq-2 wrote:
>
> Since you seem to be using facelets:
>
> http://wiki.java.net/bin/view/Projects/FaceletsFAQ#I_m_getting_Duplicate_ID_Errors
>
> SiSi'mon a écrit :
>> We are getting errors on nearly every page now that we are using MyFaces
>> 1.1.5. All seem to point to a duplicate ID problem but checking the
>> xHTML
>> there is no duplicate ID. This seems to be generated or something.
>>
>> Something seems quite mucked up. any ideas?
>>
>> ---
>>
>> SEVERE: Error Rendering View[/web/Information.xhtml]
>> java.lang.IllegalStateException: Client-id : _id81 is duplicated in the
>> faces tree. Component : idListForm:idPopupDataTable:_id81, path:
>> {Component-Path : [C
>>
>> ---
>>
>
>
--
View this message in context: http://www.nabble.com/Started-using-Myfaces-1.1.5-and-every-page-is-broken-%28duplicate-ID-in-the-faces-tree-Component%29-tf3805053.html#a10771395
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: Started using Myfaces 1.1.5 and every page is broken (duplicate
ID in the faces tree Component)
Posted by David Delbecq <de...@oma.be>.
Since you seem to be using facelets:
http://wiki.java.net/bin/view/Projects/FaceletsFAQ#I_m_getting_Duplicate_ID_Errors
SiSi'mon a écrit :
> We are getting errors on nearly every page now that we are using MyFaces
> 1.1.5. All seem to point to a duplicate ID problem but checking the xHTML
> there is no duplicate ID. This seems to be generated or something.
>
> Something seems quite mucked up. any ideas?
>
> ---
>
> SEVERE: Error Rendering View[/web/Information.xhtml]
> java.lang.IllegalStateException: Client-id : _id81 is duplicated in the
> faces tree. Component : idListForm:idPopupDataTable:_id81, path:
> {Component-Path : [C
>
> ---
>