Sorry, here is the attachment. Ruwan.
On 7/19/07, Ruwan Linton <[EMAIL PROTECTED]> wrote:
Hi Renjith, It seems now the discussion is on XSLT :D I think the attached xslt will solve your problem. > > I do have another question too . > > Regarding next expected request to the same service from the same client > will be another element > > Say right now the element is "authenticate". The next time the element > will > be "requestXML" with different child elements. (This is because after > "authenticate" the service expects "requestXML" as next request from the > client. Could you please help me in this or provide me any link that can > > really help me in this scenario. The above solution I have proposed is not bound to any particular message. I must state that I got the help of Jonathan in order to get this done correctly. Thanks, Ruwan. Thanks & Regards, > > Renjith > > > -- Ruwan Linton http://www.wso2.org - "Oxygenating the Web Services Platform"
-- Ruwan Linton http://www.wso2.org - "Oxygenating the Web Services Platform"
<?xml version="1.0"?> <!-- The Identity Transformation with and NS change--> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform";> <!-- Whenever you match any node or any attribute --> <xsl:template match="node()|@*"> <!-- Copy the current node --> <xsl:copy> <!-- Including any attributes it has and any child nodes --> <xsl:apply-templates select="@*|node()"/> </xsl:copy> </xsl:template> <xsl:template match="ns:*"> <xsl:element name="{local-name(.)}" namespace="http://sync.dtc.com/";> <xsl:apply-templates select="@*|node()"/> </xsl:element> </xsl:template> </xsl:stylesheet>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
