on 03-09-2017 1:11 PM
Hello experts,
I have a source XSD which looks like this:
<xs:element name="CreateAUserRequestMessage">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" ref="tns:TaskContext"/>
<xs:element minOccurs="0" ref="tns:CreateAUser"/>
</xs:sequence>
</xs:complexType>
</xs:element>
...
<message name="CreateAUserRequestMessage">
<part element="tns:CreateAUserRequestMessage" name="CreateAUserRequestMessagePart"/>
</message>
And a target XSD which looks like this:
<message name="CreateAUserRequestMessage">
<part element="tns:TaskContext" name="TaskContextPart"/>
<part element="tns:CreateAUser" name="CreateAUserPart"/>
</message>
TaskContext & CreateAUser are structures which are identical in the source and target XSDs
How do I convert the source to the target with XSLT mapping?
Regards.
Hello Stefan,
Thanks for your response.
The target XSD is from an external system.
Unfortunately, PI is unable to parse it in ESR (also it is not possible to generate proxy client in ECC from it) so I had to change it as described by the source XSD.
I opened an OSS message about this and got a response that it is a limitation in ESR which cannot parse a multipart message .
They suggested using XSLT mapping to construct the target message. This is the reason I requested assistance from the SDN experts.
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is nothing to do, as you have two different variants of describing the same structure.
Read here:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
9 | |
9 | |
6 | |
6 | |
6 | |
5 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.