[weld-issues] [JBoss JIRA] Updated: (WELD-554) org.jboss.weld.context.NonexistentConversationException can't be catched by a rule in web.xml

[Pete Muir (JIRA)]

     [ https://jira.jboss.org/browse/WELD-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Muir updated WELD-554:
---------------------------

    Fix Version/s: 1.1.0.BETA2
                       (was: 1.1.0.BETA1)


> 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.1.0.BETA2
>
>
> 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