Too often, developers motivate a fallback to well-understood programmatic solutions when faced with a challenge where the wizards of Oracle Fusion Middleware are too simplistic. A good example is the mapping of complex business objects, for example, a contract that contains a customer and several products. Very often, the better alternative to Java or other programming languages is the usage of a business rule engine.
The solution matrix for data access virtualization suggests the usage of a rule engine in the following scenarios:
Create SQL query: Complex query aggregating data from several tables
Data format mappings: Complex data mappings (compound entity) instead of XSLT/XQuery
Validate/sanitize data: Complex validation rules instead of XML schema checks and Schematron
Entitlement: Define roles and rights – configure rights per role in relation to data entities and their attributes
We see that the business rule engine...