Eclipse Community Forums: Eclipse Scout » Support for rpc encoded style web services

Help

Home

Home » Eclipse Projects » Eclipse Scout » Support for rpc encoded style web services

Show: Today's Messages :: Show Polls :: Message Navigator

Support for rpc encoded style web services [message #1325618]

Thu, 01 May 2014 09:44

Otmar Caduff

Messages: 3
Registered: November 2011

Junior Member

I have been given a WSDL with the following definitions (excerpt):

...
<soap:binding style="rpc" transport="[http transport*]"/>
...

and
...
<soap:body encodingStyle="[soap encoding stile*]" namespace="[client spcific details left out]" use="encoded"/>
...

Renownedly, Webservice integreation in a Scout application is supposed to be done using JAX-WS, however, JAX-WS does not seem to support this scheme:
(see question 412772 on stackoverflow.com*)

This apparingly still holds true for JAX-WS 2.2.

That post proposes using Axis. However, I know that Axis is not supported in a Scout environment.

Any suggestions on how to proceed?

*since I have posted fewer than 5 messages, eclipse.org prevents me from using links to sites other than elcipse.org... sorry for that

Report message to a moderator

Re: Support for rpc encoded style web services [message #1325633 is a reply to message #1325618]

Thu, 01 May 2014 09:53

Stephan Leicht Vogt

Messages: 104
Registered: July 2015

Senior Member

Hi Otmar

What is the problem on your side? This tutorial JAX-WS Hello World Example RPC Style explains how to build an JAX-WS (Version 2.2.4) Endpoint and Client RPC Style. Doesn't this work for you?

Greetings
Stephan

Report message to a moderator

Re: Support for rpc encoded style web services [message #1325648 is a reply to message #1325633]

Thu, 01 May 2014 10:01

Otmar Caduff

Messages: 3
Registered: November 2011

Junior Member

Hi Stephan

Thanks for your quick reply!

The subtle difference is in the WSDL: use="literal", which is supported by JAX-WS vs. use="encoded" which isn't.

I can generate stubs using Axis, but I'm not sure whether that's the way to go. JAX-WS complains:

parsing WSDL...

[ERROR] "Use of SOAP Encoding is not supported.
SOAP extension element on line 88 in file:/C:/[...] has use="encoded" "

Otmar

Report message to a moderator