Hi

I use some components from the tomahawk collection and have 
written my own components as well. 

Now I am in the process of packaging my own components into 
jar-files and have run into a nasty feature of the JSF
configuration. 
It is nice that each component-jar-file can have its own 
faces-config.xml and in that way add its components to 
the overall JSF runtime configuration. It is also easy
to replace a single renderer for a componen, just add
the renderer to the jar-file and "overwrite" the 
renderer-configuration in your own jar-faces-config. This
works great for renderers delivered by JSF itself. BUT as 
soon as I want to override a renderer from the tomahawk
components I run into troubles.

The config mechanism first inserts the standard config,
then adds the jar-faces-config and at the end adds the
configured (in web.xml) config-files. Unfortunately
there seems no way to specify the order in which the 
jar-faces-configs are added. Therefor its getting 
difficult to override single definitions (as described 
above) when having more than one jar with custom components.

How do you deal with that problem?
Alexander

Reply via email to