You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by Chathuri Wimalasena <ka...@gmail.com> on 2012/11/08 15:31:13 UTC
To which module should we add REST implementation
Hi All,
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..
Any thoughts ?
Thanks and Regards,
Chathuri
Re: To which module should we add REST implementation
Posted by Raminderjeet Singh <ra...@gmail.com>.
I will suggest to name the service as airavata-rest-service and i can merge my REST service code there. About the location my recommendation is to have this is modules directory.
Thanks
Raminder
On Nov 8, 2012, at 9:31 AM, Chathuri Wimalasena wrote:
> Hi All,
>
> 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..
>
> Any thoughts ?
>
> Thanks and Regards,
> Chathuri
Re: To which module should we add REST implementation
Posted by Amila Jayasekara <th...@gmail.com>.
Hi Suresh, Chathuri,
There are other REST based services which we will have in future.
(CredentialStore, InterpretterAPI etc ...).
Just wondering how should we organize above rest services. Currently
they lie in the same location as registry rest services. So would it
be nice if we extract out all REST services to a common module ?
(Without keeping in the registry)
In addition there will be another module (new) called "security".
Thanks
Amila
On Sun, Nov 11, 2012 at 1:59 PM, Suresh Marru <sm...@apache.org> wrote:
>
> On Nov 11, 2012, at 12:54 PM, Chathuri Wimalasena <ka...@gmail.com> wrote:
>
>> Hi Suresh,
>>
>> 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?
>
> If so, may be we should consider renaming it to indicate the functionality, something like airavata-registry-bootstrap or something like that.
>
> Suresh
>>
>> Thanks and regards,
>> Chathuri
>>
>>
>> On Sun, Nov 11, 2012 at 12:22 PM, Suresh Marru <sm...@apache.org> wrote:
>>
>>> On Nov 8, 2012, at 9:31 AM, Chathuri Wimalasena <ka...@gmail.com>
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> 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..
>>>>
>>>> Any thoughts ?
>>>
>>> Hi Chathuri,
>>>
>>> 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
>>>
>>> Will the current registry service [2] merge into your rest service
>>> implementation?
>>>
>>> Cheers,
>>> Suresh
>>>
>>> [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/
>
Re: To which module should we add REST implementation
Posted by Suresh Marru <sm...@apache.org>.
On Nov 11, 2012, at 12:54 PM, Chathuri Wimalasena <ka...@gmail.com> wrote:
> Hi Suresh,
>
> 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?
If so, may be we should consider renaming it to indicate the functionality, something like airavata-registry-bootstrap or something like that.
Suresh
>
> Thanks and regards,
> Chathuri
>
>
> On Sun, Nov 11, 2012 at 12:22 PM, Suresh Marru <sm...@apache.org> wrote:
>
>> On Nov 8, 2012, at 9:31 AM, Chathuri Wimalasena <ka...@gmail.com>
>> wrote:
>>
>>> Hi All,
>>>
>>> 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..
>>>
>>> Any thoughts ?
>>
>> Hi Chathuri,
>>
>> 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
>>
>> Will the current registry service [2] merge into your rest service
>> implementation?
>>
>> Cheers,
>> Suresh
>>
>> [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/
Re: To which module should we add REST implementation
Posted by Chathuri Wimalasena <ka...@gmail.com>.
Hi Suresh,
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.
Thanks and regards,
Chathuri
On Sun, Nov 11, 2012 at 12:22 PM, Suresh Marru <sm...@apache.org> wrote:
> On Nov 8, 2012, at 9:31 AM, Chathuri Wimalasena <ka...@gmail.com>
> wrote:
>
> > Hi All,
> >
> > 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..
> >
> > Any thoughts ?
>
> Hi Chathuri,
>
> 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
>
> Will the current registry service [2] merge into your rest service
> implementation?
>
> Cheers,
> Suresh
>
> [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/
Re: To which module should we add REST implementation
Posted by Suresh Marru <sm...@apache.org>.
On Nov 8, 2012, at 9:31 AM, Chathuri Wimalasena <ka...@gmail.com> wrote:
> Hi All,
>
> 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..
>
> Any thoughts ?
Hi Chathuri,
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
Will the current registry service [2] merge into your rest service implementation?
Cheers,
Suresh
[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/