cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Akber Choudhry <>
Subject better container compliance
Date Mon, 11 Mar 2002 15:30:43 GMT

Here are some mods done specifically for Websphere, but may be used
elsewhere. I also have my home-grown version of the IBM WAS StoredResponse
in case we agree to use some of this.

Itch: JSP generator should really be a servlet generator as JSP's are
handled by the JSP servlet, which invokes different compilers in various
implementations.  Cocoon should not be implementation specific  and not
call the compiler directly, honouring the Container and J2EE spec.  Also,
we should only take the buffered output of the response and, and ignore most
headers (until response headers from external input can participate in
complex pipeline handling -- future ).

Scratch: In this way, the servlet can be the PHP servlet, SSI, CGI or any
other existing business servlet, and the web application URI map is
honoured.  Makes cocoon co-exist and enhance web applications.

Just the relevant portions --

public class ServletEngineImplRequestDispatcherInclude extends
    implements ServletEngine, ThreadSafe {

    public byte[] executeURI(String url, HttpServletRequest httpRequest,
HttpServletResponse httpResponse, ServletContext context)
        throws IOException, ServletException, Exception {

        byte[] bytes = null;

        // get ServletEngine Dispatcher.
        javax.servlet.RequestDispatcher rd = context.getRequestDispatcher(
url );
        StoredResponse storedresponse = new StoredResponse();
        if (rd != null) {
          rd.include( httpRequest, storedresponse );
		  bytes = storedresponse.getOutputBuffer();
        } else {
          getLogger().error( "Error getting " + url + "from ServletEngine
Dispatcher" );
        return bytes;


Itch: Cocoon servlets attempts to write the content type when sending an
error to the container.  Changed -- moved sendError after the bean
creation and put the bean into the session.  Invalidate the session in the
web application error page.  Container handles gracefully.

                SimpleNotifyingBean n = new SimpleNotifyingBean(this);
                n.setTitle("Resource not found");
                n.setSource("Cocoon servlet");
                n.setMessage("The requested resource not found.");
                n.setDescription("The requested URI \""
                                 + request.getRequestURI()
                                 + "\" was not found.");
                n.addExtraDescription("path-info", uri);
                // send the notification but don't include it in the
output stream
                // as the status SC_NOT_FOUND is enough
                req.getSession(true).setAttribute("cocoon_error", n);

              // webapp error
res.setContentType(Notifier.notify(n, (OutputStream)null));

----------- sample webapp error page ---

<%@ page isErrorPage="true" %>
<jsp:useBean id="cocoon_error" scope="session"
<title>Error: <%=exception.getMessage()
<h2> Cocoon Error </h2>
<font face="Verdana" color="red" size="3">
<b><em><%= exception.getMessage() %> </em></b>
<% if (cocoon_error != null) { %>
<br/><b> Error Type:&nbsp;</b><%= cocoon_error.getType() %>
<br/><b> Error Title:&nbsp;</b><%= cocoon_error.getTitle() %>
<br/><b> Error Source:&nbsp;</b><%= cocoon_error.getSource() %>
<br/><b> Error Sender:&nbsp;</b><%= cocoon_error.getSender() %>
<br/><b> Error Message:&nbsp;</b><%= cocoon_error.getMessage() %>
<br/><b> Error Description:&nbsp;</b><%= cocoon_error.getDescription()
<br/><b> Extra Description(s):&nbsp;</b><%=
cocoon_error.getExtraDescriptions() %>
<br/><b> Stack Trace:&nbsp;</b><br/>
<% } %>
<% exception.printStackTrace(new PrintWriter(out)); %>
<% session.invalidate(); %>

Akber Choudhry
Dyanet Inc.

To unsubscribe, e-mail:
For additional commands, email:

View raw message