lem below is caused because the AXIS example was
placing a namespace in the xml element that the .NET client was not:
vs.
G.
Greg Bobak
Senior Programmer Analyst
Cole National
-Original Message-
From: Bobak, Greg P. [mailto:[EMAIL PROTECTED]
Sent: Tuesday,
Title: .NET and Axis Namespace Incompatability
The nice thing about typing out a question
is that I often answer it myself. The problem below is caused because the AXIS
example was placing a namespace in the xml element that the .NET client was
not:
vs.
G.
Greg
Title: .NET and Axis Namespace Incompatability
Hi,
We are working on creating an Axis client for a .NET web service. Our Axis client, created primarily with WSDL2java, creates the following SOAP body:
http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="Cred
