Ok...I answered my own question and switched back to JDK1.2_04 to compile and
that works, but the strings are still soap encoded when I run the client, and
therefore incompatible with .NET. Any hints? Has it just not been checked in
yet?
Also, is axis-ant.jar no longer part of the build or is i
Great! That clears it up. Unfortunately I can't get a clean compile out of the
latest CVS checkout. Inbetween the warnings about enum and deprecation warnings
(yes, yikes, JDK1.5). I get the following errors. Any advice on how to get just
WSDL2Java compiled?
[javac] /home/andym/ws-axis/java/s
Should be fixed in latest CVS.
-- dims
On Thu, 2 Dec 2004 16:11:13 -0800, Simon Fell <[EMAIL PROTECTED]> wrote:
> Yes, .NET doesn't support the soap encoding types. This seems to be a
> "feature" of axis 1.2, there was talk on the axis-dev list of changing
> this back to match axis 1.1, but I do
Yes, .NET doesn't support the soap encoding types. This seems to be a
"feature" of axis 1.2, there was talk on the axis-dev list of changing
this back to match axis 1.1, but I don't know what the current status of
that is.
Cheers
Simon
> -Original Message-
> From: ANDREW MICONE [mailto:[E
