Is there any way to generate /properly completed/ skeleton java classes
when using
the WSDL2Java tool when exposing the Java web service with Axis?
(ver 1.2.1)
We have about 200 classes - each with about 6 methods - sitting in a jar
file that we
want to expose via Axis web services. If we were to do this manually,
it would take
us an eternity viz. completing the implementation skeleton classes so
that the
parameters are "forwarded" properly to the correct classes, and then testing
our work thereafter!
We've managed to use the Java2WSDL tool successfully and Axis has
created our
doc/literal WSDL files. Great stuff. However, the next step is to
create skeleton
classes using the WSDL2Java tool and it is here we found out that Axis
simply creates
"empty" classes often with it's own interpretation of what is to be
eventually called by the
skeleton class and what's to returned by the web service. Many
documents suggest
we ought to change the skeleton (implementation) classes /manually/ so
that the correct
Java classes are referenced and called!!!
Is there any option for the WSDL2Java to actually read the contents of
the /original/
Java classes which were used by the Java2WSDL tool to create the WSDL
file and then simply call or reference those classes from the skeleton
classes - avoiding
any manual intervention?
Any ideas greatly appreciated,
Kind regards
Abdullah
