Daniel,
SDK/JRE 1.4(.1) has its own XML parser.
SDK/JRE <1.4 doesn't have a XML parser.
Removing the XML parser is not an option, because a XML parser is needed.
James, however, stated that he stopped using crimsom (XML parser) and used
the xerces one instead.
However I think that your problem is different.
You are revering to element name in the part like:
<message name="InAllConfigurations">
<part name="parameters" element="s0:RequestAllConfigurations" />
</message>
<message name="OutAllConfigurations">
<part name="parameters" element="s0:AllConfigurationsResponse" />
</message>
This is all correct WSDL, but I have bad experience with this (both .Net &
.AXIS).
The WSDL2Java generation creates stub code with invalid operation names and
parameter types/serialization.
When I changed element=xxx to type=xxx, it all works (both toolkits).
Sjaak
> -----Original Message-----
> From: Daniel Hägg [mailto:[EMAIL PROTECTED]]
> Sent: 02 October, 2002 10:34
> To: [EMAIL PROTECTED]
> Subject: Re: SAXException Bad types
>
>
> James Black wrote:
>
> >You may want to rename crimson.jar to crimson.jar.old, but
> also look in java_home/jre/lib/ext and see what is there.
> You will want to only refer to one xml parser.
> >
> I have tried renaming crimson.jar, but it did not help. I have also
> tried to remove the classpath to crimson,
> and that gave me a NoClassDefFoundError org/w3c/dom/Node.
> This makes me
> believe
> that there are no other xmlparser refered to. I found no jar files in
> jre/lib/ext that looked like xml parsers.
> I also tried "downgrading" to java 1.3.1 and got the same result.
>
> The error seems to be related to returning arrays from the
> server to the
> axis client.
> The error does not occur if I pass simple types like int.
>
> /
> / Daniel
>
>
--
The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.
