]
Dan Allen commented on JBSEAM-3741:
-----------------------------------
Oops, try now. I accidentally made view-id a method-expression instead of a
value-expression.
It is now invalid to write an an EL expression inside view-id!
--------------------------------------------------------------
Key: JBSEAM-3741
URL:
https://jira.jboss.org/jira/browse/JBSEAM-3741
Project: Seam
Issue Type: Bug
Affects Versions: 2.1.0.SP1
Reporter: Francisco Jose Peredo Noguez
Assignee: Norman Richards
Fix For: 2.1.1.CR2
I am hitting this issue JBIDE-3248, at first I thougth it was an incompatiblity problem
between JBoss Tools 2.1.2, and Seam 2.1.x, but now I think it is an error in
http://jboss.com/products/seam/pages-2.1.xsd.
In pages-2.1.xsd we have this code (that didnt exist in 2.0):
<xs:simpleType name="view-id">
<xs:restriction base="xs:string">
<xs:pattern value="(/.*)|\*"/>
</xs:restriction>
</xs:simpleType>
That is limiting view-id by preventing it from using EL expressions inside it, but EL
expression do work inside view-id:
<navigation from-action="#{someEntityHome.persist}">
<rule if-outcome="persisted" if="#{not empty
someEntityFrom}">
<end-conversation/>
<redirect view-id="{#someEntityFrom}"/>
</rule>
<rule if-outcome="persisted" if="#{empty
someEntityFrom}">
<end-conversation/>
<redirect view-id="/Crud/SomeEntityList.xhtml"/>
</rule>
</navigation>
The line <redirect view-id="{#someEntityFrom}"/> is being reported as an
error, but it is perfectly fine. I think the <xs:pattern
value="(/.*)|\*"/> specified for view-id in pages-2.1.xsd is an error.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: