cocoon-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From da...@cocoon.zones.apache.org
Subject [DAISY] Updated: Overview
Date Fri, 14 Mar 2008 16:56:56 GMT
A document has been updated:

http://cocoon.zones.apache.org/daisy/documentation/1412.html

Document ID: 1412
Branch: main
Language: default
Name: Overview (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 3/14/08 4:56:47 PM
Updated by: Reinhard Pötz

A new version has been created, state: publish

Parts
=====

Content
-------
This part has been updated.
Mime type: text/xml (unchanged)
File name:  (unchanged)
Size: 7773 bytes (previous version: 7395 bytes)
Content diff:
(26 equal lines skipped)
    
    </ul>
    
+++ <h2>Servlet Management</h2>
+++ 
+++ <p>The current implementation of the Servlet-Service-Framework uses Spring to
+++ manage servlets. All those servlets are ordinary Spring beans that implement the
+++ <tt>javax.servlet.Servlet</tt> interface. It's important to note that these
+++ servlets are not available from within a the servlet container (Jetty, Tomcat,
+++ etc.). The connection to the outside world is the <tt>DispatcherServlet</tt>
+++ that delegates requests to one of the mounted servlets (for details see the next
+++ section). This is the only servlet that is exposed in the web.xml and can
+++ directly be accessed using an HTTP call to the servlet container.</p>
+++ 
+++ <p align="center"><img src="daisy:1430"/></p>
+++ 
    <h2>Request dispatching</h2>
    
    <p>The most basic functionality is request dispatching that is handled by the
    <a href="http://cocoon.apache.org/subprojects/servlet-service/1.0/servlet-service-impl/1.0/apidocs/org/apache/cocoon/servletservice/DispatcherServlet.html"><tt>DispatcherServlet</tt></a>.
--- The dispatcher servlet, which is managed by a Java web application container, is
--- the entry point to all servlets that are managed by the servlet-service
--- framework. The current implementation of the Servlet-Service-Framework uses
--- Spring to manage the servlets:</p>
--- 
--- <p align="center"><img src="daisy:1430"/></p>
--- 
--- <p>Each servlet is registered by setting the property <tt>mount-path</tt>.
This
+++ Each servlet is registered by setting the property <tt>mount-path</tt>. This
    property defines the request path which can be used to access a particular
    servlet. When a request is being handled by the DispatcherServlet, it scans all
    the registered servlets and checks if  the <tt>mount-path</tt> property of
any
(162 equal lines skipped)


Mime
View raw message