Didier's Blog

I got several issues this week that had the same root cause though the symptoms were completely different.

The problem is related to the page encoding of the ADF Faces JSPX.
ADF Faces supports 'utf-8' only.
However, by default, the editor creates the pages with the 'windows-1252' encoding:

This leads to problems like:

• accented characters transformed to code representation during the Submit - see the discussion "Character encoding problem in ADF 11 app" in the OTN Forum
• Error: "The value is not a number" when using groupingUsed="true" with specific locale (French f.ex.)
• ...

To avoid these issues, you can edit your pages and change 'windows-1252' by 'utf-8'.
For the new pages, you can change the default to 'utf-8':

1. select menu "Tools" -> "Preferences..."
2. click "Environment"
3. select "UTF-8" in the "Encoding" list.

The new pages will be created correctly now.
Note that as from JDeveloper 11.1.1.2.0 onwards, JDeveloper will use the encoding 'utf-8' (whatever the default encoding is) when ADF Faces technology is used.

There are numerous ADF libraries and it may cause you problems to resolve a ClassNotFound exception.
To help you in finding the missing library, there is a small search utility in the "Add Library" and the "Manage Libraries" dialogs as shown in the next figure:

You can reduce the number of libraries shown, or search for a library by entering a string. You can enter

• the exact class name,
• a fully qualified name,
• a partial class or package name, using * as a wildcard anywhere in the string