BEX language allows a flexible combination of grammar and semantics by
extending the existing Java grammar and semantics presented in the
org.openl.j configuration using new grammar and semantic concepts. It enables users
to write expressions similar to natural human
language.
BEX does not require any special mapping; the existing Java business
object model automatically becomes the basis for open business
vocabulary used by BEX. For example, Java expression
'policy.effectiveDate' is equivalent with BEX expression
'Effective Date of the
Policy'.
If the Java model correctly reflects business vocabulary, there is no further action required. In case the Java model is not satisfactory, custom type-safe mapping or renaming can be applied.