Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <4E0A5B62.9070808@apache.org>
Date: Wed, 29 Jun 2011 00:53:22 +0200
From: =?ISO-8859-15?Q?Reinhard_P=F6tz?= <reinhard@apache.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
 rv:1.9.2.17) Gecko/20110516 Thunderbird/3.1.10
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: [C3] Intra-pipeline calls
References: <4E0834BA.7070901@apache.org>
In-Reply-To: <4E0834BA.7070901@apache.org>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit

On 06/27/2011 09:43 AM, Francesco Chicchiricc� wrote:
> Hi all,
> in these days I am working quite intensively in building an overalyable,
> Cocoon 3 based, web application.
>
> Looking at the sample code, it seems that the only way to make
> "intra-pipeline" calls is by using the servlet: protocol, hence the
> Servlet service.
> Is that correct?
>
> If so, would this mean that the cocoon-sample-wicket-webapp cannot make
> intra-pipeline calls because the Servlet service (namely the
> DispatcherServlet) is not in place - we have a catch-all Wicket-style
> filter there?

Unfortunately you are right. I also don't have a good solution on hand 
ATM ...

-- 
Reinhard P�tz         Founder & Managing Director, Indoqa and Deepsearch
                         http://www.indoqa.com/people/reinhard-poetz.html

Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member                  reinhard@apache.org
________________________________________________________________________

       Furthermore, I think Oracle has to honor the JSPA agreement.
     http://s.apache.org/JCPIsDead       http://s.apache.org/tck-trap