at java.lang.Thread.run(Thread.java:619)
Any ideas what might be going wrong?
-David
--
View this message in context:
http://www.nabble.com/XPathFactory.newInstance%28%29-throwing-NullPointerException-tf4243595.html#a12075612
Sent from the Xalan - J - Users mailing list archive at Nabble.com.
or, it must
> recover by ignoring the offending nodes together with their content."
> (http://www.w3.org/TR/xslt#section-Creating-Comments)
>
> In any case, there should not be a NullPointerException. Please open a
> bug
> on JIRA, and try again to whittle down the styl
text nodes. An XSLT
processor may signal the error; if it does not signal the error, it must
recover by ignoring the offending nodes together with their content."
(http://www.w3.org/TR/xslt#section-Creating-Comments)
In any case, there should not be a NullPointerException. Please open a bug
further
insight?
Thanks,
Chris
--
View this message in context:
http://www.nabble.com/NullPointerException-tf2939928.html#a8219739
Sent from the Xalan - J - Users mailing list archive at Nabble.com.
Hello.
"toadie D" <[EMAIL PROTECTED]> wrote on 2006-05-01 01:39:39 PM:
> Thanks for your reply. I've tested out your suggestions by
> using an ErrorHandler
> (import org.apache.xml.utils.DefaultErrorHandler).
>
> // get a Transformer
> SAXTransformerFactory tf = (SAXTransformerFactory)
> SAXTran
Henry,
Thanks for your reply. I've tested out your suggestions by using an ErrorHandler (import org.apache.xml.utils.DefaultErrorHandler).
// get a TransformerSAXTransformerFactory tf = (SAXTransformerFactory)SAXTransformerFactory.newInstance();// Make sure we trap all errorsDefaultErrorHandler
Hello.
"toadie D" <[EMAIL PROTECTED]> wrote on 2006-04-27 01:57:04 PM:
> Thanks for the quick reply. Yes I would say it's a bit confusing
> and misleading.
> In fact if you comment out these 2 lines in the sample code, v2.7.0
> still throws an NPE, but it's just thrown
> from somewhere else.
"toadie D" <[EMAIL PROTECTED]> wrote on 2006-04-26 04:37:50 PM:
> We are upgrading from 2.5.1 to 2.7.0 and am seeing NPE being thrown
> when 2.5.1 used to throw a TransformerException.
>
> The use case is
>
> we are using entity parameter in the XSLT . In 2.5.1, if a
> parameter is NOT defined
We are upgrading from 2.5.1 to 2.7.0 and am seeing NPE being thrown when 2.5.1 used to throw a TransformerException.
The use case is
we are using entity parameter in the XSLT . In 2.5.1, if a parameter is NOT defined but referenced, a TransformerException is thrown. But in 2.7.0, we are ge
Joseph Shraibman
wrote on 2004-12-08 01:37:41 AM:
> This template works fine with xalan 2.4.1. The line in question
looks
> like this:
>
>
>
> javax.xml.transform.TransformerException: java.lang.NullPointerException
See Jira bug report XALANJ-2009[1] for ongoing discussion
of this problem.
This template works fine with xalan 2.4.1. The line in question looks
like this:
javax.xml.transform.TransformerException: java.lang.NullPointerException
at org.apache.xalan.templates.ElemValueOf.execute(ElemValueOf.java:292)
at
org.apache.xalan.transformer.TransformerImpl.executeChildTempla
I've entered bug 21974 in bugzilla to address this.
-Original Message-
From: Koes, Derrick
Sent: Monday, July 28, 2003 3:37
PM
To: '[EMAIL PROTECTED]'
Subject: NullPointerException
My configuration is xalan j 2.5.1
(with xerces 2.4.0) and j2sdk 1.4.
Using t
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 "procedure
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 "procedure
ling the translets and the Java app worked fine.
> Transformations with one smaller translet works fine. The second
> translet, a much larger one (about 80 match templates and some 20 name
> templates), gives a NullPointerException. Here is the stack trace:
>
> java.
ogram. Compiling the translets and the Java app worked fine.
Transformations with one smaller translet works fine. The second
translet, a much larger one (about 80 match templates and some 20 name
templates), gives a NullPointerException. Here is the stack trace:
java.lang.NullPointerException
Well, then we would also have to track the DTMManager in XRTreeFrag, which
is already too bloated with member variables. Each instance could make a
new member of XPathContext... this might be the better choice. But a
bigger change than I want to make right now.
For right now, I just put in a c
Subject: Re: Stylesheet Reuse
Scott's diagnosis makes sense to me.
Simplest fix might be for each transform() call to allocate a new
DTMManager, so the late finalizers could negotiate with the old one without
any interaction with the new transformation.
Best fix might be to improve our scoping to eliminate the need for the
f
L PROTECTED]>To:
cc: [EMAIL PROTECTED],
(bcc: Scott Boag/Cambridge/IBM)
04/02/2002 12:28 Subject: Re: Stylesheet Reuse
NullPointerException
CTED]>To:
cc: [EMAIL PROTECTED],
(bcc: Scott Boag/Cambridge/IBM)
04/02/2002 12:28 Subject: Re: Stylesheet Reuse
NullPointerException
Scott, thanks for the update.
> I can reproduce it from the DOS command prompt, but
> not in my debugger.
Ouch. Maybe I'll try runiing it on Linux and see if it reproduces. Sounds like
as, Joseph said, a timing problem.
> Also, your tests are not reusing the transformer... you create a new
> t
> Because the bug seems timing dependent or environment dependent, I
suspect a garbage value as >the cause... though this kind of thing is
really rare in Java
Might be worth taking another look at the finalizer for XRTreeFrag. We had
a timing problem there since the finalizer does run in a second
IL PROTECTED]>To: [EMAIL PROTECTED]
cc: [EMAIL PROTECTED]
04/01/2002 10:29 Subject: Re: Stylesheet Reuse
NullPointerException
ess of the
frame for the second variable ref. Inside an xsl:with-param is a tricky
situation, because we are accessing variables from behind the frame that we
are defining.
Anyway, I'm guessing, but do not know, that this will also fix your
"Stylesheet Reuse NullPointerException&qu
ing you are doing something in particular in
your stylesheet to stress this kind of thing. (Since you supplied a
stylesheet in that case, I can look at that tomorrow).
To double check, the "Variable accessed before it is bound!" problem and
the NullPointerException are two completely dif
> The NullPointer occurs within a named template at
> org.apache.xpath.objects.XRTreeFrag.xstr(). The member variable m_dtm
> is null and m_allowRelease is true. I'm assuming either detach() or
> destruct() was called. It could be a race or some
> bad laogic that leads to xstr() being called afte
At long last I've nailed down a test scenario for the NullPointerException
after several transformations that reuse a
stylesheet.. The ArrayOutOfBounds may be related and is also in my hunt.
Because it takes several transformations to
hit, I have not been able to create a simple test case.
28 matches
Mail list logo
