This bug appears whenever we try to compare two entities that contain lists. The lists will be treated as PersistentBag and that object type does not implement equals.
because the monitorMetadataFields, pluginMetadataFields, and zones are all lists that will be lazily loaded (zones is set to FetchType.EAGER - see below to see why it fails).
Due to equals not being implemented, the assert will eventually fall through to hit this conditional and fail - Arrays.isArray(o1) && Arrays.isArray(o2). Both isArray calls will return false.
To avoid this problem you must add the List fields to the ignored fields and then test them directly
Fields that are annotated with EAGER retrieval will sometimes work within the above assert and othertimes fail. The reason is that when performing a repository.save() for a brand new object it will convert an ArrayList to a PersistentBag but if you are performing the save() on an existing object (i.e. doing an update) it will keep the type as ArrayList.
For this reason, tests involving updates should not need to ignore the zones field but those involved in creating or cloning objects will.
https://hibernate.atlassian.net/browse/HHH-5409
This bug appears whenever we try to compare two entities that contain lists. The lists will be treated as
PersistentBagand that object type does not implementequals.For example this assertion will fail
because the
monitorMetadataFields,pluginMetadataFields, andzonesare all lists that will be lazily loaded (zonesis set toFetchType.EAGER- see below to see why it fails).Due to
equalsnot being implemented, the assert will eventually fall through to hit this conditional and fail -Arrays.isArray(o1) && Arrays.isArray(o2). BothisArraycalls will return false.To avoid this problem you must add the
Listfields to the ignored fields and then test them directlyFetchType.EAGER Failures
Fields that are annotated with
EAGERretrieval will sometimes work within the above assert and othertimes fail. The reason is that when performing arepository.save()for a brand new object it will convert anArrayListto aPersistentBagbut if you are performing thesave()on an existing object (i.e. doing an update) it will keep the type asArrayList.For this reason, tests involving updates should not need to ignore the
zonesfield but those involved in creating or cloning objects will.