[
https://issues.jboss.org/browse/JBSEAM-4868?page=com.atlassian.jira.plugi...
]
Marek Novotny commented on JBSEAM-4868:
---------------------------------------
Conversation is lost while restoring view :-(
{noformat}
14:08:38,758 DEBUG [org.jboss.seam.contexts.FacesLifecycle] (http--127.0.0.1-8080-5)
>>> Begin JSF request for /seam-booking/hotel.seam
14:08:38,759 DEBUG [org.jboss.seam.jsf.SeamPhaseListener] (http--127.0.0.1-8080-5)
beginning transaction prior to phase: RESTORE_VIEW 1
14:08:38,759 DEBUG [org.jboss.seam.transaction.UTTransaction] (http--127.0.0.1-8080-5)
beginning JTA transaction
14:08:38,761 DEBUG [org.jboss.seam.transaction.EjbSynchronizations]
(http--127.0.0.1-8080-5) afterBegin
14:08:38,778 DEBUG [org.jboss.seam.core.Manager] (http--127.0.0.1-8080-5) No stored
conversation
{noformat}
Original log with JSF 1.2 is restoring conversation correctly
{noformat}
14:02:19,885 DEBUG [org.jboss.seam.contexts.FacesLifecycle] (http--127.0.0.1-8080-4)
>>> Begin JSF request for /seam-booking/hotel.seam
14:02:19,886 DEBUG [org.jboss.seam.jsf.SeamPhaseListener] (http--127.0.0.1-8080-4)
beginning transaction prior to phase: RESTORE_VIEW 1
14:02:19,886 DEBUG [org.jboss.seam.transaction.UTTransaction] (http--127.0.0.1-8080-4)
beginning JTA transaction
14:02:19,887 DEBUG [org.jboss.seam.transaction.EjbSynchronizations]
(http--127.0.0.1-8080-4) afterBegin
14:02:19,911 DEBUG [org.jboss.seam.core.Manager] (http--127.0.0.1-8080-4) Restoring
conversation with id: 4
{noformat}
Long conversation is time out immediately after redirect
--------------------------------------------------------
Key: JBSEAM-4868
URL:
https://issues.jboss.org/browse/JBSEAM-4868
Project: Seam 2
Issue Type: Bug
Components: Examples
Environment: JBoss AS 7.1, JSF2, migrated Booking example to JSF2/Richfaces
4.1.0.Final
Reporter: Marek Novotny
Priority: Blocker
Fix For: 2.3.0.BETA1
While migrating Booking example I hit a bug with timed out of long conversation in
redirect request.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira