Hi Ruwan, Jonnathan,
Thank you for the great help. At last I have implemented my solution. Thanks for the wonderful help. Just for curiosity I have one last question. What is the difference between proposed XSLT and the XSLT given below: Both worked for me :-) . <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"; xmlns:ns1="http://developer.intuit.com/"; version="1.0"> <xsl:template match="*"> <xsl:element name="{local-name()}" namespace="http://sync.dtc.com/";> <xsl:copy-of select="@*"/> <xsl:apply-templates/> </xsl:element> </xsl:template> </xsl:stylesheet> Thanks & Regards, Renjith _____ From: Ruwan Linton [mailto:[EMAIL PROTECTED] Sent: Thursday, July 19, 2007 1:36 AM To: [email protected] Subject: Re: "Regarding Namespace Problem with an application" 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"
