soap-enc:Array is a SOAP 1.2 creature.  MS probably only supports SOAP 1.1.
Try creating WSDL using Java2WSDL with the following option:
--typeMappingVersion 1.1.

Russell Butek
[EMAIL PROTECTED]


"Edward Gemar" <[EMAIL PROTECTED]> on 04/01/2002 03:46:19 PM

Please respond to [EMAIL PROTECTED]

To:    <[EMAIL PROTECTED]>
cc:
Subject:    Is interoperability really possible...





Hi all,

����������� We are attempting to use axis to expose EJB'sto a .net client
using axis.� We have the web service deploying fine, but when we use MS's
wsdl.exe to generate the c# proxies based on axis' WSDL we get the
following errors:



Schema validation warning: Type
'http://schemas.xmlsoap.org/soap/encoding/:Array

' isnot declared.

Schema validation warning: Type
'http://schemas.xmlsoap.org/soap/encoding/:Array

' isnot declared.

Schema validation warning: Type 'http://www.w3.org/2001/XMLSchema:Calendar'
is n

otdeclared.

Schema validation warning: Type
'http://schemas.xmlsoap.org/soap/encoding/:Array

' isnot declared.



Any ideas?� The arrays we are returning are complex types and the Calendar
class is java.util.Calendar.� I haven't seen any examples of web service
interoperability outside of simple methods returning built-in types.� Is
interoperability of non-trivial web services really possible yet?



����������� Edward





Edward Gemar

ForwardVue Technologies, Inc.

Austin, TX

Vox: 512-482-5126

Fax: 512-651-3209




Reply via email to