Weld
  1. Weld
  2. WELD-554

org.jboss.weld.context.NonexistentConversationException can't be catched by a rule in web.xml

    Details

    • Estimated Difficulty:
      Low
    • Steps to Reproduce:
      Hide

      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.

      Show
      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.
    • Similar Issues:
      Show 10 results 

      Description

      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.

        Activity

        Hide
        Ingo Fischer
        added a comment -

        I just tested this issue with the current Glassfish release V3.0.1 (what Weld does it contain, i think Weld 1.0.1Final?). As it seems it's still not possible at all to catch a ViewExpiredException NOR a NonexistentConversationException by a rule in the WEB.XML. With an ExceptionHandlerFactory it works.

        Show
        Ingo Fischer
        added a comment - I just tested this issue with the current Glassfish release V3.0.1 (what Weld does it contain, i think Weld 1.0.1Final?). As it seems it's still not possible at all to catch a ViewExpiredException NOR a NonexistentConversationException by a rule in the WEB.XML. With an ExceptionHandlerFactory it works.
        Hide
        Ingo Fischer
        added a comment -

        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.

        Show
        Ingo Fischer
        added a comment - 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.
        Hide
        Pete Muir
        added a comment -

        User reports this is now working.

        Please reopen if a specific failing example can be attached.

        Show
        Pete Muir
        added a comment - User reports this is now working. Please reopen if a specific failing example can be attached.

          People

          • Assignee:
            Pete Muir
            Reporter:
            NIkola Nikolic
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: