An application developer has changed the Java XOM. The developer then tries to update the BOM but no differences appear. What are two reasons this could happen? (Select two.)

The Business Object Model (BOM) Update wizard in IBM ODM is designed to synchronize the business-relevant, public-facing API of the Java Execution Object Model (XOM) with the BOM used for rule authoring. The wizard detects changes in class structures, method signatures, and attributes. Changes confined to the internal implementation of a method (the code within its body) do not alter its public signature. Therefore, the wizard does not register this as a difference. Similarly, the @NotBusiness annotation is a specific directive to the ODM tooling to exclude a Java member from the BOM. If a developer adds a new member to the XOM and includes this annotation, the BOM update process will filter it out, resulting in no difference being shown to the user.

A. Deleting a member is a significant change to the X-O-M's public API, which the BOM update wizard would detect and propose for synchronization.
B. The @Deprecated annotation is a recognized change. The wizard would identify it and suggest marking the corresponding BOM member as deprecated.
E. Adding a parameter, even an optional one, alters a method's signature. The wizard would detect this new method overload and propose adding it to the BOM.

1. IBM Operational Decision Manager 8.10 Documentation, Annotations for business rules:

Reference for option D: The documentation for the @NotBusiness annotation states, "Use this annotation to specify that a class or a member of a class is not for business use. When you generate a BOM from a XOM, classes and members with this annotation are not imported." This confirms that adding a new member with this annotation would cause it to be ignored by the update process, showing no difference. (IBM Documentation > IBM Operational Decision Manager 8.10 > Reference > Annotations for business rules > NotBusiness).

2. IBM Operational Decision Manager 8.10 Documentation, BOM to XOM mapping:

Reference for option C: The documentation explains that the mapping is between the business elements (BOM) and their implementation (XOM). The mapping focuses on the signatures (methods, attributes, constructors) that are exposed for rule authoring. It does not concern itself with the internal logic within a method's body. A change in implementation logic without a change in the signature is transparent to the BOM. (IBM Documentation > IBM Operational Decision Manager 8.10 > Designing > Working with the BOM > BOM to XOM mapping).