[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-3248) With pages-2.1.xsd <redirect view-id="#{archivoFrom}"/> produces error: not valid with respect to its type
Alexey Kazakov (JIRA)
jira-events at lists.jboss.org
Fri Nov 21 09:55:36 EST 2008
[ https://jira.jboss.org/jira/browse/JBIDE-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12439309#action_12439309 ]
Alexey Kazakov commented on JBIDE-3248:
---------------------------------------
Yes. It's an issue of http://jboss.com/products/seam/pages-2.1.xsd schema.
> With pages-2.1.xsd <redirect view-id="#{archivoFrom}"/> produces error: not valid with respect to its type
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-3248
> URL: https://jira.jboss.org/jira/browse/JBIDE-3248
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 2.1.2
> Reporter: Francisco Jose Peredo Noguez
>
> I know that JBoss Tools is not compatible with Seam 2.1, but so far I have migrated 3 projects from Seam 2.0.x to Seam 2.1.x and I didnt have any major problems until now, many of my pages.xml have code like this:
> <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 problem is with <redirect view-id="#{someEntityFrom}"/>, when I changed the schema to pages-2.1.xsd I get this error:
> Severity and Description Path Resource Location Creation Time Id
> cvc-attribute.3: The value '#{entityFrom}' of attribute 'view-id' on element 'redirect' is not valid with respect to its type, 'view-id'. webappsbmi/WebContent/Crud SomeEntityEdit.page.xml line 22 1227058220562 154435
> My guess is that when I change to pages-2.1.xsd the special Seam based validation for the file is disabled and plain Eclipse XSD validation kicks in and it does not like the value '#{entityFrom}' for view-id, but I do not get why (or if there is a way to workaround it).
> I guess this problem dissapears with 3.0, but it would be nice to have a way to no see pages-2.1.xsd as if they had errors when they are perfectly valid files.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list