Build failed in Jenkins: Apache Airavata #1166

See Changes: [samindaw] updating migrate script + gfac enum status obj + refactor etc. [samindaw] updating migrate script + gfac enum status obj + refactor -- Failed to access build log hudso

Re: Initiating GSoC Project - JSON support and JSON to XML bidirectional conversion for Airavata

Hi Raminder, On Thu, Jun 6, 2013 at 11:59 PM, Raminder Singh wrote: > > JSON/XML conversion can be handled using JAXB and Jackson [1] providers in > JAVA. > Or we can use Staxon[1] which provide easy way to do this by handling both JAXB and Jackson. Thanks, Shameera. [1] https://github.com/bec

Re: Initiating GSoC Project - JSON support and JSON to XML bidirectional conversion for Airavata

Hi Danushka, On Thu, Jun 6, 2013 at 11:27 PM, Danushka Menikkumbura < danushka.menikkumb...@gmail.com> wrote: > a thin JS layer that wraps > the current Java API. > +1, This would be a good solution. Thanks, Shameera. > > Thanks, > Danushka > -- Best Regards, Shameera Rathnayaka. email:

Re: Initiating GSoC Project - JSON support and JSON to XML bidirectional conversion for Airavata

Thanks Danushka for clarity. JSON/XML conversion can be handled using JAXB and Jackson [1] providers in JAVA. +1 for having thin layer of JS API to map Airavata API functions to Web UI functions Thanks Raminder 1. http://jackson.codehaus.org/Tutorial On Jun 6, 2013, at 1:57 PM, Danushka Me

Re: Initiating GSoC Project - JSON support and JSON to XML bidirectional conversion for Airavata

On Jun 6, 2013, at 1:57 PM, Danushka Menikkumbura wrote: > Raminder, > > My suggestion is to add web layer over the current API but i still see a >> need of JS API for functions performed by Web XBaya to make it more clear. >> > > We do need a JS API for the Web UI, which is the JSON/XML prot

Re: Initiating GSoC Project - JSON support and JSON to XML bidirectional conversion for Airavata

Raminder, My suggestion is to add web layer over the current API but i still see a > need of JS API for functions performed by Web XBaya to make it more clear. > We do need a JS API for the Web UI, which is the JSON/XML protocol conversion layer that we have been talking about. The point is that

[jira] [Commented] (AIRAVATA-406) Add the donated extreme lab, ogce jars to maven central

[ https://issues.apache.org/jira/browse/AIRAVATA-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677229#comment-13677229 ] Suresh Marru commented on AIRAVATA-406: --- I am importing the source code of these j

Jenkins build is back to normal : Apache Airavata » airavata-rest-service-webapp #1166

See

Re: Initiating GSoC Project - JSON support and JSON to XML bidirectional conversion for Airavata

Its good to have one API but the current API only works for Java clients. We have REST layer for registry functions but not for other API features. We need to either enhance the API to make it work for web clients or discuss other options. My suggestion is to add web layer over the current API

Re: Initiating GSoC Project - JSON support and JSON to XML bidirectional conversion for Airavata

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +1 for Amila's comments. There has been a lot of thought put into the current API. It still needs improvement but it is better to concentrate on one API with requirements from many perspectives instead of branching. Marlon On 6/6/13 9:14 AM, Amila

Re: Initiating GSoC Project - JSON support and JSON to XML bidirectional conversion for Airavata

Hi Shameera, The biggest disadvantage in having a separate JS API is, we have to maintain 2 API's (The Java API and the JS API you are going to introduce). So if we change one API for functionality, we have to make sure other API is also have that change. In the long run this will be inefficient a