1 Reply Latest reply on Sep 25, 2007 6:40 PM by steve tynor

    s:decorate input control ID change from 1.2 to 2.0

    steve tynor Novice

      I reported a Seam2 bug to Richfaces that turned out to be a Seam bug
      and apparently already fixed in CVS (http://jira.jboss.org/jira/browse/JBSEAM-1947)
      (thanks Sergey and Pete!)

      I have a related question: another change in JSF ID names have broken our selenium test and many of our Javascript functions which refer to input controls by ID.

      Given something like:

      <s:decorate id="fooDecoration" template="/WEB-INF/facelets/templates/edit.xhtml">
       <ui:define name="label">Foo</ui:define>
       <h:inputText id="foo" value="#{fooHome.instance.foo}"/>
       </s:decorate>


      In Seam1.2.1, the control was addressable as "fooForm:foo". In Seam2, that has changed and we must address it as "fooForm:fooDecoration:foo".

      Is this intentional? Is it likely to change before 2.0.0GA?

      Thanks!