[seam-issues] [JBoss JIRA] (JBSEAM-4868) Long conversation is time out immediately after redirect

Tue Jan 17 18:14:18 EST 2012

    [ https://issues.jboss.org/browse/JBSEAM-4868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660016#comment-12660016 ] 

Marek Novotny commented on JBSEAM-4868:
---------------------------------------

Even the conversation is found, Seam logic expects conversationId and conversationIsLongRunning property are set and stored in org.jboss.seam.faces.FacesPage for later usage. This is not working on JSF 2. org.jboss.seam.faces.FacesPage is not restored and conversationId and conversationIsLongRunning are not set like they was after RENDER phase.

> 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