Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 85317 invoked from network); 26 Mar 2008 10:34:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Mar 2008 10:34:48 -0000 Received: (qmail 78242 invoked by uid 500); 26 Mar 2008 10:34:45 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 78155 invoked by uid 500); 26 Mar 2008 10:34:45 -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 78144 invoked by uid 99); 26 Mar 2008 10:34:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Mar 2008 03:34:45 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of patrickheiden@gmx.de designates 213.165.64.20 as permitted sender) Received: from [213.165.64.20] (HELO mail.gmx.net) (213.165.64.20) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 26 Mar 2008 10:34:05 +0000 Received: (qmail 22426 invoked by uid 0); 26 Mar 2008 10:34:15 -0000 Received: from 91.40.215.194 by www185.gmx.net with HTTP; Wed, 26 Mar 2008 11:34:15 +0100 (CET) Content-Type: text/plain; charset="iso-8859-1" Date: Wed, 26 Mar 2008 11:34:15 +0100 From: "Patrick Heiden" Message-ID: <20080326103415.195300@gmx.net> MIME-Version: 1.0 Subject: [HELP]: Block conventions To: users@cocoon.apache.org X-Authenticated: #29485201 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 3 X-Provags-ID: V01U2FsdGVkX19/Uzcq8h9/0zX+fBzwzGEbgpuWOtYtxRcSPcRL+R L7NxCiWnIhtxfNj8cEVvb2iC/O1gopK+Qaaw== Content-Transfer-Encoding: 8bit X-GMX-UID: kB7fcwEGRkkNZ+WSsmVqn5hudWkvKBNP X-Virus-Checked: Checked by ClamAV on apache.org Hello togehter! While building a mainController-Block, wich defines my main routings and servlet-connections (through SSF) I read the following block conventions: http://cocoon.zones.apache.org/daisy/cdocs-site-main/g2/1345.html Within the tutorials there are several options, describing how blocks could be connected. So once a mainController-Block is defined and service-blocks are connected to it, one is able to call piplines and fragments from the connected blocks. The above mentioned conventions don't fit exactly into the described steps inside the tutorial, I think, because there is no usage of the recommended conventions. 1) shouldn't the 'myXsltTransformation-service' from myBlock2 be defined inside the myBlock2 pipline with id="service" to follow the conventions? 2) what is the difference between the external-recource and the service-pipeline? The conventions state, that external-recources are available to other blocks via servlet: protocol, but this is also true for the service-pipeline, not? 3) the service-pipeline (as the conventions say) is responsible for handling POST, is this 'pure' convention to possibly follow or are there any coded 'details' wich automatically enable this? The conventions are somewhat short on this point. Thanks for any comment, greetings Patrick -- Psssst! Schon vom neuen GMX MultiMessenger geh�rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org