Prob. referring XSL over URI (Pls. consider this out of context p ost)

["Dutta, Sumanta" <su...@lehman.com>]

I am trying to refer my XSL, which generates the FO, over a URI, relative to
my http codebase. If I create the XSL source by passing /x/y/z.xsl, the
transformer tries to find file://x/y/z.xsl. Is there any way to resolve this
in reference to my current http codebase. I tried to do get the servername
from http request, and append the URI, which is working in my local test
setup, but not good for actual installation, as requests may be coming
through different proxies.

Any help will be highly appreciated.
Thanks,
Sumanta Dutta


------------------------------------------------------------------------------
This message is intended only for the personal and confidential use of the designated recipient(s) named above.  If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited.  This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers.  Email transmission cannot be guaranteed to be secure or error-free.  Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such.  All information is subject to change without notice.

Re: Prob. referring XSL over URI (Pls. consider this out of context p ost)

["J.Pietschmann" <j3...@yahoo.de>]

Dutta, Sumanta wrote:
> I am trying to refer my XSL, which generates the FO, over a URI, relative to
> my http codebase. If I create the XSL source by passing /x/y/z.xsl, the
> transformer tries to find file://x/y/z.xsl. Is there any way to resolve this
> in reference to my current http codebase. I tried to do get the servername
> from http request, and append the URI, which is working in my local test
> setup, but not good for actual installation, as requests may be coming
> through different proxies.

I suppose you are implementing a servlet. If you create
the transformer yourself, you can pass any URL to the
StreamSource for the XSL, including HTTP URLs. How you
determine the URL is a matter of your servlet. I don't
understand this part of the problem, usually servlets
read XSL from files instead from HTTP requests. You'll
have to supply some more details.

J.Pietschmann