Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 61616 invoked from network); 28 May 2009 22:34:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 28 May 2009 22:34:53 -0000 Received: (qmail 11067 invoked by uid 500); 28 May 2009 22:24:33 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 10970 invoked by uid 500); 28 May 2009 22:24:33 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 10961 invoked by uid 99); 28 May 2009 22:24:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 May 2009 22:24:33 +0000 X-ASF-Spam-Status: No, hits=-0.5 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS,URIBL_BLACK X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of sukoneru@cisco.com designates 171.71.176.117 as permitted sender) Received: from [171.71.176.117] (HELO sj-iport-6.cisco.com) (171.71.176.117) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 May 2009 22:24:22 +0000 X-IronPort-AV: E=Sophos;i="4.41,267,1241395200"; d="scan'208";a="312598685" Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 28 May 2009 22:24:00 +0000 Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n4SMO0b7018396 for ; Thu, 28 May 2009 15:24:00 -0700 Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n4SMO0wu027125 for ; Thu, 28 May 2009 22:24:00 GMT Received: from xmb-sjc-21a.amer.cisco.com ([171.70.151.152]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 28 May 2009 15:24:00 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: Axis 2.0 support for Restful services Date: Thu, 28 May 2009 15:23:59 -0700 Message-ID: <5BD9FA70F5EDAC43AB816A5FDE30F6AC096107AF@xmb-sjc-21a.amer.cisco.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Axis 2.0 support for Restful services Thread-Index: Acnf3VdWGX5/EUNtQ9OTS6D0N7wZigABKYFA References: <5BD9FA70F5EDAC43AB816A5FDE30F6AC09610285@xmb-sjc-21a.amer.cisco.com> <474d01b00905272329x38873062sdcf40edaa6f44573@mail.gmail.com> <5BD9FA70F5EDAC43AB816A5FDE30F6AC09610724@xmb-sjc-21a.amer.cisco.com> From: "Suchitha Koneru (sukoneru)" To: X-OriginalArrivalTime: 28 May 2009 22:24:00.0196 (UTC) FILETIME=[FFADE840:01C9DFE2] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2707; t=1243549440; x=1244413440; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=sukoneru@cisco.com; z=From:=20=22Suchitha=20Koneru=20(sukoneru)=22=20 |Subject:=20RE=3A=20Axis=202.0=20support=20for=20Restful=20 services |Sender:=20; bh=WX/tHUvSWhNKScmNU2vyAHm6sAtiFkDPzqW2y6r9VNU=; b=nuLjI7RhSW4OojRHd9AlRLQBV89bg9cxuMey8oqBB/rS3+w/YVThXtRW7p Hf1HPv20u7o11wuay8WdVphPhfsJi6tk4fTXLbgn+z3bGu812Md+TG7C0sYJ fvQ7sKdfs1; Authentication-Results: sj-dkim-3; header.From=sukoneru@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); X-Virus-Checked: Checked by ClamAV on apache.org Thanks Andreas for the clarification. So we can post any xml payload in = a restful manner to axis 2 webservice from any webservice client. Will = Axis 2 web service engine treat the request as restful request and send = the response as xml? Thanks, Suchitha. -----Original Message----- From: Andreas Veithen [mailto:andreas.veithen@gmail.com]=20 Sent: Thursday, May 28, 2009 2:43 PM To: axis-user@ws.apache.org Subject: Re: Axis 2.0 support for Restful services OMElement is Axis2's internal representation of an XML element. Cross = platform communication has nothing to do with how the wire format is = represented internally. Andreas On Thu, May 28, 2009 at 23:06, Suchitha Koneru (sukoneru) = wrote: > Thank you Sagara and Chinmoy for your response. I have gone through = the links which are helpful. > Hello Axis Developers. > I have observed that HTTP Post is done through OMElement (which is=20 > custom class in axis). =A0This is specified in the link = http://ws.apache.org/axis2/1_1/rest-ws.html. > If I want to post simple xml Payload to Axis2 Service in a RESTFUL = manner from a .NET or a Flex client(cross platform client) How do I do = it? I cannot use OMElement here as It is not present in .NET framework = or Flex. > Any pointers are greatly appreciated. All of us use web services for = cross platform communication, so we might stumble upon this issue sooner = or later. > > Thanks, > suchitha > > > > -----Original Message----- > From: Sagara Gunathunga [mailto:sagara.gunathunga@gmail.com] > Sent: Wednesday, May 27, 2009 11:29 PM > To: axis-user@ws.apache.org > Subject: Re: Axis 2.0 support for Restful services > > Hi Suchitha, > Axis2 Supported for REST from its early releases ,you can refer = following links [1] [2] for more details ,but at the moment Axis2 does = not supports for JAX-RS (JSR 311) annotation based RESTFUL service = model. > > [1] - http://wso2.org/blog/keith/958 > [2]- http://wso2.org/library/175 > > Thanks , > > On Thu, May 28, 2009 at 9:45 AM, Chinmoy Chakraborty = wrote: >> try this: http://ws.apache.org/axis2/0_94/rest-ws.html >> >> Chinmoy >> >> On Thu, May 28, 2009 at 3:39 AM, Suchitha Koneru (sukoneru)=20 >> wrote: >>> >>> Hello all , >>> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Does Axis 2.0 support JAX-RS = and JSR 331 ? Could you=20 >>> please provide information in regard to the support provided by Axis = >>> 2.0 for developing RESTFUL services. >>> thanks, >>> suchitha. >> > > > > -- > Sagara Gunathunga > > Blog - http://ssagara.blogspot.com > Web - http://sagaras.awardspace.com/ >