Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 20556 invoked from network); 24 Jun 2000 01:25:48 -0000 Received: from smtp1.andrew.cmu.edu (128.2.10.81) by locus.apache.org with SMTP; 24 Jun 2000 01:25:48 -0000 Received: from lsec5 (LSEC5.PHIL.CMU.EDU [128.2.57.135]) by smtp1.andrew.cmu.edu (8.9.3/8.9.3) with SMTP id VAA09921 for ; Fri, 23 Jun 2000 21:25:45 -0400 (EDT) From: "Willie Wheeler" To: Subject: RE: Pulling the HTML out of CocoonServlet Date: Fri, 23 Jun 2000 21:32:56 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <3953D583.259E17DF@pwr.ch> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Hi Giacomo, Can you explain the idea of contexts here in more detail? Are the contexts just the different targets to which the XML could be transformed? (I am not familiar with SOAP, sorry.) What would the API for the abstract context-neutral class look like? If I understand you correctly, CocoonServlet would delegate to an ErrorReporter, which contains the hardcoded HTML (or whatever other formats we output to). Is it important for end users to be able to modify/customize the error messages that Cocoon displays? If so it might be better to use a server page and XSLT, as opposed to a Java class. Let me know what you think. And if you already have some concrete plans on how to proceed, tell me what they are so I can get started! :-) Willie -----Original Message----- From: giacomo@xml.apache.org [mailto:giacomo@xml.apache.org]On Behalf Of Giacomo Pati Sent: Friday, June 23, 2000 5:24 PM To: cocoon-dev@xml.apache.org Subject: Re: Pulling the HTML out of CocoonServlet Willie Wheeler wrote: > > Hi all, > > Also, I'd like to tackle the todo that says to pull the HTML out > of CocoonServlet, if somebody isn't already working on it. I'm thinking > that it would be good to forward to a dynamically generated error page. > Is this what people have in mind? Thank's for your offer to help. I had the vision of something like an abstract, context neutral class that handles the error cases. Implementing concrete classes base upon it for the different contexts (mail, soap, html, ...) Cocoon might be working in. Maybe pluggable ErrorReporters? Giacomo -- PWR GmbH, Organisation & Entwicklung Tel: +41 (0)1 856 2202 Giacomo Pati, CTO/CEO Fax: +41 (0)1 856 2201 Hintereichenstrasse 7 Mailto:Giacomo.Pati@pwr.ch CH-8166 Niederweningen Web: http://www.pwr.ch