You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by Shameera Rathnayaka <sh...@gmail.com> on 2013/06/28 20:49:23 UTC
[GSoC] Registry side JSON implementation.
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/
Re: [GSoC] Registry side JSON implementation.
Posted by Saminda Wijeratne <sa...@gmail.com>.
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 <sa...@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 <sa...@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 <sa...@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 <vi...@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 <sa...@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 <sm...@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/
>>>> >>
>>>>
>>>>
>>>
>>
>
Re: [GSoC] Registry side JSON implementation.
Posted by Saminda Wijeratne <sa...@gmail.com>.
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 <sa...@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 <sa...@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 <vi...@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 <sa...@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 <sm...@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/
>>> >>
>>>
>>>
>>
>
Re: [GSoC] Registry side JSON implementation.
Posted by Saminda Wijeratne <sa...@gmail.com>.
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 <sa...@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 <vi...@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 <sa...@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 <sm...@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/
>> >>
>>
>>
>
Re: [GSoC] Registry side JSON implementation.
Posted by Saminda Wijeratne <sa...@gmail.com>.
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 <vi...@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 <sa...@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 <sm...@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/
> >>
>
>
RE: [GSoC] Registry side JSON implementation.
Posted by Viknes Balasubramanee <vi...@msn.com>.
+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 <sa...@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 <sm...@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/
>>
Re: [GSoC] Registry side JSON implementation.
Posted by Suresh Marru <sm...@apache.org>.
On Jun 28, 2013, at 5:17 PM, Saminda Wijeratne <sa...@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 <sm...@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/
>>
Re: [GSoC] Registry side JSON implementation.
Posted by Shameera Rathnayaka <sh...@gmail.com>.
Hi Saminda,
On Sat, Jun 29, 2013 at 2:47 AM, Saminda Wijeratne <sa...@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.
>
I am ok with this time.
Thanks,
Shameera.
>
>
> 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 <sm...@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/
> >
>
--
Best Regards,
Shameera Rathnayaka.
email: shameera AT apache.org , shameerainfo AT gmail.com
Blog : http://shameerarathnayaka.blogspot.com/
Re: [GSoC] Registry side JSON implementation.
Posted by Saminda Wijeratne <sa...@gmail.com>.
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.
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 <sm...@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/
>
Re: [GSoC] Registry side JSON implementation.
Posted by Shameera Rathnayaka <sh...@gmail.com>.
Hi Suresh,
On Sat, Jun 29, 2013 at 12:29 AM, Suresh Marru <sm...@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 <sh...@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/
Re: [GSoC] Registry side JSON implementation.
Posted by Suresh Marru <sm...@apache.org>.
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?
Thanks,
Suresh
On Jun 28, 2013, at 2:49 PM, Shameera Rathnayaka <sh...@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/