Return-Path: X-Original-To: apmail-pivot-user-archive@www.apache.org Delivered-To: apmail-pivot-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0F5508F85 for ; Mon, 8 Aug 2011 13:40:07 +0000 (UTC) Received: (qmail 21418 invoked by uid 500); 8 Aug 2011 13:40:06 -0000 Delivered-To: apmail-pivot-user-archive@pivot.apache.org Received: (qmail 21319 invoked by uid 500); 8 Aug 2011 13:40:06 -0000 Mailing-List: contact user-help@pivot.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@pivot.apache.org Delivered-To: mailing list user@pivot.apache.org Received: (qmail 21308 invoked by uid 99); 8 Aug 2011 13:40:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Aug 2011 13:40:06 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Aug 2011 13:40:00 +0000 Received: from ben.nabble.com ([192.168.236.152]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1QqQ3P-00046i-ON for user@pivot.apache.org; Mon, 08 Aug 2011 06:39:39 -0700 Date: Mon, 8 Aug 2011 06:39:39 -0700 (PDT) From: "Thomas G. Schuessler" To: user@pivot.apache.org Message-ID: <1312810779750-3235577.post@n3.nabble.com> In-Reply-To: <1612972C-EE5B-4CF2-B2E7-FBE08FA909E5@verizon.net> References: <4E3D3108.30606@arasoft.de> <1312638567482-3231076.post@n3.nabble.com> <1612972C-EE5B-4CF2-B2E7-FBE08FA909E5@verizon.net> Subject: Re: Invoking an HTTP POST service that returns a value object, not a URL MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit gk_brown@verizon.net wrote: > > I forgot about one other important aspect of this. Query only defines a > single serializer property. Currently, that serializer is used to read > GETs and write POSTs and PUTs. Will you be able to use a single serializer > to address your use case? I imagine so, since Serializer defines both > readObject() and writeObject(), but I just wanted to make sure. > I do not foresee any problems. gk_brown@verizon.net wrote: > > If so, it might be possible to lift the restriction on line 469 that > requires a GET request in order to return data. Does anyone know if it is > possible to determine if a request contains a response body? Perhaps that > check could be used to gate the if block instead of method == Method.GET. > Might getContentLength() help? In the meantime I have tried out the Jersey client library. Everything I need works fine. Would it make sense to consider using Jersey with Pivot? What would need to be done to have the same level of integration as available for Pivot.Query (notifying listeners etc.)? -- View this message in context: http://apache-pivot-users.399431.n3.nabble.com/Invoking-an-HTTP-POST-service-that-returns-a-value-object-not-a-URL-tp3230971p3235577.html Sent from the Apache Pivot - Users mailing list archive at Nabble.com.