Hello there,
I have been struggling recently with that article,using most
recent
Version of Castor and axis and got all problem solved (I have even
written my own ws following that model..
According to that article, u have to start with the schema (.xsd) and
the
WSDL file
As article says, you should write a line like this
<soap:binding style="document">
<operation.....>
<soap:operation style="document">
don't forget to rebuild axis with castor serializer.
Axis1.2beta has castor serializer included, but it won't be part
Of axis by default....
Hope this helps
If not, send me ur code and I'll try to make it work :-)
Regards
marco
-----Original Message-----
From: Peter White [mailto:[EMAIL PROTECTED]
Sent: 10 September 2004 20:50
To: [EMAIL PROTECTED]
Subject: RE: A Document confusion
Hmmm, it does seem that you have everything reference and such, which is
cool, and you say you have all the serializing worked out...
You have an extra "wsdl:types" element in your wsdl... But it might not
be the problem
The problem might be that axis doesn't seem to like upper-case starting
letters in wrapped complex types passed into requests. Thus,
MortgageApplication in addUserType might have to become
mortgageApplication and so on... Otherwise the serializers won't be
happy. But you say you've fixed the de/serializers, and my (limited)
experience with axis has been using the auto-generated beans by stuffing
all the types into the WSDL I'm using to create java... but it's neat to
see how you've referenced and set up de/serializers in the deploy.wsdd
to go to other classes you've created... Maybe it's expecting you to
create the source for de/serializing the string if you're not including
the types into the WSDL your passing to WSDL2Java??
I don't have much experience with Castor, so I might not be helping you
much here... Perhaps if you pasted the types from the import into
WSDL2Java it would let you see some of the serialization logic in the
beans that were generated and see how it's different from the
serializers you're using (I remember seeing a few flags being set when
types were being mapped)
Hope this helps
Peter
-----Original Message-----
From: Robert Bateman [mailto:[EMAIL PROTECTED]
Sent: Friday, September 10, 2004 3:03 PM
To: [EMAIL PROTECTED]
Subject: A Document confusion
Apologies up front - I'm still new to Axis...
I've been folowing the Axis / Castor write up over on IBM's web site.
I've done everything in the writeup and understand (I think) up thru the
deploy step.
My environment:
Linux
Tomcat 5.0.25
Axis 1.2 beta 3
I've put together a WSDL for a User Registration web service (attached
below) that I'm playing with. The web service is supposed to accept an
XML document as input. I haven't yet gotten to the output side so I've
left output out of the wsdl (for the moment.)
I've gone thru the Axis and Castor source steps. I have a deploy.wsdd
file now that needs to be deployed (please note that the wsdd file
attached needs to be fixed to point to the proper de/serializer - that's
not my problem here... I have fixed the de/serializer in the wsdd file
that I'm attempting to deploy.)
2 things are bothering me about the deploy.wsdd file that is generated:
1) I followed the instructions for creating the Axis / Castor source.
But my source doesn't appear to be serializing a String (i.e. not using
the wrapped
style) I didn't include -W when I ran WSDL2Java, so I'm confused about
what's happening here.
2) If the generated code is not using the wrapped style, is it because I
messed up the WSDL? Or is there possible a bug I've run across?
Thanks much for your time!
Bob
