This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: RE: supposed timing problem
- From: Jay Burgess <jburgess at delanotech dot com>
- To: xsl-list at lists dot mulberrytech dot com
- Date: Wed, 30 Jan 2002 13:37:45 -0600
- Subject: RE: [xsl] RE: supposed timing problem
- Reply-to: xsl-list at lists dot mulberrytech dot com
To wrap-up my thread, once I knew that my problem wasn't XSL-related, I
turned to the Xalan bug database and found what appears to be the problem
I've encountered. Bug 5609 is still open and says:
Initial report (28-Dec-2001): When using a single Transformer object to
transform multiple XML documents, if the XSLT contains a global
<xsl:variable> declaration, the variable will be assigned a value from the
first transformation that occurs. This value will then be applied to all
subsequent transformations even though the value initially assigned the
variable was from a separate XML document.
Follow-up (2-Jan-2002): A work around for this was to make the global
variables local and pass them around to the templates where they were used.
This workaround has worked for me in version 2_2_D10 but the following is a
stack trace received when running the same scenario under 2_2_D14.
javax.xml.transform.TransformerException: java.lang.NullPointerException
...
Follow-up (7-Jan-2002): OK, is it just me, or is re-using transformers
totally broken today (07-Jan-02)?
TestID: Bugzilla5609.java
Running the new Bugzilla5609.java test the first transform runs fine but
the second one always throws an exception:
javax.xml.transform.TransformerException: java.lang.NullPointerException
...
I'm convinced this is my problem, as I'm re-using a transformer, Sun's XML
Pack uses 2_2_D14, and I'm getting the same NullPointerException. Now, on
to debugging Xalan...
Thanks.
Jay
-----Original Message-----
From: Jay Burgess [mailto:jburgess@delanotech.com]
Sent: Wednesday, January 30, 2002 10:48 AM
To: xsl-list@lists.mulberrytech.com
Subject: [xsl] RE: supposed timing problem
Thanks to you (and David McNally in a previous reply) for the
suggestion. I'll do that now. And sorry for not posting a subject line--I
hadn't had my coffee yet.
BTW, I'm using Xalan from Sun's Java XML Pack (Winter 2001). Everything
seemed to work fine before changing the version of Xalan. I'll be back if
I have more questions.
Jay
-----Original Message-----
From: Michael Kay [mailto:michael.h.kay@ntlworld.com]
Sent: Wednesday, January 30, 2002 10:39 AM
To: xsl-list@lists.mulberrytech.com
Subject: [xsl] RE: supposed timing problem
> The reason I'm
> asking is that
> it doesn't always work, and in the cases it fails, it appears
> like the
> "value2" variable is trying to initialize before "value1" is
> fully defined
> (timing problem?).
Which processor are you using?
If you suspect a processor bug, the first thing to do is to try another
processor.
Mike Kay
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list