Return-Path: Delivered-To: apmail-ws-axis-c-user-archive@www.apache.org Received: (qmail 81013 invoked from network); 31 Jan 2008 01:49:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 31 Jan 2008 01:49:22 -0000 Received: (qmail 8067 invoked by uid 500); 31 Jan 2008 01:49:12 -0000 Delivered-To: apmail-ws-axis-c-user-archive@ws.apache.org Received: (qmail 8054 invoked by uid 500); 31 Jan 2008 01:49:12 -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 8043 invoked by uid 99); 31 Jan 2008 01:49:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Jan 2008 17:49:12 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of dimuthuc@gmail.com designates 64.233.178.245 as permitted sender) Received: from [64.233.178.245] (HELO hs-out-2122.google.com) (64.233.178.245) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Jan 2008 01:48:45 +0000 Received: by hs-out-2122.google.com with SMTP id l65so438821hsc.0 for ; Wed, 30 Jan 2008 17:48:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=NOoAHpUZhUDf4HmWCzB9MGkh0TVTzlJU1BR6LiuOb7k=; b=wHADOlQ2NpBurSXtJMOy5pH8mhfB72GbGIhgBu2O4irM290g1E/Ne5dLyBUl1DoskHMC8lqhB7wQt3UHkXUPeEQVgWTGV+74rTp2YtHyQhxf/ma8d2SXco2Wh3Rb9lLQUAYji4RQbbFrudZJcUSbbp0BB8606YkzJq/cJXMMIQo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=X0dYyKd5JLX3I5qKaF3Ah+FcEiWMBF4JfjA0SV2YrrYAnfYRsAmlLRSGzgyrukKCLHRHh/XS6Coi4iu4+50cIuF7AY6i9WEI6TdGi3HktwllfvlL2pllJYm6PUiMkXLraRb16ZVClIAH61Ut7rvCOFqFZTBLYi5KeNF3p89hUHk= Received: by 10.142.79.15 with SMTP id c15mr864412wfb.105.1201744130688; Wed, 30 Jan 2008 17:48:50 -0800 (PST) Received: by 10.142.238.15 with HTTP; Wed, 30 Jan 2008 17:48:50 -0800 (PST) Message-ID: Date: Thu, 31 Jan 2008 07:18:50 +0530 From: "Dimuthu Gamage" To: "Apache AXIS C User List" Subject: Re: Questions/suggestions on WSDL2C In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Virus-Checked: Checked by ClamAV on apache.org Hi Zhang, Thanks for your suggestions. 1). In fact generating a demo client is a good idea. I will look in to that. For the time being, I'm using a ruby script to generate simple demonstrations for stub and skels (it automatically generates simple logic with adb), if you find useful you can check it from http://people.apache.org/~dimuthu/leisure/23_oct/generate_demos.rb. 2). If we are generating makefiles we may need to think about both linux and windows users. And we have to decide whether to use automake build system or just a simple Makefile which sometime not OS independent. May be some build system expert can help on this. Sanjaya,, Any Ideas? Thanks Dimuthu On Jan 31, 2008 12:18 AM, Zhang, Wayne (IT) wrote: > > > > Hi, > > I just started looking at Axis2/C two days ago and it looks pretty > promising. However I hit a snag using WSDL2C, and I couldn't find any > solutions in the mail archive, so apologies if this has already been > answered before. > > I am using WSDL2C to generate a simple "calculator" client and server. I > followed the directions in your user manual > (http://ws.apache.org/axis2/c/docs/axis2c_manual.html#wsdl2c) and was able > to generate my client stubs and server skeletons successfully. > > Implementing the server skeleton is pretty straight forward -- I just added > my business logic in the /* TODO ... */ field. However implementing the > client isn't as easy. The user manual simply states "To do this, go through > the header files generated and understand the API in line with the WSDL file > that you used to generate the code." It will be great if you can provide a > step-by-step example showing which functions to implement in what files. > > My other suggestions are: > > * Can WSDL2C generate a main() for the client that sets up the default > env/options and make required axis calls such as > axis2_endpoint_ref_create(), axis2_svc_client_send_receive(), etc. and put > /* TODO */ hints to prompt users to add his business logic? > > * It will be great if WSDL2C can also generate makefiles to assist compiling > the server and client, as well as install the server in $AXIS_HOME/services. > This will ease a user's development effort quite a bit. > > Many thanks in advance, > > Wayne Zhang > Morgan Stanley | Technology > 750 Seventh Avenue, 12th Floor | New York, NY 10019 > Phone: +1 212 762-1943 > Wayne.Zhang@morganstanley.com > > > ________________________________ > > > NOTICE: If received in error, please destroy and notify sender. Sender does > not intend to waive confidentiality or privilege. Use of this email is > prohibited when received in error. > --------------------------------------------------------------------- To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org For additional commands, e-mail: axis-c-user-help@ws.apache.org