> From: Per Kreipke [mailto:[EMAIL PROTECTED]]
> 
> The stack trace shows that JavaLanguage.compile() is the routine that
emits
> the message:
> 
> org.apache.cocoon.ProcessingException: LanguageException:  Error
compiling
> foo.xsp: Line 0, column 0: error: java.io.IOException: read error 1
error
> 
> The section in compile() that emits all the errors known by the
compiler
> object _is_ looping through them but I suspect that the transformer
hasn't
> put any useful info in that error array.
> 
> Right above that stack trace in core.log is a bunch of exceptions
thrown by
> various stages in the transformer thread (all are thrown from a
> org.apache.xalan.transformer.* class, not a single Cocoon class in the
> bunch). My question would be how does one hook into the Xalan errors
and
> return them through Cocoon to the user?

Here is the hint. I guess these two files should be patched:

xml-cocoon203\src\java\org\apache\cocoon\components\xslt\XSLTProcessorIm
pl.java
xml-cocoon203\src\java\org\apache\cocoon\util\TraxErrorHandler.java


Vadim


> Per
> 
> > Vadim,
> >
> > This doesn't work that well.
> >
> > The message I specified inside the <xsl:message> does appear in
core.log
> > along with a stack trace but is not propagated to the resulting
page.
> >
> > The resulting HTML error is unusable: "Read error on line 0 of 0"
and does
> > not include the message I generated.
> >
> > How is Cocoon handling errors that this is happening?
> >
> > Per
> >
> >
> > > -----Original Message-----
> > > From: Per Kreipke [mailto:[EMAIL PROTECTED]]
> > > Sent: Monday, July 22, 2002 11:33 AM
> > > To: [EMAIL PROTECTED]
> > > Subject: RE: [Q] Returning XSP errors on incorrect use of a
> > > logicsheet...
> > >
> > >
> > > Awesome Vadim! Didn't know about @terminate! Will try.
> > >
> > > Per
> > >
> > > > >From xsp.xsl:
> > > >
> > > >     <xsl:message terminate="yes"><xsl:value-of
> > > > select="$message"/></xsl:message>
> > > >


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to