In Part 1 of this article, we showed how to customise the values in the Mileage UoM drop-down list. However, we feel that customisations should only be used as the last resort, when all other options have been exhausted. A change to the View Object’s XML file (as suggested by Oracle) will not be resilient across patches and upgrades.
The Oracle Application Framework (OAF) provides a mechanism for us to provide a substitute definition for a View Object, With this mechanism, any time the Framework asks for the UnitOfMeasuresVO it will actually get our personalised version. The easiest way to create a personalisation of this type is to use the appropriate version of JDeveloper. You cannot use the mainstream version of JDeveloper from OTN – you need to download one that has the correct version of JDeveloper that has the OA Extension built-in (see MOS Note 416708.1 for more details).
