[idfbins]

I am trying to consume a web service written in .NET. When I generate the client using Apache Axis, most of the methods work. However, in the WSDL for the web service I am trying to consume some elements are defined as a char data type:

<s:element minOccurs="1" maxOccurs="1" name="Status" type="s1:char"/> 

For some reason Apache axis trys to map this char datatype to an “UnsignedShort”. So when the soap envelope is sent to the .NET service it contains:

<Status xsi:type="xsd:unsignedShort">1</Status> 

instead of something like:

<Status xsi:type="q0:char">1</Status>

(where namespace q0=”http://microsoft.com/wsdl/types/”)

The causes the web service to fail. How can I configure Apache Axis so that the client will send the Microsoft char type in the soap envelope:

<Status xsi:type="q0:char">1</Status> 
 

[Brian Fernandes]

Hi,

MyEclipse ships with XFire Web Services and we do not support Axis yet. The axis web services are features of the WTP plugins which are also shipped with MyEclipse (these are usually off unless explicitly turned on).

Since your question does not really pertain to the plugins but actual WS development, I’d suggest asking on the Axis mailing list or forums. You can find the Axis mailing list and archives here: http://ws.apache.org/axis/mail.html

Hope this helps,

[idfbins]

I would use the MyEclipse XFire plugin but it does not support RPC encoding. That is why we are trying to use Axis. So am I correct in stating that the MyEclipse product only supports document style web services? If this is correct then IMHO you have a huge gap in the types of web services the the MyEclipse IDE can handle. It not like I can call each WS provider and ask them to change their encoding from rpc to document because MyEclipse only handles document style web services.

[Author]

Posts