The org.apache.wsif.wsdl package contains classes used at runtime so
perhaps we should move the wsdl2java class to a different package. How
about the following suggestions:
org.apache.wsif.wsdl.tools
or
org.apache.wsif.tools
If we want to keep all Axis dependant classes under the Axis provider, then
we might want:
org.apache.wsif.providers.soap.apacheaxis.tools
or
org.apache.wsif.providers.soap.apacheaxis.wsdl
Just some ideas. Comments?
Owen
|---------+---------------------------->
| | Anthony |
| | Elder/UK/[EMAIL PROTECTED]|
| | B |
| | |
| | 11/03/2003 12:08 |
| | Please respond to|
| | wsif-dev |
| | |
|---------+---------------------------->
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: WSIF WSDL2Java
|
|
|
|
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
I've committed a hack to the AXIS WSDL2Java tool for WSIF in
org.apache.wsif.wsdl.WSDL2Java. It changes WSDL2Java to not generate the
classes WSIF doesn't use, so only generate the complex type classes and
service endpoint interface, and a WSIF specific testcase The testcase can
use either stubs or the DII or both. For example:
java org.apache.axis.wsdl.WSDL2Java -v -o\Temp -pbabel -tboth
http://www.xmethods.net/sd/2001/BabelFishService.wsdl
This makes another WSIF dependency on AXIS so maybe it shouldn't be there
at all? Perhaps it should be in a different package? And I'm open to
suggestions for a better format of the generated testcase?
...ant
Anthony Elder
[EMAIL PROTECTED]
Web Services Development
IBM UK Laboratories, Hursley Park
(+44) 01962 818320, x248320, MP208.
