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

[Keith Naas (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBSEAM-1832?page=comments#action_12400375 ] 
            
Keith Naas commented on JBSEAM-1832:
------------------------------------

As discussed in the Big Lots Case Study, this is probably the biggest issue we have.  We were using Seam 1.2.1.GA.  No matter what combination of A4J and Seam configuration we had, we could not get rid of the issue.  For example, on one screen with an onblur event we tell the users to explicitely hit tab to ensure that the screen is kosher before they hit the Save button.  

We tried using the eventQueue, requestDelay, ignoreDupResponses as well as the Seam conversation timeout and @Synchronized with a timeout.  We got so frustrated with this behavior that we wrote our own event queue widget to alleviate the problem.

> Improvments to handling of Ajax Requests in Seam
> ------------------------------------------------
>
>                 Key: JBSEAM-1832
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1832
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: JSF Integration
>    Affects Versions: 2.0.0.BETA1
>         Environment: Jboss 4.2.0.GA
>            Reporter: Vincent Latombe
>         Assigned To: Pete Muir
>            Priority: Blocker
>             Fix For: 2.1.0.GA
>
>         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: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira