Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 2505 invoked by uid 500); 12 Dec 2001 15:50:04 -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 2162 invoked from network); 12 Dec 2001 15:49:59 -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.7 March 21, 2001 Message-ID: From: "Russell Butek" Date: Wed, 12 Dec 2001 09:48:53 -0600 X-MIMETrack: Serialize by Router on D04NMS23/04/M/IBM(Release 5.0.8 |June 18, 2001) at 12/12/2001 10:49:03 AM 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 Just a suggestion. Since we're talking WSDL, shouldn't we use WSDL terminology here? Interface and Implementation aren't WSDL terms. Yea= h, I know about the WSDL Best Practices doc, but I doubt most users will. M= aybe 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. The first essential= ly says give me WSDL with types, messages, portTypes, and bindings. The second says give me WSDL with services. Maybe we want some sort of shorthand if y'all think Intf and Impl will be widely used, but do we w= ant 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: axis-dev@xml.apache.org cc: Subject: Re: ?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 sp= lit WSDL file approach that Java2Wsdl supports in the URL approach and here's one idea that I came up with.=A0 Please let me know what you think. Rather than the URL pattern http://localhost/axis/services/StockQuoteService?WSDL to create a singl= e WSDL document, why not something like: http://localhost/axis/services/StockQuoteService/Interface.wsdl and http://localhost/axis/services/StockQuoteService/Impl.wsdl ??=A0 Using this approach, we can do the on the fly WSDL generation and= include support for UDDI at the same time. - James M Snell/Fresno/IBM =A0=A0=A0 Web services architecture and strategy =A0=A0=A0 Internet Emerging Technologies, IBM =A0=A0=A0 544.9035 TIE line =A0=A0=A0 559.587.1233 Office =A0=A0=A0 919.486.0077 Voice Mail =A0=A0=A0 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?=A0 Be strong and courageous.=A0 Do not be ter= rified, 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:=A0=A0=A0=A0 axis-dev@xml.apache.org cc: Subject:=A0=A0=A0=A0=A0=A0=A0 Re: ?WSDL now uses the new Java2WSDL emit= ter 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 Emitter. I removed the existing org.apache.axis.utils.WSDLUtils.java file. Rich Scheuerle XML & Web Services Development 512-838-5115=A0 (IBM TL 678-5115) =