[
https://jira.jboss.org/browse/WELD-554?page=com.atlassian.jira.plugin.sys...
]
Ingo Fischer commented on WELD-554:
-----------------------------------
Sorry, my last comment is wrong.
After a good clean and redeploy, the error-page rule in Web.xml worked for both
NonexistentConversationException and ViewExpiredException. The redirection happens as
expected.
org.jboss.weld.context.NonexistentConversationException can't be
catched by a rule in web.xml
---------------------------------------------------------------------------------------------
Key: WELD-554
URL:
https://jira.jboss.org/browse/WELD-554
Project: Weld
Issue Type: Bug
Components: Conversations
Environment: Microsoft Windows 7 Professional. Java 1.6.0_18-b07.
Glassfish-3.0.1-b20.
Reporter: NIkola Nikolic
Fix For: 1.0.2.CR1
org.jboss.weld.context.NonexistentConversationException can't be catched by a rule in
web.xml. Let's say that page
http://localhost:8080/test6/faces/index.xhtml?cid=1 can
be rendered. If conversation time out and user tries to access page again, error page
occures with following message:
XML Parsing Error: no element found
Location:
http://localhost:8080/test6/faces/index.xhtml?cid=3
Line Number 1, Column 1:
even if rule for exception exists in web.xml
<error-page>
<exception-type>org.jboss.weld.context.NonexistentConversationException</exception-type>
<location>/faces/error.xhtml</location>
</error-page>
Same error occures if user change url manualy by changing cid number to non existing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira