Thank you very much, Anne!

Apart from this Style/Use, anything else we need to take care, 
like namespaces etc?

I really appreciate if you refer me any doc/url for this implementation.

Thanks,
Srinivas.


Anne Thomas Manes <[EMAIL PROTECTED]> wrote: Srinivas,

This configuration is not valid:

   
   
...encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; .../>

You cannot use SOAP encoding with document style.

For best interoperability with .NET, use this configuration:

   
   

Anne

On 7/16/07, Srinivasa Rao K  wrote:
> Hi,
>
> I need some help on Web Services Interoperability.
> We have an applicati0n on WebShphere 6 (RAD Development environment) and Web
> Services are working fine with Java(Axis) Client environment. But one client
> is trying to access  the same services from .Net/C# environment and we are
> not successful.
>
> WSDLs:
>
> The WSDL fils are generated dynamically and we have one service with 4
> different names
> and in each service Style/Use and encoding are different, configuration in
> server-config.wsdd
> file as follows:
>
> 
> 
> ...encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
> .../>
>
> 
> 
>
> 
> 
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/".../>
>
> 
> 
>
> All these 4 services point to a single service.
>
> Now my question is, which WSDL file generated out of the four services
> should be used
> for .Net/C# client.  Any additional things need to be done for this
> interoperablity?
>
> I really appreciate any kind of help regarding the same.
>
> Thanks in advance.
>
> Regards
> Srinivas.
>
>
>  ________________________________
> Get the free Yahoo! toolbar and rest assured with the added security of
> spyware protection.
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



 
---------------------------------
Finding fabulous fares is fun.
Let Yahoo! FareChase search your favorite travel sites to find flight and hotel 
bargains.

Reply via email to