[
http://jira.jboss.com/jira/browse/JBSEAM-1972?page=all ]
Pete Muir resolved JBSEAM-1972.
-------------------------------
Resolution: Won't Fix
Assignee: Pete Muir
Yes, it was intended. No, it won't change again. (Ids should be unique as it allows
you to assign ids easily inside the s:decorate). Sorry about the breakage. I've made
a note in the migration guide.
s:decorate input control ID change from 1.2.1 to 2.0
----------------------------------------------------
Key: JBSEAM-1972
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1972
Project: JBoss Seam
Issue Type: Bug
Components: JSF
Affects Versions: 2.0.0.CR1
Reporter: steve tynor
Assigned To: Pete Muir
I'm not sure if this is a bug or is intended behavior, but component ID's have
changed from Seam version 1.2.1 to 2.0.0.CR1. This has broken our Selenium integration
tests and many of our Javascript functions which access and manipulate the input controls
via DHTML.
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?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira