JDK-8051422 : Remove JNDI dependency on java.applet.Applet
- Type: Bug
- Component: core-libs
- Sub-Component: javax.naming
- Affected Version: 9
- Priority: P3
- Status: Closed
- Resolution: Fixed
- Submitted: 2014-07-21
- Updated: 2017-05-17
- Resolved: 2014-07-28
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 9 |
|---|
9 b26Fixed  |
Related Reports
|
Duplicate :
|
|
|
Relates :
|
Sub Tasks
|
JDK-8183386 :
|
Description
JNDI allows the environment to create an initial context being initialized with applet parameters (see javax.naming.InitialContext for details). The results in an undesirable dependency on the java.applet.Applet. It's time to examine this and maybe just remove the support for Applet properties from JNDI. Clearly this would be an incompatible change but it is unlikely to be used. If it cannot be removed then we at least need to look at the Core Reflection usage in com.sun.naming.ResourceManager and work out how this optional dependency will work with modules.