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 reinh...@apache.org
________________________________________________________________________
Furthermore, I think Oracle has to honor the JSPA agreement.
http://s.apache.org/JCPIsDead http://s.apache.org/tck-trap
