You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the mapbacked objects use the equals method of the underlying map.
If consequently uing collections below, everything is fine for data objects. However, if fields are declared as arrays, then two arrays are treated as not equal, even if they contain the same values....
Most probably this should be changed, as for domain objects, which even can be serialized and deserialized, these different instances should be equal, or? However this would require a big if/else and some reflective acrobatic, because of all the primitives ... or is there a simpler solution? Or should it not be changed at all?
Currently, the mapbacked objects use the equals method of the underlying map.
If consequently uing collections below, everything is fine for data objects. However, if fields are declared as arrays, then two arrays are treated as not equal, even if they contain the same values....
Most probably this should be changed, as for domain objects, which even can be serialized and deserialized, these different instances should be equal, or? However this would require a big if/else and some reflective acrobatic, because of all the primitives ... or is there a simpler solution? Or should it not be changed at all?
The problem is highlighted in
https://github.com/ossgang/ossgang-commons/blob/master/src/test/java/org/ossgang/commons/mapbackeds/ArrayFieldEqualsTest.java
The text was updated successfully, but these errors were encountered: