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?

Thanks.

--
Francesco Chicchiriccò

Apache Cocoon Committer and PMC Member
http://people.apache.org/~ilgrosso/

Reply via email to