Return-Path: Delivered-To: apmail-ws-axis-c-user-archive@www.apache.org Received: (qmail 69017 invoked from network); 27 Feb 2008 11:45:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Feb 2008 11:45:24 -0000 Received: (qmail 5583 invoked by uid 500); 27 Feb 2008 11:45:18 -0000 Delivered-To: apmail-ws-axis-c-user-archive@ws.apache.org Received: (qmail 5570 invoked by uid 500); 27 Feb 2008 11:45:18 -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 5559 invoked by uid 99); 27 Feb 2008 11:45:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2008 03:45:18 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [203.188.202.96] (HELO n2a.bullet.mail.tp2.yahoo.com) (203.188.202.96) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 27 Feb 2008 11:44:30 +0000 Received: from [202.43.196.225] by n2.bullet.mail.tp2.yahoo.com with NNFMP; 27 Feb 2008 11:44:48 -0000 Received: from [68.142.200.227] by t2.bullet.tpe.yahoo.com with NNFMP; 27 Feb 2008 11:44:47 -0000 Received: from [68.142.201.250] by t8.bullet.mud.yahoo.com with NNFMP; 27 Feb 2008 11:44:47 -0000 Received: from [127.0.0.1] by omp411.mail.mud.yahoo.com with NNFMP; 27 Feb 2008 11:44:47 -0000 X-Yahoo-Newman-Id: 579720.19069.bm@omp411.mail.mud.yahoo.com Received: (qmail 14272 invoked from network); 27 Feb 2008 11:44:47 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.es; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=L5DlwQeYbonXQt7zE0DoQldwebfSlu4ZWDyD4durdkMdd4gyALIJFnytdoOfX5RwTSIyvPS6ZXU6jhE6jZ10BZNvkvgLFKNJeQmn5omUDJjUkm+SX9BroSyYrzOFBTRQatTPdMv/IhA5Wcd2fd7hhU4mDNtvGCxaqfx93tE5KVI= ; Received: from unknown (HELO ?192.168.1.116?) (pepesan_mail@84.125.21.64 with plain) by smtp110.plus.mail.mud.yahoo.com with SMTP; 27 Feb 2008 11:44:46 -0000 X-YMail-OSG: f3YHn_wVM1nRxIKhTAe1TOPFSPZwXT0fg9zKMDo8n6TGozODD1l2xltlauugcP42oFuAy3g8ibXpgrH8B_WaO__KzLg3GpX29tmEEM3efKU8o9BrXL4- X-Yahoo-Newman-Property: ymail-3 Message-ID: <47C54D2A.3020209@yahoo.es> Date: Wed, 27 Feb 2008 12:44:42 +0100 From: David Vaquero User-Agent: Thunderbird 2.0.0.9 (X11/20071031) MIME-Version: 1.0 To: Apache AXIS C User List Subject: Re: [Questions][Whislist] WSDL generation, improved service information, and developer flow cicle in server References: <47C2B0AF.2040103@yahoo.es> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Hi All my comments are inline :) Dimuthu Gamage escribi�: > Hi David, > > > On Mon, Feb 25, 2008 at 5:42 PM, David Vaquero wrote: > >> Hi all, >> >> [...] >> First, there is any method in AXIS2/C to generate the WSDL file from the >> code of a service library? >> Before I used the soap2cpp tool from gsoap proyect to parse the .h file >> to generate the wsld file, in AXIS2/C, there is any similar tool? >> > > First at all, thanks for the support :) > No currently there is no such a way to generate WSDL from C code, So > the code first approach is not possible, anyway if your intension is > generate WSDLs, Axis2/Java provides one (Java2WSDL). > Thanks, I'll try it :) >> Second, the html information about the services is cool, but i think >> that if this information includes the Request and Response Paramaters >> structured, the html service info will be more usefull for the WS user. >> There is a method to include this structured information in the result >> html exit of AXIS2/C? >> > > No, I think the main reason these two are not implemented, C doesn't > support on reflection as in Java or any newer languages, and there is > no proper way to write annotations in C to describe meta data. So the > implementations are not just straight forward. > A suggest :) If in the services.xml we could define an optional "wsdlfile" tag to asociate the wsdl to the service, the info of the wsdl file includes the structs, parameters to the diferent methods. With a wsdl parser in the service load can extract the info from the wsdl and could extend the html output from the services containing: Structs, Methods, Response and Request Parameters by method. This will be interesting? > >> Third, and last :) , I dont understand well the load library process in >> Axis2/C yet (in standalone server and apache module), but there is any >> way to force the load a library service when the server is up(executed)? >> > > No, The services, modules are loaded only at the startup, But there > are soap extensions like WSF/PHP or WSF/Ruby which uses the same > Axis2/C and load PHP or Ruby services dynamically. So I think it is > possible to implement this kind of thing with Axis2/C. I believe this > will be a feature of Axis2/C 1.4?, just a thought.:) > Said by Samisa: If you want to load a service while the server is running, by placing it in the service repository, it cannot be done right now, because we do not have hot deployment implemented. However, this can be done programatically with current Axis2/C. end of the copy----------> I'll explain the feature for if it results interesting for future releases :) In the development-testing of the service, we actual had to restart the service to reload the .so's of one service, if we could force the reload a service from a control console tool (like the a2enmod or a2dismod in httpd server apache), so the other services will not affected for the charge of discharge of the other service. Samisa, where I can find info about the programatically load and discharge of the services? Regards :) Pepesan --------------------------------------------------------------------- To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org For additional commands, e-mail: axis-c-user-help@ws.apache.org