3 ms·
Tons of stuff in Java is infested with hard coded URIs and you will never find them all. For example to load properties in XML format the XML doctype is the fo
by jmount 15y ago
Tons of stuff in Java is infested with hard coded URIs and you will never find them all. For example to load properties in XML format the XML doctype is the following little gem: <!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd> http://java.sun.com/dtd/properties.dtd> . http://download.oracle.com/javase/1,5.0/docs/api/java/util/Properties.html http://download.oracle.com/javase/1,5.0/docs/api/java/util/P... claims the URI isn't loaded- but that is only if you are using the exact set of XML libraries in the exact classpath order they were thinking about when they wrote that promise (especially on the IBM JVM which isn't smart enough to put the system copy of the XML libraries in a mangled namespace to prevent the user from accidentally overriding then when they and new XML implementations to the classpath). Frankly I'd like to see all of this stuff broken and then excised.
- naner 15y agoTons of stuff in Java is infested with hard coded URIs and you will never find them all. If they all start with http:// http:// it shouldn't be too difficult to search for them.
- andrewf 15y agoThe point of those hardcoded URIs is to be a unique identifier. You really aren't supposed to load them all the time. HTML 4.01 documents are supposed to start with: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd> http://www.w3.org/TR/html4/strict.dtd> The intent was not for web browsers to hit up the W3C every time they loaded a web page.
- jmount 15y agoYes, but under many common circumstances a lot of libraries load the DTD. Really should have used a different name space to make the idea more clear.