Thomas Tolborg wrote:
>
> >
> > The xsl attribute value must start with a slash (/) and contain the
> > context-relative path for the XSL file. I.e., if the XSL file is in
> > the top-directory for the web application, use "/htmltable.xsl".
> >
> > > [...]
> >
> > Hans
> > --
> > Hans Bergsten [EMAIL PROTECTED]
> > Gefion Software http://www.gefionsoftware.com
> > Author of JavaServer Pages (O'Reilly), http://TheJSPBook.com
> >
>
> Hans,
>
> I believe I tried everything; "/htmltable.xsl",
> "/xsl-examples/htmltable.xsl", "/webapp/xsl-examples/htmltable.xsl" and so
> on.
>
> It must be a WebSphere Application Server specific problem, since I have
> tried the examples with success on Tomcat.
Possibly (I haven't tested the XSL library with WAS), but if you look at
the <xsl:apply> tag code, you see that it just calls
ServletContext.getResourceAsStream() with the value you specify for the
xsl attribute. And the path passed to getResourceAsStream() should be a
regular context-relative path (starting with a slash, interpreted as the path
from the web application's document root). So if it doesn't work with
this type of path for WAS, then WAS's implementation of getResourceAsStream()
is broken.
Hans
--
Hans Bergsten [EMAIL PROTECTED]
Gefion Software http://www.gefionsoftware.com
Author of JavaServer Pages (O'Reilly), http://TheJSPBook.com
