You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by "Thomas Andraschko (JIRA)" <ji...@apache.org> on 2015/12/18 10:27:46 UTC

[jira] [Assigned] (DELTASPIKE-1043) Loop redirect in error-page (404) with CLIENTWINDOW

     [ https://issues.apache.org/jira/browse/DELTASPIKE-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Andraschko reassigned DELTASPIKE-1043:
---------------------------------------------

    Assignee: Thomas Andraschko

> Loop redirect in error-page (404) with CLIENTWINDOW
> ---------------------------------------------------
>
>                 Key: DELTASPIKE-1043
>                 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1043
>             Project: DeltaSpike
>          Issue Type: Bug
>          Components: JSF22-Module
>    Affects Versions: 1.5.2
>         Environment: Error page in web.xml and clientWindowMode and WildFly
>            Reporter: Janario
>            Assignee: Thomas Andraschko
>         Attachments: loop-redirect.patch, workaround.patch
>
>
> I have defined an error-page in web.xml to 404
> <error-page>
>         <error-code>404</error-code>
>         <location>/faces/page-not-found.xhtml</location>
> </error-page>
> But when I use CLIENTWINDOW it starts to redirects in loop from windowhandler.html
> As I've seen this happens because the dsrid param is lost after the container forward it to error page. So ClientSideWindowStrategy.getRequestTokenParameter always return null and send to windowhandler.html
> Attached a patch to simulate it in jsf-playground
> Patch: loop-redirect.patch
> After apply it. I ran with: mvn wildfly:run -P run-wildfly-8.0.0
> And opened http://localhost:8080/ds/not-found
> I've also attached an workaround that put dsrid param as attribute and lookup for it in ClientSideWindowStrategy
> I know it isn't the best way but I couldn't find another way to do that



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)