[
http://jira.jboss.com/jira/browse/JBSEAM-1832?page=comments#action_12374741 ]
Pete Muir commented on JBSEAM-1832:
-----------------------------------
Vincent, I've generated a simple app using seam-gen, but I can't reproduce using
your instructions. Please attach a seam-gen'd add built against head without the lib
directory to this issue, and provide step-by-step instructions to reproduce. If you
modify the seam-gen app at all please say what modifications you make. Also, what browser
are you using?
John Gilbert: you are, as you say seeing a different problem. Please discuss it on the
forum or a different issue (I will look at your thread in a minute)
Tim: this issue has nothing to do with rich:panel
Demetrio Filocamo: Again a different issue, you seem to have selectXXX menus in there and
no s:validate's
Charl Fourie: You aren't using the same version of Seam as Vincent so this is another
problem. You need to discuss this on the forum
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.CR1
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