Thanks Brian. Looking through your wsdl and comparing
it to mine put me in the right direction. I put
together a smaller prototype where business object
getters/setters return only typed arrays for 1 - m
relationships. .Net wsdl.exe had no problems with the
Axis generated wsdl.
.Net did not
Thanks for the reply. What version Axis are your
working with? I understand doc literal is the way to
go but I was also under the impression that some
people had this working with soap rpc encoding.
My goal is to get this working with as little effort
as possible. That's why I started with
generated by
Axis.
Brian Davis
Software Developer
JMM Ventures
-Original Message-
From: John Deviney [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 06, 2005 6:35 PM
To: [EMAIL PROTECTED]
Subject: Axis - .Net Interop Problems
Problem:
The .Net 1.1 wsdl tool does
Problem:
The .Net 1.1 wsdl tool does not like the wsdl
generated by Axis 1.1. The datatype 'Array' is
missing.
Environment:
Jboss 3.2.3/Axis 1.1 - .NET 1.1
Hosting services via Axis SOAP RPC Encoding which
include complex types and arrays of other complex
types.
I've
)
at sun.rmi.transport.Transport.serviceCall(Transport.java:143)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:7
01)
John Deviney
Texas Windstorm Insurance Association
5700 S. MoPac Exp
I should also include information about my environment:
Axis 1.0 or whatever version was bundled by default in jboss, deployed in
Jboss 3.2.2
John Deviney
Texas Windstorm Insurance Association
5700 S. MoPac Exp., Building E, Suite 530
Austin, TX 78749
[EMAIL PROTECTED]
-Original Message
