On 23.11.2007 9:58 Uhr, Giacomo Pati wrote:
How can this be null after all? From what I see value can only be null
if value was null in the first place, i.e. before replace(..). This
means that null must already have been in the Properties object which is
kind of impossible since Properties.put(..) inherited from HashTable
throws NPE on value being null.
Exactly! I have the situation where value _IS NULL_ and it throws a NPE.
Where do you have this Properties object from which is only injected by
the user into AbstractSettingsBeanFactoryPostProcessor?
I don't know where what is comming from. I suddenly had this NPE as soon as I
access a URL (while
something is creating a Setting bean).
Since you reverted the commit have you figured out where the null is
coming from? I'm really curious how the original Properties object could
have null.
Joerg
