IRL and Extender Mapping

ILOG JRules User Guide > Creating Rule Projects > Concepts > BOM and XOM > The BOM to XOM Mapping Mechanism > IRL and Extender Mapping

IRL and Extender Mapping

Using this mapping mechanism, rule artifacts based on the BOM can be translated into rule artifacts based on the XOM at runtime.

The BOM to XOM mapping mechanism provides a default mapping and supports two kinds of explicit mapping:

IRL mapping: With IRL mapping, you associate an IRL function based on the XOM to a business element. With IRL mapping you can call functions, ruleset parameters and variables, and rule instances from the IRL code.
Extender mapping: With extender mapping, in a Java extender class, you create static elements that have exactly the same name as business class members.

You can only use extender mapping on a Java XOM. If you have a dynamic XOM, use IRL mapping.

BOM to XOM Lookup Strategy

At runtime, the rule engine uses the following order to find the right mapping:

Explicit mapping in IRL.
Explicit mapping with extender class.
Implicit mapping done by default when nothing is specified.

If the rule engine does not find any mapping by default, an error is raised.

The BOM to XOM mapping is defined in a BOM to XOM mapping XML schema.

Related Concepts

Execution Object Model (XOM)

Business Object Model (BOM)

Related Tasks

Defining How Business Elements Map to the XOM

Troubleshooting Execution

Related Reference

Related Samples and Tutorials

Tutorial: Defining a Vocabulary

How to Write Rules Independently of the Execution Model

Copyright © 1987-2008 ILOG S.A. All rights reserved. Legal terms. Documentation homepage.