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] 
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";). 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"; and still able to communicate with Client1 (Which is
being generated using namespace "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"; (Instead of Namespace "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";)

 

So in the end I need to expose my Service's WSDL with Namespace
"http://sync.dtc.com"; instead of "http://developer.intuit.com"; and works
fine with the client developed using WSDL having Namespace
"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]

Reply via email to