A mock-up of the WSDL would certainly help us help you. At least tell us a little bit about the WSDL:
- does it validate? (using Cape Clear SOA Editor, SOAPScope, xmlspy, etc)
- what's its style and use?
- if it's doc/lit, is it wrapped or unwrapped?
- does it have any unusual schema structures?
- are there any particular structures that generate the errors?
- can you at least give us a mock-up of the structures that cause the errors?
Anne
On 11/9/05, Stefan Freyr Stefansson <[EMAIL PROTECTED]> wrote:
Hello.
First off, sorry for the long subject!
I've been having a terrible time creating a web service client in Java that
communicates with a .NET webservice.
For the record, unfortunately I can't show you the WSDL that I'm using to
generate code due to general paranoia. I do understand that this will make it
that much more difficult to answer my questions :o( I'll try to make some
sort of a mockup of it but that is a lot of work so I want to ask this first
to see if anyone can figure this out without the WSDL.
So the idea is basically to generate Java client code using one of Axis, Axis2
or JWSDP and use that code to communicate with the web service.
I've tried this with Axis 1.2.1, Axis 1.3, JWSDP 1.6 and Axis2. In short, Axis
1.2.1 is the only thing that works! Axis 1.3 and JWSDP 1.6 both have some
sort of a runtime exception when parsing XML. But what surprised me the most
was Axis2. I realize that it's not final yet but the fact that it produced
non-compilable code was a little more than I expected. Following is the error
I get (I get the same error in more than one place):
/home/stefan/hugsmidjan/test/consumer/src/axis2-generated/codegen/databinding/org/xmlsoap/schemas/ArrayTypeAttribute.java
Error: Error: line (19)package
schemaorg_apache_xmlbeans.system.sB0E21F2812E326300081920E02D527F9.TypeSystemHolder
does not exist
Anybody have any idea about what might be going on with these things? Are
there any major differences betwene Axis 1.2.1 and 1.3 that might result in
the fact that one works and the other one doesn't? Anybody have a clue as to
why Axis2 is producing code that doesn't compile?
I know this is all very vague and light on the details and for that I
apologise. I just thought maybe someone has had a similar experience whent
evaluating the different wsdl2java generators and might have some good
pointers to share.
Kind regards, Stefan Freyr.
