JDK-4922835 : DOC: Statement javadoc should indicate that target and methodName cannot be null
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.beans
  • Affected Version: 1.4.0
  • Priority: P5
  • Status: Resolved
  • Resolution: Fixed
  • OS: linux
  • CPU: x86
  • Submitted: 2003-09-15
  • Updated: 2017-05-16
  • Resolved: 2010-02-16
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 7
7 b84Fixed
Related Reports
Relates :  
JDK-4653179 - LTP: java.beans.Statement compares Strings "by reference" instead of "by value"
Description
As part of the negotiation for the fix to 4653179, we have agreed that the a null target or methodName for Statement should not be null.

The javadoc for the Statement constructor, getMethodName and getTarget should reflect this.
Comments
EVALUATION Constructors should be documented too.
10-12-2009
EVALUATION The constructor should not be documented since the MutableExpression subclass will use the 3 args ctor with null. The only work to be done is to document the return type for getMethodName and getTargetName must not return null. ###@###.### 2003-09-16
16-09-2003