Return-Path: X-Original-To: apmail-airavata-dev-archive@www.apache.org Delivered-To: apmail-airavata-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DCA5EDCCC for ; Sun, 11 Nov 2012 18:59:34 +0000 (UTC) Received: (qmail 14943 invoked by uid 500); 11 Nov 2012 18:59:34 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 14904 invoked by uid 500); 11 Nov 2012 18:59:34 -0000 Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airavata.apache.org Delivered-To: mailing list dev@airavata.apache.org Received: (qmail 14848 invoked by uid 99); 11 Nov 2012 18:59:34 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 11 Nov 2012 18:59:34 +0000 Received: from localhost (HELO [10.0.1.5]) (127.0.0.1) (smtp-auth username smarru, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Sun, 11 Nov 2012 18:59:34 +0000 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: To which module should we add REST implementation From: Suresh Marru In-Reply-To: Date: Sun, 11 Nov 2012 13:59:33 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <54626C2A-D92B-46BD-B1D1-4D3AEF9A2159@apache.org> References: To: dev@airavata.apache.org X-Mailer: Apple Mail (2.1499) On Nov 11, 2012, at 12:54 PM, Chathuri Wimalasena = wrote: > Hi Suresh, >=20 > This airavata registry service is an axis2 service, which will create > database tables and insert necessary data when starting airavata. This = does > not have any impact on the rest implementation. I will add the REST > implementation to the registry module as you suggested. Hi Chathuri, Do you think its a bad idea to merge this initial data population into = the registry service itself?=20 If so, may be we should consider renaming it to indicate the = functionality, something like airavata-registry-bootstrap or something = like that.=20 Suresh >=20 > Thanks and regards, > Chathuri >=20 >=20 > On Sun, Nov 11, 2012 at 12:22 PM, Suresh Marru = wrote: >=20 >> On Nov 8, 2012, at 9:31 AM, Chathuri Wimalasena = >> wrote: >>=20 >>> Hi All, >>>=20 >>> I'm planning to move Airavata REST implementation from sandbox to = the >>> airavata trunk. To which module should I add it ? At the moment REST >>> service is only for Registry API. But there's another REST service = that >>> Raman has implemented for methods in Airavata Client which we should >> merge >>> eventually. So we can't add the current REST implementation to = registry >>> module. I' m wondering what is the best module that we should add = the >> REST >>> service.. >>>=20 >>> Any thoughts ? >>=20 >> Hi Chathuri, >>=20 >> I would vote for having this within the registry module itself [1]. = May be >> we should re-look at what all various registry modules are and make = them >> self-explanatory. >> * a single registry service api (the rest service you propose to move = from >> sandbox). >> * a airavata registry data model or api which can be implemented >> * the current JPA based implementation >> * any needed utilities >>=20 >> Will the current registry service [2] merge into your rest service >> implementation? >>=20 >> Cheers, >> Suresh >>=20 >> [1] - = https://svn.apache.org/repos/asf/airavata/trunk/modules/registry/ >> [2] - >> = https://svn.apache.org/repos/asf/airavata/trunk/modules/registry/airavata-= registry-service/