-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P2
-
Affects Version/s: 17
-
Component/s: core-libs
-
None
-
b29
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8269463 | 18 | Mandy Chung | P2 | Closed | Fixed | b04 |
| JDK-8270657 | 17.0.1 | Mandy Chung | P2 | Resolved | Fixed | b03 |
Creating as a P2 for now as this may need attention in Java 17.
Proxy.newProxyInstance doesn't specify how it deals with sealed interfaces. I suspect we may need to update the list of restrictions so that IllegalArgumentException is thrown if an interface is sealed.
As things stand, a confusing IncompatibleClassChangeError will be thrown when attempting to define the proxy class.
Proxy.newProxyInstance doesn't specify how it deals with sealed interfaces. I suspect we may need to update the list of restrictions so that IllegalArgumentException is thrown if an interface is sealed.
As things stand, a confusing IncompatibleClassChangeError will be thrown when attempting to define the proxy class.
- backported by
-
JDK-8270657 Proxy::newProxyInstance and MethodHandleProxies::asInterfaceInstance should reject sealed interfaces
-
- Resolved
-
-
-
- Closed
-
- csr for
-
JDK-8269396 Proxy::newProxyInstance and MethodHandleProxies::asInterfaceInstance should reject sealed interfaces
-
- Closed
-
