]
Anton Belevich commented on RF-10728:
-------------------------------------
a4j:ajax behavior is the same as f:ajax behavior. I'll report about this issue in
myfaces jira.
Ajax: different behavior in Mojarra and MyFaces when disabled
-------------------------------------------------------------
Key: RF-10728
URL:
https://issues.jboss.org/browse/RF-10728
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: compatibility, component-a4j-core
Affects Versions: 4.0.0.CR1
Environment: RichFaces 4.0.0-SNAPSHOT r.22114
Metamer 4.0.0-SNAPSHOT r.
Mojarra 2.1.0-FCS +GlassFish Server Open Source Edition 3.1-SNAPSHOT
Apache MyFaces JSF-2.0 Core Impl 2.0.4 + Apache Tomcat 6.0.26
OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux
Chrome 10.0.648.127 @ Linux x86_64
Reporter: Pavol Pitonak
Assignee: Anton Belevich
Fix For: 4.0.0.Final
1. deploy Metamer and open
http://localhost:8080/metamer/faces/components/a4jAjax/hCommandLink.xhtml
2. set disabled=true
When enabled, an Ajax request is fired which is OK, but for disabled, it behaves
differently in MyFaces and Mojarra
MyFaces: no request
Mojarra: http request
--
This message is automatically generated by JIRA.
For more information on JIRA, see: