Bug 760115
Summary: | RichFaces with Spring WebFlow requires additional configuration | ||
---|---|---|---|
Product: | [Retired] JBoss Enterprise WFK Platform 2 | Reporter: | Karel Piwko <kpiwko> |
Component: | RichFaces, Spring | Assignee: | Brian Leathem <bleathem> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Karel Piwko <kpiwko> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.0.0.DR05, 2.0.0.DR06 | CC: | bleathem, irooskov, misty, mnovotny, myarboro |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
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 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.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-08-09 14:02:14 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Karel Piwko
2011-12-05 13:28:05 UTC
Technical note will be required if this is not fixed in spring-faces. External reference https://jira.springsource.org/browse/SWF-1473 Where does that configuration change have to be added? Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: 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> This is in upstream issue, moving to ASSIGNED and unscheduling. Pete Muir <pmuir.uk> made a comment on jira WFK2-145 [~jowilson] [~bleathem] can you check if this is still an issue for us? Joshua Wilson <jowilson> made a comment on jira WFK2-145 [~bleathem] Here is a Spring WebFlow example that uses JSF. Would you be able to modify it to use Richfaces to test this? https://github.com/SpringSource/spring-webflow-samples/tree/master/booking-faces Brian Leathem <bleathem> made a comment on jira WFK2-145 I just did a quick scan through the snowdrop examples, and it appears we have a working RichFaces/Webflow demo: https://github.com/snowdrop/snowdrop-examples/blob/master/sportsclub/spring-3_2/sportsclub-reservations-webflow/pom.xml [~jowilson] can you run the above example with current versions (RichFaces 4.3.3.Final) and see if the problem persists? Joshua Wilson <jowilson> made a comment on jira WFK2-145 I ran Sportsclub with RichFaces 4.3.3 and I didn't see anything wrong. Looks like it works. Brian Leathem <bleathem> made a comment on jira WFK2-145 Indeed, it looks like this has been resolved in Spring Webflow 2.4.0: https://jira.springsource.org/browse/SWF-1473 Joshua Wilson <jowilson> made a comment on jira WFK2-145 [~bleathem] - Good find. Marek Novotny <mnovotny> made a comment on jira WFK2-145 Cool, that we know what could be fixed. [~jowilson] Could you set devel_ack to + ? We need to upgrade Spring WebFlow in WFK Spring BOMs, where it uses 2.3.1.RELEASE and 2.3.2.RELEASE. Marek Schmidt <maschmid> made a comment on jira WFK2-145 Spring webflow 2.4 has not yet been released. |