[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1832) Improvments to handling of Ajax Requests in Seam

[asookazian (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBSEAM-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12425888#action_12425888 ] 

asookazian commented on JBSEAM-1832:
------------------------------------

We've been experiencing this problem as well on Seam 1.2.1.GA and now Seam 2.0.1.GA.  It's easily the most frustrating problem in the current JBoss dev stack that I've experienced thus far.

What's the status on this fix?  After reading Seam in Action, it sounds like ICEfaces does not have this problem:

"Contention for the conversation isn't seen when using ICEFaces since the ICEfaces framework automatically synchronizes requests from the same page to ensure that the server-side DOM remains uncorrupted."

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=140796

I'm not sure there is going to be a real fix to this problem so that the Seam dev's won't have to use attributes (patching) like eventQueue, requestDelay in a4j/rich components and concurrent-request-timeout config in components.xml.

It's difficult to reproduce these a4j/rich concurrency-related errors and thus difficult to trouble-shoot and fix.  In addition, the error text itself is not very helpful to the end-user or developer:

"The conversation ended, timed out or was processing another request ." which apparently is being addressed in https://jira.jboss.org/jira/browse/JBSEAM-2610



> Improvments to handling of Ajax Requests in Seam
> ------------------------------------------------
>
>                 Key: JBSEAM-1832
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-1832
>             Project: Seam
>          Issue Type: Bug
>          Components: JSF Integration
>    Affects Versions: 2.0.0.BETA1
>         Environment: Jboss 4.2.0.GA
>            Reporter: Vincent Latombe
>            Assignee: Pete Muir
>            Priority: Blocker
>             Fix For: 2.1.0.BETA2
>
>         Attachments: ConcurrentCalls.diff, hello.zip
>
>
> I've seen the problem from BETA1 to HEAD
> To reproduce the bug, try the following :
> Create some seam-gen based project and generate-entities.
> Go to an edit page, fill some data, and click on the submit button, without clicking elsewhere (the focus must be on an edited field just before submit). Instead of validation error, or adding the new data, you should get the "The conversation ended, timed out or was processing another request" message. It seems that the validation triggered by the onblur event messes up with the validation.
> I have also seen the bug occuring while I was switching from one field to another quite fast (fast enough to have many validation on queue in ajax4jsf). It seems that adding <s:conversationId/> to the a:support solves this part.
> Here is the snippet I currently use
> <a:support event="onblur" bypassUpdates="true" reRender="cityCodeDecoration">
>   <s:conversationId/>
> </a:support>
> I tried to upgrade ajax4jsf + richfaces 3.0.1 to richfaces 3.1.0 rc2, but it didn't change anything.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira