Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airavata.apache.org
Received-SPF: pass (athena.apache.org: domain of samindaw@gmail.com designates
 209.85.215.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CANotcz7iOMjydK8veGvF6vfGbfZvus+yFDPUY+W_3nyvv8R6Hw@mail.gmail.com>
References: 
 <CAJvLytoMiczZ_P1jTAXw9=ngzbPFdMGodpSm0CCew78XhV+HHA@mail.gmail.com>
 <2EEEEF8E-819A-4DA8-A34A-4BE229F29BCF@apache.org>
 <CAJvLytrB-tzkXdX8UEhsCoCTfvprCQp8G-ZGwm0=tUms60MS=A@mail.gmail.com>
 <CANotcz6d3XEmVzK_d5vPzDGdyGFAZJND5t3CX3SyYfu3df30nw@mail.gmail.com>
 <8B5D14EA-524D-4BCA-9889-8D940A5B703F@apache.org>
 <BLU405-EAS330FA9EB741F0DA67BE23D6AB710@phx.gbl>
 <CANotcz4BqY9e6aX8u54Z3425pZJoOYdqydhxGFK0wdxviFJj-g@mail.gmail.com>
 <CANotcz4cocCKBWn9axCWawfwrFmB0M1U2YvYYafGczTzt0xBRA@mail.gmail.com>
 <CANotcz7iOMjydK8veGvF6vfGbfZvus+yFDPUY+W_3nyvv8R6Hw@mail.gmail.com>
From: Saminda Wijeratne <samindaw@gmail.com>
Date: Tue, 2 Jul 2013 12:07:31 -0400
Message-ID: 
 <CANotcz6w3UGEFCtHVzotVR0-=9bmGZV_b8zy7iNQVOXtRGeNhA@mail.gmail.com>
Subject: Re: [GSoC] Registry side JSON implementation.
To: dev@airavata.apache.org, viknesb <viknesb@msn.com>
Content-Type: multipart/alternative; boundary=089e0117721311228a04e0898c00

--089e0117721311228a04e0898c00
Content-Type: text/plain; charset=ISO-8859-1

The slides,

https://docs.google.com/presentation/d/1v2BBHJYTMJ8qJ4emReR0UBIme3h_LuNJjGMUaoVIhuM/edit#slide=id.gef340dc3_0156


On Tue, Jul 2, 2013 at 10:23 AM, Saminda Wijeratne <samindaw@gmail.com>wrote:

> this is the hangout url
> https://plus.google.com/hangouts/_/d00a36670639c25200b314bf2d04f7345e5c335c?authuser=0
> let me know if you need to be added.
>
>
> On Tue, Jul 2, 2013 at 10:00 AM, Saminda Wijeratne <samindaw@gmail.com>wrote:
>
>> The hangout session will start at 10:15am EST. Will send out the hangout
>> url 5 minutes before it starts (provided my linux machine complies).
>>
>>
>> On Mon, Jul 1, 2013 at 6:49 PM, Saminda Wijeratne <samindaw@gmail.com>wrote:
>>
>>> Great. See you at that time then. Like Suresh said I'll create the
>>> hangout session just before the session starts and send out the list to
>>> this mail thread.
>>>
>>>
>>> On Mon, Jul 1, 2013 at 4:39 PM, Viknes Balasubramanee <viknesb@msn.com>wrote:
>>>
>>>> +1 for July 2nd 10am EST.
>>>>
>>>> Viknes
>>>>
>>>> -----Original Message-----
>>>> From: Suresh Marru [mailto:smarru@apache.org]
>>>> Sent: Monday, July 01, 2013 9:55 AM
>>>> To: dev@airavata.apache.org
>>>> Subject: Re: [GSoC] Registry side JSON implementation.
>>>>
>>>> On Jun 28, 2013, at 5:17 PM, Saminda Wijeratne <samindaw@gmail.com>
>>>> wrote:
>>>>
>>>> > Yep lets do it next week. Does July 2nd 10am EST work for anyone who
>>>> > wants to join in the discussion? Or suggest another date/time please.
>>>>
>>>> + 1, I will join in as well. My experience with pre-scheduled google
>>>> hangout
>>>> on the air was not good. So I suggest you start the hangout on air few
>>>> minutes before the schedule and send a link to the list.
>>>>
>>>> Suresh
>>>>
>>>> >
>>>> >
>>>> > On Fri, Jun 28, 2013 at 5:02 PM, Shameera Rathnayaka
>>>> > <shameerainfo@gmail.com
>>>> >> wrote:
>>>> >
>>>> >> Hi Suresh,
>>>> >>
>>>> >> On Sat, Jun 29, 2013 at 12:29 AM, Suresh Marru <smarru@apache.org>
>>>> wrote:
>>>> >>
>>>> >>> Hi Shameera
>>>> >>>
>>>> >>> I would have been surprised if the API did not confuse you and
>>>> others.
>>>> >>>
>>>> >>> Hi Saminda,
>>>> >>>
>>>> >>> I think your recent API discussions were useful but I do not think
>>>> >>> they are still conveying the story. Can we have a google hangout and
>>>> >> brainstorm
>>>> >>> and also have a WIKI documentation on the API?
>>>> >>>
>>>> >>
>>>> >> +1 , It would be great if we can have a google hangout for this as i
>>>> >> +have
>>>> >> come to difficult state of development.
>>>> >>
>>>> >> Thanks,
>>>> >> Shameera.
>>>> >>
>>>> >>
>>>> >>>
>>>> >>> Thanks,
>>>> >>> Suresh
>>>> >>>
>>>> >>> On Jun 28, 2013, at 2:49 PM, Shameera Rathnayaka
>>>> >>> <shameerainfo@gmail.com
>>>> >>>
>>>> >>> wrote:
>>>> >>>
>>>> >>>> Hi all,
>>>> >>>>
>>>> >>>> As i am done with workflow interpreter, now i am working with
>>>> >>>> registry side. Here i have some concerns
>>>> >>>>
>>>> >>>> 1. With my observation , registry rest api already can work with
>>>> >>>> json
>>>> >> but
>>>> >>>> inside the rest api it uses airavata java client  api to do the
>>>> >>>> actual invocation (registry rest api is wirtten by wrapping
>>>> >>>> airavata java
>>>> >> client
>>>> >>>> API). Seems it will be required to improve airavata java client to
>>>> >>>> work with json in this case. This can be done by introducing JAXB
>>>> >>>> to JSON convertion layer same as JAXB to XML layer. It would be
>>>> >>>> good to know thoughts on this scenario to know whether i am doing
>>>> >>>> right thing here
>>>> >> or
>>>> >>>> in wrong path.
>>>> >>>>
>>>> >>>> 2. Is airavata java client an axis2 client?, I am bit confused
>>>> >>>> about
>>>> >>> this.
>>>> >>>>
>>>> >>>> 3. As we discussed it is required to store JSON instead of XML in
>>>> >>> database,
>>>> >>>> Seems this is required more effort and need more changes. are we
>>>> >>>> going
>>>> >> do
>>>> >>>> this now ?
>>>> >>>>
>>>> >>>> Any thoughts and feedbacks on following things are more than
>>>> welcome.
>>>> >>>>
>>>> >>>>
>>>> >>>> Thanks,
>>>> >>>> Shameera.
>>>> >>>>
>>>> >>>> --
>>>> >>>> Best Regards,
>>>> >>>> Shameera Rathnayaka.
>>>> >>>>
>>>> >>>> email: shameera AT apache.org , shameerainfo AT gmail.com Blog :
>>>> >>>> http://shameerarathnayaka.blogspot.com/
>>>> >>>
>>>> >>>
>>>> >>
>>>> >>
>>>> >> --
>>>> >> Best Regards,
>>>> >> Shameera Rathnayaka.
>>>> >>
>>>> >> email: shameera AT apache.org , shameerainfo AT gmail.com Blog :
>>>> >> http://shameerarathnayaka.blogspot.com/
>>>> >>
>>>>
>>>>
>>>
>>
>

--089e0117721311228a04e0898c00--