Hi Ruwan, Thanks a lot for the information. Let me try with the information provided by you.
Thanks, Renjith -----Original Message----- From: Ruwan Linton [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 20, 2007 11:47 PM To: [email protected] Subject: Re: "Regarding Namespace Problem with an application" Hi Renjith, Here is some more explanation, This is what U have to do; 1. get the wsdl from your original service and save it in to repository folder inside synapse installation folder and then change the NS of that as required. 2. Write your synapse configuration as follows; <definitions xmlns="http://ws.apache.org/ns/synapse";> <proxy name="$NAME_OF_THE_PROXY"> <target> <endpoint> <address uri="$ACTUAL_SERVICE_EPR"/> </endpoint> <outSequence> <send/> </outSequence> </target> <publishWSDL uri="file:repository/$WSDL_FILE_NAME"/> </proxy> </definitions> 3. start Synapse Now you will be able to invoke the Synapse proxy service with the former NS even though it's WSDL is published with a different NS. If you have any trouble in doing this, please let us know... Thanks, Ruwan. On 6/21/07, Asankha C. Perera <[EMAIL PROTECTED]> wrote: > > Hi Renjith > > Sample #100 shows you how you could provide the WSDL of your choice and > create a proxy to an existing service ( > http://ws.apache.org/synapse/Synapse_Samples.html#Sample100) > > Also check "Proxy Services" on the Quickstart guide ( > http://ws.apache.org/synapse/Synapse_QuickStart.html) > > asankha > > Renjith wrote: > > > > Hi Asankha, > > Thanks for the Reply. > > > > Could you please point me to any link that explains how to do as mentioned > in your suggestion? > > And Also this time I attached the WSDL also. > > > > Thanks, > > Renjith > ------------------------------ > > *From:* Asankha C. Perera [mailto:[EMAIL PROTECTED] <[EMAIL PROTECTED]>] > *Sent:* Wednesday, June 20, 2007 1:58 PM > *To:* [email protected] > *Subject:* Re: "Regarding Namespace Problem with an application" > > > > Hi Renjith > > For Details please see the WSDL Attached. > > Seems like you forgot to attach it ;-) > > I have a client that is been developed using the attached WSDL, that > works fine if I am building a service using the same WSDL. But since our > proposed service have similar kind of clients to deal with . But those > clients are generated using almost same WSDL, except the target Namespace > changes and in different package itself. > > > > So for the first client (Client1) I have to create the supporting classes > in package com.intuit.developer to work fine (as per mentioned in > namespace "http://developer.intuit.com"; <http://developer.intuit.com>). > But is there any way I can package the classes into com.dtc.sync and also > able to change the namespace of WSDL to "http://sync.dtc.com";<http://sync.dtc.com>and still able to communicate with Client1 (Which is being generated using > namespace "http://developer.intuit.com"; <http://developer.intuit.com>. > And I cannot > > Change the Clinet1 code/WSDL). > > > > So I need to have my Service to be generated using WSDL with Namespace " > http://sync.dtc.com"; <http://sync.dtc.com> (Instead of Namespace " > http://developer.intuit.com"; <http://developer.intuit.com>) > > And still able to do service for the Client that is been generated using > the WSDL attached (ie with Namespace "http://developer.intuit.com";<http://developer.intuit.com> > ) > > > > So in the end I need to expose my Service's WSDL with Namespace " > http://sync.dtc.com"; <http://sync.dtc.com> instead of " > http://developer.intuit.com"; <http://developer.intuit.com> and works fine > with the client developed using WSDL having Namespace " > http://developer.intuit.com"; <http://developer.intuit.com> > > OK.. if I am understanding your problem correctly, this could be > simplified to the requirement that you want to expose your existing service > under different WSDLs (using different namespaces) to different clients? If > so, this is trivial in Synapse. You just create one or more proxy services > with a publish WSDL specified to that which the client expects, and then > forward the messages to the actual endpoint. > > asankha > --------------------------------------------------------------------- To > unsubscribe, e-mail: [EMAIL PROTECTED] For additional > commands, e-mail: [EMAIL PROTECTED] > > ------------------------------ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To > unsubscribe, e-mail: [EMAIL PROTECTED] For additional > commands, e-mail: [EMAIL PROTECTED] > -- Ruwan Linton http://www.wso2.org - "Oxygenating the Web Services Platform" --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
