duplicate component ids after mirgration to JSF 1.2

2009-12-10 Thread Michael Heinen
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

Antwort: duplicate component ids after mirgration to JSF 1.2

2009-12-10 Thread Andreas . Schmidt
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

AW: Antwort: duplicate component ids after mirgration to JSF 1.2

2009-12-10 Thread Günther, Rene - Innflow AG
: 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

Re: Antwort: duplicate component ids after mirgration to JSF 1.2

2009-12-10 Thread Leonardo Uribe
: 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