Limitations
Some restrictions currently apply to Java™ XOM management.
- URI format
- The ruleset.managedxom.uris ruleset property
supports only URIs that follow the
resuriorreslibprotocol. - No JMX API
- No Java Management Extensions (JMX) API is available for you to manage the XOM. JMX API for RuleApp and ruleset management in Rule Execution Server is not supported.
- No notification of version conflicts
- If you add a reference to a list of resources and that list already contains the same resource in another version, no message warns you.
- No minor version increment from Rule Designer
- When you deploy a resource from Rule Designer, you cannot increment its minor version instead of its major version. To increment the minor version, use the res-xom-deploy Ant task.
- No support of file persistence or database persistence
- The current integration of Java XOM management in Rule Designer supports deployment only to a Rule Execution Server server instance for which the Rule Execution Server console is deployed. Configurations where the persistence type is set to file or database are filtered out or raise an error message, depending on the wizard. The deployment configuration and the Deploy XOM wizard filter out the nonsupported Rule Execution Server. The RuleApp deployment wizard shows the nonsupported configurations but displays an error message.
- No RuleApp download from Decision Center
- You cannot download a RuleApp version in Decision Center by using the ruleset.managedxom.uris property because the URI values depend on the target Rule Execution Server instance.
- Class loader
- You cannot reverse the behavior of the class loader as described in Managed Java XOM setup and lifecycle.
- You cannot retrieve the managed-XOM class loader from rule sessions: Whether POJO or Java SE, rule sessions cannot access the class loader to build input and output objects for execution. The managed Java XOM is made available to the engine for ruleset parsing but not to the code that calls the ruleset. Therefore, if the ruleset parameters are of XOM custom types, you must make those XOM classes accessible to the rule session. Typically, package them into the deployed application.