ILOG JRules User Guide > Creating Rule Projects > Tasks > Setting Up a Rule Project > Defining the Execution Object Model > Defining a Dynamic XOM

You can define a dynamic XOM either in the New Rule Project wizard when you create the project, or later, using the rule project Properties dialog. The procedure is the same in each case.

Note
The use of WSDL files in the XOM is now deprecated. We recommend you use the JAX-WS API instead.

To define a dynamic XOM using the Properties dialog:

  1. In the Rule Explorer view, select the rule project, then on the Project menu click Properties.
  2. In the left pane of the Properties dialog, click Dynamic Execution Object Model.
  3. In the Dynamic Execution Object Model wizard, on the Dynamic Bindings tab, select one of the following:
  4. To add XSDs that have been imported into the Eclipse workspace, click Add XSD, select the required XSD file(s) from the XSD Files dialog then click OK.
    To add XSDs that are held in your file system, click Add External XSD, select the required XSD file(s) from the External XSD Files dialog then click Open.
    To add WSDL files that have been imported into the workspace, click Add WSDL, select the required WSDL file(s) from the WSDL Files dialog then click OK.
    To add WSDL files that are held in your file system, click Add External WSDL, type the internet address of the WSDL file then click OK.
    The following image shows a selection of XSDs, but the behavior is the same for XSDs and WSDL files.
    images/newxsd-wsdl.png
    For each schema namespace, a package name is defined in which the XOM classes will be stored. You can expand each list entry to see the XML namespaces and the package names.
    At the bottom of the Dynamic Bindings tab, there is a hidden section that lists the XSD files that will be included in the ruleset archive. To see this list, click the black arrow to the left of:
    images/schemadeps2.png
    This list of files may be important when you use the hosted transparent decision service.
    The following image shows a list of selected XSDs, with one of them expanded to show how the packages are organized. In this example, the schema types.xsd imports the schema nameType.xsd, which itself imports the schema subNameType.xsd.
    images/schemadeps.png
    All dependencies are automatically selected. You would not normally deselect any of them.
  5. The default package name is derived from the namespace. If you want to rename a package:
    1. Select the package and click Edit.
    2. Type the new package name in the Package Name Configuration dialog, then click OK.
  6. If you want to change the order in which the selected dynamic binding files are listed, click the Order tab and use the up or down arrows to move the required files.
  7. You might want to re-order files if the same element exists in more than one file and you want to dictate which schema or file to use first to identify it.
  8. When you have selected all your dynamic binding files, click OK to close the Dynamic Execution Object Model dialog.
  9. The dynamic XOM is now defined. The new packages appear in the BOM Entry and behave like any normal package.
  10. To remove dynamic binding files from the XOM, select the required file(s), then click Remove.

Related Concepts

Execution Object Model (XOM)
XML Binding
Web Service Binding
Rulesets and Ruleset Archives
Transparent Decision Services

Related Tasks

Defining the Execution Object Model

Related Reference

New Rule Project Wizard
Rule Project Properties Dialog

Related Samples and Tutorials

Tutorial: Defining a Vocabulary