Re: VAJava XSLT result (perfect HTML) different from WAS 3.0 result (SAXException) - same jars, etc - Newguy QQQ

[igort@xxxxxxxxxxxxx]

My guess is that WebSphere can`t find your XSL file - the thing about XSL
parser is that at some point it catches all exceptions and raises it`s own
SAXException, so lets say if you dig inside the XSL parser code and add
some printing to stack trace you`ll probably get a FileNotFoundException.

I had a simular problem where I used a relative URL
("/dir/sub_dir/FileName") when I placed this when I placed this file
in a "/WebSphere/AppServer/servlet/myServlet" directory, but once I`ve put
in "/HTTP Server" directory it worked well.
(WebSphere 2)
if you use WebSphere 3 then all additional files should be located at
"/WebSphere/AppServer/web/"
or "/WebSphere/AppServer/hosts/your_host/your_path"

Just in order to check my theory - try to use a complete URL to your file

Hope it helps

Igor Tatarinov

IgorT@xxxxxxxxxxxxx


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list