Hi, thank you guys for your posts! Actually section "6.9. Concurrent calls to conversational components" in the reference documentation really covers the topic in an excellent way.
But I think I don't fully understand, why this behavior can still occur if there is the same eventQueue set on all ajax request generating input fields on the page? Shouldn't then only one ajax request be sent at the time, hence no concurrent calls on the conversational component and no need for Seam to serialize them. Also I wonder if there is a way to simply ignore (not even showing) the "Conversation ended" message. If I'm getting it right, the worst that could happen is, that a validationMessage (coming from one of the many ajax request) is not properly displayed, but not this "Conversation ended" behavior. Am I miss something here and simply ignoring is not a good idea anyway? Cheers, Kurt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110219#4110219 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110219 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
