Issue #128 has been updated by Jonathan Clarke.

Status changed from Resolved to Closed
% Done changed from 0 to 100

Released in 1.1.1. Closing.
----------------------------------------
Bug #128: Bad value checking for default values in BeanComparator
http://tools.lsc-project.org/issues/show/128

Author: Jonathan Clarke
Status: Closed
Priority: Low
Assigned to: Jonathan Clarke
Category: Core
Target version: 1.1.1


In a very rare case, a NullPointerException might have been thrown when all 
following conditions are true:
* Doing a modify operation
* A default value is defined for an attribute
* This default value is applied to the destination (ie, attribute is in MERGE 
mode, or doesn't exist in the source for this entry)
* After evaluation by the JavaScript engine, the value to write is Java "null" 
(I don't know if Rhino will actually return nulls, but I recall that it does)

I have never seen this happen, but I found this bug using FindBugs 
(http://findbugs.sourceforge.net/). A fix is coming.


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://tools.lsc-project.org/my/account
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.lsc-project.org/pipermail/lsc-dev/attachments/20091106/fa26877d/attachment.htm>

Reply via email to