JDK-8068580 : JavaAdapterFactory.isAutoConvertibleFromFunction should be more robust
- Type: Bug
- Component: core-libs
- Affected Version: 9
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2015-01-07
- Updated: 2015-09-29
- Resolved: 2015-01-12
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 8 | JDK 9 |
|---|---|
8u60Fixed  |
9 b46Fixed |
Related Reports
|
Relates :
|
Description
Sometimes, a Java adapter can't be generated because it's simply too big, e.g. a class with somewhere between 4600-4700 methods will do. Since adapters are being generated also to determine whether a class can be treated as a SAM type (JDK-8067935), even querying this can fail for large classes. As a basic fix, at least we should capture all ASM related error conditions and robustly report it and also presume that for such classes isAutoConvertibleFromFunction is false