Return-Path: X-Original-To: apmail-airavata-dev-archive@www.apache.org Delivered-To: apmail-airavata-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 15C8B104F1 for ; Fri, 7 Jun 2013 01:40:00 +0000 (UTC) Received: (qmail 22245 invoked by uid 500); 7 Jun 2013 01:40:00 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 22209 invoked by uid 500); 7 Jun 2013 01:40:00 -0000 Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airavata.apache.org Delivered-To: mailing list dev@airavata.apache.org Received: (qmail 22201 invoked by uid 99); 7 Jun 2013 01:39:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Jun 2013 01:39:59 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of shameerainfo@gmail.com designates 209.85.128.181 as permitted sender) Received: from [209.85.128.181] (HELO mail-ve0-f181.google.com) (209.85.128.181) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Jun 2013 01:39:56 +0000 Received: by mail-ve0-f181.google.com with SMTP id db10so2637876veb.40 for ; Thu, 06 Jun 2013 18:39:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=/1eDYhnXzLSAcAYz9IQ2itx+7gsqgixq6LxIQydmN3o=; b=b33vetMsI4pfFejSWXow1HjpRjOTjeloEgguv2y12Hz3cpp5/D/4zN4UgCxyvVs9ez scbq8DXR25Lxk/ip8/SH752hpi5+ru7ijozUQKYMIgC6qc3fwcEgFqB92+LeArhMtvWJ iTBqonuQC4bqTul0MufFhTZrVsQvNrYHSOOzT7xPmtnWpBVnHSHAblb06WoE+1LdK8EY woihsV3H3J3294TaSW2VJIINqMaOC3Va6pChbDNwyYBpmVbD8ys+nWfgBtWSengMJSCN J54g50B/y9CHFPWqfZyg9/eUKrZl58m+2jcebdtCOa0hYHv0mA7ONpsxCazy1XhE1zbp 8uXQ== X-Received: by 10.58.221.134 with SMTP id qe6mr193756vec.2.1370569175084; Thu, 06 Jun 2013 18:39:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.58.8.81 with HTTP; Thu, 6 Jun 2013 18:39:14 -0700 (PDT) In-Reply-To: <241964AD-D670-4BF6-B7BD-0FCA78033E1C@gmail.com> References: <51B08CA7.7010002@iu.edu> <56CDE5CC-C79B-4FC3-A566-6935FA12412F@gmail.com> <241964AD-D670-4BF6-B7BD-0FCA78033E1C@gmail.com> From: Shameera Rathnayaka Date: Fri, 7 Jun 2013 07:09:14 +0530 Message-ID: Subject: Re: Initiating GSoC Project - JSON support and JSON to XML bidirectional conversion for Airavata To: dev Content-Type: multipart/alternative; boundary=047d7bf0e8ded240d604de868062 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bf0e8ded240d604de868062 Content-Type: text/plain; charset=ISO-8859-1 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/beckchr/staxon/wiki/Using-JAXB > > +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 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 protocol > > conversion layer that we have been talking about. The point is that it > > should not be a native, heavyweight JS API but, a thin JS layer that > wraps > > the current Java API. > > > > Thanks, > > Danushka > > -- Best Regards, Shameera Rathnayaka. email: shameera AT apache.org , shameerainfo AT gmail.com Blog : http://shameerarathnayaka.blogspot.com/ --047d7bf0e8ded240d604de868062--