Hi
Marco,
I
tried putting try / catch blocks round all of the code in the methods I have
overridden but no exceptions were caught.
Do you
suggest any other ways to debug a transformer?
Keith.
-----Original Message-----
From: Marco Rolappe [mailto:[EMAIL PROTECTED]
Sent: 12 March 2003 14:43
To: [EMAIL PROTECTED]
Subject: AW: Problem writing a BetwixtTransformerhi keith,I didn't analyze the code and can't tell you directly where the bug is but...I also got a similar exception which seemed to be an XSLT/xalan exception but actually was an exception thrown from within a custom transformer. somehow the stack trace seems to have been lost.you might want to debug your trasformer to find the actual bug.-----Ursprüngliche Nachricht-----
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]Im Auftrag von Lyall, Keith
Gesendet: Mittwoch, 12. März 2003 14:16
An: '[EMAIL PROTECTED]'
Betreff: Problem writing a BetwixtTransformerHi,
I am trying to write a BetwixtTransformer based on CastorTransformer but have run into a problem.
Everything appears to be working Ok according to my logging messages until the XML is serialized when I get this error:
java.lang.RuntimeException: java.lang.NullPointerException
at org.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java:3231)
at java.lang.Thread.run(Thread.java:536)
******************************************************************************** This electronic mail system is used for information purposes and is not intended to form any legal contract or binding agreement. The content is confidential and may be legally privileged. Access by anyone other than the addressee(s) is unauthorised and any disclosure, copying, distribution or any other action taken in reliance on it is prohibited and maybe unlawful All incoming and outgoing e-mail communications and attachments are scanned automatically by software designed to detect and remove any material containing viruses or other unauthorised content. While we undertake best endeavours to ensure that this content checking software is up to date, recipients should take steps to assure themselves that e-mails received are secure. ********************************************************************************