[
https://issues.jboss.org/browse/RF-13018?page=com.atlassian.jira.plugin.s...
]
Rob Hare commented on RF-13018:
-------------------------------
"When you set the type to button, the form should be submitted via javascript, but I
expect there is an error in setting the source (button) of the submission when the type is
button."
The problem also occurs when coming from a a4j:jsFunction, it will also cause all of the
actions on all of the buttons to be called.
I also played with setting all the buttons to type="submit", it has a
problematic side effect in that on a form with inputText fields, pressing return in one of
those fields will normally cause the first submit button on a page to be activated, when
you set all the buttons to submit you will activate the first submit button which may be
the wrong one.
a4j:commandButton wrong actions performed
-----------------------------------------
Key: RF-13018
URL:
https://issues.jboss.org/browse/RF-13018
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-a4j-core
Affects Versions: 4.2.3.Final, 4.3.2
Environment: Server: Fedora 17, Jboss AS 7.1.1.Final, Jboss EAP 6.1.0.Beta, Java
1.7.0_15
Browsers: Chrome 26 and Chrome 27 on (Linux & Windows 7), Firefox 20.0 (Linux &
Windows 7), IE 9
Reporter: Rob Hare
Assignee: Brian Leathem
Fix For: 5.0.0.Alpha2
Attachments: RF-13018.zip
When an a4j commponent (a4j:commandButton, a4j:jsFunction) is activated, actions of other
a4j:commandButtons on the page with type=button will be fired.
For example, pressing either button in the following code will cause both
richBean.function1() and richBean.function2() actions.
{noformat}
<h:form id="testForm">
<a4j:commandButton id="button1" type="button"
value="Button 1"
action="#{richBean.function1}" />
<a4j:commandButton id="button2" type="button"
value="Button 2"
action="#{richBean.function2}" />
</h:form>
{noformat}
Note, if one of the a4j:commandButton is marked immediate, then only one action (possibly
the wrong action) will be performed and block others. For instance if an a4j:jsFunction
action was being triggered, the a4j:commandButton action may occur making appear that the
a4j:jsFunction failed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira