Hy;
I get mad debugging complex stylesheets with cocoon.
When i use saxon from commandline i get the error line
where the problem occured. That helps much more, than
the cocoon output:
Look at this original cocoon error message:
#######################################################################
type fatal
message Exception during processing of file:/tomcat/webapps/cocoon/engine/xsl/search.xsl
description org.apache.cocoon.ProcessingException:
Exception during processing of file:/tomcat/webapps/cocoon/engine/xsl/search.xsl:
org.apache.xml.utils.WrappedRuntimeException: Could not find variable with the name of bgcolor
sender org.apache.cocoon.servlet.CocoonServlet
source Cocoon servlet
stack-trace
#########################################################################
How can i determine, where the parser stumbled over the problem ?
by the way, in this case i found the error after a while and i was really
surprised, what caused the problem, but this is another story ;-(
Anyway with cocoon-2.0 it was merely a "try and error" game, until
i found the problem ...
I wonder, if cocoon could be a little more friendly, when
it comes to error detection. Maybe there is a magic switch somewhere,
that could help?
If there is nothing, maybe someone could give me a hint, where to look
in the cocoon sources to enhance the error reporter ...
best regards, Hussayn
--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
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: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
