Element substitution not supported by BPEL Transformation tools
(Doc ID 378372.1)
Last updated on APRIL 23, 2019
Applies to:Oracle(R) BPEL Process Manager 10g - Version 10.1.2.2 and later
Information in this document applies to any platform.
On 10.1.2.0.2 in Production:
When attempting to implementing transformation logic in BPEL using BPEL Designer , the following error occurs.
The issue can be reproduced at will with the following steps.
An industry standard XSD for the utility business - Multispeak.xsd, is used in the project. It was developed using abstract objects of type mspObject that are implemented as concrete objects using inheritance via the syntax "<xsd:complexContent> <xsd:extension base="mspObject">". In the BPEL Designer transformation tool, only the highest level mspObject XML tag is displayed; no objects that are an extension of the base object are visible in the GUI transformation mapper. This renders the GUI transformation tool unusable for this schema. The Multispeak schema is used as our canonical format, and it is an extremely long and complex schema which all of the current business processes XML transactions need to be mapped to.
Open BPEL Designer, import Multispeak.xsd. Create a transformation using Multispeak.xsd as the target and an input XML document of a known subtype of the Multispeak schema as the source. In the Design mode of the transformation, expand the Multispeak schema mspObject; you will not be able to map the input XML document to the details of the type you would like but can only map to the mspObject.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document