Hi
I am currently evaluating Camel for use on a project. I am having a problem
with xpath filtering - which always returns false even if the xpath matches the
inbound document.
So I have the following route definition:
public void configure() throws Exception {
from("jms:queue:TEST.QUEUE
Willem
Attached are sample XMLs, config and java code which replicates the problem.
Unfortunately I don't know how to read from a file (I'm very new to this) and
so it still depends on JMS.
I am using Camel version 2.5-SNAPSHOT.
Thanks for your help
Steven Hedges
-Original Message-
Claus
Thanks very much
Steven Hedges
-Original Message-
From: Claus Ibsen [mailto:claus.ib...@gmail.com]
Sent: 24 September 2010 16:40
To: users@camel.apache.org
Subject: Re: Problem with XPATH filtering
Hi
You are using namespaces in your XML and therefore the XPath expression mus
Hi
This is probably very straightforward, but I've scoured the docs and can't find
an answer.
Is it possible to get details of the actual exception that occurred in an error
handler? So far, I can see how to access the message that caused an error
(using the $body variable) but not the except
I'll get the book...
>From the info on that page, is it correct to assume that it is impossible to
>get at the exception info from the Spring XML config? All I want to do is to
>log the actual exception to a file.
Steven Hedges
IT - Credit Booking Derivs
-Original Message-
Fro
I've bought the book!
Steven Hedges
IT - Credit Booking Derivs
10 The South Colonnade
Canary Wharf,
London E14 4PU,
United Kingdom
02031344655
x44655
-Original Message-
From: Claus Ibsen [mailto:claus.ib...@gmail.com]
Sent: 28 September 2010 14:33
To: users@camel.apache.org
Sub
You realise I am going to have to get my 50 c of help now :-)
Is it possible to use a route as an error handler? I would like to be able to
log an exception, raise an SMS and push the message onto a queue for later
reprocessing. We are trying to keep all of our config in the Spring XML.
(Con
Claus
I am having difficulty with this as I am using the Spring XML config approach.
The errorHandler is defined outside of the camelContext while the routes are
defied inside the camel context. At the point at which the errorHandler is
instantiated it cannot see the error route.
So I have:
Claus
This is the relevant (more complete) extract of the spring config:
http://camel.apache.org/schema/spring"; />
http://www.barcap.com/gcd/stpengine/1-0";>
You're right - it should be:
And not
Many thanks again
Steven Hedges
IT - Credit Booking Derivs
-Original Message-
From: Claus Ibsen [mailto:claus.ib...@gmail.com]
Sent: 29 September 2010 10:18
To: users@camel.apache.org
Subject: Re: Exception details
Just use "d
10 matches
Mail list logo
