Two/many conversations

[marius.oancea]

Hi, What should be the seam behavior if i do the following:
I have a SFSB with a conversational context (just like HotelBookingAction). Conversation starts when find is called.

What happens if i will call another @Begin annoteated method from another SFSB ?

What happens with the original conversation ?

Only one conversation can exists at a time ?

Thanx for enlighten me

[gavin.king]

Right, calling a @Begin method inside the scope of an existing conversation has no effect.

[marius.oancea]

I have the feeling that @Begin destroy the old conversation. If yes this is quite bad. Anyway this is a quite big limit IMHO.

I think conversations are a incontrolable thing if so. The only way to avoid mistakes is to have no more than one Action having methods annotaded with @Begin and @End. If you ahve many, it's a kind of art to keep the application state correct. Maybe I'm wrong but this is what i see now.

[gavin.king]

Your "feelings" are unreliable.

See my previous post for the actual behavior.

[patrick_ibg]

gavin,

will this be the behavior going forward? i know there's been discussion of "nested" conversation contexts, i'm not sure how that will affect the current behavior.

[gavin.king]

I expect so. Nested conversations will need some kind of name to identify them, I suppose.

[marius.oancea]

Not a second @Begin destroyed the conversation but calling of the method in a

<t:tree2 id="clientTree" value="#{mySFSB.aMethod}" var="node" varNodeToggler="t">


aMethod is called to get the tree content but the conversation is destroyed (in mySFSB i have a destroy method that gets called). Any ideea why? Is that the correct behavior? What is the reason to do that ?