You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2010/02/11 16:57:35 UTC
[jira] Issue Comment Edited: (CAMEL-2463) xslt component - Should
be able to load resources from classpath in xsl:include
[ https://issues.apache.org/activemq/browse/CAMEL-2463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57531#action_57531 ]
Claus Ibsen edited comment on CAMEL-2463 at 2/11/10 3:56 PM:
-------------------------------------------------------------
trunk: 909028, 909036, 909038.
was (Author: davsclaus):
trunk: 909028.
> xslt component - Should be able to load resources from classpath in xsl:include
> -------------------------------------------------------------------------------
>
> Key: CAMEL-2463
> URL: https://issues.apache.org/activemq/browse/CAMEL-2463
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-spring
> Affects Versions: 1.6.2, 2.0.0, 2.1.0, 2.2.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.3.0
>
>
> If you use xsl include
> {code}
> <xsl:include href="staff_template.xsl"/>
> {code}
> Then currently staff_template.xsl is expected to be loaded from file system from the folder where Camel was started.
> What it should support is to load it relative to the endpoint uri configured and from classpath.
> So if you have configured the endpoint as follows
> {code}
> .to("xslt:org/apache/camel/component/xslt/staff_include_relative.xsl")
> {code}
> Then the {{staff_template.xsl}} file should be loaded from classpath in the folder {{org/apache/camel/component/xslt}}.
> Which means the 2 xsl files is in the same location.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.