[richfaces-issues] [JBoss JIRA] Updated: (RF-11292) Metamer: rich:editor: a4j:submit doesn't submit editor's value (MyFaces)
Jay Balunas (JIRA)
jira-events at lists.jboss.org
Thu Aug 11 17:33:01 EDT 2011
[ https://issues.jboss.org/browse/RF-11292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jay Balunas updated RF-11292:
-----------------------------
Fix Version/s: 4.1.0.Tracking
Component/s: component-input
We'll need to see if this is myfaces specific, and the what is happening that the value is not being submitted.
> 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
> Fix For: 4.1.0.Tracking
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the richfaces-issues
mailing list