I notice that ODI does not do a good job of reverse-engineering JMS queue models where an element name is referenced in different parts of the schema.
In the above, ODI will reverse-engineer the 'event' element under 'load', but not the one under 'unload'.
I don't have control over the xsd models and was therefore wondering if there is some sort of workaround I can perform in this scenario?
Actually, I just found the following Oracle note sums this up: 757642.1 Is it possible to use the SAME ELEMENT as a SUB-ELEMENT in multiple DIFFERENT Elements of an XML File?
If so, what is the impact of this approach on the reverse engineered Model and Datastores and how can Integration Interfaces be set up to map these identical ELEMENT for which the content is semantically different and as a result to be used differently in different Oracle Data Integrator (ODI) Integration Interfaces.
The following XML is a simple example in which the ITEM Element is logically set as a sub-element to three other XML Elements:
Such an approach must be avoided. This is a strict limitation of the ODI XML Driver.
See Bug:8563428 DUPLICATE SUBELEMENTS WITH DIFFERETNT TYPES ARE NOT SUPPORTED BY XML DRIVER