Return-Path: Delivered-To: apmail-incubator-cxf-issues-archive@locus.apache.org Received: (qmail 80114 invoked from network); 8 Sep 2006 09:07:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 8 Sep 2006 09:07:59 -0000 Received: (qmail 2435 invoked by uid 500); 8 Sep 2006 09:07:58 -0000 Delivered-To: apmail-incubator-cxf-issues-archive@incubator.apache.org Received: (qmail 2396 invoked by uid 500); 8 Sep 2006 09:07:58 -0000 Mailing-List: contact cxf-issues-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cxf-dev@incubator.apache.org Delivered-To: mailing list cxf-issues@incubator.apache.org Received: (qmail 2371 invoked by uid 99); 8 Sep 2006 09:07:57 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Sep 2006 02:07:57 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Sep 2006 02:07:57 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 5BE8A7142F4 for ; Fri, 8 Sep 2006 09:04:23 +0000 (GMT) Message-ID: <8942861.1157706263373.JavaMail.jira@brutus> Date: Fri, 8 Sep 2006 02:04:23 -0700 (PDT) From: "Jervis Liu (JIRA)" To: cxf-issues@incubator.apache.org Subject: [jira] Commented: (CXF-43) Support HTTP GET on server side for REST In-Reply-To: <18789321.1157618302983.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/CXF-43?page=comments#action_12433361 ] Jervis Liu commented on CXF-43: ------------------------------- Actually this does nothing with REST binding or XML binding. What we need is the capability on the HTTP transport layer to deal with HTTP GEt. When server side provider approach is used, we just need to grab URI path info and throw it into MessageContext, this info will be consumed later on by provider implementation. > Support HTTP GET on server side for REST > ---------------------------------------- > > Key: CXF-43 > URL: http://issues.apache.org/jira/browse/CXF-43 > Project: CeltiXfire > Issue Type: Sub-task > Reporter: Jervis Liu > > If we decide to creat a new binding called "REST binding", we need to make this REST binding be able to receive REST request using HTTP GET. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira