We attempted to have the LocalizationService override the XSD file locations
used by the parser to validate the files, but it turns out its not working
correctly and is still hitting the XSD files.
This causes the server to not startup sometimes if it can't get to the w3c.org
and oasis.org websites to get the XSD files.
Need to fix this so it really does get the stuff locally.
Currently, we turned off validation in the Java code until this can be fixed.