You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Vjacheslav Borisov (JIRA)" <ji...@apache.org> on 2014/07/04 13:06:33 UTC
[jira] [Created] (CXF-5849) XSLTJaxbProvider document() resources
and URIResolver
Vjacheslav Borisov created CXF-5849:
---------------------------------------
Summary: XSLTJaxbProvider document() resources and URIResolver
Key: CXF-5849
URL: https://issues.apache.org/jira/browse/CXF-5849
Project: CXF
Issue Type: New Feature
Reporter: Vjacheslav Borisov
Priority: Minor
XSLTJaxbProvider provider may include some default URIResolver class, to resolve relative adressed resources included in xslt with document('path/to/file')
Currently relative addressing works only in case of Client-side xslt transformation XSLTTransform.TransformType.CLIENT (when browser resolves relative paths)
Eg I have {WEBROOT}/stylesheets/document.xsl and {WEBROOT}/schemas/document.xsd
and I can relatively address document.xsd with
document('../schemas/document.xsd')
But in case of XSLTTransform.TransformType.SERVER relative address is comuted against current dir (user.dir property, which defaults to ${catalina_home}/bin) and not against dir where xslt file is placed.
So XSLTTransform.TransformType.SERVER differs from XSLTTransform.TransformType.CLIENT.
As a workaround if this is unacceptable, can someone point me is it possible to configure XSLTJaxbProvider uri resolver without Spring?
--
This message was sent by Atlassian JIRA
(v6.2#6252)