[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1832) Use of <a:support> tag breaks conversation in Seam-gen (and elsewhere)

Charl Fourie (JIRA) jira-events at lists.jboss.org
Wed Sep 12 05:43:11 EDT 2007

    [ http://jira.jboss.com/jira/browse/JBSEAM-1832?page=comments#action_12376342 ] 
Charl Fourie commented on JBSEAM-1832:

I know that (as stated above) I am using an older version of Seam, but the work-around that worked for me will also be applicable to Seam2 and can therefore be helpfull.  The following work-around fixed my problems:

In components.xml, set the concurrent-request-timeout to something high like 10000 (10 seconds)

	<core:manager concurrent-request-timeout="10000"
		conversation-timeout="120000" conversation-id-parameter="cid"
		conversation-is-long-running-parameter="clr" />

I also found that any lists used to populate list boxes should be cashed in the page context to prevent SQL queries from executing every time a list box looses focus (should be done anyway)

Hope this helps.

> Use of <a:support> tag breaks conversation in Seam-gen (and elsewhere)
> ----------------------------------------------------------------------
>                 Key: JBSEAM-1832
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1832
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: JSF
>    Affects Versions: 2.0.0.BETA1
>         Environment: Jboss 4.2.0.GA
>            Reporter: Vincent Latombe
>         Assigned To: Pete Muir
>             Fix For: 2.0.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


More information about the seam-issues mailing list