forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <>
Subject capture cocoon error messages (Was: How do I create Forrest:* styles?)
Date Thu, 21 Oct 2004 04:24:09 GMT
Dave Brondsema wrote:
> David Crossley wrote:
> > Ross Gardler wrote:
> > 
> >>I'm afraid I don't know what to suggest, but the fact that Open Office 
> >>will no longer open your file does not sound good with respect to the 
> >>correctness of your modified Open Office document.
> > 
> > This is the sort of thing that worries me about enabling
> > these other formats as sources for Forrest. It will be
> > Forrest that gets blamed for the almost un-intelligible
> > messages that Cocoon is forced to spew out.
> > 
> > I suppose we can always add FAQs about such things.
> > 
> > It is also of concern that we might get dragged into
> > user help situations about those formats. We will need
> > good defense against a certain infamous word processor.
> > 
> > One defense would be to have very good example documents
> > in our seed site. That way we can simply say "go compare
> > with the xxxx-v11.sxw file".
> It'd be ideal if our error messages pointed people at the *real* 
> problem.  If we said something like
> "Cocoon Error:
> Could not validate document ..../file.sxw
> This is an .sxw file that is probably not formatted 
> properly.  Please make sure this file is formatted correctly and compare 
> it with the example in the 'forrest seed' site"
> This notes that the problem is coming from Cocoon (although that doesn't 
> really help the end-user, I guess).  And if we intercept the error 
> message to give context-sensitive help (for jspwiki,, etc)

Ah, i did not realise that we could capture those.
Is this the <handle-errors> component at the end of
the Cocoon sitemap?

David Crossley

View raw message