Return-Path: 
 <cloudstack-dev-return-20726-apmail-incubator-cloudstack-dev-archive=incubator.apache.org@incubator.apache.org>
X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org
Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 7D1D7E2C3
	for <apmail-incubator-cloudstack-dev-archive@minotaur.apache.org>;
 Tue,  5 Feb 2013 23:28:39 +0000 (UTC)
Received: (qmail 91103 invoked by uid 500); 5 Feb 2013 23:28:38 -0000
Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org
Received: (qmail 91065 invoked by uid 500); 5 Feb 2013 23:28:38 -0000
Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:cloudstack-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:cloudstack-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:cloudstack-dev@incubator.apache.org>
List-Id: <cloudstack-dev.incubator.apache.org>
Delivered-To: mailing list cloudstack-dev@incubator.apache.org
Received: (qmail 91055 invoked by uid 99); 5 Feb 2013 23:28:38 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Feb 2013 23:28:38 +0000
X-ASF-Spam-Status: No, hits=-5.0 required=5.0
	tests=RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of Edison.su@citrix.com designates
 66.165.176.89 as permitted sender)
Received: from [66.165.176.89] (HELO SMTP.CITRIX.COM) (66.165.176.89)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Feb 2013 23:28:32 +0000
X-IronPort-AV: E=Sophos;i="4.84,610,1355097600";
   d="scan'208";a="6405321"
Received: from sjcpmailmx01.citrite.net ([10.216.14.74])
  by FTLPIPO01.CITRIX.COM with ESMTP/TLS/RC4-MD5; 05 Feb 2013 23:28:10 +0000
Received: from SJCPMAILBOX01.citrite.net ([10.216.4.73]) by
 SJCPMAILMX01.citrite.net ([10.216.14.74]) with mapi; Tue, 5 Feb 2013 15:28:09
 -0800
From: Edison Su <Edison.su@citrix.com>
To: 'Mike Tutkowski' <mike.tutkowski@solidfire.com>,
	"cloudstack-dev@incubator.apache.org" <cloudstack-dev@incubator.apache.org>
Date: Tue, 5 Feb 2013 15:28:10 -0800
Subject: RE: JSON Question
Thread-Topic: JSON Question
Thread-Index: Ac4D94WQzaFD6sbRQoqIyLVXxIxZDgAANfJg
Message-ID: 
 <C66C814C1ABFA8449FF65CB44953A8B4012CC09A8BC5@SJCPMAILBOX01.citrite.net>
References: 
 <CACOnxCgmmv6r05urBhdT13Rcx=AhTTvDafGriTNJycrPF9fNTw@mail.gmail.com>
In-Reply-To: 
 <CACOnxCgmmv6r05urBhdT13Rcx=AhTTvDafGriTNJycrPF9fNTw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Virus-Checked: Checked by ClamAV on apache.org

You can add:

    <dependency>
      <groupId>com.google.code.gson</groupId>
      <artifactId>gson</artifactId>
      <version>${cs.gson.version}</version>
    </dependency>
Into your maven pom file, then use gson right away.

> -----Original Message-----
> From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
> Sent: Tuesday, February 05, 2013 3:21 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: JSON Question
>=20
> Hi everyone,
>=20
> I'm writing a storage plug-in and have gotten to the point where I need t=
o
> make a call out to our SAN to dynamically create storage for a Compute or
> Disk Offering.
>=20
> Our SAN's API talks JSON.
>=20
> Do we already make use of JSON inside of the Management Server?  I expect
> we use it in other parts of the system, but want to make sure I'm leverag=
ing
> the right component(s) when I start writing this API code.
>=20
> Thanks!
>=20
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud<http://solidfire.com/solution/overview/?video=3Dplay>
> *(tm)*