[
http://jira.jboss.com/jira/browse/JBSEAM-1641?page=comments#action_12368719 ]
Gavin King commented on JBSEAM-1641:
------------------------------------
OK, 1 is fixed.
About 2, I agree with you which is why I never implemented before. So how is the developer
supposed to declare which adhoc navigation is OK, and which isn't?
redirect do proper page in pageflow as out of order request comes in
--------------------------------------------------------------------
Key: JBSEAM-1641
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1641
Project: JBoss Seam
Issue Type: Feature Request
Components: BPM
Reporter: Michael Kozak
Assigned To: Gavin King
Fix For: 2.0.0.CR1
I'll describe scenario.
Pages used in page flow "p1, p2, p3, pfinal".
Transitions:
p1 to p2
p2 to p3
p3 to pfinal
eg. p1 -> p2 -> p3 -> pfinal
p1 starts conversation, pfinal ends conversation
p2,p3,pfinal requires conversation.
Now let's consider out of order requests.
I enter page p1, conversation is started.
Next I point the browser manually to page p3 with cid included.
Page p3 is displayed with "garbage" - no logic in p2 was executed.
Buttons on page redirect to p1 of course.
Feature request: redirect the request to page p3 to go to proper page (p1 in this case).
This applies only when conversation is in progress as other requests are handled by
no-conversation-view-id.
Seam has org.jboss.seam.core.pageflow in conversation scope with "page" and
"node" properties set to "p1" but it seems that it is checked only on
POST requests.
--
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