t any advises
Thank you.
--
View this message in context:
http://camel.465427.n5.nabble.com/Relative-URL-for-XSL-in-XSLT-component-tp5724794p5768059.html
Sent from the Camel - Users mailing list archive at Nabble.com.
ge in context:
http://camel.465427.n5.nabble.com/XSLT-Component-empty-elements-tp5761456p5761468.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hello,
We are upgrading from Apache Camel version 2.12.2 to 2.14.0 but have some
problems with XSLT component.
The input for the XSLT component is xml with no namespaces in it (see
below).
The result after the transformation does not contain any elements because
tests on the elements do not
us.ib...@gmail.com]
Sent: Donnerstag, 31. Juli 2014 10:08
To: users@camel.apache.org
Subject: Re: XSLT component produces different result after logging a CXF
PAYLOAD request
Hi
Sounds a bit like this
http://camel.apache.org/why-is-my-message-body-empty.html
On Thu, Jul 31, 2014 at 10:06 AM
> the namespace URI when the request is logged before it goes to the XSLT
> component:
>
>
>
>
>
>
>
>
> Is the XML parsed with different namespace aware settings when it
different. In particular this
template creates an empty element, while it correctly writes the namespace URI
when the request is logged before it goes to the XSLT component:
Is the XML parsed with
Thanks for quick response. I was sure that @Qualifier annotation gives an id
to bean. Now I have it working with annotations too
--
View this message in context:
http://camel.465427.n5.nabble.com/Custom-URIResolver-for-XSLT-component-tp5730913p5730957.html
Sent from the Camel - Users mailing
You need to assign an id to that bean so Camel can find it
#xsltUriResolver
means the id of the bean should be: xsltUriResolver
On Mon, Apr 15, 2013 at 4:19 PM, nikagra wrote:
> Hello
> I'd like to implement custom URI resolver for XSLT component. I'm using
> Spring to conf
Hello
I'd like to implement custom URI resolver for XSLT component. I'm using
Spring to configure Camel context. The problem is when I configure URI
resolver using @Component and @Qualifier annotations I got
No bean {bean id} could be found in the registry of type:
javax.xml.transform.U
ange.getIn().setBody(new SAXSource(xmlReader, new
> InputSource(inputStream)));
> }
>
> The Transformer used by the xsltComponent will then use this xmlReader.
>
> Dirk
>
Maybe the camel xslt component can be enhanced to support to plugin a
custom EntityResolver?
We love cont
> > Datum: Tue, 19 Feb 2013 20:04:54 +0100
> > Von: Claus Ibsen
> > An: users@camel.apache.org
> > Betreff: Re: Make xslt component not to validate dtd\'s (or use local
> copy)
>
> > On Tue, Feb 19, 2013 at 1:56 PM, wrote:
> > > Hello,
> > >
y the xsltComponent will then use this xmlReader.
Dirk
Original-Nachricht
> Datum: Tue, 19 Feb 2013 20:04:54 +0100
> Von: Claus Ibsen
> An: users@camel.apache.org
> Betreff: Re: Make xslt component not to validate dtd\'s (or use local copy)
> On Tue, Feb 19, 2013 at 1:
On Tue, Feb 19, 2013 at 1:56 PM, wrote:
> Hello,
>
> We are using the camel xslt component to transform a xhtml file. But for
> transforming the file, the used XMLReader tries to download the dtd from thw
> w3c website.
>
> Is it possible, to tell the xslt component, to con
Hello,
We are using the camel xslt component to transform a xhtml file. But for
transforming the file, the used XMLReader tries to download the dtd from thw
w3c website.
Is it possible, to tell the xslt component, to configure the xml reader to
use local version (e.g. by using xml catalogs) or
an 2, 2013 at 5:36 PM, felixnutella wrote:
> Hi all
>
> I'm quite new at Camel but have managed to get it up and running using a
> few
> custom components/converters...
>
> But..
>
> Is it true that you need to specify an absolute path for the XSL in the
> X
Hi all
I'm quite new at Camel but have managed to get it up and running using a few
custom components/converters...
But..
Is it true that you need to specify an absolute path for the XSL in the XSLT
component? Whenever I try to specify an relative, it comes up with File not
found.
For XSLT transformation you need a XSLT file.
For validation, you can use the XSD file.
You can use maven to check which version of the dependency the camel-xslt
component use.
Sent from a mobile device
Am 09.11.2012 13:23 schrieb "anakin59490" :
> Ok !
>
> Do you think tha
Ok !
Do you think that i could transform my xml in another xml (the same without
specifics tags) with Xalan and a xsd file ? Do you use xalan 2.7.1 ? (i
found this version on maven repository...)
thank you
--
View this message in context:
http://camel.465427.n5.nabble.com/xslt
On 9 November 2012 11:46, anakin59490 wrote:
> Thank you very much Bob !!
>
> It works !!
>
> In fact check, was my first step, but i used xslt: component because i must
> transform my xml file in an other xml file (the same without specifics
> tags).
>
> But i th
Thank you very much Bob !!
It works !!
In fact check, was my first step, but i used xslt: component because i must
transform my xml file in an other xml file (the same without specifics
tags).
But i thought that it could do both (check and transform).
I work with camel version 2.9. I've
ith a xsd file.
>
> I try to use the xslt: component but it doesn't work.
>
> this is my xml file:
>
>
>
>
>
> 90
> 80
> 99
>
>
>
>
> this is my xsd file :
>
>
Hello,
I would like to check a xml file with a xsd file.
I try to use the xslt: component but it doesn't work.
this is my xml file:
90
80
99
this is my xsd file :
http://www.w3.org/2001/XMLSchema";
elementFormDefault="qualified">
lay around much.
>>
>
> Ah yeah the xslt endpoint need to be lenient if you use the http for
> the xslt, fell free to log a JIRA ticket
> then we can add support for that.
>
I logged a ticket to not forget about this
https://issues.apache.org/jira/browse/CAMEL-5232
>
>
xslt, fell free to log a JIRA ticket
then we can add support for that.
> Thanks!
>
> JM
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-XSLT-Component-Load-XSLT-from-database-tp5033499p5670143.html
> Sent from the Camel - Users mailing l
e on the
route. I could not get URL's with query parameters to work, but I didn't
play around much.
Thanks!
JM
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-XSLT-Component-Load-XSLT-from-database-tp5033499p5670143.html
Sent from the Camel - Users maili
e:input").to("xslt:export/xml2json_bundle1.xslt");
If I provide some local bundle 2 resource to xslt component it works fine.
In 2.8.x camel version it works just fine.
--
View this message in context:
http://camel.465427.n5.nabble.com/Issue-on-XSLT-component-in-OSGI-environment-2-9-0-camel-tp
Thanks Claus. I will give it a try when I get a breather and I'll report
back. The project is barrelling along!
Josh
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-XSLT-Component-Load-XSLT-from-database-tp5033499p5042751.html
Sent from the Camel - Users mailing
Hi
Can you try the 2.9.0-RC1 release.
We have moved the xslt component from camel-spring to camel-core. And
as part of that move, the logic for loading the xslt resource changed
to be non-spring dependent and thus it may work now with http.
On Tue, Nov 29, 2011 at 9:00 PM, mccab...@gmail.com
ed something.
Thanks in advance to any that are able to provide help and guidance.
JM
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-XSLT-Component-Load-XSLT-from-database-tp5033499p5033499.html
Sent from the Camel - Users mailing list archive at Nabble.com.
your XSL to load the
appropriate files.
--
View this message in context:
http://camel.465427.n5.nabble.com/xslt-component-and-URI-Resolver-tp3396685p3399434.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi,
I'm trying to use the camel XSLT component with a stylsheet that contains xpath
"document()" instructions. I've seen that default URIResolver works only with
classpath resources, but my resources are available on relative web URLs (I'm
using the Camel Servlet compo
Try using instead of
--
View this message in context:
http://camel.465427.n5.nabble.com/how-to-use-a-dynamic-file-name-in-the-xslt-component-output-file-tp3265551p3265789.html
Sent from the Camel - Users mailing list archive at Nabble.com.
32 matches
Mail list logo