Unable to deploy Tobago sample application to JSF RI 1.2_05 RC3
---------------------------------------------------------------
Key: TOBAGO-516
URL: https://issues.apache.org/jira/browse/TOBAGO-516
Project: MyFaces Tobago
Issue Type: Bug
Components: Demo
Affects Versions: 1.0.11
Environment: Ubuntu Feisty Fawn
JDK 1.6.0_03
JSF-RI 1.2_05 RC3
Reporter: Ryan Lubke
When attempting to deploy the latest Tobago snapshot demo, I see the following
error upon deployment:
[#|2007-10-15T11:24:42.109-0700|SEVERE|sun-appserver9.1|javax.enterprise.system.container.web|_ThreadID=16;_ThreadName=Timer-5;_RequestID=d4c3328a-551f-42df-a738-9d82f6217276;|WebModule[/tobago]PWC1275:
Exception sending context initialized event to listener instance of class
com.sun.faces.config.ConfigureListener
com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! Unable to
parse document 'jndi:/server/tobago/WEB-INF/faces-config.xml':
cvc-pattern-valid: Value '404' is not facet-valid with respect to pattern
'#\{.*\}' for type 'faces-config-el-expressionType'.
Looking at the faces-config.xml in question, the following navigation rule is
specified:
<navigation-rule>
<from-view-id>/best-practice/error.jsp</from-view-id>
<navigation-case>
<from-action>404</from-action>
<to-view-id>/best-practice/not-existing-page.jsp</to-view-id>
</navigation-case>
<navigation-case>
<from-action>syntax</from-action>
<to-view-id>/best-practice/error-in-syntax.jsp</to-view-id>
</navigation-case>
</navigation-rule>
The description of from-action:
The "from-action" element contains an action reference expression
that must have been executed (by the default ActionListener for handling
application level events) in order to select this navigation rule.
That having been said, this will probably work fine on JSF-RI 1.2_04 P02.
1.2_05 change the config parsing to use schemas for all validation.
1.2_05 includes a private 1.1 version of the schema. Any 1.x based faces-config
files will be converted to refer to the private schema internally and then
validated
using a cached schema instance. This was done as it is very difficult to
provide
both schema and dtd validation without relying on implementation specific
properties.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
