There are a lot of nested conversations in my application and I've been
struggling with the conversation states for days (especially when a son
conversation begins exactly inside a method which is annotated as @End in the
mother conversation). This fix can help me enormously, I'm really
There is a method which ends a mother conversation like this:
|
| @End
| public void doA(){
| ...
| // call a method of another action bean which is annotated with
@Begin(nested=true)
| ...
| // call a method of another action bean which is annotated with @End
| ...
You can't end two conversations in a single request. That's not how the model
works. @End simply says at the end of the request, end the current
conversation.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4063048#4063048
Reply to the post :
[EMAIL PROTECTED] wrote : You can't end two conversations in a single
request. That's not how the model works. @End simply says at the end of the
request, end the current conversation.
For error handling a typical idiom in pages.xml is:
| exception
Wolfgang, although you question is not directed to me, I would suggest filling
JIRA issue for this, because this behavior looks like not intended, indeed.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4060679#4060679
Reply to the post :
anonymous wrote : IllegalStateException should be thrown if @Begin(nested=true)
is encountered and there is no long-running conversation active.
I think that might cause some difficulties with reuse and recursive use.
I.e. In crud application i can start creation of a new object from a master
hkarapuu wrote : anonymous wrote : IllegalStateException should be thrown if
@Begin(nested=true) is encountered and there is no long-running conversation
active.
|
|
| I think that might cause some difficulties with reuse and recursive use.
|
| I.e. In crud application i can start
The intended behavior is that a non-nested long-running conversation should
begin in this case. thanks for reporting this.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4060932#4060932
Reply to the post :
anonymous wrote : When @Begin(nested=true) is encountered and there is NO
long-running conversation active, a nested conversation does NOT get created.
Instead, the temporary conversation being active gets promoted to a
long-running conversation. So we get the same behavior in this case as
anonymous wrote : hkarapuu, do I understand you correctly that you want the
following behavior? (The following is the behavior I'd prefer to see if I
could choose...)
|
| When @Begin(nested=true) is encountered and there is already a long-running
conversation active, a new nested
Any comments about this, or should I add it to JIRA?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4060609#4060609
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4060609
___
11 matches
Mail list logo
