This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: null pointer exception in Saxon


How would I test for a java-object-wrapper containing null?  It appears to
me that Saxon is throwing the exception when it attempts to send toString()
to the null object, although I'm not certain.  I also get null pointer
exception from:

  <xsl:value-of select="hashtable:get($lookup, @name)"/>

How can I do something like this:

  <xsl:if test="hashtable:get($lookup, @name) = null">

Dave

----- Original Message -----
From: Kay Michael <Michael.Kay@icl.com>
To: <xsl-list@mulberrytech.com>
Sent: Monday, June 05, 2000 2:33 AM
Subject: RE: null pointer exception in Saxon


>       <xsl:if test="hashtable:get($lookup, @name)">
>
> But, if the hashtable key is not present in the hashtable,
> Saxon throws a null pointer exception.  I would expect the expression in
the xsl:if
> statement to return false.

Interesting. I think it should probably return a java-object-wrapper whose
contained object is null; it's not an unreasonable suggestion that
converting such a value to a boolean should return false. I'll think about
it. At present the effect of calling an external Java function that returns
null is not defined, so the null pointer exception, while unfriendly, is not
exactly a bug.

Mike Kay


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]