Have you checked the JSF 2.0 examples in the Seam download?
I'd try work this out for you but, I just don't have the time at the moment. But, my guess is that one of the examples should have an ajax call in there somewhere.
I have. I saw that the Booking example has several ajax requests in it, but none of them are conversational, with the exception of performing validation on event="blur". I haven't seen anything that calls a method on a backend object that has @Scope(scope=CONVERSATION). The examples in Seam 2.3beta1 are pretty sparse. My guess is they haven't finished migrating all of the examples over from 2.2.
I've moved my test code to the page that starts off my conversation (the no-conversation-view-id page) to make testing a bit easier. I am clearly able to see that each call via <a:ajax /> or <f:ajax /> results in a new conversation being created, rather than propagating the existing cid in the call. The flow should be: 1) Go to the start page which results in a new conversation being created, and 2) Make the ajax calls which propagate the existing conversation. That's not the behavior I'm seeing though, which is puzzling since this works with no problem in Seam 2.2 (albeit using the <a:support /> tags instead)
I am getting the same problem when using <h:selectOneMenu with <s:convertEntity>.
I thin that the conversation isn't propagated when using these components.
I think it worked when using <s:conversationId /> with <h:commandButtons the problem stopped.
But I am still having problem with ajax calls.
I think this is a bug!!!
Yes. It's related.
I loose almost a day before trying to search for bugs in jboss seam.