Troubleshooting a Custom Look and Feel

Sometimes an invalid look and feel configuration or UIX configuration file will cause problems with registering a custom look and feel in ADF UIX. When a custom look and feel is not properly registered, UIX will not be able to render your UIX pages in the custom look and feel you have specified, but instead it uses another look and feel such as BLAF to render your pages.

When your UIX pages do not appear to be rendering in the custom look and feel you have provided, use these steps to determine why the custom look and feel is not being used:

Make sure the look and feel configuration file is valid. To do this, in the Application Navigator, right-click the look and feel configuration file and choose Validate XML . This should report any validation errors that might prevent your look and feel from being registered in UIX.
Make sure the UIX configuration file uix-config.xml is valid. To do this, in the Application Navigator, right-click the uix-config.xml file and choose Validate XML . Again, any validation errors that would prevent your look and feel from being registered will be reported.
If the look and feel configuration file and the uix-config.xml file are both valid, make sure you have registered your custom look and feel. You should have an <look-and-feel-config> entry in your uix-config.xml file for each custom look and feel.
Make sure you have specified the preferred look and feel. The preferred look and feel is specified using the <look-and-feel> element in the uix-config.xml file.
If you still have problems, turn on design time message logging to check for other errors that might be preventing your look and feel from being used by UIX. To do this, choose Tools | Preferences and select the UIX Visual Editor item. Then enable the Show Design Time Messages In Log option.