Hi, I would like to make a proposition to extend the 'EnsureArgumentNotNull' exception in the following case:

at Xtensive.Core.ArgumentValidator.EnsureArgumentNotNull(Object value, String parameterName) at Xtensive.Storage.EntityEventBroker.AddSubscriber(Key key, FieldInfo fieldInfo, Object eventKey, Delegate subscriber) at Xtensive.Storage.EntityEventBroker.RemapKeys(KeyMapping keyMapping) at Xtensive.Storage.Session.RemapEntityKeys(KeyMapping keyMapping) at Xtensive.Storage.DisconnectedState.ApplyChanges(Session targetSession) at Xtensive.Storage.DisconnectedState.ApplyChanges()

I had created some entities and tried to save them. I made an error and left a navigation property 'null' that is not nullable. Now I get the exception "Value cannot be null.\r\nParameter name: subscriber" which is perfectly ok. But I am missing the info which one of the entities produces the problem. May I propose to add the Key of the entity to the 'Data' collection? In our system we are dumping the Data collection always if we get an exception. This would help.


This thread was imported from our support forum. The original discussion may contain more detailed answer. Original topic by AndresRohr.

asked Jul 20 '10 at 17:09

Editor's gravatar image


Most likely, it's a bug introduced by the latest update. We'll try to fix it today.

(Jul 20 '10 at 17:09) Alex Yakunin Alex%20Yakunin's gravatar image
Be the first one to answer this question!
Please start posting your answer anonymously - your answer will be saved within the current session and published after you log in or create a new account. Please try to give a substantial answer, for discussions, please use comments and please do remember to vote (after you log in)!
toggle preview

powered by OSQA