-
1. Re: RichFaces Skinning Problem
nbelaevski May 28, 2009 4:52 AM (in response to gleenders)Hi Gert,
Please provide some more details: what skinning is not working - built-in (for standard components) or skin switching? Are there are any errors loading resources in Firebug? What application server is used? -
2. Re: RichFaces Skinning Problem
gleenders May 28, 2009 5:06 AM (in response to gleenders)nbelaevski,
It just doesn't load the css files. When i try for example to go to the basic_both.xcss url it gives me a 404.
In the separate RF project it just opens the specified xcss.
If a manually include a css file then the layout is expected.
For the rest no javascript errors.
The app server is a WLS 10.3
Regards,
Gert -
3. Re: RichFaces Skinning Problem
ilya_shaikovsky May 28, 2009 5:11 AM (in response to gleenders)show web.xml please.
-
4. Re: RichFaces Skinning Problem
gleenders May 28, 2009 5:47 AM (in response to gleenders)Thanks for the effort guys!
web.xml
<?xml version = '1.0' encoding = 'windows-1252'?>
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
version="2.5" xmlns="http://java.sun.com/xml/ns/javaee">
Richfaces Test
<context-param>
<param-name>javax.faces.STATE_SAVING_METHOD</param-name>
<param-value>server</param-value>
</context-param>
<!-- Plugging the "Blue Sky" skin into the project -->
<context-param>
<param-name>org.richfaces.SKIN</param-name>
<param-value>blueSky</param-value>
</context-param>
<!-- Making the RichFaces skin spread to standard HTML controls -->
<context-param>
<param-name>org.richfaces.CONTROL_SKINNING</param-name>
<param-value>enable</param-value>
</context-param>
<!-- Defining and mapping the RichFaces filter -->
<filter-name>JpsFilter</filter-name>
<filter-class>oracle.security.jps.ee.http.JpsFilter</filter-class>
<display-name>RichFaces Filter</display-name>
<filter-name>richfaces</filter-name>
<filter-class>org.ajax4jsf.Filter</filter-class>
<filter-mapping>
<filter-name>JpsFilter</filter-name>
<servlet-name>Faces Servlet</servlet-name>
FORWARD
REQUEST
INCLUDE
</filter-mapping>
<filter-mapping>
<filter-name>richfaces</filter-name>
<servlet-name>Faces Servlet</servlet-name>
REQUEST
FORWARD
INCLUDE
</filter-mapping>
<listener-class>com.sun.faces.config.ConfigureListener</listener-class>
<servlet-name>Faces Servlet</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup>1</load-on-startup>
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>/faces/*</url-pattern>
</servlet-mapping>
<session-config>
<session-timeout>35</session-timeout>
</session-config>
<mime-mapping>
html
<mime-type>text/html</mime-type>
</mime-mapping>
<mime-mapping>
txt
<mime-type>text/plain</mime-type>
</mime-mapping>
</web-app>
but because they are both the same in the separate and the ADF project i suppose the Oracle ADF faces mess things up. I just don't know how that happens....
I can send you both my test projects but than you'll have to download Jdeveloper.... :-) -
5. Re: RichFaces Skinning Problem
ilya_shaikovsky May 28, 2009 5:54 AM (in response to gleenders)please try to change the filters sequence in your web.xml to make RichFaces filter and mapping going first.
does ADF requires viewHandler to be defined? If so please define it using our context param in web.xml instead of entity in faces-config.