Description Jason Peterson 2008-03-07 02:28:55 EST

Created attachment 91842 [details]
patch

Having two major issues when removeMofValue(x,y) is called.

1.  A MOF object's adapter is removed before a check is even done to see
if this adapter can be removed from the DOM node as well.  I am having cases where I am left with an adapter on a DOM node that has a target set to null.  This is because the adapter was removed from the MOF object, but was not found on the DOM node; thus not removed from the DOM node.  NPEs are thrown whenever attempts are made to set the MOF value of the translator.  

2.  An unload is then done on this invalid object as part of removeMofValue(x, y) even though the adapter was not removed from the DOM node.  This causes a completely different NPE whenever a get and set feature is attempted on this proxy object. 

The solution was to first check to see if the DOM node even had the adapter.  If not then return from removeMofValue(x, y).  Do not remove the MOF object and attempt the unload if the adapter cannot be removed from the DOM node.