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

[Pete Muir (JIRA)]

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

Pete Muir commented on JBSEAM-1832:
-----------------------------------

As a first step, I've added support for setting the concurrent request timeout on a page-by-page basis in components.xml

The second step will be to change the default behaviour so that a concurrent request which exceeds the timeout doesn't kick you out of an LRC. There are two options:

1) The request is processed anyway in a temporary conversation, but the LRC is maintained for future requests
2) The request is aborted and an error sent to the client

Please add a comment if you have strong opinion about which one we should use.

The third step will be to make event queues easier to use.

> 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.CR1
>
>         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