[
https://issues.apache.org/jira/browse/CXF-5849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053116#comment-14053116
]
Vjacheslav Borisov commented on CXF-5849:
-----------------------------------------
systemId property of XSLTJaxbProvider set sytemId of result document:
Result result = new StreamResult(os);
if (systemId != null) {
result.setSystemId(systemId);
}
But to resolve context of "document()" function in xslt document, need to set
systemId of xslt source in method
protected Templates createTemplates(InputStream is) {
}
but now i think this is not fully resolves the problem of relative address
calculation
this only sets systemId of head stylesheet (which is in method annotation), but
if i want to use document() function in some included xslt (using
<xsl;include>), this will not work.
i will recheck this and write later
> 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
> Assignee: Sergey Beryozkin
> 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)
