]
Gavin King closed JBSEAM-1810.
------------------------------
Fix Version/s: (was: 2.0.0.CR1)
Resolution: Rejected
conversation-required="true"
no-conversation-view-id malfunction or a need for improvement
-------------------------------------------------------------
Key: JBSEAM-1810
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1810
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 2.0.0.BETA1
Environment: Tomcat 6.0.13, latest Seam 2.0 snapshot
Reporter: Przemyslaw Jaskierski
Priority: Critical
I have a bunch of views that are used by pageflow-defined conversation. Lets call them
page1.xhtml, page2.xhtml, page3.xhtml. I want to prevent user from simply typing arbitrary
url and accessing any view from those above. When a user types in a browser
http://url.com/page2.xhtml he should be redirected to a configured
no-conversation-view-id. That would be expected behaviour, but adding to the pages.xml
file this section:
<page view-id="/page2.xhtml"
no-conversation-view-id="/invalidconversationerror.xhtml"/>
Doesn't work, and user can enter with an undefined state into the middle of
conversational pages chain.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: