-
1. Re: Two/many conversations
gavin.king Oct 31, 2005 11:56 AM (in response to marius.oancea)Right, calling a @Begin method inside the scope of an existing conversation has no effect.
-
2. Re: Two/many conversations
marius.oancea Oct 31, 2005 12:36 PM (in response to 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. -
3. Re: Two/many conversations
gavin.king Oct 31, 2005 2:46 PM (in response to marius.oancea)Your "feelings" are unreliable.
See my previous post for the actual behavior. -
4. Re: Two/many conversations
patrick_ibg Oct 31, 2005 3:45 PM (in response to marius.oancea)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. -
5. Re: Two/many conversations
gavin.king Oct 31, 2005 4:07 PM (in response to marius.oancea)I expect so. Nested conversations will need some kind of name to identify them, I suppose.
-
6. Re: Two/many conversations
marius.oancea Nov 1, 2005 2:14 AM (in response to 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 ?