Subject: RE: [xsl] RE: supposed timing problem From: Jay Burgess <jburgess@xxxxxxxxxxxxxx> Date: Wed, 30 Jan 2002 13:37:45 -0600 |
javax.xml.transform.TransformerException: java.lang.NullPointerException ...
-----Original Message----- From: Jay Burgess [mailto:jburgess@xxxxxxxxxxxxxx] Sent: Wednesday, January 30, 2002 10:48 AM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx 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.
-----Original Message----- From: Michael Kay [mailto:michael.h.kay@xxxxxxxxxxxx] Sent: Wednesday, January 30, 2002 10:39 AM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx 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?).
If you suspect a processor bug, the first thing to do is to try another processor.
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] RE: supposed timing problem, Jay Burgess | Thread | [xsl] copying attributes, Mulberry Technologie |
[xsl] An issue with XPath 2.0 seque, Dimitre Novatchev | Date | [xsl] Javascript inside XSL(Just wh, Gene LaCava |
Month |