Help: Problems accessing XML file in WebSphere 3.5 Fix Pack 4 on Solaris
We are having an emergent issue with WebSphere 3. 5 Fix Pack 4 on Solaris 2.6: The WAR file we deployed fails with runtime exception due to the inability
to access a local resource(XML file) in the converted WAR file's web directory.
The way we access this XML file is as follows:
ServletContext theCon = getServletContext();
URL u = theCon.getResource ("/web/test.xml");
String newPath = u.toExternalForm ();
InputStream is = new URL (newPath).openStream();
The InputStream returned from the URL object is NULL.
After checked the URL's externalForm string, we noticed that its protocol part is "classloader", e.g. the whole URL string is like "classloader:/opt/...../web/test.xml". However, if we replaced "classloader" with "file", the problem disappeared and the XML file can be read without error.
Anybody know why "classloader:" in the URL string cause this problem, and what is the solution without changing the URL string?
Thanks a lot!
