Return-Path: Delivered-To: apmail-ws-axis-c-user-archive@www.apache.org Received: (qmail 42785 invoked from network); 4 Oct 2004 16:33:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 4 Oct 2004 16:33:40 -0000 Received: (qmail 98075 invoked by uid 500); 4 Oct 2004 16:33:24 -0000 Delivered-To: apmail-ws-axis-c-user-archive@ws.apache.org Received: (qmail 97957 invoked by uid 500); 4 Oct 2004 16:33:23 -0000 Mailing-List: contact axis-c-user-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: List-Id: "Apache AXIS C User List" Reply-To: "Apache AXIS C User List" Delivered-To: mailing list axis-c-user@ws.apache.org Received: (qmail 97820 invoked by uid 99); 4 Oct 2004 16:33:21 -0000 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=DNS_FROM_RFC_ABUSE,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from [195.212.29.135] (HELO mtagate2.uk.ibm.com) (195.212.29.135) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 04 Oct 2004 09:33:17 -0700 Received: from d06nrmr1307.portsmouth.uk.ibm.com (d06nrmr1307.portsmouth.uk.ibm.com [9.149.38.129]) by mtagate2.uk.ibm.com (8.12.10/8.12.10) with ESMTP id i94GXDGH082890; Mon, 4 Oct 2004 16:33:13 GMT Received: from d06ml068.portsmouth.uk.ibm.com (d06av04.portsmouth.uk.ibm.com [9.149.37.216]) by d06nrmr1307.portsmouth.uk.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i94GXALQ143086; Mon, 4 Oct 2004 17:33:10 +0100 In-Reply-To: Subject: RE: failure notice To: "Apache AXIS C User List" Cc: axis-c-dev@ws.apache.org X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003 Message-ID: From: John Hawkins Date: Mon, 4 Oct 2004 17:31:41 +0100 X-MIMETrack: Serialize by Router on D06ML068/06/M/IBM(Release 6.51HF338 | June 21, 2004) at 04/10/2004 17:36:19 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N What was the problem? I just ran WSDL2WS against this and it produced "stuff" with no errors - I did not compile the code it produced though :-) John Hawkins To 04/10/2004 16:59 cc Please respond to Subject "Apache AXIS C RE: failure notice User List" I did see it, but it struck me as overly complex. I think a simple exception to catch with a few simple properties would be better for a simple SOAP:fault. See what a lot of Java kits do. I have lost focus with Axis C++ at present because I was unable to make it consume our "hello world" service, getCustomerProfile, WSDL follows: MMBI service CH020X operation getCustomerProfile. getCustomerProfile. Returns Customer details by telephone number. An example CHIS service script. I wonder if the relatively complex return structure is too much for Axis C++ at present. Regards, Adrian -----Original Message----- From: John Hawkins [mailto:HAWKINSJ@uk.ibm.com] Sent: 04 October 2004 16:25 To: Apache AXIS C User List Subject: RE: failure notice Hi Adrian. did you take a look at Fred's note - was this the type of thing you were thinking of? John Hawkins To 30/09/2004 13:48 cc Please respond to Subject "Apache AXIS C RE: failure notice User List" Better SOAP:Fault handling - i.e. be able to access the fields within the SOAP:Fault from a client. -----Original Message----- From: John Hawkins [mailto:HAWKINSJ@uk.ibm.com] Sent: 30 September 2004 13:34 To: axis-c-user@ws.apache.org Subject: Re: failure notice Hi Folks, Big note coming up ! I would like to propose some features that we should put into 1.4. I would like to know what everyone is thinking is useful to have in the 1.4 release and this small list should act as a starter. C support - firstly define feasibility of making a 100% C++ engine and design, then (if feasible) implement. We will temporarily remove C support in 1.4 to be replaced in 1.5 with new wrapper. Apache Builds - This item is all about getting a daily build. We must also create all the relevant web pages so it's usable. We will build the client first then the server. Refactor WSDL2WS - As it says ! This is a pretty much open-ended item so we do as much as we can. Remember - at this point we have no C support so anything we can do here to make that easier to reimplement C in 1.5 is good ! Test documentation - document the handler mechanism and other test related stuff we have. AND - A Quick overview of 1.5 work 1.5 C support - put back into WSDL2 WS C wrappers for the new 100% C++ engine Purify and fix - As it says - run Rational purify and tackle issues that come out of it. Improve HTTP Support. Fix outstanding issues with HTTP support in the new transport layer. There is a lot we can do here and we haven't really defined what it highest priority. Documentation User documentation and CVS based documentation. including sample can be improved With the resource that we have here - we can contain all the above 1.4 items within a 24th November Time-schedule. I would like to propose that we try to maintain this shorter time-line for releases. That way we keep new function to a minimum and therefore maintain stability within builds. I would also like to propose that we move away from our current waterfall model of code then test. When we have daily builds we can see immediately what has broken and this will help us tremedously. The more we automate our testing the better. The one issue with this is that the daily builds will only cover certain compilation options (as discussed in previous mails). The test-cycle now appears to consist of running the same tests on different configurations - is this true? In which case I would ask that someone find the time to automate those configurations and run them daily as well? Please can you feedback your thoughts and ideas on what we should put into 1.4 and what you would like to see in 1.4 We can then make a judgement as to what the final goal is to be. many thanks, John.