Re: Unexpected behaviour of duplicate id check algorithm

Hi, you are absolutely right: i am using nested custom facelet tags calling each other inside of c:forEach tag. I have already tried your fix: it works now! Thanks a lot and best regards, Alexey Am 24.11.2014 um 21:09 schrieb Leonardo Uribe: Hi I think I found the problem. In UserTagHandl

Re: Unexpected behaviour of duplicate id check algorithm

Hi In 2.1.x the logic in UserTagHandler was a bit different, so the bug is only in 2.2.x branch. I suppose it will solve the problem. I have already committed the code on trunk. regards, Leonardo Uribe 2014-11-24 15:09 GMT-05:00 Leonardo Uribe : > Hi > > I think I found the problem. In UserTagH

Re: Unexpected behaviour of duplicate id check algorithm

Hi I think I found the problem. In UserTagHandler there is a missing call to fcc.endComponentUniqueIdSection(); . That means all custom facelet tags will have the problem, but it will only be found when you use nested combinations of custom facelet tags and c:forEach tags. I'll fix it under MYFACE

Re: Unexpected behaviour of duplicate id check algorithm

Hi The only change that could cause like that between 2.1.x and 2.2.x is: https://issues.apache.org/jira/browse/MYFACES-3811 Fix c:forEach behavior once for all The previous algorithm (in 2.1.x) caused problems when you try combinations of c:forEach and ui:include and other tags, so in that sens

Unexpected behaviour of duplicate id check algorithm

Hi, I have upgraded Myfaces version from 2.1.6 to 2.2.5 in my project and getting strange exception now, stating, that smth. wrong with ids on the page. Exception differs, depending on javax.faces.PARTIAL_STATE_SAVING parameter value. With javax.faces.PARTIAL_STATE_SAVING set to false: java