So you need one instance of a component in your ADF application to have a different color. Your first instinct would be to just go to the style area in the property inspector and change it. Well, you might want to rethink this, a better way would be to define your style in a central location for easier future maintenance, and an even better way might be to use an ADF Skin for this. This way you have one location for your global skinning and specific styles.
Here is a demo of how to go about doing this.
Also in this demo a quick explanation of the difference between InlineStyle, ContentStyle and StyleClass.
The ODTUG Kscop11 conference was a great success with lots of sessions about FMW running in a special track. I did several sessions and labs in the conference, and I thought it might be a good idea to at least give you a taste of what you might have missed.
So here is most of what I demoed in my ADF Faces Skinning session (not all though - that session was 60 minutes long, and while everyone did end up going out of the building in the middle because of a fire drill for about 5 minutes, there was other things covered in the session as well).
In the demo here you'll see how to generate new images and default color scheme, how to identify a component class with Firebug, how to skin a component, how to identify the global selector of a property, how to change fonts and how to change strings.
By the way, for more on ADF Skinning you should also listen to the ADF Insider seminar that Frank Nimphius recorded on skinning, it will give you better understanding of the overall skinning process.
P.S. in the demo I add an entry to the web.xml file which prevent ADF Faces from compressing the HTML that is generated.
The entry is for org.apache.myfaces.trinidad.DISABLE_CONTENT_COMPRESSION
and I set it to true. This is very useful when you work on creating the skin, but don't forget to un-set it before you go production.