You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Lajos Moczar <lm...@galatea.com> on 2002/07/16 22:04:32 UTC

Debugging buggy XSL code

Hi all -

At various times (or versions), I though I have seen Cocoon spit out 
messages about XSL errors, like "The element type "xsl:if" must be 
terminated by a matching end-tag". In 2.0.2, these messages come at the 
Tomcat console window or logs. Wouldn't it be helpful to capture these 
messages and add them to Cocoon error page? It would certainly help me - 
the "Transform error: null pointer exception" doesn't mean very much.

If someone has an idea of where the change needs to be made, unless it 
has already been done, I'll gladly look into doing it.

Regards,

Lajos

-- 
galatea.com
Cocoon training, consulting & support



---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>


Re: Debugging buggy XSL code

Posted by "Andrew C. Oliver" <ac...@apache.org>.
Hi Lajos,

Generally you can have these errors spit out on a nice error page, but 
you probably also see errors regarding not being able to find some error 
stylesheet thing.  I believe its called error2html.xsl or maybe 
error2document.xsl.  You'll notice cocoon is looking for this somewhere 
other than where it actually is located.  If you copy this to where it 
is looking for it then you'll get a pretty helpful error page.  I'm not 
sure if this is a bug or what, but its certainly annoying.

thanks,

-Andy

Lajos Moczar wrote:

> Hi all -
>
> At various times (or versions), I though I have seen Cocoon spit out 
> messages about XSL errors, like "The element type "xsl:if" must be 
> terminated by a matching end-tag". In 2.0.2, these messages come at 
> the Tomcat console window or logs. Wouldn't it be helpful to capture 
> these messages and add them to Cocoon error page? It would certainly 
> help me - the "Transform error: null pointer exception" doesn't mean 
> very much.
>
> If someone has an idea of where the change needs to be made, unless it 
> has already been done, I'll gladly look into doing it.
>
> Regards,
>
> Lajos
>




---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>