Return-Path: Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list axis-dev@xml.apache.org Received: (qmail 47565 invoked from network); 26 Feb 2001 15:09:17 -0000 Received: from e21.nc.us.ibm.com (32.97.136.227) by h31.sny.collab.net with SMTP; 26 Feb 2001 15:09:17 -0000 Received: from southrelay02.raleigh.ibm.com (southrelay02.raleigh.ibm.com [9.37.3.209]) by e21.nc.us.ibm.com (8.9.3/8.9.3) with ESMTP id KAA61220 for ; Mon, 26 Feb 2001 10:04:45 -0600 Received: from d04nm204.raleigh.ibm.com (d04nm204.raleigh.ibm.com [9.67.228.13]) by southrelay02.raleigh.ibm.com (8.11.2/NCO v4.95) with ESMTP id f1QF9BL56408 for ; Mon, 26 Feb 2001 10:09:13 -0500 Importance: Normal Subject: Re: WSDL awareness To: axis-dev@xml.apache.org X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000 Message-ID: From: "Doug Davis" Date: Mon, 26 Feb 2001 10:09:08 -0500 X-MIMETrack: Serialize by Router on D04NM204/04/M/IBM(Release 5.0.6 |December 14, 2000) at 02/26/2001 10:09:13 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N TBD - could be WSDL elements, could be WSDD elements. Maybe require the new method to modify the response message - building the WSDL or WSDD as it goes. -Dug Steve Graham/Raleigh/IBM@IBMUS on 02/26/2001 09:18:45 AM Please respond to axis-dev@xml.apache.org To: axis-dev@xml.apache.org cc: Subject: Re: WSDL awareness what does deployment information mean? WSDL elements? ++++++++ Steve Graham sggraham@us.ibm.com (919)254-0615 (T/L 444) Web Services Architect Emerging Internet Technologies ++++++++ Doug Davis/Raleigh/IBM@IBMUS on 02/26/2001 09:05:28 AM Please respond to axis-dev@xml.apache.org To: axis-dev@xml.apache.org cc: Subject: Re: WSDL awareness Wanted to wait until the F2F but since you brought it up... I was going to propose a new method on Handler that would allow it to return deployment information that will be used to construct the complete deployment picture for a given service. This new method would be very similar to the invoke method in that it takes basically the same parameters but doesn't do any of the work - just uses the data to figure out what deployment data should be returned. In the case of Handlers that are Routers, some work might need to be done to determine who's the next Handler to call, but that work will need to be transient. -Dug Sam Ruby/Raleigh/IBM@IBMUS on 02/26/2001 08:56:44 AM Please respond to axis-dev@xml.apache.org To: axis-dev@xml.apache.org cc: Subject: Re: WSDL awareness Sanjiva Weerawarana wrote: > > What's the current design ref being aware of the service > description when processing the message? I don't know about during the processing of a message, but one thing I like about the Microsoft DotNet implementation is that a (W)SDL description will be produced upon demand based on metadata provided by the service. If the axis implementation distributes the processing across handlers, it would be nice if some sort of mechanism were provided for each handler to provide some input into the construction of a WSDL description. - Sam Ruby