X hits on this document





15 / 20

Chapter 4. The RichFaces Migration Issues 3.1.x

  • -


</h:selectBooleanCheckbox> <h:commandButton id="go" value="Submit"/> </h:form> <h:outputText id="three" value="#{bean.name} #{bean.option}"/> ... Causes

Behavior of the "immediate" attribute is changed according to to JSF 1.2 specification. Workarounds

The solution includes the following steps:

  • replace "immediate" attribute with ajaxSingle="true"

  • add "process" attribute. This attribute points to the components that should be processed

together with the command component.

4.3. Issues with compatibility with third party frameworks

This section covers issues related to compatibility with third party frameworks.

4 . 3 . 1 . T h e " f i l e U p l o a d L i s t e n e r " w i t h M y F a c e s o r J S F - R I 1 . 2 _ 0 4 Description

T h e " f i l e U p l o a d L i s t e n e r " ( " U p l o a d E v e n t " e v e n t ) i s n o t i n v o k e d w h e n M y F a c e s o r J S F - R I 1 . 2 _ 0 4 i used. But file is uploaded successfully. s Links

  • Jira(for MyFaces) [http://jira.jboss.com/jira/browse/RF-2935]

  • RichFaces



module=bb&op=viewtopic&t=132530&postdays=0&postorder=asc&start=0] How to reproduce

M y F a c e s o r J S F - R I 1 . 2 _ 0 4 w i t h d e f a u l t c o n f i g u r a t i o n Causes

In case MyFaces org.apache.myfaces.CHECK_EXTENSIONS_FILTER parameter is set to "true", the parameter checks if the extensions-filter has been properly configured.


Document info
Document views84
Page views84
Page last viewedMon Jan 23 05:07:10 UTC 2017