Return-Path: Delivered-To: apmail-axis-c-user-archive@www.apache.org Received: (qmail 83807 invoked from network); 12 May 2010 13:29:19 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 12 May 2010 13:29:19 -0000 Received: (qmail 17358 invoked by uid 500); 12 May 2010 13:29:18 -0000 Delivered-To: apmail-axis-c-user-archive@axis.apache.org Received: (qmail 17343 invoked by uid 500); 12 May 2010 13:29:17 -0000 Mailing-List: contact c-user-help@axis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache AXIS C User List" Delivered-To: mailing list c-user@axis.apache.org Received: (qmail 17335 invoked by uid 500); 12 May 2010 13:29:17 -0000 Delivered-To: apmail-ws-axis-c-user@ws.apache.org Received: (qmail 17332 invoked by uid 99); 12 May 2010 13:29:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 May 2010 13:29:17 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of scarleton@gmail.com designates 209.85.221.201 as permitted sender) Received: from [209.85.221.201] (HELO mail-qy0-f201.google.com) (209.85.221.201) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 May 2010 13:29:10 +0000 Received: by qyk39 with SMTP id 39so634487qyk.8 for ; Wed, 12 May 2010 06:28:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=3gLNaqGHUHhc2+ou5KQkbQkkOr9vSGZQBiWwhJXfXLk=; b=MJqXQ5XXRFdeLTnSYBs51yXiE7fUlPUA+ledzI+qrPrpJaTUBDqYPDJjrZfCn5ACh6 U2a6faFLdPbpkbQ7l5M9lZqjGuOLQYDKtCR5SlU2FwB401Z39fGTGFIXGhx5tRQfceJv HL4UOGfuzuFbNwQx3CiT+MzqSn3sDcz1oPDfo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=Dgl+m07jsYcQFw28ZXFiAqkrrtZrGLQLLl68me4/96LXFZ4HIY3lYsXYL88ImwnDLq PS3ScLfVlgTUkEdDNyxhdDrFL8ZOYgjhse6F5Fc/6bRBf9aqdlyVMxOEIFzLXJIQvMlf Z/3ldrJ9zRsOR9sHOoMfQTBdVPof88c70S2ws= MIME-Version: 1.0 Received: by 10.224.59.30 with SMTP id j30mr5010120qah.143.1273670929091; Wed, 12 May 2010 06:28:49 -0700 (PDT) Sender: scarleton@gmail.com Received: by 10.224.11.3 with HTTP; Wed, 12 May 2010 06:28:49 -0700 (PDT) Date: Wed, 12 May 2010 09:28:49 -0400 X-Google-Sender-Auth: vVXJh_fCNBxA5kxyyxd04EREz3s Message-ID: Subject: JSON support From: Sam Carleton To: Apache AXIS C User List Content-Type: multipart/alternative; boundary=00c09f9235fe4a135c0486659f5a X-Virus-Checked: Checked by ClamAV on apache.org --00c09f9235fe4a135c0486659f5a Content-Type: text/plain; charset=UTF-8 I see that Microsoft supports JSON services in their WCF framework. I am wondering if the Axis2 team has ever considered adding JSON support? It is my impression that the engine would already support it, it is just a matter of adding support to WSDL2C, correct? Sam --00c09f9235fe4a135c0486659f5a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I see that Microsoft supports JSON services in their WCF framework.=C2=A0 I= am wondering if the Axis2 team has ever considered adding JSON support?=C2= =A0 It is my impression that the engine would already support it, it is jus= t a matter of adding support to WSDL2C, correct?

Sam
--00c09f9235fe4a135c0486659f5a--