Community
Participate
Working Groups
Util.equals(Object[], Object[] is returning false if one Object is null and the other is an empty array. See bug 390379 for the performance problem that this causes in 4.2.
Created attachment 221515 [details] proposed patch against 4_2_maintenance This patch adds an additional check for one Object being null and the other being an empty array. Thus it will return true for this use case. I think the javadoc comment of Util.equals should be updated as well. It claims that the "must not be <code>null</code>". But then the javadoc for each parameter says they can be null.
That's an API method, and I'm loathe to change it's behaviour. Perhaps we should fix it in BindingManagerEvent PW
back to bug 390379
(In reply to comment #2) > That's an API method, and I'm loathe to change it's behaviour. Perhaps we > should fix it in BindingManagerEvent > > PW +1.
+1 your fix in BindingManagerEvent looks good to me