cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Uli Mayring <>
Subject Re: what is relationship between cocoon and java servlet?
Date Fri, 26 May 2000 23:33:12 GMT
On Fri, 26 May 2000, sudhi wrote:

> Cocoon is a Servlet, which serves all the user requests which has a .xml
> at the end.
> How to map all the .xml requests to Cocoon is done by configuring
> servlet engine.

Only in the case where the servlet engine acts as a web server. The web
server is responsible for this mapping, it has to decide which URIs it
asks the servlet engine to resolve.

> A request comes in which is requesting an xml file. The request is
> passed to Servlet engine. Servlet engine then sends this request to
> Cocoon, then Cocoon which itself is a servlet serves this request.

This has nothing to do with the .xml extension, the webserver can send any
URI to the servlet engine. What is important is what servlet the request
is sent to. If you specify in your web server that all files with
extension .xml are sent to the URI
then what you described happens. Of course only if Cocoon actually runs in
the servlet zone myservlets and the servlet server serving that zone runs
on host server.myorg.tld and listens on port 4444.

In our case, for example, we have many servlet servers running on
many machines and only some of them run cocoon. Others run other
servlets and yet others run cocoon and other servlets. We even have
machines running more than one servlet server. So, our processing
workflow is driven by the URI that the user request. Within the URI there
are three parts that you can use to define your processing workflow:

1. Hostname/IP address
2. Port
3. Servlet Zone

Within cocoon itself you can further refine your workflow with processing
instructions, but that is kind of ugly. Much better will be cocoon2 with
the sitemap.


Ulrich Mayring
DENIC eG, Softwareentwicklung

View raw message