X hits on this document

51 views

0 shares

0 downloads

0 comments

9 / 20

Chapter 4. The RichFaces Migration Issues 3.1.x

  • -

    3.2.0

        • 4.1.4.4.

          Workarounds

You should define the id for the command component and parent namespace components (<h:form>, <f:subview>, <h:dataTable> and so on) explicitly. As soon as this is a core JSF 1.2 functionality, the problem cannot be solved on the RichFaces level.

      • 4.1.5.

        Resources for standard skinning classes

        • 4.1.5.1.

          Description

When standard skinning classes or background images are inaccessible "Resource not registered : org.richfaces.renderkit.html.images.InputBackgroundImage" (another name is possible) exception appears in server log.

4.1.5.2. Links

  • Jira [http://jira.jboss.com/jira/browse/RF-2944 ]

  • RichFaces

Forum

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

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

4.1.5.3. How to reproduce

The described above problem usually occurs after server restart when user refreshes the page

4.1.5.4. Causes

The problem is caused when resources for standard skinning classes are not available to be registered during RichFaces library build

4.1.5.5. Workarounds

Switch off standard skinning classes by setting initial parameter in web.xml:

... <context-param>

< p a r a m - n a m e > o r g . r i c h f a c e s . C O N T R O L _ S K I N N I N G _ C L A S S E S < / p a r a m - n a m <param-value>disable</param-value> </context-param> ... e >

Add META-INF/resources-config.xml [http://docs.google.com/View?docid=dqk93fg_3ggsznfz5] to the application classpath.

10

Document info
Document views51
Page views51
Page last viewedFri Oct 28 12:18:08 UTC 2016
Pages20
Paragraphs460
Words3352

Comments