Hi Colin,
I'm not sure how you're testing, but using the Xalan command line driver,
errors, messages, and warnings are all reported to stdout. This is the
default, unless you've installed a ProblemListener that does something
else. Have you written your own code using XalanTransformer, or are you
using the command line utility?
Dave
Colin Paul Adams
<[EMAIL PROTECTED] To:
[email protected]
mon.co.uk> cc: (bcc: David N
Bertoni/Cambridge/IBM)
Subject: Capturing output (Was:
function-available not working)
03/04/2003 11:47
PM
>>>>> "David" == David N Bertoni/Cambridge/IBM <[EMAIL PROTECTED]>
writes:
David> Hi Colin,
David> When I add the missing xsl:choose, I get the following:
Oh dear - I am really rusty on XSLT -n I must get back to speed soon.
David> way you capture output from the processor, because you
David> missed the error message.
Now this is something that puzzles me. I would have expected to see
the error message on standard error (it is where I see the output from
xsl:message when I eliminate syntax errors).
What parameters affect this?
--
Colin Paul Adams
Preston Lancashire
- function-available not working Colin Paul Adams
- Re: function-available not working David N Bertoni/Cambridge/IBM
- Capturing output (Was: function-ava... Colin Paul Adams
- Re: Capturing output (Was: func... David N Bertoni/Cambridge/IBM
- Re: Capturing output (Was: ... Colin Paul Adams
- Re: Capturing output (... David N Bertoni/Cambridge/IBM
- Re: Capturing outp... Colin Paul Adams
- Re: Capturing ... David N Bertoni/Cambridge/IBM
- Re: Capturing ... Colin Paul Adams
- Re: Capturing ... David N Bertoni/Cambridge/IBM
