Thanks for your final conclusion. Surely will save valuable time for many other developers !
There are too few postings of final outcomes to the list, especially in case of 'no solution'. Greetings Andreas ----- Original Message ---- From: Steven D. Majewski <[EMAIL PROTECTED]> To: users@cocoon.apache.org Sent: Thursday, July 12, 2007 5:55:10 PM Subject: Re: Using xsl:message and Cocoon As the OP in that thread, I should note that despite Mark's help, I was still never able to find a trace of the xsl:message output. However, I gave up and tried some alternative ways of debugging instead, so I didn't spend a lot of time trying to figure out why it didn't work for me. Perhaps a xalan vs saxon issue? -- Steve Majewski On Jul 11, 2007, at 8:09 PM, Joerg Heinicke wrote: > On 05.07.2007 11:43, Mike Dawson wrote: > >> I have a few XSL's I'm attempting to do some basic debugging on >> and would like to use just plain old xsl:message to get an idea >> about certain variables through the execution of the XSL. > >> Unfortunately after grepping the logs directory there was no sign >> of the string I had in xsl:message - and no sign of core.log > >> Any help getting to xsl:message would be most appreciated. > > There is a thread from the beginning of this year [1], especially > Mark Lundquist's message [2] explains where the message goes to. > > Joerg > > [1] http://marc.info/?l=xml-cocoon-users&m=116983397905795&w=4 > [2] http://marc.info/?t=116961044500003&r=1&w=4 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
