X hits on this document

73 views

0 shares

0 downloads

0 comments

8 / 20

Chapter 4. The RichFaces Migration Issues 3.1.x

  • -

    3.2.0

  • RichFaces

Forum

[http://www.jboss.com/index.html?

module=bb&op=viewtopic&p=4140368#4140368]

4.1.3.3. How to reproduce

The described above problem occurs if binding attribute is used with RichFaces components.

4.1.3.4. Causes

There was a wrong <classname>java.lang.String</classname> specified instead of <classname>javax.faces.component.UIComponent</classname> in configuration files.

4.1.3.5. Workarounds

The solution is to use Facelets upgrade to RichFaces 3.2.0 SP1 [ http://www.jboss.org/ jbossrichfaces/downloads/]

      • 4.1.4.

        Ajax requests in JSF 1.2

        • 4.1.4.1.

          Description

Ajax requests stop to work without any errors messages displayed, when intensive Ajax traffic is

expected. No errors or other messages to detect cause of the defect are shown.

4.1.4.2. How to reproduce

The described above problem occurs if an id for Ajax command component is not defined.

... <h:form> <h:panelGrid columns="2"> <h:inputText id="myinput" value="#{userBean.name}"> <a4j:support event="onkeyup" reRender="outtext" /> </h:inputText> <h:outputText id="outtext" value="#{userBean.name}" /> </h:panelGrid> </h:form> ...

4.1.4.3. Causes

The problem occurred due to specific usage of the dynamic id generation implementing JSF 1.2. In case of simultaneous request processing, the id of the command component becomes out-of- sync with id of the same component on the page. After that any Ajax requests of the component with old id is not processed.

9

Document info
Document views73
Page views73
Page last viewedWed Jan 18 18:36:06 UTC 2017
Pages20
Paragraphs460
Words3352

Comments