Re: [GSoC] Registry side JSON implementation.

[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/