-
Bug
-
Resolution: Fixed
-
P2
-
1.1.4
-
1.1.5
-
generic
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2016650 | 1.2.0 | Benjamin Renaud | P2 | Resolved | Fixed | 1.2beta |
This could be bad for HotJava under JavaOS, if we ever decide to use
setURLStreamHandlerFactory (and we might). JavaOS uses the http protocol
before HotJava gets to run, so the http handler would already have been
recorded in java.net.URL.handlers.
The fix is trivial. Add this line to java.net.URL:
public static synchronized void setURLStreamHandlerFactory(URLStreamHandlerF
actory fac) {
if (factory != null) {
throw new Error("factory already defined");
}
SecurityManager security = System.getSecurityManager();
if (security != null) {
security.checkSetFactory();
}
--> handlers = new Hashtable()
factory = fac;
}
A Pumpkin fix would be desirable
setURLStreamHandlerFactory (and we might). JavaOS uses the http protocol
before HotJava gets to run, so the http handler would already have been
recorded in java.net.URL.handlers.
The fix is trivial. Add this line to java.net.URL:
public static synchronized void setURLStreamHandlerFactory(URLStreamHandlerF
actory fac) {
if (factory != null) {
throw new Error("factory already defined");
}
SecurityManager security = System.getSecurityManager();
if (security != null) {
security.checkSetFactory();
}
--> handlers = new Hashtable()
factory = fac;
}
A Pumpkin fix would be desirable
- backported by
-
JDK-2016650 java.net.URL.setURLStreamHandlerFactory() doesn't clear handlers cache
- Resolved