I am getting SAXException Bad types
(class RemotableExampleTypes.TExample -> int)
and do not know how to diagnose the problem.
My web service is a Delphi 7 app, so I used
WSDL2Java to create the bindings from the WSDL.
The GetCust operation responds with the complex
type TExample. Any h
Hi!
If anyone is still reading this thread, I just thought I would tell you
that I have figured
out why I get the "Bad Types" exception. It turns out that even if the
WSDL says
Axis still tries to interpret any type
information present
in the soap body.
My soap response looks like this:
James Black wrote:
>setOperationStyle is rpc, so I will assume rpc/encoded.
>
I have given up on rpc/encoded (for the moment), because I cannot get
WSDL2Java
to generate deserializers for the array. And I also have problem with
C# in rpc mode.
Microsoft says that literal is "preferred" somewhe
Daniel Hägg wrote:
> Is that document/literal or rpc/encoded ?
setOperationStyle is rpc, so I will assume rpc/encoded.
James Black wrote:
>In my wsdl file (generated by java2wsdl) it uses type.
>
>
>
>
>
>
>
>
>
>
>
>
>
Is that document/literal or rpc/encoded ?
/
/ Daniel
Daniel Hägg wrote:
> Yeah, I have tried that too.
> It currently seems impossible to create a "real world" WSDL file that
> both .NET
> and Axis can handle. :-(
I am trying to figure out the problem I am having with rc2, but with
rc1 I had interoperability between C# and my web service.
Now
Daniel Hägg wrote:
> Schie, Sjaak van wrote:
>
> >When I changed element=xxx to type=xxx, it all works (both toolkits).
> >
> Can you please show me what your type definition looks like.
> It cannot be the same as when element=xxx is used.
In my wsdl file (generated by java2wsdl) it uses type.
Schie, Sjaak van wrote:
>Sorry I used rpc/encoded that gave problems on both toolkits.
>.Net would not import it and AXIS RC1 created bad stub code.
>
Yeah, I have tried that too.
It currently seems impossible to create a "real world" WSDL file that
both .NET
and Axis can handle. :-(
>James sug
L PROTECTED]]
> Sent: 02 October, 2002 12:48
> To: [EMAIL PROTECTED]
> Subject: Re: SAXException Bad types
>
>
>
> Schie, Sjaak van wrote:
>
> >You are revering to element name in the part like:
> >
> >
> >
> >
> >
> &
Schie, Sjaak van wrote:
>You are revering to element name in the part like:
>
>
>
>
>
>
>
>This is all correct WSDL, but I have bad experience with this (both .Net &
>.AXIS).
>
Really? But I have copied this from how .NET generates WSDL.
>When I changed element=xxx to type=xxx,
en 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:
>
&
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 crim
Daniel Hägg wrote:
> I have the following jars in my classpath.
>
> crimson-1.1.3\crimson.jar
> xml-axis-rc2\lib\axis.jar
> xml-axis-rc2\lib\jaxrpc.jar
> xml-axis-rc2\lib\saaj.jar
> xml-axis-rc2\lib\commons-logging.jar
> xml-axis-rc2\lib\commons-discovery.jar
> xml-axis-rc2\lib\wsdl4j.jar
You
James Black wrote:
>This is where I went to. The crimson.jar files I believe were old, but I am not
>certain. As I stated, updating my jar files helped me solve this problem. I am
>moving away from using java web service package and just
>going to the apache jar files.
>
I have the following
Daniel Hägg wrote:
> Are you saying that some jar files in the jdk should be replaced with
> jar files from xerces ?
> What jars? What version of xerces?
This is where I went to. The crimson.jar files I believe were old, but I am not
certain. As I stated, updating my jar files helped me solv
James Black wrote:
>You may want to update your jar files. I had recently updated to using the
>xmlsecurity jar file and stopped using crimson, with the jdk1.4 distro, and started
>to use the updated jar files for xml from apache (xerces).
> You may want to do the same thing, it should solve t
Daniel Hägg wrote:
> The SOAP communications looks fine (see attachment).
> But I get the following error when the response is deserialized:
>
> 2002-okt-01 13:00:54 org.apache.axis.client.Call invoke
> ALLVARLIG: Exception:
> org.xml.sax.SAXException: Bad types (class [Ljava.lang.Object; -> clas
Daniel Hägg wrote:
> Hi!
> I have a web service with a WSDL that works fine with both
> soap implementations in Microsoft .NET (ATL and ASP).
> But I cannot get it to work with Axis 1.0 RC2.
I am getting this to happen now also. I am currently testing to see if it was
something I did, or not.
Hi!
I have a web service with a WSDL that works fine with both
soap implementations in Microsoft .NET (ATL and ASP).
But I cannot get it to work with Axis 1.0 RC2.
Generated java code like this (see attached wsdl):
java org.apache.axis.wsdl.WSDL2Java -p AxisClient.dab DabCtrlApi.wsdl
No probl
19 matches
Mail list logo
