I've been assigned to test the Ajax4JSF framework on an OC4J instance, together with Richfaces to use as a component library for a new web application. I've been going through the developer guide and some of the older examples, and quite frankly they've got me puzzled quite a bit.
I've enabled skinning by using the ajax4jsf filter, which basically should alter my existing jsf facelet to the ajax4jsf selected look and feel, yet it doesn't. My web.xml contains the following:
<context-param> <param-name>org.ajax4jsf.SKIN</param-name> <param-value>blueSky</param-value> </context-param> <filter> <display-name>Ajax4jsf Filter</display-name> <filter-name>ajax4jsf</filter-name> <filter-class>org.ajax4jsf.Filter</filter-class> </filter> <filter-mapping> <filter-name>ajax4jsf</filter-name> <servlet-name>Faces Servlet</servlet-name> <dispatcher>FORWARD</dispatcher> <dispatcher>INCLUDE</dispatcher> <dispatcher>REQUEST</dispatcher> </filter-mapping>
According to the developer guide and one of the examples I looked at (JSFColors from the exadel site) this addition should change the look of any of the inputText and outputText fields I might be using. This is actually not happening, everything looks exactly the same as before, no new styling is applied.
When I include richfaces components to the page, they in turn are rendered according to the skin setting used by ajax4jsf, so this must mean that skinning does in fact work. Why are the standard JSF components unaffected by the ajax4jsf filter? I think this is a bug, because building a screen that has some skinned items and some unskinned items just looks a bit strange. Especially the font size differences are quite ugly.
NOTE: I've checked the online demo, if you have a look at the suggestionbox component, you can see that the inputText it is assigned to also lacks the styling you'd expect the component to have. This means the problem is not only occuring on my system.
I am using Facelets, Sun RI 1.1, OC4J 10.1.3.2 standalone, ajax4jsf 1.1.1, richfaces 3.0.1