Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Fri, 4 Jul 2014 12:36:34 +0000 (UTC)
From: "Vjacheslav Borisov (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12725466.1404471941595.4532.1404477394222@arcas>
In-Reply-To: <JIRA.12725466.1404471941595@arcas>
References: <JIRA.12725466.1404471941595@arcas>
Subject: [jira] [Commented] (CXF-5849) XSLTJaxbProvider document() resources
 and URIResolver
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CXF-5849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14052407#comment-14052407 ] 

Vjacheslav Borisov commented on CXF-5849:
-----------------------------------------

So final question - cluld be XSLTJaxbProvider patched with source.setSystemId() to make custom URIResolver make relative url calculations?

> 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)