Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.223.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1373619527149-5735567.post@n5.nabble.com>
References: <1365001174139-5730288.post@n5.nabble.com>
 <CAGB5yNnn5kfym5+9scfXoMR42vaz8g2HTKbm5JSwLT0u3ryAVA@mail.gmail.com>
 <1365058398784-5730313.post@n5.nabble.com>
 <CAGB5yNmB32kEE1xgJqxx5wUdS0i-OQ8zNrhj0LFF9cwbvEaGJA@mail.gmail.com>
 <1365062509581-5730315.post@n5.nabble.com>
 <1373619527149-5735567.post@n5.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Sat, 13 Jul 2013 09:45:43 +0200
Message-ID: 
 <CAGB5yNkUoSS-hx2SsCUfxOPh=0=U1u_j1x6GvyQN6pMc3BJA3w@mail.gmail.com>
Subject: Re: xslt: TransformerException: include href is empty
To: "users@camel.apache.org" <users@camel.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

Hi

Yeah we love contributions. See here
http://camel.apache.org/contributing.html

On Fri, Jul 12, 2013 at 10:58 AM, per.cedde@gmail.com
<per.cedde@gmail.com> wrote:
> Hi again,
>
> Is this problem existing, due to camels own XsltUriResolver?
> It seems that camels XsltUriResolver only is capable to handle files
> either from the classpath or the file system.
> With the xlst function, document(''), the xslt processer should be able to
> handle that the result "is the source XML of the XSLT document itself".
>
>
> Should I create a JIRA case for camel? Is there any guidelines how to
> proceed?
>
> Regards / Per
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/xslt-TransformerException-include-href-is-empty-tp5730288p5735567.html
> Sent from the Camel - Users mailing list archive at Nabble.com.


-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen