JDK-8001108 : an attempt to use "" as a method name should elicit NoSuchMethodException
- Type: Bug
- Component: core-libs
- Sub-Component: java.lang.invoke
- Affected Version: 7,8-pool
- Priority: P4
- Status: Closed
- Resolution: Fixed
- Submitted: 2012-10-18
- Updated: 2017-05-17
- Resolved: 2013-10-05
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.
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 | JDK 8 |
|---|---|
7u65Fixed  |
8 b112Fixed |
Description
When findVirtual (etc.) is presented with the special name <init>, the answer should always be the same as if some other illegal name (<foo>) were presented, regardless of whether there happens to be a matching constructor present. This is a gray area in the JSR 292 spec. The existing OpenJDK behavior is to refuse to admit that a "method" named <init> exists. We will document this behavior as the standard.
Comments
|