Hi Alex,
You'll probably have a much easier time of it if you use Jibx2Wsdl
(included in the current 1.2.1 release of JiBX) rather than Java2WSDL.
Jibx2Wsdl has a number of nice features, including Java 5 typed
collection and enum support, automatic JavaDoc extraction to WSDL and
schema documentation, and extensive customizations support. To include
extra classes in your data model (such as the subclasses in your
example), you just need to specify the extra classes on the command line
using an '-x' argument flag. See the /examples/jibx2wsdl/example3 code
and build for an example doing just this, using an interface rather than
an abstract class.
Using Jibx2Wsdl in no way commits you to using JiBX for your services
(though it's easy to do so, since you get JiBX bindings out of Jibx2Wsdl
as well as the WSDL and schema).
See the Jibx2Wsdl documentation on the JiBX site (still somewhat
limited, unfortunately) for details:
http://jibx.sourceforge.net/fromcode/jibx2wsdl.html
- Dennis
Dennis M. Sosnoski
SOA and Web Services in Java
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
Alexander Rosemann wrote:
Hi,
I know, this has been asked before, though I couldn't find an answer
to it.
I'm busy fiddling around with the Java2WSDL ant task shipped with
Axis2. The tool works fine until I try to generate the WSDL from an
abstract class.
Having an abstract class called Animal and a subclass Dog, it creates
the schema for the Animal but misses out on the Dog type.
I presume I just can't see what parameter has to be set to get this
going.
Any pointers that lead to a resolution of my issue are much appreciated.
Thanks,
Alex
