Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 65184 invoked from network); 2 Jan 2006 13:37:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 Jan 2006 13:37:51 -0000 Received: (qmail 32773 invoked by uid 500); 2 Jan 2006 13:37:49 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 32555 invoked by uid 500); 2 Jan 2006 13:37:48 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 32524 invoked by uid 99); 2 Jan 2006 13:37:47 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jan 2006 05:37:47 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of davanum@gmail.com designates 66.249.82.199 as permitted sender) Received: from [66.249.82.199] (HELO xproxy.gmail.com) (66.249.82.199) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jan 2006 05:37:47 -0800 Received: by xproxy.gmail.com with SMTP id t16so1484020wxc for ; Mon, 02 Jan 2006 05:37:26 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=IlX2iynhXDdwLy1UgxB/saX4JTURZfgPq3i5I946a6hDBK4b9IHYJ62I8c7DPYvO2w1pOjI2WYBK+Cnu6IvZ3A56Au6bkvXCKUnFgvszgIcOj1z3Pwf7nZ9nLhgIHFzWAq+xGnmU8VDNbPtYbURcCk011zbPu6PXIB5kGKX5W9I= Received: by 10.11.120.11 with SMTP id s11mr157513cwc; Mon, 02 Jan 2006 05:37:26 -0800 (PST) Received: by 10.11.122.64 with HTTP; Mon, 2 Jan 2006 05:37:26 -0800 (PST) Message-ID: <19e0530f0601020537h27d1570cr2726e0a0798e8084@mail.gmail.com> Date: Mon, 2 Jan 2006 08:37:26 -0500 From: Davanum Srinivas Reply-To: dims@apache.org To: axis-dev@ws.apache.org Subject: Re: [axis2] Module versions support In-Reply-To: <1136201407.9836.18.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <029801c60d33$3893a090$c201a8c0@Deepal> <19e0530f0512300536k7a4f3a24h85490090e7446a19@mail.gmail.com> <43B61031.2010103@sosnoski.com> <1136007835.8593.119.camel@localhost.localdomain> <19e0530f0512302150o654cec6bqd1c67720082cd3cb@mail.gmail.com> <1136009523.8593.122.camel@localhost.localdomain> <02c601c60f5e$4ac3b480$c201a8c0@Deepal> <03a401c60f86$c53a6290$c201a8c0@Deepal> <1136201407.9836.18.camel@localhost.localdomain> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N +1 from me. On 1/2/06, Sanjiva Weerawarana wrote: > +1! > > Sanjiva. > > On Mon, 2006-01-02 at 16:24 +0600, Deepal Jayasinghe wrote: > > Hi all; > > > > Without having a knowledge of module version user should be able to eng= age a > > module . In that case we have to get the default version > > (there will be two ways of engaging a module ) > > 1. engageModule(String moduleName); > > 2 . engageModule(String moduleName , String moduleVersion); > > > > Finding default version of some module if there are more than one modul= e, > > 1. If there are multiple versions of the same module it can possible t= o > > specify the default version in axis2.xml as follows > > > > > > > > > > 2. If there are multiple versions of the same module and user does not > > specify that in axis2.xml then the default version will be the latest > > version > > > > comments .....? > > > > Thanks, > > Deepal > > ................................................................ > > ~Future is Open~ > > > > ----- Original Message ----- > > From: "Deepal Jayasinghe" > > To: > > Sent: Monday, January 02, 2006 11:35 AM > > Subject: Re: [axis2] Module versions support > > > > > > >I think we are done with the format of the version number , > > > but I have some other problem to solve now say we have multiple versi= on of > > > the same module in the system , and right now at the deployment time = I > > > call the init method of each module (since we don't have the notion o= f > > > module version yet) , there if the module want to do some stuff they = can > > > do that , as an example in RM case if it has saved some data they ca= n get > > > them back at the initialization stage. > > > > > > But the problem is what are we going to do if there are multiple vers= ions > > > of the same module , should we need to call init method of all the mo= dules > > > ? where they are going to be engaged or not. > > > > > > Thanks, > > > Deepal > > > ................................................................ > > > ~Future is Open~ > > > > > > ----- Original Message ----- > > > From: "Sanjiva Weerawarana" > > > To: > > > Cc: > > > Sent: Saturday, December 31, 2005 12:12 PM > > > Subject: Re: [axis2] Module versions support > > > > > > > > >> On Sat, 2005-12-31 at 00:50 -0500, Davanum Srinivas wrote: > > >>> just reviewed the original email again...it talks about > > >>> xyz-00.0000.mar hence the confusion. > > >>> > > >>> So, we should go with say security-1.23.mar. Right? just to be > > >>> absolutely clear. > > >> > > >> Right .. or security-1.235486.mar etc... basically we expect the for= mat > > >> to be modulename-{majorversion}.{minorversion}.mar where the two ver= sion > > >> #s are integers. (Major should not have any leading zeros but that's > > >> just a redundant comment - anyone who puts that deserves whatever > > >> behavior they get.) > > >> > > >> Sanjiva. > > >> > > >> > > >> > > > > > > > > > > > > > > > -- Davanum Srinivas : http://wso2.com/blogs/