You can also specify the methods to expose,
using the -m option.
Tony
Tim K. wrote on 01/12/2004 19:21:04:
Vy Ho wrote:
I wonder if you declare an interface for this service, then use
it to
generate wsdl.
This shields you from how you implement your service.
Right, that's the
Which in effect does the same thing, it creates an interface for you
with only those methods, right?
Personally I prefer defining the interface myself rather than doing it
via command line options, you get more compile time checking and catch
mistakes early than deal with sometimes obscure
the WSDL cannot be dynamically generated.
-David
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Tim K. (Gmane)
Sent: Tuesday, November 30, 2004 5:53 PM
To: [EMAIL PROTECTED]
Subject: Re: Problem generating WSDL from Java
David Song wrote:
Hi all,
I am getting
I wonder if you declare an interface for this service, then use it to
generate wsdl.
This shields you from how you implement your service.
Vy Ho wrote:
I wonder if you declare an interface for this service, then use it to
generate wsdl.
This shields you from how you implement your service.
Right, that's the way to do it, just create an interface for only the
methods you want exposed. The class can have a lot more stuff in it that
Hi all,
I am getting the following error from Java2WSDL. It was working before,
I just changed some method signatures. Many thanks for the help!
-David
- The class org.apache.axis.MessageContext does not contain a default
constructor, which is a requirement for a bean class. The class cannot
David Song wrote:
Hi all,
I am getting the following error from Java2WSDL. It was working before,
I just changed some method signatures. Many thanks for the help!
-David
- The class org.apache.axis.MessageContext does not contain a default
constructor, which is a requirement for a bean class.
