Back to bug 760115

Who When What Removed Added
Karel Piwko 2011-12-05 13:28:05 UTC Link ID JBoss Issue Tracker RFPL-1430
Karel Piwko 2011-12-05 13:29:06 UTC Priority unspecified medium
Severity unspecified medium
Karel Piwko 2011-12-05 14:53:50 UTC QA Contact kpiwko
Brian Leathem 2011-12-05 19:54:15 UTC CC bleathem
Karel Piwko 2011-12-14 17:48:51 UTC Group private
Version 2.0.0.DR06
Assignee jbalunas bleathem
Rebecca Newton 2012-02-28 06:24:44 UTC CC rnewton
Marek Novotny 2012-05-31 12:19:50 UTC Status NEW MODIFIED
CC mnovotny
Flags needinfo?(kpiwko)
Karel Piwko 2012-05-31 15:45:58 UTC Status MODIFIED VERIFIED
Flags needinfo?(kpiwko)
Karel Piwko 2012-06-22 07:56:05 UTC Status VERIFIED ASSIGNED
Target Release 2.0.0.GA ---
Karel Piwko 2012-06-22 07:56:38 UTC Group private
Marek Novotny 2012-09-25 11:48:40 UTC CC rnewton irooskov
mark yarborough 2012-11-12 14:49:31 UTC Target Release --- 2.2.0
CC myarboro
Misty Stanley-Jones 2012-11-15 03:37:57 UTC CC misty
Doc Text Using Spring WebFlow 2.3 and RichFaces 4 together requires an extra bean to resolve RichFace resources but this bean is not automatically part of faces:resources and gives a 404 error when a CSS file is requested. The workaround for this issue is to change the order of flowMapping to 2 and add the following configuration:
<bean name="richfacesResourceHandler"
class="org.springframework.faces.webflow.JsfResourceRequestHandler" />

<bean
class="org.springframework.web.servlet.handler.SimpleUrlHandlerMapping">
<property name="order" value="1" />
<property name="mappings">
<value>
/rfRes/**=richfacesResourceHandler
</value>
</property>
</bean>
If you need to use Spring WebFlow 2.3 and RichFaces 4 together, you need to create an extra bean to resolve RichFace resources. This bean is not automatically included as part of faces:resources. If it is not present a 404 error occurs when a CSS file is requested. To work around this issue, change the order of flowMapping to 2 and add the following bean to your application:
<bean name="richfacesResourceHandler"
class="org.springframework.faces.webflow.JsfResourceRequestHandler" />

<bean class="org.springframework.web.servlet.handler.SimpleUrlHandlerMapping">
<property name="order" value="1" />
<property name="mappings">
<value>
/rfRes/**=richfacesResourceHandler
</value>
</property>
</bean>

After this configuration change, the request for the CSS file succeeds, and no error occurs.
Misty Stanley-Jones 2012-11-15 04:01:43 UTC Doc Text If you need to use Spring WebFlow 2.3 and RichFaces 4 together, you need to create an extra bean to resolve RichFace resources. This bean is not automatically included as part of faces:resources. If it is not present a 404 error occurs when a CSS file is requested. To work around this issue, change the order of flowMapping to 2 and add the following bean to your application:
<bean name="richfacesResourceHandler"
class="org.springframework.faces.webflow.JsfResourceRequestHandler" />

<bean class="org.springframework.web.servlet.handler.SimpleUrlHandlerMapping">
<property name="order" value="1" />
<property name="mappings">
<value>
/rfRes/**=richfacesResourceHandler
</value>
</property>
</bean>

After this configuration change, the request for the CSS file succeeds, and no error occurs.
If you need to use Spring WebFlow 2.3 and RichFaces 4 together, you need to create an extra bean to resolve RichFace resources. This bean is not automatically included as part of faces:resources. If it is not present a 404 error occurs when a CSS file is requested. To work around this issue, change the order of the flowMapping so that RichFaces has higher priority than the user-generated flow (the lower number gets higher priority) and add the following bean to your application:
<bean name="richfacesResourceHandler"
class="org.springframework.faces.webflow.JsfResourceRequestHandler" />

<bean class="org.springframework.web.servlet.handler.SimpleUrlHandlerMapping">
<property name="order" value="1" />
<property name="mappings">
<value>
/rfRes/**=richfacesResourceHandler
</value>
</property>
</bean>

After this configuration change, the request for the CSS file succeeds, and no error occurs.
mark yarborough 2013-02-28 12:57:49 UTC Target Release 2.2.0 2.3.0
Karel Piwko 2013-04-19 10:06:41 UTC Type --- Bug
mark yarborough 2013-06-04 00:43:37 UTC Target Release 2.3.0 2.4.0
Marek Novotny 2013-08-09 14:02:14 UTC Status ASSIGNED CLOSED
Target Release 2.4.0 ---
Resolution --- INSUFFICIENT_DATA
Doc Type Bug Fix Known Issue
Link ID JBoss Issue Tracker WFK2-145
Last Closed 2013-08-09 10:02:14 UTC
Red Hat Bugzilla 2013-08-09 14:02:14 UTC Doc Type Known Issue Bug Fix

Back to bug 760115