airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lahiru Gunathilake <glah...@gmail.com>
Subject Re: Removing previous registry API usage from airavata components
Date Thu, 21 Aug 2014 17:47:28 GMT
On Thu, Aug 21, 2014 at 11:08 PM, Saminda Wijeratne <samindaw@gmail.com>
wrote:

> +1
>
> I gather you've updated the app catalog to support workflows right?
>
I haven't touched app-catalog or workflows.

Regards
Lahiru

>
>
> On Thu, Aug 21, 2014 at 12:47 PM, Lahiru Gunathilake <glahiru@gmail.com>
> wrote:
>
>> +1
>>
>>
>> On Thu, Aug 21, 2014 at 10:08 PM, Chathuri Wimalasena <
>> kamalasini@gmail.com> wrote:
>>
>>> Hi Lahiru,
>>>
>>> I have another question regarding GFac. We have two classes called
>>> GFacImpl and BetterGFacImpl. Why are we using the both ? Is it ok if I
>>> change all the places that uses GFacImpl to use BetterGFacImpl ?
>>>
>>>
>>> On Thu, Aug 21, 2014 at 12:12 PM, Suresh Marru <smarru@apache.org>
>>> wrote:
>>>
>>>> + 1, great idea and thanks for volunteering Chathuri.
>>>>
>>>> But did we get GFac away from using it yet?
>>>>
>>>> Suresh
>>>>
>>>> On Aug 21, 2014, at 11:39 AM, Chathuri Wimalasena <kamalasini@gmail.com>
>>>> wrote:
>>>>
>>>> > Hi Devs,
>>>> >
>>>> > I'm planning to remove previous registry API (AiravataRegistry2)
>>>> usage from airavata components. I believe we no longer need to rely on
>>>> previous registry API. Please let me know if you have any objections or
>>>> concerns.
>>>> >
>>>> > Thanks..
>>>> > Chathuri
>>>>
>>>>
>>>
>>
>>
>> --
>> System Analyst Programmer
>> PTI Lab
>> Indiana University
>>
>
>


-- 
System Analyst Programmer
PTI Lab
Indiana University

Mime
View raw message