Return-Path: 
 <dev-return-94772-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@www.apache.org
Received: (qmail 20005 invoked from network); 16 May 2007 12:42:32 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 16 May 2007 12:42:31 -0000
Received: (qmail 21099 invoked by uid 500); 16 May 2007 12:42:36 -0000
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 21012 invoked by uid 500); 16 May 2007 12:42:36 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
List-Post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
List-Id: <dev.cocoon.apache.org>
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 21001 invoked by uid 99); 16 May 2007 12:42:36 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 May 2007 05:42:36 -0700
X-ASF-Spam-Status: No, hits=1.3 required=10.0
	tests=RCVD_NUMERIC_HELO,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: domain of ap-cocoon-dev@m.gmane.org
 designates 80.91.229.2 as permitted sender)
Received: from [80.91.229.2] (HELO ciao.gmane.org) (80.91.229.2)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 May 2007 05:42:27 -0700
Received: from list by ciao.gmane.org with local (Exim 4.43)
	id 1HoIpI-0001Qz-SI
	for dev@cocoon.apache.org; Wed, 16 May 2007 14:41:56 +0200
Received: from 217.244.9.5 ([217.244.9.5])
        by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <dev@cocoon.apache.org>; Wed, 16 May 2007 14:41:56 +0200
Received: from alexander.klimetschek by 217.244.9.5 with local (Gmexim 0.1
 (Debian))
        id 1AlnuQ-0007hv-00
        for <dev@cocoon.apache.org>; Wed, 16 May 2007 14:41:56 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: dev@cocoon.apache.org
From: Alexander Klimetschek <alexander.klimetschek@mindquarry.com>
Subject: Re: More problems with implementing servlet services
Date: Wed, 16 May 2007 14:41:44 +0200
Lines: 42
Message-ID: <f2eu67$3dp$1@sea.gmane.org>
References: <4640A55B.8070200@tuffmail.com> <46424753.1020005@nada.kth.se>
 <4643DB37.8070009@reverycodes.com> <f21l0q$heg$1@sea.gmane.org>
 <464477AB.4010903@nada.kth.se> <46448C13.2070508@apache.org>
 <464509E6.4010406@reverycodes.com> <46458BBF.7020909@apache.org>
 <f254m0$lki$1@sea.gmane.org> <4646C241.6040103@apache.org>
 <f27tob$uf8$1@sea.gmane.org> <46477F2C.8020708@apache.org>
 <4647FE2F.80404@apache.org> <464813FE.3050807@nada.kth.se>
 <4648781E.6040607@apache.org> <46487E7A.4060007@nada.kth.se>
 <46488E92.9050404@apache.org> <464962D7.9050406@nada.kth.se>
 <4649934A.3000703@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: 217.244.9.5
User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326)
In-Reply-To: <4649934A.3000703@apache.org>
Sender: news <news@sea.gmane.org>
X-Virus-Checked: Checked by ClamAV on apache.org

Reinhard Poetz schrieb:
> I think the problem here is that we have two sources and depending on 
> the context, one is the "main" source. But if it's only me having this 
> view on that, I won't argue for it any more.
> 
> Any other opinions?

I tend to Reinhard's opinion: from the user POV the src should state the 
service, because that is where I get my data from, ie. the data that is used 
in the subsequent pipeline.

The important point is how this compares with a simple servlet call, where I 
don't want to POST anything but simply retrieve data:

<generate src="servlet:something:/foo/bar" />

In this case you state the servlet as source. And this guides the user's 
model when adding the POST-feature; thus it is more natural to think of the 
POST as an addition, simply by using another generator and an additional 
parameter (I'd name it "postData" to be more concise):

<generate type="servletService" src="servlet:something:/foo/bar">
   <parameter name="postData" src="test.htm" />
</generate>

Only that seems logic to me...

Another question: did you think of the possibility of posting the initial 
HTTP request body to the servlet service? Eg. having a postData (or src) 
parameter like

   <parameter name="postData" src="request:body" />

???? A use case would be upon a PUT of some XML data from a client to a 
server and as a first step you wanna send the XML to a validating service.


Alex

-- 
Alexander Klimetschek
http://www.mindquarry.com