Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 77235 invoked by uid 500); 12 Dec 2001 17:09:35 -0000 Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@xml.apache.org Received: (qmail 76519 invoked from network); 12 Dec 2001 17:09:24 -0000 Importance: Normal Subject: Re: ?WSDL now uses the new Java2WSDL emitter code To: axis-dev@xml.apache.org X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000 Message-ID: From: "Doug Davis" Date: Wed, 12 Dec 2001 12:09:18 -0500 X-MIMETrack: Serialize by Router on D04NM204/04/M/IBM(Release 5.0.8 |June 18, 2001) at 12/12/2001 12:09:19 PM MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Don't want to get into the middle of this but: ?wsdl&debug or ?wsdl&debug=3D1 would be nicer. (imo) -Dug R J Scheuerle Jr/Austin/IBM@IBMUS on 12/12/2001 12:04:48 PM Please respond to axis-dev@xml.apache.org To: axis-dev@xml.apache.org cc: Subject: Re: ?WSDL now uses the new Java2WSDL emitter code +1 to ?wsdl, ?wsdl-interface and wsdl-implementation. +1 to separate tool that would split an existing wsdl into component pa= rts. Then the Java2WSDL code wouldn't be polluted with all the extra functio= n. (volunteers to write this ?) It would also be nice to have ?wsdl-debug, ?wsdl-interface-debug and ?wsdl-implementation-debug for development purposes. =A0(Or provide ano= ther way to get debug information.) Comments ? Rich Scheuerle XML & Web Services Development 512-838-5115 =A0(IBM TL 678-5115) = =20 "Sanjiva Weerawarana" = =20 = =20 12/12/2001 10:22 AM =A0 =A0 =A0 =A0 c= c: =20 Please respond to =A0 =A0 =A0 =A0 S= ubject: =20 axis-dev Re: ?WSDL now use= s =20 the new Java2WSDL= =20 emitter code = =20 = =20 = =20 = =20 +1. Anything else would be major overkill from my point of view and would amount to make the ?WSDL feature a WSDL browser/navigator. Sanjiva. ----- Original Message ----- From: "Glen Daniels" To: Sent: Wednesday, December 12, 2001 10:07 PM Subject: RE: ?WSDL now uses the new Java2WSDL emitter code > > Why not just stick with ?wsdl and let users do the split themselves i= f they > want to? =A0Alternately, if people are really psyched about this, bui= ld a > command-line tool which can take a WSDL document and split it in vari= ous > interesting ways. > > I can pretty much see the utility of ?wsdlIface, so that other WSDL d= ocs can > import that, but that's as far as I think I'd want to go with this. > > --Glen > > > -----Original Message----- > > From: Russell Butek [mailto:butek@us.ibm.com] > > Sent: Wednesday, December 12, 2001 10:49 AM > > To: axis-dev@xml.apache.org > > Subject: Re: ?WSDL now uses the new Java2WSDL emitter code > > > > > > Just a suggestion. =A0Since we're talking WSDL, shouldn't we use WS= DL > > terminology here? =A0Interface and Implementation aren't WSDL > > terms. =A0Yeah, I > > know about the WSDL Best Practices doc, but I doubt most > > users will. =A0Maybe > > folks would want to split the WSDL in other ways? > > > > http://localhost/axis/services/StockQuoteService?WSDL+t+m+pt+b > > http://localhost/axis/services/StockQuoteService?WSDL+s > > > > Forgive my syntax, I don't know what it should be. =A0The first > > essentially > > says give me WSDL with types, messages, portTypes, and bindings. =A0= The > > second says give me WSDL with services. =A0Maybe we want some sort = of > > shorthand if y'all think Intf and Impl will be widely used, > > but do we want > > to only support those 2 splits? > > > > Russell Butek > > butek@us.ibm.com > > > > > > Ravi Kumar on 12/11/2001 07:16:03 PM > > > > Please respond to axis-dev@xml.apache.org > > > > To: =A0 axis-dev@xml.apache.org > > cc: > > Subject: =A0Re: ?WSDL now uses the new Java2WSDL emitter code > > > > > > > > sounds like a good idea. How about > > http://localhost/axis/services/StockQuoteService?WSDL > > http://localhost/axis/services/StockQuoteService?WSDLIntf > > http://localhost/axis/services/StockQuoteService?WSDLImpl > > > > Ravi > > JBuilder Development > > > > > > James M Snell wrote: I've been thinking about how we can > > support the split > > WSDL file approach > > that Java2Wsdl supports in the URL approach and here's one idea tha= t I > > came up with. Please let me know what you think. > > > > Rather than the URL pattern > > http://localhost/axis/services/StockQuoteService?WSDL to > > create a single > > WSDL document, why not something like: > > > > http://localhost/axis/services/StockQuoteService/Interface.wsdl and= > > http://localhost/axis/services/StockQuoteService/Impl.wsdl > > > > ?? Using this approach, we can do the on the fly WSDL generation an= d > > include support for UDDI at the same time. > > > > - James M Snell/Fresno/IBM > > Web services architecture and strategy > > Internet Emerging Technologies, IBM > > 544.9035 TIE line > > 559.587.1233 Office > > 919.486.0077 Voice Mail > > jasnell@us.ibm.com > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > Have I not commanded you? Be strong and courageous. Do not > > be terrified, > > > > do not be discouraged, for the Lord your God will be with you > > wherever you > > go. > > - Joshua 1:9 > > > > Please respond to axis-dev@xml.apache.org > > To: axis-dev@xml.apache.org > > cc: > > Subject: Re: ?WSDL now uses the new Java2WSDL emitter code > > > > Great! > > > > Thanks Rick. > > > > Next for Java2WSDL is ONE STEP publish: > > 1. generate wsdl > > 2. generate client and > > 3. generate deploy > > > > Expect to checkin the client part tommorow > > > > Ravi > > JBuilder Development > > > > R J Scheuerle Jr wrote: > > > > > > The ?WSDL runtime wsdl generation code now uses the Java2WSDL Emitt= er. > > > > I removed the existing org.apache.axis.utils.WSDLUtils.java file. > > > > > > Rich Scheuerle > > XML & Web Services Development > > 512-838-5115 (IBM TL 678-5115) > > > > =