BUG: Oracle Schema Processor does not work in Servlets

Question

We found a bug with Oracle's Schema Processor. It does not work in Servlets.
When we try to validate a XML document in a Servlet it does not work, but we can execute the same code in a stand alone application and it works.
The following is the code we are using:
try {
File f =new File(filename);
FileReader r = new FileReader(f);
DOMParser dp = new DOMParser();
URL url = createURL (filename);
dp.setValidationMode(false);
dp.setSchemaValidationMode(true);
dp.setPreserveWhitespace(true);
dp.parse(url);
System.out.println("it is parsed");
} catch(Exception e){System.out.println("there is Error"+e.getMessage());}
null

Answer 1

I don't think this is related to Servlets per se.
Check that the Schema processor classes used by the servlet container, and your application are the same.
Java does not have proper versioning of classes, I have seen many applications collapse. People compiled their code on developer machines, where it worked fine, but when moved to a production machine they failed because the production machine had a different version of classes. Usually the name of the class doesn't change, but either a method or a variable is missing in several classes. VM doesn't complain but simply crashes.
In your Schema Processor classes that are used by the servlet engine might be different from the one that the app uses. Do a search on the file system to see how many copy of the same class bundle (zip, jar) you have on the system.