You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Srinivasa Rao K <re...@yahoo.com> on 2007/07/16 18:38:17 UTC
Web Services Interoperability
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:
<service name="service1" provider="java:RPC" style="document"
<typeMapping ...encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" .../>
<service name="service2" provider="java:RPC" style="document" use="literal">
<typeMapping ...encodingStyle="" .../>
<service name="service3" provider="java:RPC">
<typeMapping ... encodingStyle="http://schemas.xmlsoap.org/soap/encoding/".../>
<service name="service4" provider="java:RPC" use="literal">
<typeMapping ... encodingStyle="" .../>
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.
Re: Web Services Interoperability
Posted by Srinivasa Rao K <re...@yahoo.com>.
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 <at...@gmail.com> 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: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------
Finding fabulous fares is fun.
Let Yahoo! FareChase search your favorite travel sites to find flight and hotel bargains.
Re: Web Services Interoperability
Posted by Anne Thomas Manes <at...@gmail.com>.
Srinivas,
This configuration is not valid:
<service name="service1" provider="java:RPC" style="document"
<typeMapping
...encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" .../>
You cannot use SOAP encoding with document style.
For best interoperability with .NET, use this configuration:
<service name="service2" provider="java:RPC" style="wrapped" use="literal">
<typeMapping ...encodingStyle="" .../>
Anne
On 7/16/07, Srinivasa Rao K <re...@yahoo.com> 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:
>
> <service name="service1" provider="java:RPC" style="document"
> <typeMapping
> ...encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
> .../>
>
> <service name="service2" provider="java:RPC" style="document" use="literal">
> <typeMapping ...encodingStyle="" .../>
>
> <service name="service3" provider="java:RPC">
> <typeMapping ...
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/".../>
>
> <service name="service4" provider="java:RPC" use="literal">
> <typeMapping ... encodingStyle="" .../>
>
> 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: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Web Services Interoperability
Posted by Eran Chinthaka <ch...@opensource.lk>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jorge Fernandez wrote:
> Hi,
>
> I have a doubt related with interoperability. I'm using soap session and
> I realized that ServiceGroupID has an axis2 namespace so I think this
> would make my servie incompatible with some clients. Is this right?? Any
> of the session scopes is compatible between all plataforms??
Axis2 service groupId is meant to be used if you have your service
deployed in an Axis2 server. This header is used if you want to maintain
a session between invocations.
Having said that, the presence of this header doesn't harm
interoperability in any means. This header doesn't have
mustUnderstand=true, so any SOAP engine can ignore this and still work
without a problem. As I mentioned earlier also you will see this header
only if you are using Axis2 server. But the server doesn't expect this
header all the times. If it is present it will try to maintain the
session and if it is not there, you won't have any session.
The web service client can simply ignore this header when it is
processing the SOAP message.
Think about this header as an optional optimization mechanism, if Axis2
server and Axis2 client are used to invoke related services.
HTH.
Chinthaka
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGnXtejON2uBzUhh8RAqByAJ9fuMvnZS1lXAXCeQJxcIcPCI2pNgCgjo6t
Mz1YxdO85mg7PnknOPLx05U=
=oU36
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: Web Services Interoperability
Posted by Jorge Fernandez <in...@yahoo.es>.
Hi,
I have a doubt related with interoperability. I'm using soap session and I realized that ServiceGroupID has an axis2 namespace so I think this would make my servie incompatible with some clients. Is this right?? Any of the session scopes is compatible between all plataforms??
Thanks and regards,
Jorge Fernández
Srinivasa Rao K <re...@yahoo.com> escribió: Thank you!
To be honest, WS-Addressing is new for me and I think we are not using the Adressing.
Thanks
Zachary Marshall <Za...@sas.com> wrote:
Are you using WS-Addressing? I had an interoperability problem going the other way, from Java client to .NET service. The problem was with mismatched namespaces. In that case, the following fixed the problem:
_options.setProperty(AddressingConstants.WS_ADDRESSING_VERSION, AddressingConstants.Submission.WSA_NAMESPACE);
Obviously, since you have a .NET client and a Java server, this might not be the issue. If you are using WS-Addressing, then I would examine the payload sent from .NET and ensure the namespaces match what you expect for your Java server.
I can't specifically address your second question.
---------------------------------
From: Srinivasa Rao K [mailto:reach2srinivas@yahoo.com]
Sent: Monday, July 16, 2007 12:38 PM
To: axis-user@ws.apache.org
Subject: Web Services Interoperability
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:
<service name="service1" provider="java:RPC" style="document"
<typeMapping ...encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" .../>
<service name="service2" provider="java:RPC" style="document" use="literal">
<typeMapping ...encodingStyle="" .../>
<service name="service3" provider="java:RPC">
<typeMapping ... encodingStyle="http://schemas.xmlsoap.org/soap/encoding/".../>
<service name="service4" provider="java:RPC" use="literal">
<typeMapping ... encodingStyle="" .../>
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.
---------------------------------
Be a better Globetrotter. Get better travel answers from someone who knows.
Yahoo! Answers - Check it out.
---------------------------------
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
RE: Web Services Interoperability
Posted by Srinivasa Rao K <re...@yahoo.com>.
Thank you!
To be honest, WS-Addressing is new for me and I think we are not using the Adressing.
Thanks
Zachary Marshall <Za...@sas.com> wrote:
Are you using WS-Addressing? I had an interoperability problem going the other way, from Java client to .NET service. The problem was with mismatched namespaces. In that case, the following fixed the problem:
_options.setProperty(AddressingConstants.WS_ADDRESSING_VERSION, AddressingConstants.Submission.WSA_NAMESPACE);
Obviously, since you have a .NET client and a Java server, this might not be the issue. If you are using WS-Addressing, then I would examine the payload sent from .NET and ensure the namespaces match what you expect for your Java server.
I can't specifically address your second question.
---------------------------------
From: Srinivasa Rao K [mailto:reach2srinivas@yahoo.com]
Sent: Monday, July 16, 2007 12:38 PM
To: axis-user@ws.apache.org
Subject: Web Services Interoperability
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:
<service name="service1" provider="java:RPC" style="document"
<typeMapping ...encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" .../>
<service name="service2" provider="java:RPC" style="document" use="literal">
<typeMapping ...encodingStyle="" .../>
<service name="service3" provider="java:RPC">
<typeMapping ... encodingStyle="http://schemas.xmlsoap.org/soap/encoding/".../>
<service name="service4" provider="java:RPC" use="literal">
<typeMapping ... encodingStyle="" .../>
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.
---------------------------------
Be a better Globetrotter. Get better travel answers from someone who knows.
Yahoo! Answers - Check it out.
RE: Web Services Interoperability
Posted by Zachary Marshall <Za...@sas.com>.
Are you using WS-Addressing? I had an interoperability problem going the other way, from Java client to .NET service. The problem was with mismatched namespaces. In that case, the following fixed the problem:
_options.setProperty(AddressingConstants.WS_ADDRESSING_VERSION, AddressingConstants.Submission.WSA_NAMESPACE);
Obviously, since you have a .NET client and a Java server, this might not be the issue. If you are using WS-Addressing, then I would examine the payload sent from .NET and ensure the namespaces match what you expect for your Java server.
I can't specifically address your second question.
________________________________
From: Srinivasa Rao K [mailto:reach2srinivas@yahoo.com]
Sent: Monday, July 16, 2007 12:38 PM
To: axis-user@ws.apache.org
Subject: Web Services Interoperability
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:
<service name="service1" provider="java:RPC" style="document"
<typeMapping ...encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" .../>
<service name="service2" provider="java:RPC" style="document" use="literal">
<typeMapping ...encodingStyle="" .../>
<service name="service3" provider="java:RPC">
<typeMapping ... encodingStyle="http://schemas.xmlsoap.org/soap/encoding/".../>
<service name="service4" provider="java:RPC" use="literal">
<typeMapping ... encodingStyle="" .../>
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 <http://us.rd.yahoo.com/evt=48226/*http://new.toolbar.yahoo.com/toolbar/features/norton/index.php> and rest assured with the added security of spyware protection.