You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Nirmal Mukhi <nm...@us.ibm.com> on 2003/03/11 18:37:10 UTC
Re: WSIF WSDL2Java
Hi,
WSDL tools, not related specifically to WSIF or Axis, should be shared.
They would be of interest to any project within ws.apache.org and should
belong to a common project, say ws-commons or something like that, IMHO.
In WSDL2Java alone we have the following code, split between the Axis
version and new WSIF version (which has some minor differences with the
Axis one, see below):
1. Code to parse WSDL types, generate java classes for user-defined types
2. Code to parse WSDL port type, message and generate stub interfaces
3. Code to generate Axis stubs and related classes
4. Code to generate WSIF test cases
(1) and (2) belong to ws-commons. (3) belongs within Axis, (4) belongs
within WSIF. Right now I don't have any strong preferences over where the
common code should go (as of today it is duplicated between Axis and
WSIF), but eventually we should reorganize along the above lines.
Nirmal.
"Owen D Burroughs" <OW...@uk.ibm.com>
03/11/2003 08:42 AM
Please respond to wsif-dev
To: wsif-dev@ws.apache.org
cc:
Subject: Re: WSIF WSDL2Java
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/IBM@IBMG|
| | B |
| | |
| | 11/03/2003 12:08 |
| | Please respond to|
| | wsif-dev |
| | |
|---------+---------------------------->
>--------------------------------------------------------------------------------------------------------------------------------------------------|
| |
| To: wsif-dev@ws.apache.org |
| 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
ant.elder@uk.ibm.com
Web Services Development
IBM UK Laboratories, Hursley Park
(+44) 01962 818320, x248320, MP208.
Re: WSIF WSDL2Java
Posted by Paul Fremantle <pz...@hursley.ibm.com>.
Nirmal
I agree!
We should specifically factor out the JAX-RPC neutral code. Both Axis and WSIF are designed to use the JAX-RPC SEI definition, and this should be available independent of implementation. When we moved WSIF to use the SEI, the whole point was to *share* tools with JAX-RPC. So what would be nice is if the core code generated the interfaces neutrally, and then subclasses generated any implementation specific code.
Paul
----- Original Message -----
From: Nirmal Mukhi
To: axis-dev@ws.apache.org ; wsif-dev@ws.apache.org
Sent: Tuesday, March 11, 2003 5:43 PM
Subject: Re: WSIF WSDL2Java
Hi,
Just a clarification: the WSIF version of the WSDL2Java tool doesn't duplicate the Axis code, it overrides some methods. So what I was saying is that the common code should be factored out of the Axis WSDL2Java code and Axis will extend it (to generate Axis stubs) and WSIF will extend it (to generate WSIF test cases), so we share the stub interface and java type generation in a clean way.
Nirmal.
Nirmal Mukhi/Watson/IBM@IBMUS
03/11/2003 12:37 PM
Please respond to wsif-dev
To: wsif-dev@ws.apache.org, axis-dev@ws.apache.org
cc:
Subject: Re: WSIF WSDL2Java
Hi,
WSDL tools, not related specifically to WSIF or Axis, should be shared. They would be of interest to any project within ws.apache.org and should belong to a common project, say ws-commons or something like that, IMHO.
In WSDL2Java alone we have the following code, split between the Axis version and new WSIF version (which has some minor differences with the Axis one, see below):
1. Code to parse WSDL types, generate java classes for user-defined types
2. Code to parse WSDL port type, message and generate stub interfaces
3. Code to generate Axis stubs and related classes
4. Code to generate WSIF test cases
(1) and (2) belong to ws-commons. (3) belongs within Axis, (4) belongs within WSIF. Right now I don't have any strong preferences over where the common code should go (as of today it is duplicated between Axis and WSIF), but eventually we should reorganize along the above lines.
Nirmal.
"Owen D Burroughs" <OW...@uk.ibm.com>
03/11/2003 08:42 AM
Please respond to wsif-dev
To: wsif-dev@ws.apache.org
cc:
Subject: Re: WSIF WSDL2Java
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/IBM@IBMG|
| | B |
| | |
| | 11/03/2003 12:08 |
| | Please respond to|
| | wsif-dev |
| | |
|---------+---------------------------->
>--------------------------------------------------------------------------------------------------------------------------------------------------|
| |
| To: wsif-dev@ws.apache.org |
| 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
ant.elder@uk.ibm.com
Web Services Development
IBM UK Laboratories, Hursley Park
(+44) 01962 818320, x248320, MP208.
Re: WSIF WSDL2Java
Posted by Nirmal Mukhi <nm...@us.ibm.com>.
Hi,
Just a clarification: the WSIF version of the WSDL2Java tool doesn't
duplicate the Axis code, it overrides some methods. So what I was saying
is that the common code should be factored out of the Axis WSDL2Java code
and Axis will extend it (to generate Axis stubs) and WSIF will extend it
(to generate WSIF test cases), so we share the stub interface and java
type generation in a clean way.
Nirmal.
Nirmal Mukhi/Watson/IBM@IBMUS
03/11/2003 12:37 PM
Please respond to wsif-dev
To: wsif-dev@ws.apache.org, axis-dev@ws.apache.org
cc:
Subject: Re: WSIF WSDL2Java
Hi,
WSDL tools, not related specifically to WSIF or Axis, should be shared.
They would be of interest to any project within ws.apache.org and should
belong to a common project, say ws-commons or something like that, IMHO.
In WSDL2Java alone we have the following code, split between the Axis
version and new WSIF version (which has some minor differences with the
Axis one, see below):
1. Code to parse WSDL types, generate java classes for user-defined types
2. Code to parse WSDL port type, message and generate stub interfaces
3. Code to generate Axis stubs and related classes
4. Code to generate WSIF test cases
(1) and (2) belong to ws-commons. (3) belongs within Axis, (4) belongs
within WSIF. Right now I don't have any strong preferences over where the
common code should go (as of today it is duplicated between Axis and
WSIF), but eventually we should reorganize along the above lines.
Nirmal.
"Owen D Burroughs" <OW...@uk.ibm.com>
03/11/2003 08:42 AM
Please respond to wsif-dev
To: wsif-dev@ws.apache.org
cc:
Subject: Re: WSIF WSDL2Java
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/IBM@IBMG|
| | B |
| | |
| | 11/03/2003 12:08 |
| | Please respond to|
| | wsif-dev |
| | |
|---------+---------------------------->
>--------------------------------------------------------------------------------------------------------------------------------------------------|
| |
| To: wsif-dev@ws.apache.org |
| 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
ant.elder@uk.ibm.com
Web Services Development
IBM UK Laboratories, Hursley Park
(+44) 01962 818320, x248320, MP208.
Re: WSIF WSDL2Java
Posted by Nirmal Mukhi <nm...@us.ibm.com>.
Hi,
Just a clarification: the WSIF version of the WSDL2Java tool doesn't
duplicate the Axis code, it overrides some methods. So what I was saying
is that the common code should be factored out of the Axis WSDL2Java code
and Axis will extend it (to generate Axis stubs) and WSIF will extend it
(to generate WSIF test cases), so we share the stub interface and java
type generation in a clean way.
Nirmal.
Nirmal Mukhi/Watson/IBM@IBMUS
03/11/2003 12:37 PM
Please respond to wsif-dev
To: wsif-dev@ws.apache.org, axis-dev@ws.apache.org
cc:
Subject: Re: WSIF WSDL2Java
Hi,
WSDL tools, not related specifically to WSIF or Axis, should be shared.
They would be of interest to any project within ws.apache.org and should
belong to a common project, say ws-commons or something like that, IMHO.
In WSDL2Java alone we have the following code, split between the Axis
version and new WSIF version (which has some minor differences with the
Axis one, see below):
1. Code to parse WSDL types, generate java classes for user-defined types
2. Code to parse WSDL port type, message and generate stub interfaces
3. Code to generate Axis stubs and related classes
4. Code to generate WSIF test cases
(1) and (2) belong to ws-commons. (3) belongs within Axis, (4) belongs
within WSIF. Right now I don't have any strong preferences over where the
common code should go (as of today it is duplicated between Axis and
WSIF), but eventually we should reorganize along the above lines.
Nirmal.
"Owen D Burroughs" <OW...@uk.ibm.com>
03/11/2003 08:42 AM
Please respond to wsif-dev
To: wsif-dev@ws.apache.org
cc:
Subject: Re: WSIF WSDL2Java
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/IBM@IBMG|
| | B |
| | |
| | 11/03/2003 12:08 |
| | Please respond to|
| | wsif-dev |
| | |
|---------+---------------------------->
>--------------------------------------------------------------------------------------------------------------------------------------------------|
| |
| To: wsif-dev@ws.apache.org |
| 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
ant.elder@uk.ibm.com
Web Services Development
IBM UK Laboratories, Hursley Park
(+44) 01962 818320, x248320, MP208.