[
https://issues.jboss.org/browse/RF-11331?page=com.atlassian.jira.plugin.s...
]
Brian Leathem commented on RF-11331:
------------------------------------
a4j:commandButton does an ajax request by default, and the h:commandButton does a full
page submit. An accurate comparison of the buttons is as follows:
{code}
a4j: <a4j:commandButton value="Show message"
actionListener="#{richBean.showMessage}"/>
h: <h:commandButton value="Show message"
actionListener="#{richBean.showMessage}">
<f:ajax execute="@this" render="@from" />
</h:commandButton>
{code}
In which case they behave the same: not rendering the message.
FacesMessages not shown when using a4j:commandButton and myFaces
----------------------------------------------------------------
Key: RF-11331
URL:
https://issues.jboss.org/browse/RF-11331
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-a4j-core, component-validators
Affects Versions: 4.0.0.Final, 4.1.0.Milestone1
Environment: Tomcat 6.0.32, myFaces 2.0.6/2.0.7/2.1.1, Richfaces 4.0 and 4.1.0
M1
Reporter: Jordi Cano
Assignee: Brian Leathem
Labels: FacesMessage, commandButton, myFaces
Fix For: 4.3.0.Milestone1
FacesMessages are not displayed when they are thrown from a a4j:commnandButton action and
myFaces 2.0.6/2.0.7/2.1.1 is used, they appear on server console instead.
Works fine when myFaces 2.0.5 is used or h:commandButton is used instead of
a4j:commandButton (any myFaces version).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira