I don't have an answer as to why we null the reference out. Can I get a
stacktrace for a bit of context?
On Fri, Feb 20, 2015 at 10:02 AM, Mark Struberg <struberg@yahoo.de> wrote:
> Does anyone have a clue or remember why the
> TransferFieldManager#fetchObjectField sets the val to null after returning
> it?
>
>
> The reason why I ask is that this currently creates an issue in the
> InverseManager for me.
>
> In InverseManager#storeField line 332 this 'destroys' the field sm as the
> val of it is null afterwards. And this subsequently creates an
> InvalidStateException in SingleFieldManager#preFlush line 567.
>
>
> Does anyone remember something about that?
>
> LieGrue,
> strub
--
*Rick Curtis*
|