NullPointerException

Subjects

•	Home
•	Xalan extension functions
•	Fomatting question serializing DOM with pretty print
•	xalan with pull parser
•	Cannot find the declaration
•	Apache Xalan drop support to run on JRE 1 1 x
•	Why does Doctype change processing of a document
•	Node set to XML string via Java extensions in Xalan J: possible?
•	Templates/Transformers + thread safety???
•	Problem evaluating xpath with muliple prefix with different namespace
•	remove an arbitrary attribute from xsl output
•	Xalan3 XSLT 2 0 XPath 2 0 support?
•	Problem using compiled translets with Xalan !!
•	Xalan and jstl 1 1 problem with transform tag
•	NullPointer in DOM2DTM getLocalName
•	URIResolvers base parameter with xsltc and cascaded imports
•	Performance problem for Xalan J on intel dual core
•	Standard libraries in JAXP?
•	Serializing a DOM tree to XML file, customize entities replacement
•	Library Conflict Involving BCEL Library
•	A question on how users are using <xsl:message >
•	Kevin Cormier as a new Apache Xalan J committer
•	Struggling to iterate over tokenized string
•	Xalan count() trouble
•	Problem with recursive xpath
•	Error when switching to java 1 5
•	document( ' ')
•	Problem with Xalan2 7 0 transformation
•	cr/lf options
•	entity encoded XML
•	can xalan transform 2 xml using one xslt?
•	Xalan J JIRA defect review Monday October 16, 2006 from 2:00 to 3:30 pm ED
•	xsl transform with cdata section elements
•	xslt parameters not expanded
•	Weird behavior of XPath evaluate()
•	How to avoid <xsl:message > instruction prints stylesheet file informations ?
•	Cannot find SimpleTransform subdirectory after installing Xalan J
•	recover from document not found exceptions
•	jdk1 5 and Xalan jar differences?
•	Performance Issue
•	Error/Bug adding floating point numbers
•	XPathAPI: eval exp using nodes with default namespace
•	modifying xalan to output invalid XML
•	NullPointerException
•	mege two separate xml nodes into one
•	Is this a XALAN document identification bug?
•	is StylesheetRoot really java io Serializable ?
•	transform() fails for DOMSource but succeeds for StreamSource
•	Thoughts on Transformer parameter passing
•	HELP, Xalan and jstl 1 1 problem with transformer
•	Problem with XPath namespace axis?
•	string utils:replace deleting search string if replacement string is an HTML
•	help with enumeration values pls
•	xalan 2 5 1 vs 2 7 performance question
•	How to insert/update in XML document
•	HTML Serialization and Handling of Ampersands in HREF Attributes
•	XHTML link tag stripping
•	SystemId Unknown; Line #24; Column #49; java lang NullPointerException
•	xpath text() help
•	Apostrophe problem with xalan 2 7 0
•	How to set variables in XML document?

Links

Home

Oracle database error code ...

NullPointerException

NullPointerException

2003-07-28 - By Koes, Derrick

Reply: 1 2 3 4 5 6

My configuration is xalan j 2.5.1 (with xerces 2.4.0) and j2sdk 1.4.
Using the interpretive transformer
(org.apache.xalan.processor.TransformerFactoryImpl) I can transform the
attached xml and xsl fine.
Using the command line method, I can successfully transform the attached
with the XSLTC transformer. How do you pass params to the translet on the
command line?

However, I cannot transform the attached with an XSLTC transformer when
running "embedded". I get a NullPointerException.
This seems to be particularly true when I pass a value for the param
"procedureChanged". I am running several other transforms this way without
problem, so currently I believe it to be a bug with XSLTC, but can't exhibit
the defect from the command line (unless I can figure out how to pass
params???). The stack trace is below.

java.lang.NullPointerException
at org.apache.xalan.xsltc.trax.DOM2SAX.parse(DOM2SAX.java:350)
at org.apache.xalan.xsltc.trax.DOM2SAX.parse(DOM2SAX.java:329)
at org.apache.xalan.xsltc.trax.DOM2SAX.parse(DOM2SAX.java:329)
at org.apache.xalan.xsltc.trax.DOM2SAX.parse(DOM2SAX.java:329)
at org.apache.xalan.xsltc.trax.DOM2SAX.parse(DOM2SAX.java:329)
at org.apache.xalan.xsltc.trax.DOM2SAX.parse(DOM2SAX.java:329)
at org.apache.xalan.xsltc.trax.DOM2SAX.parse(DOM2SAX.java:250)
at org.apache.xalan.xsltc.trax.DOM2SAX.parse(DOM2SAX.java:201)
at
org.apache.xalan.xsltc.dom.XSLTCDTMManager.getDTM(XSLTCDTMManager.java:242)
at
org.apache.xalan.xsltc.dom.XSLTCDTMManager.getDTM(XSLTCDTMManager.java:174)
at
org.apache.xalan.xsltc.trax.TransformerImpl.getDOM(TransformerImpl.java:483)

Any help is appreciated.

Thanks,
Derrick

This electronic transmission is strictly confidential to Smith & Nephew and
intended solely for the addressee. It may contain information which is
covered by legal, professional or other privilege. If you are not the
intended addressee, or someone authorized by the intended addressee to
receive transmissions on behalf of the addressee, you must not retain,
disclose in any form, copy or take any action in reliance on this
transmission. If you have received this transmission in error, please
notify the sender as soon as possible and destroy this message.

<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas
-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">

<meta name=ProgId content=Word.Document>
<meta name=Generator content="Microsoft Word 10">
<meta name=Originator content="Microsoft Word 10">
<link rel=File-List href="cid:filelist.xml@(protected)">

<style>

</style>

</head>

<body lang=EN-US link=blue vlink=purple style='tab-interval:.5in'>

<div class=Section1>

My configuration is xalan j 2.5.1
(with xerces 2.4.0) and j2sdk 1.4.<o:p></o:p>

Using the interpretive transformer (org
.apache.xalan.processor.TransformerFactoryImpl)
I can transform the attached xml and xsl fine.<o:p></o:p>

Using the command line method, I can successfully transform
the attached with the XSLTC transformer. 
How do you pass params to the translet on the command line?<o:p></o:p>

<o:p> </o:p>

However, I cannot transform the attached with an XSLTC
transformer when running "embedded".  I get a NullPointerException.<o:p></o:p>

This seems to be particularly true when I pass a value for
the param "procedureChanged
".  I am running several other transforms
this way without problem, so currently I believe it to be a bug with XSLTC, but
can't exhibit the defect from the command line (unless I can figure out
how to pass params???).  The stack trace is below.<o:p></o:p>

<o:p> </o:p>

java.lang.NullPointerException<o:p></o:p>

     
       at
org.apache.xalan.xsltc.trax.DOM2SAX.parse(DOM2SAX.java:350)<o:p></o:p>

     
       at
org.apache.xalan.xsltc.trax.DOM2SAX.parse(DOM2SAX.java:329)<o:p></o:p>

     
       at
org.apache.xalan.xsltc.trax.DOM2SAX.parse(DOM2SAX.java:329)<o:p></o:p>

     
       at org.apache.xalan.xsltc.trax.DOM2SAX.parse(DOM2SAX.java
:329)<o:p></o:p>

     
       at
org.apache.xalan.xsltc.trax.DOM2SAX.parse(DOM2SAX.java:329)<o:p></o:p>

     
       at
org.apache.xalan.xsltc.trax.DOM2SAX.parse(DOM2SAX.java:329)<o:p></o:p>

     
       at
org.apache.xalan.xsltc.trax.DOM2SAX.parse(DOM2SAX.java:250)<o:p></o:p>

     
       at org.apache.xalan.xsltc.trax.DOM2SAX.parse(DOM2SAX.java
:201)<o:p></o:p>

     
       at org.apache.xalan.xsltc.dom
.XSLTCDTMManager.getDTM(XSLTCDTMManager.java:242)<o:p></o:p>

     
       at org.apache.xalan.xsltc.dom
.XSLTCDTMManager.getDTM(XSLTCDTMManager.java:174)<o:p></o:p>

     
       at org.apache.xalan.xsltc.trax
.TransformerImpl.getDOM(TransformerImpl.java:483)<o:p></o:p>

<o:p> </o:p>

<o:p> </o:p>

Any help is appreciated.<o:p></o:p>

<o:p> </o:p>

Thanks,<o:p></o:p>

Derrick<o:p></o:p>

<o:p> </o:p>

<o:p> </o:p>

<o:p> </o:p>

</div>

</body>

</html>

This electronic transmission is strictly
confidential to Smith & Nephew and intended solely for the addressee. It may
contain information which is covered by legal, professional or other privilege.
If you are not the intended addressee, or someone authorized by the intended
addressee to receive transmissions on behalf of the addressee, you must not
retain, disclose in any form, copy or take any action in reliance on this
transmission. If you have received this transmission in error, please notify
the sender as soon as possible and destroy this message.