Re: WSDL2Java and one-way binding

[Benjamin Fan]

I've given up on service-generated-WSDL - I hand-cut/validate WSDL and use WSDL2Java to generate both the server-side skeleton and the client side stubs. I haven't done it yet but I'm told its straight forward to modify the generated code to return static WSDL files rather than genertaing WSDL on the fly. ANy chance of you manually maintaining the generated skeleton? This is what I'm going to have to do...

On 6/29/06, John Mani <[EMAIL PROTECTED]> wrote:

Hi all

Any comments on the below issue ? I'd expect this to be a common scenario .. so am I
misunderstanding something ?

thanx
-john

________________________________

From: John Mani [mailto:[EMAIL PROTECTED]]
Sent: Tue 6/27/2006 6:53 PM
To: axis-user@ws.apache.org
Subject: WSDL2Java and one-way binding


I'm using Axis 1.4 WSDL2Java to generate skeletons for a webservice from a WSDL doc.

The source WSDL (generated by .NET) uses one-way binding - it just specifies a
<wsdl:input> element, no <wsdl:output> element.

However, the generated skeleton code seems to be including a response to the request.
This is proven by checking the deployed skeleton's WSDL (deployed in tomcat, using
the axis war) - it contains  <wsdl:input> and <WSDL:output> messages. Also, when
I run the .NET client against the deployed skeleton, the client complaints about the
unexpected entity body in the response.

Any comments/help ?

thanx
-jm

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]