By Juergenkress-Oracle on Apr 17, 2016
scripting is improved in ADF 12.2.1. There are no inline Groovy
expressions anymore. Expressions are saved in separate Groovy language
file, external codesource. Each EO/VO will be assigned with separate
file to keep Groovy expressions. This improves Groovy script maintenance
(easier to check all Groovy expressions from EO/VO located in one
file), also it improves runtime performance (as JDeveloper ADF code
audit rule suggests).
Inline Groovy expressions created with previous JDeveloper versions are compatible in 12.2.1. All new expressions are created in separate *.bcs file. Sample application - ADFGroovyApp.zip, comes with validation rule implement in Groovy script expression:
should check how validation rule definition looks in EO source. There
is one inline Groovy expression I have created with previous JDeveloper
version. It is marked as deprecated and suggested to be moved to
external codebase: Read the complete article here.
For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.