CSS links generated by RichFaces

[frosted]

Hi,

I am building an application that has to sit behind a reverse proxy (WebSEAL) which does URL translations based on certain types (CSS, images, etc.) to transform the urls generated by the application server to prepend a junction name to them. The CSS links generated by RichFaces do NOT end with .css which is causing the URLs not to be translated (and therefore the pages do not look as they should).

Is there any way to change this behavior or do I have to manually create *valid* css file names from the generated ones and include them manually? Of course, I'd like to not have to hack my way through this, so if there is a clean solution to this, please let me know.

Any help is appreciated.

Thank you.

[dmdm]

Hey chuck ...did you get any luck on this ?

[nbelaevski]

Hi Chuck,

You can do two things to solve the problem:

1. Configure prefix mapping, not suffix for JSF servlet (that's to avoid *.jsf).

2. Register your own instance of ResourceBuilder class via SPI file and form URIs you need there.

[dmdm]

Hi Nick ...could you please elaborate or point us to some notes about setting that up...thanks n regards

[nbelaevski]

There are some notes about ResourceBuilder in this document: http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html/RichFaces/RichFacesArchitectureOverview.html

Sources of RichFaces can be explored for existing builders, e.g. this class: http://docs.jboss.org/richfaces/3.3.3.CR1/en/apidoc_impl/org/ajax4jsf/resource/cached/CachedResourceBuilder.html; you can extend/wrap existing builder to generate URLs you need.

[dmdm]

Hi Nick,

As per the note we will need to register the resource builder under metainf/services ...does that mean I shall have to build the richfaces source ? If yes, is it possible to extend that behaviour externally  in our application (ie without requiring to build the richfaces source) ?

Thanks and Regards

Deepesh

[nbelaevski]

Deepesh,

No, this doesn't require RichFaces rebuild. Place the file in your app classpath.