cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <>
Subject [jira] [Commented] (CXF-5849) XSLTJaxbProvider document() resources and URIResolver
Date Mon, 07 Jul 2014 10:29:33 GMT


Sergey Beryozkin commented on CXF-5849:

You are right, I've applied your proposed fix with very minor modifications

> XSLTJaxbProvider document() resources and URIResolver
> -----------------------------------------------------
>                 Key: CXF-5849
>                 URL:
>             Project: CXF
>          Issue Type: New Feature
>            Reporter: Vjacheslav Borisov
>            Assignee: Sergey Beryozkin
>            Priority: Minor
>             Fix For: 2.6.15, 2.7.12, 3.0.1
> 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

View raw message