Your WSDL is not valid.
When using document style, your message part definitions must
reference elements rather than types. You can only reference types if
you are using RPC style. You have two choices:
1. Define a schema in the <wsdl:types> section and define your message
structures as elements, and change your <wsdl:part> definitions to
point to the appropriate elements. (NOTE that with Document style, a
message may contain at most one part -- if your operation has multiple
parameters, you must define a wrapper element for those parameters).
2. You can switch to RPC style, but then you must add a namespace
attribute to the <soap:body> definitions, e.g.,
<soap:body use="literal" namespace="http://new.webservice.namespace"/>
Anne
On 12/20/06, Nate - Hotmail <[EMAIL PROTECTED]> wrote:
Amila,
I have attached a simple wsdl (test.wsdl) that I have tried also and got
the same result (TestServiceSkeleton.java). I have part elements as part of
my output messages, but in the generated code the method signatures are
void. I am using Apache axis2-1.1, and executed the following command to
get the result:
WSDL2Java -uri test.wsdl -ss -sd
Thank you,
Nate Douglas
----- Original Message -----
From: Amila Suriarachchi
To: [email protected] ; Nate - Hotmail
Sent: Wednesday, December 20, 2006 1:41 AM
Subject: Re: WSDL2Java Issue
On 12/19/06, Nate - Hotmail <[EMAIL PROTECTED]> wrote:
>
>
> When I execute the WSDL2Java command, I get the skeleton code, but the
> generated signatures are all void when they shouldn't be. Is this
> normal for the code generation, and I just change the signatures as I
> need them,
no it should generate the code according to your messages defined in the
wsdl. it is *void* if you have messages without any part elements as output
messages.
>
>
> or should they have been correctly generated from the WSDL?
without looking your wsdl I can not really answer this question. Can you
please attach your wsdl or a simple wsdl which demonstrate your problem?
Amila
--
Amila Suriarachchi,
Software Engineer,
WSO2 Inc.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
