Have you checked out all the different possibilities outlined under
http://camel.apache.org/xslt.html to use Saxon?
You can set options on the endpoints or set a JVM property which looks
different from what you're setting.
Regards,
Raúl.
Sent from my iPhone
On 23 Jun 2012, at 08:03, weather99
Hello,
It's correct.
>From my point of view to break infinite loop you need configure your
RedeliveryPolicy without
.to(Constants.INBOUND_QUEUE) instruction
--Filippo
2012/6/23 E.Gherardini :
> My question lies behind the fact that I understood onException clause is used
> until the set maximu
My question lies behind the fact that I understood onException clause is used
until the set maximumRedelivery is reached, and then the DLC would come in.
Is this correct?
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-2-9-1-DeadLetterChannel-infinite-loop-tp5714961p571
Thank you for response. I ended up with issue. Using encoding UTF-16BE is
suitable solution.
--
View this message in context:
http://camel.465427.n5.nabble.com/data-coding-in-camel-smpp-tp5714925p5714966.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Ah i forgot to mention that the above route is preceeded by another route,
with its own errorHandler:
[code]
dlcb = new
DeadLetterChannelBuilder(Constants.MAIN_INBONUND_QUEUE+"/deadLetter");
dlcb.setFailureProcessor(new MyLoggingProcessor("Message
Delivery
Failure"));
...
@Override
Hello ,
I am struggling with a strange issue using a simple deadLetterChannel error
handler with some onException clauses.
The route goes into an infinite loop, and debugging (going step by step in
the method "RedeliveryErrorHandler.processErrorHandler(exchange,
asynchcallback, data) )
I observe
Yes, or something even more flexible such as
to("direct-vm:/parent/child")
and for the expression, a simple xpath like:
from("foo:bar").recipientList(directVm("/parent/*"))
or
/parent//*
Just a thought though, not sure if that's really needed.
On Sat, Jun 23, 2012 at 9:18 AM, Claus Ibsen
On Fri, Jun 22, 2012 at 10:41 PM, Sergey Zhemzhitsky wrote:
> Hello Guillaume,
>
> I suppose static method to retrieve consumers that can be filtered by a custom
> expression will be quite enough.
>
Yeah that may be a good idea and fairly easy to implement.
The regular direct component could in
Hi
See the blockWhenFull option at
http://camel.apache.org/seda
The default behavior would be an exception will be thrown if the queue
is full. but that option allows you to wait and block instead.
On Fri, Jun 22, 2012 at 6:56 PM, Edwin wrote:
> Hi Folks,
>
> If I have a route (route1) where I
On Fri, Jun 22, 2012 at 10:41 PM, Deepthi wrote:
> Hi,
>
> I am trying to aggregate in the following manner:
>
>
>
>
>
> /order/id
>
>
>
>
>
>
> I am using camel 2.8.0.
> The above route throws me an exception "Definition has no children on
> Aggregat
Hi Christian
wish you a nice as well as recreative weekend too :-)
Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/Lazy-Camel-tp5714949p5714951.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi Folks,
If I have a route (route1) where I send messages to a seda queue and I have
another route (route2) that consumes messages from this seda queue and the
maximum size of the queue is set at 1000.
And, lets say that route2 cannot consume messages from the queue as quick as
route1 is placing
I tried installing camel-saxon but got the same results.
I made the following change to ./etc/system.properties:
#javax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl
javax.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryImpl
This also had no ef
13 matches
Mail list logo
