Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 72645 invoked from network); 4 Dec 2006 15:46:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Dec 2006 15:46:57 -0000 Received: (qmail 37217 invoked by uid 500); 4 Dec 2006 15:46:57 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 37202 invoked by uid 500); 4 Dec 2006 15:46:57 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 37191 invoked by uid 99); 4 Dec 2006 15:46:56 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Dec 2006 07:46:56 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [206.206.38.185] (HELO brightmail.idfbins.com) (206.206.38.185) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Dec 2006 07:46:45 -0800 Received: from brightmail.idfbins.com (unknown [127.0.0.1]) by brightmail.idfbins.com (Symantec Mail Security) with ESMTP id 668EF40402 for ; Mon, 4 Dec 2006 08:46:24 -0700 (MST) X-AuditID: 0a647012-b0591bb000000a32-12-457442cf5d46 Received: from smtp.idfbins.com (fbms2003.idfbins.com [10.100.112.3]) by brightmail.idfbins.com (Symantec Mail Security) with ESMTP id 1EC01403BA for ; Mon, 4 Dec 2006 08:46:23 -0700 (MST) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C717BB.5976F75B" X-MimeOLE: Produced By Microsoft Exchange V6.5 Subject: How Can I Handle a Microsoft char data type from Axis client Date: Mon, 4 Dec 2006 08:47:12 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: How Can I Handle a Microsoft char data type from Axis client Thread-Index: AccXu3ckiBVv95AKS6W5QeRzrvfiFw== From: "James Frankman" To: X-Brightmail-Tracker: AAAAAA== X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C717BB.5976F75B Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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 Microsoft char data type:=20 =20 =20 =20 =20 For some reason Apache axis tries to map this char datatype to an "UnsignedShort". So when the soap envelope is sent to the .NET service it contains:=20 =20 1 =20 =20 =20 instead of something like:=20 =20 =20 1=20 (where namespace q0=3D"http://microsoft.com/wsdl/types/")=20 =20 =20 The causes the web service call to fail because the .NET web service is expecting a char datatype, not an unsignedShort. How can I configure Apache Axis so that the client will send the Microsoft char type in the soap envelope:=20 =20 =20 1 =20 ------_=_NextPart_001_01C717BB.5976F75B Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

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 Microsoft char data type:

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

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

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

instead of something like: =

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

(where namespace = q0=3D"http://microsoft.com/wsdl/types/")

The causes the web service call to fail because the = .NET web service is expecting a char datatype, not an unsignedShort. How can I = configure Apache Axis so that the client will send the Microsoft char type in the = soap envelope:

------_=_NextPart_001_01C717BB.5976F75B--