You're probably doing something wrong, but I can't tell what without seeing some details.
 
Generally, NullPointerExceptions shouldn't happen in Saxon, unless you actually supply a null value for a parameter that Saxon requires to be non-null.
 
Do you have a good reason to supply a DOMSource to Saxon? It's generally bad news from a performance point of view. If the data already exists as a DOM, then supply it that way, but never create a DOM specifically to provide the Saxon input. If you need to preprocess the data before transformation, use a SAX filter if at all possible.
 

Michael Kay
Software AG
home: Michael.H.Kay@ntlworld.com
work: Michael.Kay@softwareag.com

 
 -----Original Message-----
From: saxon-help-admin@lists.sourceforge.net [mailto:saxon-help-admin@lists.sourceforge.net] On Behalf Of Grant C. Peters
Sent: 25 September 2002 20:53
To: saxon-help@lists.sourceforge.net
Subject: [saxon] using a DOMSource

Everytime I try to transform a DOMSource with a org.w3c.dom.Element as my arg to the c'tor, I get a null pointer exception

Does anyone know why this is?

thanks

 

Grant C. Peters

grantcpeters@earthlink.net

phone  : 415.948.7030