Hi There was a change due to a bug found:
https://issues.apache.org/jira/browse/MYFACES-3665 f:metadata section removed when refresh view and is not included in the template directly The problem was that the f:viewParam was removed and added to the tree, destroying the state. The fix done exclude the content of f:metadata from mark/delete algorithm. When do this happen? in a postback? ajax? or the first time the view is rendered. Could you provide a test case to reproduce it? The strange part is I used a similar test case for this one and there was no bug. regards, Leonardo Uribe 2013/4/10 Howard W. Smith, Jr. <smithh032...@gmail.com> > On Wed, Apr 10, 2013 at 8:42 AM, Thomas Andraschko < > andraschko.tho...@gmail.com> wrote: > > > Hi, > > > > i get following exception after upgrading from 2.1.10 to 2.1.11: > > > > java.lang.IllegalStateException: component with duplicate id "j_id__md_1" > > found > > at > > > org.apache.myfaces.view.facelets.compiler.CheckDuplicateIdFaceletUtils.checkIds(CheckDuplicateIdFaceletUtils.java:100) > > > > If i remove the f:viewParam, it works fine. > > Is anything wrong with my code or is it a bug? > > > > > From MyFaces 2.1.11 release notes, I would assume that the bug was > introduced, possibly, by one of the following bugs listed in the > bugs-resolved list. > > > Release Notes - MyFaces Core - Version 2.1.11 > > Bug > > * [MYFACES-3659] - Conditional include of scripts and stylesheets > * [MYFACES-3663] - UIViewRoot.createUniqueId() should generate > unique ids for all the component tree. > * [MYFACES-3665] - f:metadata section removed when refresh view > and is not included in the template directly > * [MYFACES-3668] - CLONE - UIForm.createUniqueId should take into > account prependId logic >
