-
Enhancement
-
Resolution: Fixed
-
P3
-
9
-
b93
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8163784 | 8u121 | Attila Szegedi | P3 | Resolved | Fixed | b01 |
| JDK-8158352 | 8u112 | Attila Szegedi | P3 | Resolved | Fixed | b01 |
| JDK-8167951 | emb-8u121 | Attila Szegedi | P3 | Resolved | Fixed | b01 |
Nashorn Context objects currently have two class loaders: the one passed from the factory as the "application" class loader, as well as an optional "classpath" URL class loader loading classes specified by the optional -classpath command line argument. When a classPathLoader is present Context code is doing a lookup in classPathLoader with a fallback to appLoader. This should be simplified to a single class loader: when -classpath is specified the newly created URLClassLoader should simply have the appLoader as its parent.
- backported by
-
JDK-8158352 Simplify Nashorn's Context class loader handling
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-