ADDITIONAL SYSTEM INFORMATION :
not OS / runtime specific issue.
A DESCRIPTION OF THE PROBLEM :
In Objects.equals(myObject1, myObject2), if myObject2 is null and if myObject1.equals() doesn't handle null check, nullPointerException will be thrown.
JavaDoc says, false will be returned if either of the parameter is null but it is not handled for second parameter.
FREQUENCY : always
not OS / runtime specific issue.
A DESCRIPTION OF THE PROBLEM :
In Objects.equals(myObject1, myObject2), if myObject2 is null and if myObject1.equals() doesn't handle null check, nullPointerException will be thrown.
JavaDoc says, false will be returned if either of the parameter is null but it is not handled for second parameter.
FREQUENCY : always
- csr for
-
JDK-8223265 Clarify operational semantics of java.util.Objects.equals()
-
- Closed
-
- duplicates
-
JDK-8196069 Misleading documentation of Objects.equals
-
- Closed
-
- relates to
-
-
- Resolved
-
-
-
- Closed
-
-
JDK-8283762 Modify if (e1 == null) to if (e1 == null || e2 == null) in "deepEquals" method of Arrays.java
-
- Closed
-