Hello everybody,
I have a very basic question about conversations in Seam.
One thing that is confusing me with conversation feature of Seam.
To my understanding, lets say I defined a workflow with 5 JSF pages which should run
under a converstational scope.
If I read and understand the documentation correctly, if I am going to navigate directly
at the 3rd JSF page without going 1st and 2nd first (in the middle of the worklfow and
conversation), because I didn't initialise the conversation at the 1st page with a
begin tag, Seam should complain about this.
This is the behaviour, I can't get at the practice, 3rd page rendered successfully and
now if I click the continue or back button at the 3rd page, now it complains about the
conversational state is not initialised because the method with begin tag is never
called.
So is conversion scope bounded to action listeners or to actions? I always thought the
controller is checking for the conversationId in the URL and if it is missing, it is not
letting go in the middle of the conversation.
And I am also confused with the example codes now. @Conversational tag is not necessary
now(examples are missing it)? ifNotBegunOutcome is depracated, is there a special reason
for this?
The alternative no-conversation-view-id is defined pages.xml, but now is this defined once
for the whole application? What if I have more then workflows and different entry points?
As you may see, I am confused little bit, any help would be appreciated :)
Thx in advance...
PS. If Seam conversation is not designed to provide this behaviour, do you know anyother
framework that provide this behaviour out of the box
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110148#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...