cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vjacheslav Borisov (JIRA)" <>
Subject [jira] [Commented] (CXF-5849) XSLTJaxbProvider document() resources and URIResolver
Date Fri, 04 Jul 2014 11:43:33 GMT


Vjacheslav Borisov commented on CXF-5849:

Update: I found way to configure using ApplicationConfig
    public Set<Object> getSingletons() {
        Set<Object> resources = new java.util.HashSet<>();
        XSLTJaxbProvider xsltJaxbProvider=new XSLTJaxbProvider();
        xsltJaxbProvider.setResolver(new ServletContextURIResolver());
        return resources;

But unfortunately in ServletContextURIResolver in method resolve(String string, String string1)
fir parameter is path to ../schemas/document.xsd ,and second parameter is null,
so there is no possibility to calculate relative path to xslt document

> XSLTJaxbProvider document() resources and URIResolver
> -----------------------------------------------------
>                 Key: CXF-5849
>                 URL:
>             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

View raw message