a4j:poll redirect redux

[robertgary1]

I see that there has been some discussion about this previously but I don't see a clear solution. I have a filter that may occasionally attempt to redirect the user to another page...

web.xml

    <filter>

        <filter-name>JsfLoginCheckFilter</filter-name>

        <filter-class>

            com.xxx.client.jsf.filter.LoginFilter

        </filter-class>

    </filter>

The filter does...

        ..... (isValid is set for a variety of complex reasons)

        if ( isValid == false)

        {

            response.sendRedirect("/servlet.html?page=login");

            if ( session != null )

            {

                session.invalidate();

            }

        }

        else

            chain.doFilter(request, response); // let other filters do their job

However, a4j:poll just shutsdown after a redirect request and does not honor the redirect. Is there anyway I can detect a redirect request in a a4j:poll hook or a way to pass a response or session variable that I can read somewhere in JS to make the redirect happen?

-Robert

[ilya40umov]

Take a look at this link:

http://docs.jboss.org/richfaces/latest_3_3_X/en/devguide/html/ArchitectureOverview.html

It says:

5.10. Request Errors and Session Expiration Handling

expand all

5.10.1. Request Errors Handling

5.10.2. Session Expired Handling

RichFaces allows to redefine standard handlers responsible for processing of different exceptional situations. It helps to define own JavaScript, which is executed when these situations occur.

Add the following code to web.xml:

<context-param> 
    <param-name>org.ajax4jsf.handleViewExpiredOnClient</param-name> 
    <param-value>true</param-value> 
</context-param> 
        

5.10.1. Request Errors Handling

To execute your own code on the client in case of an error during Ajax request, it's necessary to redefine the standard "A4J.AJAX.onError" method:

 A4J.AJAX.onError = function(req, status, message){
    window.alert("Custom onError handler "+message);
}

The function defined this way accepts as parameters:

• req - a params string of a request that calls an error
• status - the number of an error returned by the server
• message - a default message for the given error

Thus, it's possible to create your own handler that is called on timeouts, internal server errors, and etc.

5.10.2. Session Expired Handling

It's possible to redefine also the "onExpired" framework method that is called on the "Session Expiration" event.

Example:

A4J.AJAX.onExpired = function(loc, expiredMsg){
    if(window.confirm("Custom onExpired handler "+expiredMsg+" for a location: "+loc)){
      return loc;
    } else {
     return false;
    }
}

Here the function receives in params:

• loc - URL of the current page (on demand can be updated)
• expiredMsg - a default message on "Session Expiration" event.

Note:

Note that custom "onError", "onExpire" handlers do not work under MyFaces. MyFaces handles exception by its internals generating debug page. You could use the following code to prevent such behavior:

...
<context-param> 
    <param-name>org.apache.myfaces.ERROR_HANDLING</param-name> 
    <param-value>false</param-value> 
</context-param> 
...

[robertgary1]

Thank you!!!!

I was already using A4J.AJAX.on* functions but did not have the web.xml setting for org.ajax4jsf.handleViewExpiredOnClient. After putting that in it seems to be working.

-Robert