Hi

Testing some examples to debug myfaces core 2.0, it was found the solution
for this problem. See:

https://issues.apache.org/jira/browse/MYFACES-1834

for details.

regards,

Leonardo Uribe

2009/12/10 "Günther, Rene - Innflow AG" <rene.guent...@innflow.com>

> Another cause could be the use of <%...@include file Tags . I dont know
> whether
> that falls in the dirty tag category :)
>
>
> -----Ursprüngliche Nachricht-----
> Von: andreas.schm...@hella.com [mailto:andreas.schm...@hella.com]
> Gesendet: Donnerstag, 10. Dezember 2009 15:47
> An: MyFaces Discussion
> Cc: MyFaces Discussion
> Betreff: Antwort: duplicate component ids after mirgration to JSF 1.2
>
> Hello,
>
> we had the same problems when updating from Faces 1.1.x to 1.2.x.
>
>
> Cause 1) Comment tags i.e. <!-- some comment --> inside a <t:dataTable>
> and or <t:dataScroller>
>
> Cause 2) input field is set readOnly, ie. after a save whiele staying on
> the page  (only in combination with a <t:saveState>
>
>
>
>
>
>
>
> Michael Heinen <michael.hei...@recommind.com>
>
> 10.12.2009 12:56
> Bitte antworten an
> "MyFaces Discussion" <users@myfaces.apache.org>
>
>
> An
> MyFaces Discussion <users@myfaces.apache.org>
> Kopie
>
> Thema
> duplicate component ids after mirgration to JSF 1.2
>
>
>
>
>
>
> I have massive problems with duplicate component ids after updating:
> - myFaces from 1.1.6 to 1.2.8
> - tomahawk from 1.1.7 to tomahawk12-1.1.9
> - tomhahawk sandbox from 1.1.7 to 1.1.9
> - richfaces from 3.1.5 to 3.3.2 (api,impl and ui)
> - tiles from 1 to 2.0.5
>
> The curious thing is that unique ids are claimed to be a duplicate.
> If I rename such an id to another one with a random number then this id is
> claimed!
>
> Sample stack:
> java.lang.IllegalStateException: duplicate Id for a component searches
>      at
> org.ajax4jsf.application.TreeStructureNode.apply(TreeStructureNode.java:68)
>      at
> org.ajax4jsf.application.TreeStructureNode.apply(TreeStructureNode.java:92)
>      at
> org.ajax4jsf.application.TreeStructureNode.apply(TreeStructureNode.java:92)
>      at
> org.ajax4jsf.application.TreeStructureNode.apply(TreeStructureNode.java:92)
>      at
> org.ajax4jsf.application.TreeStructureNode.apply(TreeStructureNode.java:92)
>      at
> org.ajax4jsf.application.TreeStructureNode.apply(TreeStructureNode.java:92)
>      at
> org.ajax4jsf.application.TreeStructureNode.apply(TreeStructureNode.java:92)
>      at
> org.ajax4jsf.application.TreeStructureNode.apply(TreeStructureNode.java:92)
>      at
> org.ajax4jsf.application.TreeStructureNode.apply(TreeStructureNode.java:92)
>      at
> org.ajax4jsf.application.TreeStructureNode.apply(TreeStructureNode.java:92)
>      at
> org.ajax4jsf.application.TreeStructureNode.apply(TreeStructureNode.java:92)
>      at
> org.ajax4jsf.application.TreeStructureNode.apply(TreeStructureNode.java:92)
>      at
> org.ajax4jsf.application.TreeStructureNode.apply(TreeStructureNode.java:92)
>      at
> org.ajax4jsf.application.TreeStructureNode.apply(TreeStructureNode.java:92)
>      at
> org.ajax4jsf.application.TreeStructureNode.apply(TreeStructureNode.java:92)
>      at
>
> org.ajax4jsf.application.AjaxStateManager.getTreeStructureToSave(AjaxStateMa
> nager.java:187)
>      at
>
> org.ajax4jsf.application.AjaxStateManager.buildViewState(AjaxStateManager.ja
> va:498)
>      at
>
> org.ajax4jsf.application.AjaxStateManager.saveView(AjaxStateManager.java:462
> )
>      at
>
> org.apache.myfaces.tomahawk.application.jsp.JspTilesTwoViewHandlerImpl.rende
> rTilesView(JspTilesTwoViewHandlerImpl.java:211)
>
> Sample tag:
> <t:div id="searches" forceId="true">
>
> I use this tag with forceId many times (with different ids of course) and
> on some pages I get the duplicate id exceptions!
> I don't use c-tags, scriptlets or other "dirty" tags and the ebove div is
> not inside collection tags like datatable or datalist. I cannot see any
> pattern in this kind of error.
>
> Are there any known issues regarding duplicate ids or the tree creation?
> Is this rather a myfaces, tomahawk or richfaces issue?
>
> Thanks,
> Michael
>
>
>

Reply via email to