[ICE-3186] auto navigate on session-timeout does not work - ICEsoft JIRA Issue Tracker

Details

Type: Bug
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: 1.6
Fix Version/s: 1.7.2
Component/s: Framework
Labels:
None
Environment:
Any

Affects:

Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial

Description

Using this:
     <error-page>
         <exception-type>com.icesoft.faces.webapp.http.core.SessionExpiredException</exception-type>
         <location>/index.jsp</location>
     </error-page>

I have tried this using sync and async, and tested on 1.7.1 build 2, 1.7.0, and 1.6.2.

Options
- Sort By Name
- Sort By Date
- Ascending
- Descending
- Download All

Attachments

Hide
redirectonexpiry.zip

20/Jun/08 1:48 PM

5.18 MB

Mircea Toma
redirectonexpiry/.DS_Store 6 kB

__MACOSX/redirectonexpiry/._.DS_Store 0.1 kB

redirectonexpiry/build.xml 2 kB

redirectonexpiry/src/.DS_Store 6 kB

__MACOSX/redirectonexpiry/.../._.DS_Store 0.1 kB

redirectonexpiry/src/com/.DS_Store 6 kB

__MACOSX/redirectonexpiry/.../._.DS_Store 0.1 kB

redirectonexpiry/src/.../icesoft/.DS_Store 6 kB

__MACOSX/redirectonexpiry/.../._.DS_Store 0.1 kB

redirectonexpiry/.../SessionBoundBean.java 3 kB

redirectonexpiry/src/.../ViewBoundBean.java 0.6 kB

redirectonexpiry/web/.DS_Store 6 kB

__MACOSX/redirectonexpiry/.../._.DS_Store 0.1 kB

redirectonexpiry/web/index.jsp 0.1 kB

redirectonexpiry/web/page.jspx 0.5 kB

__MACOSX/redirectonexpiry/.../._page.jspx 0.1 kB

redirectonexpiry/web/WEB-INF/.DS_Store 6 kB

__MACOSX/redirectonexpiry/.../._.DS_Store 0.1 kB

redirectonexpiry/.../SessionBoundBean.class 2 kB

redirectonexpiry/.../SessionBoundBean.java 3 kB

redirectonexpiry/web/.../ViewBoundBean.class 1 kB

redirectonexpiry/web/.../ViewBoundBean.java 0.6 kB

redirectonexpiry/web/.../faces-config.xml 3 kB

redirectonexpiry/.../backport-util-concurrent.jar 319 kB

redirectonexpiry/.../commons-beanutils.jar 184 kB

redirectonexpiry/.../commons-collections.jar 558 kB

redirectonexpiry/.../commons-digester.jar 140 kB

redirectonexpiry/.../commons-discovery.jar 70 kB

redirectonexpiry/web/.../lib/commons-el.jar 110 kB

redirectonexpiry/.../commons-fileupload.jar 87 kB

Showing 30 of 38 items Download Zip
Show

redirectonexpiry.zip

20/Jun/08 1:48 PM

5.18 MB

Mircea Toma

Issue Links

blocks

ICE-3106 New sessionExpiredRedirectURI context parameter

Closed

ICE-3232 Support redirect on session expiry via ICEfaces bridge configuration

Closed

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Ken Fyten added a comment - 16/Jun/08 11:02 AM

Greg notes:

That wont work. The way the error code stuff works is that if the request throws an exception, the servlet container fetches the appropriate file and serves up the response including the contents of the file.

This bit in web.xml

<error-page>
<exception-type>java.lang.Exception</exception-type>
<location>/error.html</location>
</error-page>

causes this type of response to be sent to the browser:

HTTP/1.1 500 java.lang.RuntimeException
Server: Apache-Coyote/1.1
ETag: W/"278-1209424220000"
Last-Modified: Mon, 28 Apr 2008 23:10:20 GMT
Content-Type: text/html
Content-Length: 278
Date: Thu, 05 Jun 2008 15:23:45 GMT
Connection: close

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Insert title here</title>
</head>
<body>
Something bad happened.
</body>
</html>[52.659103s]
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Content-Length: 0
Date: Thu, 05 Jun 2008 15:23:45 GMT

For this to work, the exception has to be thrown to the servlet container, and the servlet container fetches the resource and serves it up all in one motion.

The framework doesn't throw sessionExpired exceptions. The framework and bridge engage in a protocol to shut down the bridge instance and dipose of the views.

Show

Ken Fyten added a comment - 16/Jun/08 11:02 AM Greg notes: That wont work. The way the error code stuff works is that if the request throws an exception, the servlet container fetches the appropriate file and serves up the response including the contents of the file. This bit in web.xml <error-page> <exception-type>java.lang.Exception</exception-type> <location>/error.html</location> </error-page> causes this type of response to be sent to the browser: HTTP/1.1 500 java.lang.RuntimeException Server: Apache-Coyote/1.1 ETag: W/"278-1209424220000" Last-Modified: Mon, 28 Apr 2008 23:10:20 GMT Content-Type: text/html Content-Length: 278 Date: Thu, 05 Jun 2008 15:23:45 GMT Connection: close <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <title>Insert title here</title> </head> <body> Something bad happened. </body> </html> [52.659103s] HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Content-Length: 0 Date: Thu, 05 Jun 2008 15:23:45 GMT For this to work, the exception has to be thrown to the servlet container, and the servlet container fetches the resource and serves it up all in one motion. The framework doesn't throw sessionExpired exceptions. The framework and bridge engage in a protocol to shut down the bridge instance and dipose of the views.

7 older comments

Hide

Permalink

Jacky Lee added a comment - 08/Jul/08 3:44 PM

the fix is broken on 1.7 branch at revision 17030

Show

Jacky Lee added a comment - 08/Jul/08 3:44 PM the fix is broken on 1.7 branch at revision 17030

Hide

Permalink

Mircea Toma added a comment - 09/Jul/08 10:50 AM

Tested successfully with 1.7 branch.

Show

Mircea Toma added a comment - 09/Jul/08 10:50 AM Tested successfully with 1.7 branch.

Hide

Permalink

Deryk Sinotte added a comment - 12/Sep/08 12:12 PM

Investigate and verify

Show

Deryk Sinotte added a comment - 12/Sep/08 12:12 PM Investigate and verify

Hide

Permalink

Greg Dick added a comment - 12/Sep/08 12:53 PM

I have an application that this works in. It successfully navigates to my configured page on session timeout. My test application has the following:

<context-param>
<param-name>com.icesoft.faces.sessionExpiredRedirectURI</param-name>
<param-value>'sessionExpired.jsp'</param-value>
</context-param>

and I do have the connection status indicator on the page.

Show

Greg Dick added a comment - 12/Sep/08 12:53 PM I have an application that this works in. It successfully navigates to my configured page on session timeout. My test application has the following: <context-param> <param-name>com.icesoft.faces.sessionExpiredRedirectURI</param-name> <param-value>'sessionExpired.jsp'</param-value> </context-param> and I do have the connection status indicator on the page.

Hide

Permalink

Tiberiu Benedek added a comment - 17/Feb/09 8:37 AM

I am working with icefaces 1.7.2 SP1.

<context-param>
<param-name>com.icesoft.faces.synchronousUpdate</param-name>
<param-value>true</param-value>
</context-param>

<context-param>
<param-name>com.icesoft.faces.sessionExpiredRedirectURI</param-name>
<param-value>sessionExpired.jsp</param-value>
</context-param>

This does NOT work in synchronous mode. It only works on asynchronous mode.

Show

Tiberiu Benedek added a comment - 17/Feb/09 8:37 AM I am working with icefaces 1.7.2 SP1. <context-param> <param-name>com.icesoft.faces.synchronousUpdate</param-name> <param-value>true</param-value> </context-param> <context-param> <param-name>com.icesoft.faces.sessionExpiredRedirectURI</param-name> <param-value>sessionExpired.jsp</param-value> </context-param> This does NOT work in synchronous mode. It only works on asynchronous mode.

People

Assignee:

Unassigned

Reporter:

Jacky Lee

Votes:

0 Vote for this issue

Watchers:

1 Start watching this issue

Dates

Created:

13/Jun/08 1:24 PM

Updated:

17/Feb/09 8:37 AM

Resolved:

12/Sep/08 7:01 PM