Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 89196 invoked from network); 31 Jul 2007 19:15:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 31 Jul 2007 19:15:48 -0000 Received: (qmail 94090 invoked by uid 500); 31 Jul 2007 19:15:44 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 94040 invoked by uid 500); 31 Jul 2007 19:15:44 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: users@cocoon.apache.org List-Id: Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 94026 invoked by uid 99); 31 Jul 2007 19:15:44 -0000 Received: from Unknown (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Jul 2007 12:15:44 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [216.86.168.179] (HELO mxout-04.mxes.net) (216.86.168.179) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Jul 2007 19:15:35 +0000 Received: from [192.168.0.129] (unknown [80.240.191.89]) by smtp.mxes.net (Postfix) with ESMTP id 0F24BA3238 for ; Tue, 31 Jul 2007 15:15:09 -0400 (EDT) Message-ID: <46AF8A34.6030509@apache.org> Date: Tue, 31 Jul 2007 21:15:00 +0200 From: Grzegorz Kossakowski User-Agent: Thunderbird 2.0.0.5 (X11/20070716) MIME-Version: 1.0 To: users@cocoon.apache.org Subject: Re: [cocoon 2.2.x] how to get request params in called block? References: <11928299.post@talk.nabble.com> In-Reply-To: <11928299.post@talk.nabble.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org xweber pisze: > hi, > > i want to deal e.g. html POST parameters in the called block. The sitemap in > myBlock1 has something like: > > > but unfortunatly in the called block all parameters are gone. It's a known problem and limitation of current implementation. See COCOON-2050[1] for some details. Alex, actually I recommend you taking a look at JIRA page[2] for Servlet Service framework issues overview. This will give an idea what's already there and what's not. Also, voting for particular issues can speed up process of implementing them. Of course you should choose issues carefully, voting for all of them will not help us anyhow. Speaking about myself, I would be very happy to work on all these issues but currently I'm busy with my Google of Summer tasks that have highest priority. > so, how to get request params in called block? If parameters are simple strings you can pass them using such construct: servlet:someblock:/somepipeline?request1={request-param:request1} Of course, such solution has it's own limitations but may be sufficient in many situations. As you want to use some pipeline for processing XML stream I think that the best way would be to use servletService transformer. You need your XML data in the pipeline, so you should use: And then you should use servletService transformer: > Alex > > PS: is there any "pure" cocoon 2.2 project out there, so i could get a sneak > peak how to put all things together? Unfortunately, not yet. I'm working on such project, but as I said above, GSoC is more important for me now. [1] https://issues.apache.org/jira/browse/COCOON-2050 [2] https://issues.apache.org/jira/secure/IssueNavigator.jspa?sorter/field=created&sorter/order=DESC -- Grzegorz Kossakowski http://reflectingonthevicissitudes.wordpress.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org