[
http://jira.jboss.com/jira/browse/JBSEAM-1605?page=all ]
Gavin King closed JBSEAM-1605.
------------------------------
Fix Version/s: 2.0.0.CR1
Resolution: Done
Assignee: Gavin King
OK, fixed in CVS - please test my fix and reopen this if you still have problems.
NotLoggedInExceptions handled by the ExceptionFilter arent
propegating the conversation correctly.
--------------------------------------------------------------------------------------------------
Key: JBSEAM-1605
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1605
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.0.0.BETA1
Reporter: Chris Rudd
Assigned To: Gavin King
Fix For: 2.0.0.CR1
I have Login Redirection setup as specified in 13.4.5/13.4.6 of the documentation.
When the NotLoggedInException is thrown the redirection is not propagating the
conversation correctly, so the return information stored in the
redirect.captureCurrentView call is not available when the returnToCaptureView is
executed.
NOTE: if the the login-required="true" is set for the view (instead of relying
on the beans @Restrict methods) the conversation IS propagated correctly, and you are
returned to the proper url after login.
This use to work correctly in 1.3.0-ALPHA. I belive the culprit may be the following line
that was added in 2.0.0-BETA :
ExceptionFilter.endWebRequestAfterException line 80
FacesLifecycle.beginExceptionRecovery( facesContext.getExternalContext() );
+ Manager.instance().initializeTemporaryConversation();
try
This initializes a new conversation, and the old conversation is no longer available
(known) to be propagated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira