Return-Path: Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 10739 invoked by uid 500); 11 Mar 2003 17:43:58 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 10721 invoked from network); 11 Mar 2003 17:43:57 -0000 In-Reply-To: To: axis-dev@ws.apache.org, wsif-dev@ws.apache.org MIME-Version: 1.0 Subject: Re: WSIF WSDL2Java X-Mailer: Lotus Notes Release 6.0 September 26, 2002 Message-ID: From: Nirmal Mukhi Date: Tue, 11 Mar 2003 12:43:56 -0500 X-MIMETrack: Serialize by Router on D01ML233/01/M/IBM(Release 6.0.1 [IBM]NP|March 10, 2003) at 03/11/2003 12:43:58, Serialize complete at 03/11/2003 12:43:58 Content-Type: multipart/alternative; boundary="=_alternative 0061688085256CE6_=" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N This is a multipart message in MIME format. --=_alternative 0061688085256CE6_= Content-Type: text/plain; charset="US-ASCII" 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" 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. --=_alternative 0061688085256CE6_= Content-Type: text/html; charset="US-ASCII"
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" <OWENB@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.
--=_alternative 0061688085256CE6_=--