on 08-25-2014 1:04 PM
Hi experts,
I have created a scenario with a message type with the two elements "at-baustein,ref" and "parameters". These two elements are desigend als followed:
So within one message there is the possibility to have multiple entries for "at-baustein.ref" and "parameters". But these two entries need to be put within the same order in the response datatype, as they are dependent on each other.
During the mapping I have mapped the fields almost one by one. But within the message mapping the order isn't hold. Currently the message gets mapped as followed:
As you can see with the blue and red arrow the order isn't correct. Is there an chance to keep the correct order during the mapping. Unfortunately it's not an option to wrap this two entry by another element.
regards
Christian
Hi Christian,
should be not problem with an xslt:
<xsl:for-each select="//at-artikel/*">
<xsl:value-of select="."/>
should list all children of at-artikel.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Udo,
thanks for this hint. Can you help me out a little bit more with the xsl-stylesheet as I'm new to xslt-mappingß
I have created the following xslt-stylesheet based on my external defintion (my message type):
But when I try the transformation in the operation mapping I neither getting an error nor a created output data type.
Any clue why this happens?
regards
Christian
Hi Christian,
the root element ED..OB should be created in any case, there is no X-Path condition. So - if you dont get any test result - the reason fort that is not the stylesheet but something else. May be wrong extension (should be xsl), may be the operatioin mapping is not updated (close and reopen), may be wrong linked stylesheet or what ever.
/Udo
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.