Hi Kandula,

You can get the prefix from the name of the parent element (iob:varyOn).  Try the following

<?xml version="1.0" encoding="UTF-8"?><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"  version="1.0">   <xsl:template match="soapenv:Body/*">     <xsl:copy>       <xsl:apply-templates select="@* | node()" />       <xsl:variable name="prefix" select="substring-before(name(), ':')" />       <xsl:element name="{concat($prefix, ':', 'replyStatus')}" namespace="{namespace-uri(.)}">ERR</xsl:element>       <xsl:element name="{concat($prefix, ':', 'faultCode')}" namespace="{namespace-uri(.)}">ESB0017</xsl:element>       <xsl:element name="{concat($prefix, ':', 'faultString')}" namespace="{namespace-uri(.)}">Invalid message format</xsl:element>     </xsl:copy>   </xsl:template>    <!-- all other elements, simply copy them -->    <xsl:template match="*">        <xsl:copy>            <xsl:apply-templates select="@* | node()" />        </xsl:copy>    </xsl:template></xsl:stylesheet>

Hi Kandula,

You can get the prefix from the name of the parent element (iob:varyOn).  Try the following

<?xml version="1.0" encoding="UTF-8"?><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"  version="1.0">   <xsl:template match="soapenv:Body/*">     <xsl:copy>       <xsl:apply-templates select="@* | node()" />       <xsl:variable name="prefix" select="substring-before(name(), ':')" />       <xsl:element name="{concat($prefix, ':', 'replyStatus')}" namespace="{namespace-uri(.)}">ERR</xsl:element>       <xsl:element name="{concat($prefix, ':', 'faultCode')}" namespace="{namespace-uri(.)}">ESB0017</xsl:element>       <xsl:element name="{concat($prefix, ':', 'faultString')}" namespace="{namespace-uri(.)}">Invalid message format</xsl:element>     </xsl:copy>   </xsl:template>    <!-- all other elements, simply copy them -->    <xsl:template match="*">        <xsl:copy>            <xsl:apply-templates select="@* | node()" />        </xsl:copy>    </xsl:template></xsl:stylesheet>

Hi Kandula,

I received your private message with additional questions, but that does not allow me to respond directly to you as that email's reply address is a do not reply address of this community forum.  Please clarify your question here so I can respond.  The request as shown above appears to be a web service request to a iob:varyOn web service.  The example I provided added the additional information you wanted added to that web service request.  Your subsequent question shows an SOAP message with the root body element <iob:Reply> which I'd assume would be your web service's response to the iob:varyOn request you sent??  Are you wanting to manipulate it as well?  Or is the transformation on the request something that the web service didn't like? Since you only provided an expected response and not an actual response for comparison it is difficult to determine what your requirement is.  I'd also refer you to documentation on xslt identity transformations which the example I provided implements a variation for your specific requirement.  There are plenty of sites you can find in an internet search for "xslt identity transformation".

Best Regards,
Steve

Hi Kandula,

You can get the prefix from the name of the parent element (iob:varyOn).  Try the following

<?xml version="1.0" encoding="UTF-8"?><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"  version="1.0">   <xsl:template match="soapenv:Body/*">     <xsl:copy>       <xsl:apply-templates select="@* | node()" />       <xsl:variable name="prefix" select="substring-before(name(), ':')" />       <xsl:element name="{concat($prefix, ':', 'replyStatus')}" namespace="{namespace-uri(.)}">ERR</xsl:element>       <xsl:element name="{concat($prefix, ':', 'faultCode')}" namespace="{namespace-uri(.)}">ESB0017</xsl:element>       <xsl:element name="{concat($prefix, ':', 'faultString')}" namespace="{namespace-uri(.)}">Invalid message format</xsl:element>     </xsl:copy>   </xsl:template>    <!-- all other elements, simply copy them -->    <xsl:template match="*">        <xsl:copy>            <xsl:apply-templates select="@* | node()" />        </xsl:copy>    </xsl:template></xsl:stylesheet>

Hi Kandula,

I received your private message with additional questions, but that does not allow me to respond directly to you as that email's reply address is a do not reply address of this community forum.  Please clarify your question here so I can respond.  The request as shown above appears to be a web service request to a iob:varyOn web service.  The example I provided added the additional information you wanted added to that web service request.  Your subsequent question shows an SOAP message with the root body element <iob:Reply> which I'd assume would be your web service's response to the iob:varyOn request you sent??  Are you wanting to manipulate it as well?  Or is the transformation on the request something that the web service didn't like? Since you only provided an expected response and not an actual response for comparison it is difficult to determine what your requirement is.  I'd also refer you to documentation on xslt identity transformations which the example I provided implements a variation for your specific requirement.  There are plenty of sites you can find in an internet search for "xslt identity transformation".

Best Regards,
Steve

Hi Kandula,

You can get the prefix from the name of the parent element (iob:varyOn).  Try the following

<?xml version="1.0" encoding="UTF-8"?><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"  version="1.0">   <xsl:template match="soapenv:Body/*">     <xsl:copy>       <xsl:apply-templates select="@* | node()" />       <xsl:variable name="prefix" select="substring-before(name(), ':')" />       <xsl:element name="{concat($prefix, ':', 'replyStatus')}" namespace="{namespace-uri(.)}">ERR</xsl:element>       <xsl:element name="{concat($prefix, ':', 'faultCode')}" namespace="{namespace-uri(.)}">ESB0017</xsl:element>       <xsl:element name="{concat($prefix, ':', 'faultString')}" namespace="{namespace-uri(.)}">Invalid message format</xsl:element>     </xsl:copy>   </xsl:template>    <!-- all other elements, simply copy them -->    <xsl:template match="*">        <xsl:copy>            <xsl:apply-templates select="@* | node()" />        </xsl:copy>    </xsl:template></xsl:stylesheet>

Hi Kandula,

So the new requirement:

1. Replace iob:varyOn with iob:Reply

2. Add as a child to iob:Header the element iob:replyStatus

3. Add as a child to iob:Reply the elements iob:faultCode and iob:faultString as before

4. Continue to be dynamic as far as the namespace uri prefix

Please try the following:

<?xml version="1.0" encoding="UTF-8"?><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"  version="1.0">     <xsl:variable name="globalPrefix" select="substring-before(name(/soapenv:Envelope/soapenv:Body/*[1]), ':')" />   <xsl:variable name="globalNamespace" select="namespace-uri(/soapenv:Envelope/soapenv:Body/*[1])" />   <xsl:template match="soapenv:Body/*">     <xsl:element name="{concat($globalPrefix, ':', 'Reply')}" namespace="{namespace-uri(.)}">       <xsl:apply-templates select="@* | node()" />       <xsl:element name="{concat($globalPrefix, ':', 'faultCode')}" namespace="{namespace-uri(.)}">ESB0017</xsl:element>       <xsl:element name="{concat($globalPrefix, ':', 'faultString')}" namespace="{namespace-uri(.)}">Invalid message format</xsl:element>     </xsl:element>   </xsl:template>   <xsl:template match="*[local-name() = 'Header' and namespace-uri() = $globalNamespace]">     <xsl:copy>       <xsl:apply-templates select="@* | node()" />       <xsl:element name="{concat($globalPrefix, ':', 'ReplyStatus')}" namespace="{namespace-uri(.)}">ERR</xsl:element>     </xsl:copy>   </xsl:template>    <!-- all other elements, simply copy them -->    <xsl:template match="*">        <xsl:copy>            <xsl:apply-templates select="@* | node()" />        </xsl:copy>    </xsl:template></xsl:stylesheet>

Which produces with your input

<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:iob="http://www.iob.com">  <soapenv:Header />  <soapenv:Body>    <iob:Reply>      <iob:Header>        <iob:header_channel>extinternal</iob:header_channel>        <iob:header_user>nag</iob:header_user>        <iob:header_workstation>pronteff</iob:header_workstation>        <iob:ReplyStatus>ERR</iob:ReplyStatus>      </iob:Header>      <iob:header_transactionDate>07072022</iob:header_transactionDate>      <iob:header_transactionTime>13:02</iob:header_transactionTime>      <iob:faultCode>ESB0017</iob:faultCode>      <iob:faultString>Invalid message format</iob:faultString>    </iob:Reply>  </soapenv:Body></soapenv:Envelope>

Given you want to inject at iob:Header a new element, you need an additional template to match that element, copy the iob:Header element, apply templates to copy all of its current children, and then add the new element.

Regards,

Steve

Hi Kandula,

I received your private message with additional questions, but that does not allow me to respond directly to you as that email's reply address is a do not reply address of this community forum.  Please clarify your question here so I can respond.  The request as shown above appears to be a web service request to a iob:varyOn web service.  The example I provided added the additional information you wanted added to that web service request.  Your subsequent question shows an SOAP message with the root body element <iob:Reply> which I'd assume would be your web service's response to the iob:varyOn request you sent??  Are you wanting to manipulate it as well?  Or is the transformation on the request something that the web service didn't like? Since you only provided an expected response and not an actual response for comparison it is difficult to determine what your requirement is.  I'd also refer you to documentation on xslt identity transformations which the example I provided implements a variation for your specific requirement.  There are plenty of sites you can find in an internet search for "xslt identity transformation".

Best Regards,
Steve

Hi Kandula,

You can get the prefix from the name of the parent element (iob:varyOn).  Try the following

<?xml version="1.0" encoding="UTF-8"?><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"  version="1.0">   <xsl:template match="soapenv:Body/*">     <xsl:copy>       <xsl:apply-templates select="@* | node()" />       <xsl:variable name="prefix" select="substring-before(name(), ':')" />       <xsl:element name="{concat($prefix, ':', 'replyStatus')}" namespace="{namespace-uri(.)}">ERR</xsl:element>       <xsl:element name="{concat($prefix, ':', 'faultCode')}" namespace="{namespace-uri(.)}">ESB0017</xsl:element>       <xsl:element name="{concat($prefix, ':', 'faultString')}" namespace="{namespace-uri(.)}">Invalid message format</xsl:element>     </xsl:copy>   </xsl:template>    <!-- all other elements, simply copy them -->    <xsl:template match="*">        <xsl:copy>            <xsl:apply-templates select="@* | node()" />        </xsl:copy>    </xsl:template></xsl:stylesheet>

Hi Kandula,

So the new requirement:

1. Replace iob:varyOn with iob:Reply

2. Add as a child to iob:Header the element iob:replyStatus

3. Add as a child to iob:Reply the elements iob:faultCode and iob:faultString as before

4. Continue to be dynamic as far as the namespace uri prefix

Please try the following:

<?xml version="1.0" encoding="UTF-8"?><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"  version="1.0">     <xsl:variable name="globalPrefix" select="substring-before(name(/soapenv:Envelope/soapenv:Body/*[1]), ':')" />   <xsl:variable name="globalNamespace" select="namespace-uri(/soapenv:Envelope/soapenv:Body/*[1])" />   <xsl:template match="soapenv:Body/*">     <xsl:element name="{concat($globalPrefix, ':', 'Reply')}" namespace="{namespace-uri(.)}">       <xsl:apply-templates select="@* | node()" />       <xsl:element name="{concat($globalPrefix, ':', 'faultCode')}" namespace="{namespace-uri(.)}">ESB0017</xsl:element>       <xsl:element name="{concat($globalPrefix, ':', 'faultString')}" namespace="{namespace-uri(.)}">Invalid message format</xsl:element>     </xsl:element>   </xsl:template>   <xsl:template match="*[local-name() = 'Header' and namespace-uri() = $globalNamespace]">     <xsl:copy>       <xsl:apply-templates select="@* | node()" />       <xsl:element name="{concat($globalPrefix, ':', 'ReplyStatus')}" namespace="{namespace-uri(.)}">ERR</xsl:element>     </xsl:copy>   </xsl:template>    <!-- all other elements, simply copy them -->    <xsl:template match="*">        <xsl:copy>            <xsl:apply-templates select="@* | node()" />        </xsl:copy>    </xsl:template></xsl:stylesheet>

Which produces with your input

<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:iob="http://www.iob.com">  <soapenv:Header />  <soapenv:Body>    <iob:Reply>      <iob:Header>        <iob:header_channel>extinternal</iob:header_channel>        <iob:header_user>nag</iob:header_user>        <iob:header_workstation>pronteff</iob:header_workstation>        <iob:ReplyStatus>ERR</iob:ReplyStatus>      </iob:Header>      <iob:header_transactionDate>07072022</iob:header_transactionDate>      <iob:header_transactionTime>13:02</iob:header_transactionTime>      <iob:faultCode>ESB0017</iob:faultCode>      <iob:faultString>Invalid message format</iob:faultString>    </iob:Reply>  </soapenv:Body></soapenv:Envelope>

Given you want to inject at iob:Header a new element, you need an additional template to match that element, copy the iob:Header element, apply templates to copy all of its current children, and then add the new element.

Regards,

Steve

Hi Kandula,

I received your private message with additional questions, but that does not allow me to respond directly to you as that email's reply address is a do not reply address of this community forum.  Please clarify your question here so I can respond.  The request as shown above appears to be a web service request to a iob:varyOn web service.  The example I provided added the additional information you wanted added to that web service request.  Your subsequent question shows an SOAP message with the root body element <iob:Reply> which I'd assume would be your web service's response to the iob:varyOn request you sent??  Are you wanting to manipulate it as well?  Or is the transformation on the request something that the web service didn't like? Since you only provided an expected response and not an actual response for comparison it is difficult to determine what your requirement is.  I'd also refer you to documentation on xslt identity transformations which the example I provided implements a variation for your specific requirement.  There are plenty of sites you can find in an internet search for "xslt identity transformation".

Best Regards,
Steve

Hi Kandula,

You can get the prefix from the name of the parent element (iob:varyOn).  Try the following

<?xml version="1.0" encoding="UTF-8"?><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"  version="1.0">   <xsl:template match="soapenv:Body/*">     <xsl:copy>       <xsl:apply-templates select="@* | node()" />       <xsl:variable name="prefix" select="substring-before(name(), ':')" />       <xsl:element name="{concat($prefix, ':', 'replyStatus')}" namespace="{namespace-uri(.)}">ERR</xsl:element>       <xsl:element name="{concat($prefix, ':', 'faultCode')}" namespace="{namespace-uri(.)}">ESB0017</xsl:element>       <xsl:element name="{concat($prefix, ':', 'faultString')}" namespace="{namespace-uri(.)}">Invalid message format</xsl:element>     </xsl:copy>   </xsl:template>    <!-- all other elements, simply copy them -->    <xsl:template match="*">        <xsl:copy>            <xsl:apply-templates select="@* | node()" />        </xsl:copy>    </xsl:template></xsl:stylesheet>

Hi Kandula,
My apologies, missed that, the match on the generic template wasn't handling attributes.  Change it to

    <!-- all other elements, simply copy them -->    <xsl:template match="@* | *">        <xsl:copy>            <xsl:apply-templates select="@* | node()" />        </xsl:copy>    </xsl:template>

As for adding attributes in the response for the future, it is simply a matter of adding a template match for the element you wish to add the attribute, and then in addition to the xsl:copy and xsl:apply templates, to do an xsl:attribute to add the desired attribute to the matched element.  For example, I added before the final template a match for header_user and added an attribute newAttribute="somevalue" with the following:

   <!-- add attribute to iob:header_user element -->   <xsl:template match="*[local-name() = 'header_user' and namespace-uri() = $globalNamespace]">     <xsl:copy>       <xsl:attribute name="newAttribute">somevalue</xsl:attribute>       <xsl:apply-templates select="@* | node()" />     </xsl:copy>   </xsl:template>

which produced the following with your input

<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:iob="http://www.iob.com">  <soapenv:Header />  <soapenv:Body>    <iob:Reply>      <iob:Header>        <iob:header_channel domain="ext">internal</iob:header_channel>        <iob:header_user newAttribute="somevalue">nag</iob:header_user>        <iob:header_workstation>pronteff</iob:header_workstation>        <iob:ReplyStatus>ERR</iob:ReplyStatus>      </iob:Header>      <iob:header_transactionDate>07072022</iob:header_transactionDate>      <iob:header_transactionTime>13:02</iob:header_transactionTime>      <iob:faultCode>ESB0017</iob:faultCode>      <iob:faultString>Invalid message format</iob:faultString>    </iob:Reply>  </soapenv:Body></soapenv:Envelope>

Ultimately, these are all pretty standard xslt identity transformation techniques that you should be able to find examples with your favorite search engine.

Regards,
Steve

Hi Kandula,

So the new requirement:

1. Replace iob:varyOn with iob:Reply

2. Add as a child to iob:Header the element iob:replyStatus

3. Add as a child to iob:Reply the elements iob:faultCode and iob:faultString as before

4. Continue to be dynamic as far as the namespace uri prefix

Please try the following:

<?xml version="1.0" encoding="UTF-8"?><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"  version="1.0">     <xsl:variable name="globalPrefix" select="substring-before(name(/soapenv:Envelope/soapenv:Body/*[1]), ':')" />   <xsl:variable name="globalNamespace" select="namespace-uri(/soapenv:Envelope/soapenv:Body/*[1])" />   <xsl:template match="soapenv:Body/*">     <xsl:element name="{concat($globalPrefix, ':', 'Reply')}" namespace="{namespace-uri(.)}">       <xsl:apply-templates select="@* | node()" />       <xsl:element name="{concat($globalPrefix, ':', 'faultCode')}" namespace="{namespace-uri(.)}">ESB0017</xsl:element>       <xsl:element name="{concat($globalPrefix, ':', 'faultString')}" namespace="{namespace-uri(.)}">Invalid message format</xsl:element>     </xsl:element>   </xsl:template>   <xsl:template match="*[local-name() = 'Header' and namespace-uri() = $globalNamespace]">     <xsl:copy>       <xsl:apply-templates select="@* | node()" />       <xsl:element name="{concat($globalPrefix, ':', 'ReplyStatus')}" namespace="{namespace-uri(.)}">ERR</xsl:element>     </xsl:copy>   </xsl:template>    <!-- all other elements, simply copy them -->    <xsl:template match="*">        <xsl:copy>            <xsl:apply-templates select="@* | node()" />        </xsl:copy>    </xsl:template></xsl:stylesheet>

Which produces with your input

<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:iob="http://www.iob.com">  <soapenv:Header />  <soapenv:Body>    <iob:Reply>      <iob:Header>        <iob:header_channel>extinternal</iob:header_channel>        <iob:header_user>nag</iob:header_user>        <iob:header_workstation>pronteff</iob:header_workstation>        <iob:ReplyStatus>ERR</iob:ReplyStatus>      </iob:Header>      <iob:header_transactionDate>07072022</iob:header_transactionDate>      <iob:header_transactionTime>13:02</iob:header_transactionTime>      <iob:faultCode>ESB0017</iob:faultCode>      <iob:faultString>Invalid message format</iob:faultString>    </iob:Reply>  </soapenv:Body></soapenv:Envelope>

Given you want to inject at iob:Header a new element, you need an additional template to match that element, copy the iob:Header element, apply templates to copy all of its current children, and then add the new element.

Regards,

Steve

Hi Kandula,

I received your private message with additional questions, but that does not allow me to respond directly to you as that email's reply address is a do not reply address of this community forum.  Please clarify your question here so I can respond.  The request as shown above appears to be a web service request to a iob:varyOn web service.  The example I provided added the additional information you wanted added to that web service request.  Your subsequent question shows an SOAP message with the root body element <iob:Reply> which I'd assume would be your web service's response to the iob:varyOn request you sent??  Are you wanting to manipulate it as well?  Or is the transformation on the request something that the web service didn't like? Since you only provided an expected response and not an actual response for comparison it is difficult to determine what your requirement is.  I'd also refer you to documentation on xslt identity transformations which the example I provided implements a variation for your specific requirement.  There are plenty of sites you can find in an internet search for "xslt identity transformation".

Best Regards,
Steve

Hi Kandula,

You can get the prefix from the name of the parent element (iob:varyOn).  Try the following

<?xml version="1.0" encoding="UTF-8"?><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"  version="1.0">   <xsl:template match="soapenv:Body/*">     <xsl:copy>       <xsl:apply-templates select="@* | node()" />       <xsl:variable name="prefix" select="substring-before(name(), ':')" />       <xsl:element name="{concat($prefix, ':', 'replyStatus')}" namespace="{namespace-uri(.)}">ERR</xsl:element>       <xsl:element name="{concat($prefix, ':', 'faultCode')}" namespace="{namespace-uri(.)}">ESB0017</xsl:element>       <xsl:element name="{concat($prefix, ':', 'faultString')}" namespace="{namespace-uri(.)}">Invalid message format</xsl:element>     </xsl:copy>   </xsl:template>    <!-- all other elements, simply copy them -->    <xsl:template match="*">        <xsl:copy>            <xsl:apply-templates select="@* | node()" />        </xsl:copy>    </xsl:template></xsl:stylesheet>

Hi Kandula,
My apologies, missed that, the match on the generic template wasn't handling attributes.  Change it to

    <!-- all other elements, simply copy them -->    <xsl:template match="@* | *">        <xsl:copy>            <xsl:apply-templates select="@* | node()" />        </xsl:copy>    </xsl:template>

As for adding attributes in the response for the future, it is simply a matter of adding a template match for the element you wish to add the attribute, and then in addition to the xsl:copy and xsl:apply templates, to do an xsl:attribute to add the desired attribute to the matched element.  For example, I added before the final template a match for header_user and added an attribute newAttribute="somevalue" with the following:

   <!-- add attribute to iob:header_user element -->   <xsl:template match="*[local-name() = 'header_user' and namespace-uri() = $globalNamespace]">     <xsl:copy>       <xsl:attribute name="newAttribute">somevalue</xsl:attribute>       <xsl:apply-templates select="@* | node()" />     </xsl:copy>   </xsl:template>

which produced the following with your input

<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:iob="http://www.iob.com">  <soapenv:Header />  <soapenv:Body>    <iob:Reply>      <iob:Header>        <iob:header_channel domain="ext">internal</iob:header_channel>        <iob:header_user newAttribute="somevalue">nag</iob:header_user>        <iob:header_workstation>pronteff</iob:header_workstation>        <iob:ReplyStatus>ERR</iob:ReplyStatus>      </iob:Header>      <iob:header_transactionDate>07072022</iob:header_transactionDate>      <iob:header_transactionTime>13:02</iob:header_transactionTime>      <iob:faultCode>ESB0017</iob:faultCode>      <iob:faultString>Invalid message format</iob:faultString>    </iob:Reply>  </soapenv:Body></soapenv:Envelope>

Ultimately, these are all pretty standard xslt identity transformation techniques that you should be able to find examples with your favorite search engine.

Regards,
Steve

Hi Kandula,

So the new requirement:

1. Replace iob:varyOn with iob:Reply

2. Add as a child to iob:Header the element iob:replyStatus

3. Add as a child to iob:Reply the elements iob:faultCode and iob:faultString as before

4. Continue to be dynamic as far as the namespace uri prefix

Please try the following:

<?xml version="1.0" encoding="UTF-8"?><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"  version="1.0">     <xsl:variable name="globalPrefix" select="substring-before(name(/soapenv:Envelope/soapenv:Body/*[1]), ':')" />   <xsl:variable name="globalNamespace" select="namespace-uri(/soapenv:Envelope/soapenv:Body/*[1])" />   <xsl:template match="soapenv:Body/*">     <xsl:element name="{concat($globalPrefix, ':', 'Reply')}" namespace="{namespace-uri(.)}">       <xsl:apply-templates select="@* | node()" />       <xsl:element name="{concat($globalPrefix, ':', 'faultCode')}" namespace="{namespace-uri(.)}">ESB0017</xsl:element>       <xsl:element name="{concat($globalPrefix, ':', 'faultString')}" namespace="{namespace-uri(.)}">Invalid message format</xsl:element>     </xsl:element>   </xsl:template>   <xsl:template match="*[local-name() = 'Header' and namespace-uri() = $globalNamespace]">     <xsl:copy>       <xsl:apply-templates select="@* | node()" />       <xsl:element name="{concat($globalPrefix, ':', 'ReplyStatus')}" namespace="{namespace-uri(.)}">ERR</xsl:element>     </xsl:copy>   </xsl:template>    <!-- all other elements, simply copy them -->    <xsl:template match="*">        <xsl:copy>            <xsl:apply-templates select="@* | node()" />        </xsl:copy>    </xsl:template></xsl:stylesheet>

Which produces with your input

<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:iob="http://www.iob.com">  <soapenv:Header />  <soapenv:Body>    <iob:Reply>      <iob:Header>        <iob:header_channel>extinternal</iob:header_channel>        <iob:header_user>nag</iob:header_user>        <iob:header_workstation>pronteff</iob:header_workstation>        <iob:ReplyStatus>ERR</iob:ReplyStatus>      </iob:Header>      <iob:header_transactionDate>07072022</iob:header_transactionDate>      <iob:header_transactionTime>13:02</iob:header_transactionTime>      <iob:faultCode>ESB0017</iob:faultCode>      <iob:faultString>Invalid message format</iob:faultString>    </iob:Reply>  </soapenv:Body></soapenv:Envelope>

Given you want to inject at iob:Header a new element, you need an additional template to match that element, copy the iob:Header element, apply templates to copy all of its current children, and then add the new element.

Regards,

Steve

Hi Kandula,

I received your private message with additional questions, but that does not allow me to respond directly to you as that email's reply address is a do not reply address of this community forum.  Please clarify your question here so I can respond.  The request as shown above appears to be a web service request to a iob:varyOn web service.  The example I provided added the additional information you wanted added to that web service request.  Your subsequent question shows an SOAP message with the root body element <iob:Reply> which I'd assume would be your web service's response to the iob:varyOn request you sent??  Are you wanting to manipulate it as well?  Or is the transformation on the request something that the web service didn't like? Since you only provided an expected response and not an actual response for comparison it is difficult to determine what your requirement is.  I'd also refer you to documentation on xslt identity transformations which the example I provided implements a variation for your specific requirement.  There are plenty of sites you can find in an internet search for "xslt identity transformation".

Best Regards,
Steve

Hi Kandula,

You can get the prefix from the name of the parent element (iob:varyOn).  Try the following

<?xml version="1.0" encoding="UTF-8"?><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"  version="1.0">   <xsl:template match="soapenv:Body/*">     <xsl:copy>       <xsl:apply-templates select="@* | node()" />       <xsl:variable name="prefix" select="substring-before(name(), ':')" />       <xsl:element name="{concat($prefix, ':', 'replyStatus')}" namespace="{namespace-uri(.)}">ERR</xsl:element>       <xsl:element name="{concat($prefix, ':', 'faultCode')}" namespace="{namespace-uri(.)}">ESB0017</xsl:element>       <xsl:element name="{concat($prefix, ':', 'faultString')}" namespace="{namespace-uri(.)}">Invalid message format</xsl:element>     </xsl:copy>   </xsl:template>    <!-- all other elements, simply copy them -->    <xsl:template match="*">        <xsl:copy>            <xsl:apply-templates select="@* | node()" />        </xsl:copy>    </xsl:template></xsl:stylesheet>

Hi Kandula,
My apologies, missed that, the match on the generic template wasn't handling attributes.  Change it to

    <!-- all other elements, simply copy them -->    <xsl:template match="@* | *">        <xsl:copy>            <xsl:apply-templates select="@* | node()" />        </xsl:copy>    </xsl:template>

As for adding attributes in the response for the future, it is simply a matter of adding a template match for the element you wish to add the attribute, and then in addition to the xsl:copy and xsl:apply templates, to do an xsl:attribute to add the desired attribute to the matched element.  For example, I added before the final template a match for header_user and added an attribute newAttribute="somevalue" with the following:

   <!-- add attribute to iob:header_user element -->   <xsl:template match="*[local-name() = 'header_user' and namespace-uri() = $globalNamespace]">     <xsl:copy>       <xsl:attribute name="newAttribute">somevalue</xsl:attribute>       <xsl:apply-templates select="@* | node()" />     </xsl:copy>   </xsl:template>

which produced the following with your input

<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:iob="http://www.iob.com">  <soapenv:Header />  <soapenv:Body>    <iob:Reply>      <iob:Header>        <iob:header_channel domain="ext">internal</iob:header_channel>        <iob:header_user newAttribute="somevalue">nag</iob:header_user>        <iob:header_workstation>pronteff</iob:header_workstation>        <iob:ReplyStatus>ERR</iob:ReplyStatus>      </iob:Header>      <iob:header_transactionDate>07072022</iob:header_transactionDate>      <iob:header_transactionTime>13:02</iob:header_transactionTime>      <iob:faultCode>ESB0017</iob:faultCode>      <iob:faultString>Invalid message format</iob:faultString>    </iob:Reply>  </soapenv:Body></soapenv:Envelope>

Ultimately, these are all pretty standard xslt identity transformation techniques that you should be able to find examples with your favorite search engine.

Regards,
Steve

Hi Kandula,

So the new requirement:

1. Replace iob:varyOn with iob:Reply

2. Add as a child to iob:Header the element iob:replyStatus

3. Add as a child to iob:Reply the elements iob:faultCode and iob:faultString as before

4. Continue to be dynamic as far as the namespace uri prefix

Please try the following:

<?xml version="1.0" encoding="UTF-8"?><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"  version="1.0">     <xsl:variable name="globalPrefix" select="substring-before(name(/soapenv:Envelope/soapenv:Body/*[1]), ':')" />   <xsl:variable name="globalNamespace" select="namespace-uri(/soapenv:Envelope/soapenv:Body/*[1])" />   <xsl:template match="soapenv:Body/*">     <xsl:element name="{concat($globalPrefix, ':', 'Reply')}" namespace="{namespace-uri(.)}">       <xsl:apply-templates select="@* | node()" />       <xsl:element name="{concat($globalPrefix, ':', 'faultCode')}" namespace="{namespace-uri(.)}">ESB0017</xsl:element>       <xsl:element name="{concat($globalPrefix, ':', 'faultString')}" namespace="{namespace-uri(.)}">Invalid message format</xsl:element>     </xsl:element>   </xsl:template>   <xsl:template match="*[local-name() = 'Header' and namespace-uri() = $globalNamespace]">     <xsl:copy>       <xsl:apply-templates select="@* | node()" />       <xsl:element name="{concat($globalPrefix, ':', 'ReplyStatus')}" namespace="{namespace-uri(.)}">ERR</xsl:element>     </xsl:copy>   </xsl:template>    <!-- all other elements, simply copy them -->    <xsl:template match="*">        <xsl:copy>            <xsl:apply-templates select="@* | node()" />        </xsl:copy>    </xsl:template></xsl:stylesheet>

Which produces with your input

<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:iob="http://www.iob.com">  <soapenv:Header />  <soapenv:Body>    <iob:Reply>      <iob:Header>        <iob:header_channel>extinternal</iob:header_channel>        <iob:header_user>nag</iob:header_user>        <iob:header_workstation>pronteff</iob:header_workstation>        <iob:ReplyStatus>ERR</iob:ReplyStatus>      </iob:Header>      <iob:header_transactionDate>07072022</iob:header_transactionDate>      <iob:header_transactionTime>13:02</iob:header_transactionTime>      <iob:faultCode>ESB0017</iob:faultCode>      <iob:faultString>Invalid message format</iob:faultString>    </iob:Reply>  </soapenv:Body></soapenv:Envelope>

Given you want to inject at iob:Header a new element, you need an additional template to match that element, copy the iob:Header element, apply templates to copy all of its current children, and then add the new element.

Regards,

Steve

Hi Kandula,

I received your private message with additional questions, but that does not allow me to respond directly to you as that email's reply address is a do not reply address of this community forum.  Please clarify your question here so I can respond.  The request as shown above appears to be a web service request to a iob:varyOn web service.  The example I provided added the additional information you wanted added to that web service request.  Your subsequent question shows an SOAP message with the root body element <iob:Reply> which I'd assume would be your web service's response to the iob:varyOn request you sent??  Are you wanting to manipulate it as well?  Or is the transformation on the request something that the web service didn't like? Since you only provided an expected response and not an actual response for comparison it is difficult to determine what your requirement is.  I'd also refer you to documentation on xslt identity transformations which the example I provided implements a variation for your specific requirement.  There are plenty of sites you can find in an internet search for "xslt identity transformation".

Best Regards,
Steve

Hi Kandula,

You can get the prefix from the name of the parent element (iob:varyOn).  Try the following

<?xml version="1.0" encoding="UTF-8"?><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"  version="1.0">   <xsl:template match="soapenv:Body/*">     <xsl:copy>       <xsl:apply-templates select="@* | node()" />       <xsl:variable name="prefix" select="substring-before(name(), ':')" />       <xsl:element name="{concat($prefix, ':', 'replyStatus')}" namespace="{namespace-uri(.)}">ERR</xsl:element>       <xsl:element name="{concat($prefix, ':', 'faultCode')}" namespace="{namespace-uri(.)}">ESB0017</xsl:element>       <xsl:element name="{concat($prefix, ':', 'faultString')}" namespace="{namespace-uri(.)}">Invalid message format</xsl:element>     </xsl:copy>   </xsl:template>    <!-- all other elements, simply copy them -->    <xsl:template match="*">        <xsl:copy>            <xsl:apply-templates select="@* | node()" />        </xsl:copy>    </xsl:template></xsl:stylesheet>

Hi Kandula,
In xslt, the identity transformations are essentially recursive template calls that build the output from the top down but then inside out.   There is a under to covers apply-templates that is done by the xslt engine to run your transformation starting with the root element.  Given your xslt does not have a match="/", the template that matches for the root element is <xsl:template match="@* | *"> which is why you see your message 6 and 7 first as it is processing the soapenv:Envelope element.  So let's look at that template:

<xsl:template match="@* | *">  <xsl:copy>    <xsl:apply-templates select="@* | node()"/>    <xsl:message dp:priority="error">      <xsl:text>6th:</xsl:text>      <xsl:copy-of select="."/>    </xsl:message>  </xsl:copy>  <xsl:message dp:priority="error">    <xsl:text>7th:</xsl:text>    <xsl:copy-of select="."/>  </xsl:message></xsl:template>

The xsl copy will copy the current element which will create the

<soapenv:Envelope 

element.  It then does an apply templates, passing in ALL of its nodes and attributes.

This same template would match the soapenv:Body which would create the <soap:Body and again, it does an apply template, which this time is matched by a different template, as the <iob:varyOn> element is matching 

<xsl:template match="soapenv:Body/*">  <xsl:element name="{concat($globalPrefix, ':', 'Reply')}" namespace="{namespace-uri(.)}">    <xsl:apply-templates select="@* | node()"/>    <xsl:message dp:priority="error">      <xsl:text>3rd:</xsl:text>      <xsl:copy-of select="."/>    </xsl:message>    <xsl:element name="{concat($globalPrefix, ':', 'faultCode')}" namespace="{namespace-uri(.)}">ESB0017</xsl:element>    <xsl:element name="{concat($globalPrefix, ':', 'faultString')}" namespace="{namespace-uri(.)}">Invalid message format</xsl:element>  </xsl:element>  <xsl:message dp:priority="error">    <xsl:text>8th:</xsl:text>    <xsl:copy-of select="."/>  </xsl:message></xsl:template>

that template matches all elements that are children of soapEnv:Body, of course there is only one element here, but this time instead of doing a xsl:copy to create the <iob:varyOn> element, it has an xsl:element to create the iob:Reply element instead.  It then does an apply templates to pass all of the children and attributes of iob:varyOn, all of which will match the last template, and when that recursion reaches a point where there are no child attributes or nodes to process, the </xsl:copy closes out that element.  When this apply-template finally returns, the two xsl:elements will add the two additional elements to the iob:Reply.

There is no "debugger" that I've used.  I generated these examples with eclipse so perhaps there is a debugger there that will allow you to step through the input xml and see which template is matching.  It's all about understanding xslt and recursion that is inherent in the apply-template processing.  I found this on the net years ago which I found useful at the time.  Hope it helps https://lenzconsulting.com/how-xslt-works/

Regards,

Steve

Hi Kandula,
My apologies, missed that, the match on the generic template wasn't handling attributes.  Change it to

    <!-- all other elements, simply copy them -->    <xsl:template match="@* | *">        <xsl:copy>            <xsl:apply-templates select="@* | node()" />        </xsl:copy>    </xsl:template>

As for adding attributes in the response for the future, it is simply a matter of adding a template match for the element you wish to add the attribute, and then in addition to the xsl:copy and xsl:apply templates, to do an xsl:attribute to add the desired attribute to the matched element.  For example, I added before the final template a match for header_user and added an attribute newAttribute="somevalue" with the following:

   <!-- add attribute to iob:header_user element -->   <xsl:template match="*[local-name() = 'header_user' and namespace-uri() = $globalNamespace]">     <xsl:copy>       <xsl:attribute name="newAttribute">somevalue</xsl:attribute>       <xsl:apply-templates select="@* | node()" />     </xsl:copy>   </xsl:template>

which produced the following with your input

<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:iob="http://www.iob.com">  <soapenv:Header />  <soapenv:Body>    <iob:Reply>      <iob:Header>        <iob:header_channel domain="ext">internal</iob:header_channel>        <iob:header_user newAttribute="somevalue">nag</iob:header_user>        <iob:header_workstation>pronteff</iob:header_workstation>        <iob:ReplyStatus>ERR</iob:ReplyStatus>      </iob:Header>      <iob:header_transactionDate>07072022</iob:header_transactionDate>      <iob:header_transactionTime>13:02</iob:header_transactionTime>      <iob:faultCode>ESB0017</iob:faultCode>      <iob:faultString>Invalid message format</iob:faultString>    </iob:Reply>  </soapenv:Body></soapenv:Envelope>

Ultimately, these are all pretty standard xslt identity transformation techniques that you should be able to find examples with your favorite search engine.

Regards,
Steve

Hi Kandula,

So the new requirement:

1. Replace iob:varyOn with iob:Reply

2. Add as a child to iob:Header the element iob:replyStatus

3. Add as a child to iob:Reply the elements iob:faultCode and iob:faultString as before

4. Continue to be dynamic as far as the namespace uri prefix

Please try the following:

<?xml version="1.0" encoding="UTF-8"?><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"  version="1.0">     <xsl:variable name="globalPrefix" select="substring-before(name(/soapenv:Envelope/soapenv:Body/*[1]), ':')" />   <xsl:variable name="globalNamespace" select="namespace-uri(/soapenv:Envelope/soapenv:Body/*[1])" />   <xsl:template match="soapenv:Body/*">     <xsl:element name="{concat($globalPrefix, ':', 'Reply')}" namespace="{namespace-uri(.)}">       <xsl:apply-templates select="@* | node()" />       <xsl:element name="{concat($globalPrefix, ':', 'faultCode')}" namespace="{namespace-uri(.)}">ESB0017</xsl:element>       <xsl:element name="{concat($globalPrefix, ':', 'faultString')}" namespace="{namespace-uri(.)}">Invalid message format</xsl:element>     </xsl:element>   </xsl:template>   <xsl:template match="*[local-name() = 'Header' and namespace-uri() = $globalNamespace]">     <xsl:copy>       <xsl:apply-templates select="@* | node()" />       <xsl:element name="{concat($globalPrefix, ':', 'ReplyStatus')}" namespace="{namespace-uri(.)}">ERR</xsl:element>     </xsl:copy>   </xsl:template>    <!-- all other elements, simply copy them -->    <xsl:template match="*">        <xsl:copy>            <xsl:apply-templates select="@* | node()" />        </xsl:copy>    </xsl:template></xsl:stylesheet>

Which produces with your input

<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:iob="http://www.iob.com">  <soapenv:Header />  <soapenv:Body>    <iob:Reply>      <iob:Header>        <iob:header_channel>extinternal</iob:header_channel>        <iob:header_user>nag</iob:header_user>        <iob:header_workstation>pronteff</iob:header_workstation>        <iob:ReplyStatus>ERR</iob:ReplyStatus>      </iob:Header>      <iob:header_transactionDate>07072022</iob:header_transactionDate>      <iob:header_transactionTime>13:02</iob:header_transactionTime>      <iob:faultCode>ESB0017</iob:faultCode>      <iob:faultString>Invalid message format</iob:faultString>    </iob:Reply>  </soapenv:Body></soapenv:Envelope>

Given you want to inject at iob:Header a new element, you need an additional template to match that element, copy the iob:Header element, apply templates to copy all of its current children, and then add the new element.

Regards,

Steve

Hi Kandula,

I received your private message with additional questions, but that does not allow me to respond directly to you as that email's reply address is a do not reply address of this community forum.  Please clarify your question here so I can respond.  The request as shown above appears to be a web service request to a iob:varyOn web service.  The example I provided added the additional information you wanted added to that web service request.  Your subsequent question shows an SOAP message with the root body element <iob:Reply> which I'd assume would be your web service's response to the iob:varyOn request you sent??  Are you wanting to manipulate it as well?  Or is the transformation on the request something that the web service didn't like? Since you only provided an expected response and not an actual response for comparison it is difficult to determine what your requirement is.  I'd also refer you to documentation on xslt identity transformations which the example I provided implements a variation for your specific requirement.  There are plenty of sites you can find in an internet search for "xslt identity transformation".

Best Regards,
Steve

Hi Kandula,

You can get the prefix from the name of the parent element (iob:varyOn).  Try the following

<?xml version="1.0" encoding="UTF-8"?><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"  version="1.0">   <xsl:template match="soapenv:Body/*">     <xsl:copy>       <xsl:apply-templates select="@* | node()" />       <xsl:variable name="prefix" select="substring-before(name(), ':')" />       <xsl:element name="{concat($prefix, ':', 'replyStatus')}" namespace="{namespace-uri(.)}">ERR</xsl:element>       <xsl:element name="{concat($prefix, ':', 'faultCode')}" namespace="{namespace-uri(.)}">ESB0017</xsl:element>       <xsl:element name="{concat($prefix, ':', 'faultString')}" namespace="{namespace-uri(.)}">Invalid message format</xsl:element>     </xsl:copy>   </xsl:template>    <!-- all other elements, simply copy them -->    <xsl:template match="*">        <xsl:copy>            <xsl:apply-templates select="@* | node()" />        </xsl:copy>    </xsl:template></xsl:stylesheet>

Hi Kandula,
In xslt, the identity transformations are essentially recursive template calls that build the output from the top down but then inside out.   There is a under to covers apply-templates that is done by the xslt engine to run your transformation starting with the root element.  Given your xslt does not have a match="/", the template that matches for the root element is <xsl:template match="@* | *"> which is why you see your message 6 and 7 first as it is processing the soapenv:Envelope element.  So let's look at that template:

<xsl:template match="@* | *">  <xsl:copy>    <xsl:apply-templates select="@* | node()"/>    <xsl:message dp:priority="error">      <xsl:text>6th:</xsl:text>      <xsl:copy-of select="."/>    </xsl:message>  </xsl:copy>  <xsl:message dp:priority="error">    <xsl:text>7th:</xsl:text>    <xsl:copy-of select="."/>  </xsl:message></xsl:template>

The xsl copy will copy the current element which will create the

<soapenv:Envelope 

element.  It then does an apply templates, passing in ALL of its nodes and attributes.

This same template would match the soapenv:Body which would create the <soap:Body and again, it does an apply template, which this time is matched by a different template, as the <iob:varyOn> element is matching 

<xsl:template match="soapenv:Body/*">  <xsl:element name="{concat($globalPrefix, ':', 'Reply')}" namespace="{namespace-uri(.)}">    <xsl:apply-templates select="@* | node()"/>    <xsl:message dp:priority="error">      <xsl:text>3rd:</xsl:text>      <xsl:copy-of select="."/>    </xsl:message>    <xsl:element name="{concat($globalPrefix, ':', 'faultCode')}" namespace="{namespace-uri(.)}">ESB0017</xsl:element>    <xsl:element name="{concat($globalPrefix, ':', 'faultString')}" namespace="{namespace-uri(.)}">Invalid message format</xsl:element>  </xsl:element>  <xsl:message dp:priority="error">    <xsl:text>8th:</xsl:text>    <xsl:copy-of select="."/>  </xsl:message></xsl:template>

that template matches all elements that are children of soapEnv:Body, of course there is only one element here, but this time instead of doing a xsl:copy to create the <iob:varyOn> element, it has an xsl:element to create the iob:Reply element instead.  It then does an apply templates to pass all of the children and attributes of iob:varyOn, all of which will match the last template, and when that recursion reaches a point where there are no child attributes or nodes to process, the </xsl:copy closes out that element.  When this apply-template finally returns, the two xsl:elements will add the two additional elements to the iob:Reply.

There is no "debugger" that I've used.  I generated these examples with eclipse so perhaps there is a debugger there that will allow you to step through the input xml and see which template is matching.  It's all about understanding xslt and recursion that is inherent in the apply-template processing.  I found this on the net years ago which I found useful at the time.  Hope it helps https://lenzconsulting.com/how-xslt-works/

Regards,

Steve

Hi Kandula,
My apologies, missed that, the match on the generic template wasn't handling attributes.  Change it to

    <!-- all other elements, simply copy them -->    <xsl:template match="@* | *">        <xsl:copy>            <xsl:apply-templates select="@* | node()" />        </xsl:copy>    </xsl:template>

As for adding attributes in the response for the future, it is simply a matter of adding a template match for the element you wish to add the attribute, and then in addition to the xsl:copy and xsl:apply templates, to do an xsl:attribute to add the desired attribute to the matched element.  For example, I added before the final template a match for header_user and added an attribute newAttribute="somevalue" with the following:

   <!-- add attribute to iob:header_user element -->   <xsl:template match="*[local-name() = 'header_user' and namespace-uri() = $globalNamespace]">     <xsl:copy>       <xsl:attribute name="newAttribute">somevalue</xsl:attribute>       <xsl:apply-templates select="@* | node()" />     </xsl:copy>   </xsl:template>

which produced the following with your input

<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:iob="http://www.iob.com">  <soapenv:Header />  <soapenv:Body>    <iob:Reply>      <iob:Header>        <iob:header_channel domain="ext">internal</iob:header_channel>        <iob:header_user newAttribute="somevalue">nag</iob:header_user>        <iob:header_workstation>pronteff</iob:header_workstation>        <iob:ReplyStatus>ERR</iob:ReplyStatus>      </iob:Header>      <iob:header_transactionDate>07072022</iob:header_transactionDate>      <iob:header_transactionTime>13:02</iob:header_transactionTime>      <iob:faultCode>ESB0017</iob:faultCode>      <iob:faultString>Invalid message format</iob:faultString>    </iob:Reply>  </soapenv:Body></soapenv:Envelope>

Ultimately, these are all pretty standard xslt identity transformation techniques that you should be able to find examples with your favorite search engine.

Regards,
Steve

Hi Kandula,

So the new requirement:

1. Replace iob:varyOn with iob:Reply

2. Add as a child to iob:Header the element iob:replyStatus

3. Add as a child to iob:Reply the elements iob:faultCode and iob:faultString as before

4. Continue to be dynamic as far as the namespace uri prefix

Please try the following:

<?xml version="1.0" encoding="UTF-8"?><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"  version="1.0">     <xsl:variable name="globalPrefix" select="substring-before(name(/soapenv:Envelope/soapenv:Body/*[1]), ':')" />   <xsl:variable name="globalNamespace" select="namespace-uri(/soapenv:Envelope/soapenv:Body/*[1])" />   <xsl:template match="soapenv:Body/*">     <xsl:element name="{concat($globalPrefix, ':', 'Reply')}" namespace="{namespace-uri(.)}">       <xsl:apply-templates select="@* | node()" />       <xsl:element name="{concat($globalPrefix, ':', 'faultCode')}" namespace="{namespace-uri(.)}">ESB0017</xsl:element>       <xsl:element name="{concat($globalPrefix, ':', 'faultString')}" namespace="{namespace-uri(.)}">Invalid message format</xsl:element>     </xsl:element>   </xsl:template>   <xsl:template match="*[local-name() = 'Header' and namespace-uri() = $globalNamespace]">     <xsl:copy>       <xsl:apply-templates select="@* | node()" />       <xsl:element name="{concat($globalPrefix, ':', 'ReplyStatus')}" namespace="{namespace-uri(.)}">ERR</xsl:element>     </xsl:copy>   </xsl:template>    <!-- all other elements, simply copy them -->    <xsl:template match="*">        <xsl:copy>            <xsl:apply-templates select="@* | node()" />        </xsl:copy>    </xsl:template></xsl:stylesheet>

Which produces with your input

<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:iob="http://www.iob.com">  <soapenv:Header />  <soapenv:Body>    <iob:Reply>      <iob:Header>        <iob:header_channel>extinternal</iob:header_channel>        <iob:header_user>nag</iob:header_user>        <iob:header_workstation>pronteff</iob:header_workstation>        <iob:ReplyStatus>ERR</iob:ReplyStatus>      </iob:Header>      <iob:header_transactionDate>07072022</iob:header_transactionDate>      <iob:header_transactionTime>13:02</iob:header_transactionTime>      <iob:faultCode>ESB0017</iob:faultCode>      <iob:faultString>Invalid message format</iob:faultString>    </iob:Reply>  </soapenv:Body></soapenv:Envelope>

Given you want to inject at iob:Header a new element, you need an additional template to match that element, copy the iob:Header element, apply templates to copy all of its current children, and then add the new element.

Regards,

Steve

Hi Kandula,

I received your private message with additional questions, but that does not allow me to respond directly to you as that email's reply address is a do not reply address of this community forum.  Please clarify your question here so I can respond.  The request as shown above appears to be a web service request to a iob:varyOn web service.  The example I provided added the additional information you wanted added to that web service request.  Your subsequent question shows an SOAP message with the root body element <iob:Reply> which I'd assume would be your web service's response to the iob:varyOn request you sent??  Are you wanting to manipulate it as well?  Or is the transformation on the request something that the web service didn't like? Since you only provided an expected response and not an actual response for comparison it is difficult to determine what your requirement is.  I'd also refer you to documentation on xslt identity transformations which the example I provided implements a variation for your specific requirement.  There are plenty of sites you can find in an internet search for "xslt identity transformation".

Best Regards,
Steve

Hi Kandula,

You can get the prefix from the name of the parent element (iob:varyOn).  Try the following

<?xml version="1.0" encoding="UTF-8"?><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"  version="1.0">   <xsl:template match="soapenv:Body/*">     <xsl:copy>       <xsl:apply-templates select="@* | node()" />       <xsl:variable name="prefix" select="substring-before(name(), ':')" />       <xsl:element name="{concat($prefix, ':', 'replyStatus')}" namespace="{namespace-uri(.)}">ERR</xsl:element>       <xsl:element name="{concat($prefix, ':', 'faultCode')}" namespace="{namespace-uri(.)}">ESB0017</xsl:element>       <xsl:element name="{concat($prefix, ':', 'faultString')}" namespace="{namespace-uri(.)}">Invalid message format</xsl:element>     </xsl:copy>   </xsl:template>    <!-- all other elements, simply copy them -->    <xsl:template match="*">        <xsl:copy>            <xsl:apply-templates select="@* | node()" />        </xsl:copy>    </xsl:template></xsl:stylesheet>