[JBoss-user] [JBoss Seam] - Re: Problems with pages.xml...

2006-07-10 Thread bkyrlach
Problem 3: So, trying it a new way, I had the pages action start a conversation by invoking a method with the following annotation... @Begin(id=1) in a stateful conversational bean. However, when submitting the form on the page, the following exception is thrown... 14:15:21,805 ERROR [PhaseLis

[JBoss-user] [JBoss Seam] - Re: Problems with pages.xml...

2006-07-10 Thread [EMAIL PROTECTED]
If the page action begins the conversation, there is already a conversation - so you should not have a @Begin annotation on the form action method. This is not in any way contrary to the documentation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956690#39

[JBoss-user] [JBoss Seam] - Re: Problems with pages.xml...

2006-07-10 Thread bkyrlach
Gavin... I think you misunderstood me. There is no form action that starts a conversation. That method annotated with @Begin is the method that the page action is calling... not the form action. Either way, the documentation clearly states that calling a method annotated with @Begin(id="somethi

[JBoss-user] [JBoss Seam] - Re: Problems with pages.xml...

2006-07-10 Thread [EMAIL PROTECTED]
OK then, but you typed: anonymous wrote : However, when submitting the form on the page, the following exception is thrown Is it thrown when you render the page, or when you submit the form? Anyway, AFAICT, the exception is being thrown because you already have a long-running conversation asso

[JBoss-user] [JBoss Seam] - Re: Problems with pages.xml...

2006-07-10 Thread bkyrlach
It's happening when right before the render-response phase after a form submission. I guess I'm still misunderstanding the way conversation works. It definitely still throws the exception when I remove the (id=1) part. I'm not sure what you mean by "calling the method twice", but either way, I'm

[JBoss-user] [JBoss Seam] - Re: Problems with pages.xml...

2006-07-10 Thread [EMAIL PROTECTED]
Right, i think what you are telling me is that the page action is called twice: once when we first navigate to the page, and again when we submit the form. The second time blows up, b/c it tries to start a conversation when one already exists. Right? Page actions are called *every* time a view-

[JBoss-user] [JBoss Seam] - Re: Problems with pages.xml...

2006-07-10 Thread [EMAIL PROTECTED]
BTW, the problem is easily fixed by using @Begin(join=true) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956753#3956753 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956753 -

[JBoss-user] [JBoss Seam] - Re: Problems with pages.xml...

2006-07-10 Thread bkyrlach
Gavin... Does @Begin(join=true) still invoke the code in the annotated method if you're joining an existing conversation? If not, that definitely would be a solution to my problem. Either way, what you just said pointed me to the real problem (yes, I feel pretty dumb now). When I changed folder

[JBoss-user] [JBoss Seam] - Re: Problems with pages.xml...

2006-07-10 Thread [EMAIL PROTECTED]
anonymous wrote : Does @Begin(join=true) still invoke the code in the annotated method if you're joining an existing conversation? Yes it does. I assumed that your method was basically a no-op. anonymous wrote : I'm now guessing that the documentation was speaking of a user who wasn't in a conv