[
https://issues.jboss.org/browse/RF-11292?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-11292:
-------------------------------
Fix Version/s: 4.3.0.Milestone1
(was: 4.3-Tracking)
Targeting MyFaces compatibility with 4.3.0.M1
Metamer: rich:editor: a4j:submit doesn't submit editor's
value (MyFaces)
------------------------------------------------------------------------
Key: RF-11292
URL:
https://issues.jboss.org/browse/RF-11292
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-input
Affects Versions: 4.1.0.Milestone1
Environment: RichFaces 4.1.0.20110805-M1
r.10246d45dddd1d2aa2034317d5a832394cc919f9
Metamer 4.1.0.20110805-M1 r.22604
Apache MyFaces JSF-2.1 Core Impl 2.1.1
Apache Tomcat 7.0.19
Java(TM) SE Runtime Environment 1.6.0_26-b03 @Linux
Chrome 12.0.742.112 @ Linux i686, IE9
Reporter: Ján Jamrich
Labels: myfaces
Fix For: 4.3.0.Milestone1
Editors value is not submitted by a4j:button.
When an value typed into editor, then pressed "a4j: submit", nothing happens.
Then click on "h:submit" and value is submitted. (It is clear from valueChange
listener bound to editor - where after click on "h:submit" following record
appears: "*3 value changed: null -> <p> asdfasdf dfdfd" which
indication that previous value (submited by a4j:button is null)
(Note: I don't consider value not sent by output element value change since it is
a4j:outputPanel, and now we know that it doesn't work reliable with MyFaces)
(RF-11287)
--
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