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 3166810AC4 for ; Fri, 28 Jun 2013 18:50:11 +0000 (UTC) Received: (qmail 5981 invoked by uid 500); 28 Jun 2013 18:50:11 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 5945 invoked by uid 500); 28 Jun 2013 18:50:11 -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 5937 invoked by uid 99); 28 Jun 2013 18:50:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Jun 2013 18:50:11 +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 (nike.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, 28 Jun 2013 18:50:04 +0000 Received: by mail-ve0-f181.google.com with SMTP id db10so2107154veb.40 for ; Fri, 28 Jun 2013 11:49:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:cc:content-type; bh=i6oXNR/JHFRXOQWn4S/AL6XD8G4QCiCPsanJ4hBjlUE=; b=da10xFEOonnHnO/ivL0aheN846jSzmlxs5Bn7HfQvLNCu7MT41kO0wsCkctzNrIEAs wFHMWScfidSWvlBrDSEaQ59wRz9dcjhwqi1FegmqBW1yORycBFxQvS6Y1Tu+alSjrLZd ME9Vn23I54dc9BRvT9Uz9Nze3BHQUwKvZx6rZtWS5hfLiN2JmdQgICivIts1jEY6YYot 2iT4p+nMu/fmSrL7N8+4AuIML+3UUP/1cyKG5dZRsUix2yW5x2Qh+To16T9Z6Gr4oBND bZcMZ/xN/K/4F8KZy38e7P+J1Welf+tHh851BvB0i+h3EDSKMuIju5Gp87ZLofF/boeo tDiw== X-Received: by 10.52.164.227 with SMTP id yt3mr5091267vdb.107.1372445383732; Fri, 28 Jun 2013 11:49:43 -0700 (PDT) MIME-Version: 1.0 Received: by 10.58.228.41 with HTTP; Fri, 28 Jun 2013 11:49:23 -0700 (PDT) From: Shameera Rathnayaka Date: Sat, 29 Jun 2013 00:19:23 +0530 Message-ID: Subject: [GSoC] Registry side JSON implementation. To: dev Cc: Lahiru Gunathilake , Chathuri Wimalasena Content-Type: multipart/alternative; boundary=001a11c206929238b804e03b57a8 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c206929238b804e03b57a8 Content-Type: text/plain; charset=ISO-8859-1 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/ --001a11c206929238b804e03b57a8--