Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 3.3
-
Fix Version/s: EE-3.3.0.GA, 4.0.BETA, 4.0
-
Labels:None
-
Environment:JBoss 6, CDI, Weld
-
Assignee Priority:P1
-
Salesforce Case Reference:
-
Workaround Exists:Yes
-
Workaround Description:
Description
After a CDI Conversation is started the sessionExpireRedirectURI does not redirect the user after the session has expired. If a CDI conversation is not started then the parameter works correctly.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Field | Original Value | New Value |
---|---|---|
Salesforce Case Reference | 5007000000T6BYOAA3 |
Attachment | 12134.war [ 15844 ] |
Assignee | Deryk Sinotte [ deryk.sinotte ] | |
Fix Version/s | EE-3.3.0.GA [ 10572 ] | |
Fix Version/s | 3.4 [ 10770 ] | |
Assignee Priority | P1 [ 10010 ] |
Attachment | 12134-mod.war [ 15852 ] |
Workaround Description |
As noted in the case, it's possible to handle the CDI exception from the client using either the JSF or ICE API for error handling.
It's also possible to make your own ExceptionHandler that can either remove the exception and let the SessionExpiredException propagate to the client so that the redirect behaves normally or handle the error in some other way. |
|
Workaround Exists | Yes [ 10007 ] |
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Won't Fix [ 2 ] |
Fix Version/s | 4.0 [ 11382 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |