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 help
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
soap:body use=literal/ Axis still tries to interpret any type
information present
in the soap body.
My soap response
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
Schie, Sjaak van wrote:
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
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.
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 I am
James Black wrote:
In my wsdl file (generated by java2wsdl) it uses type.
wsdl:message name=lookupAccessResponse3
wsdl:part name=lookupAccessReturn type=intf:ArrayOf_tns2_Access/
/wsdl:message
complexType name=ArrayOf_tns2_Access
complexContent
restriction base=soapenc:Array
Daniel Hägg wrote:
Is that document/literal or rpc/encoded ?
setOperationStyle is rpc, so I will assume rpc/encoded.
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.
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; - class
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 the
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 solve
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 jars
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 may want
14 matches
Mail list logo
