[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-4223) Error page is called relative to invoking URL

[Norman Richards (JIRA)]

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

Norman Richards updated JBSEAM-4223:
------------------------------------

    Fix Version/s: 2.2.0.CR1
         Assignee: Norman Richards


> Error page is called relative to invoking URL
> ---------------------------------------------
>
>                 Key: JBSEAM-4223
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-4223
>             Project: Seam
>          Issue Type: Bug
>          Components: Core, Exception Handling
>    Affects Versions: 2.1.2.CR2
>         Environment: Windows XP, WAS V7
>            Reporter: Holger Schildberg
>            Assignee: Norman Richards
>             Fix For: 2.2.0.CR1
>
>
> Hi,
> the problem occurs when an exception is thrown on a page that has an rewrite pattern associated in the pages.xml. During the redirection in the exception handling process the MockViewHandler.getActionURL(FacesContext, String) constructs the wrong URL to the error page.
> Instead of returning an absolute URL it simply adds the error page's URL to the invoking address. The result is a 404 error message from the container.
> Here's the relevant configuration part of the pages.xml:
> [...]
> <page view-id="/pages/myBookings.xhtml">
>   <rewrite pattern="/booking/list" />
> </page>
> <exception logLevel="error">
>   <redirect view-id="/pages/error.xhtml">
>     <message>A problem occured</message>
>   </redirect>
> </exception>
> [...]
> Normally, after the exception occurs on /booking/list the framework should redirect to /pages/error.seam but instead it redirects to /pages/myBookings.seam/pages/error.xhtml
> As you also see, the wrong extension is used as the MockViewHandler adds the complete view Id without replacing it with the current view handler mapping.
> Regards
> Holger

-- 
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