On Wed, Jan 9, 2013 at 8:13 AM, orz wrote:
> Hi,
>
> Thanks for your reply. I have already read chapters 8 and 9.
>
> I understand that I can use HawtDBAggregationRepository and redirect the
> aggregated exchange(s) to a DLQ after a certain number of retries.
>
> However, that is not what I want.
Can you provide the non working route?
On Tue, Jan 8, 2013 at 9:44 PM, neilac333
wrote:
> I have a Camel route that starts off with an executable for which I use
> exec
> and which produces an output file. The name of the file is specified in the
> outFile parameter to Exec. What I want to do ne
On Tue, Jan 8, 2013 at 9:44 PM, neilac333
wrote:
> I have a Camel route that starts off with an executable for which I use exec
> and which produces an output file. The name of the file is specified in the
> outFile parameter to Exec. What I want to do next is to pass that file
> /name/--not the c
Hi
Yeah for method 3 we should have a method so you can set that.
I have logged a ticket
https://issues.apache.org/jira/browse/CAMEL-5945
On Wed, Jan 9, 2013 at 8:00 AM, liugang wrote:
> Hi All:
>
>
>
> When I plan to use recipientList component, I can only select one from:
>
>
>
> Meth
On Tue, Jan 8, 2013 at 5:56 PM, sscott wrote:
> sscott wrote
>> I set up rsyslogd to forward *.* to localhost:5140. Every log message
>> causes Camel to output an InvalidPayloadException caused by a
>> NoTypeConversionAvailableException with the detail "No type converter
>> available to convert f
OK, thanks.
GangLiu
-Original Message-
From: Claus Ibsen [mailto:claus.ib...@gmail.com]
Sent: Wednesday, January 09, 2013 4:23 PM
To: users@camel.apache.org
Subject: Re: RecipientList with delimiter argument
Hi
Yeah for method 3 we should have a method so you can set that.
I have logg
I have an Apache Camel Splitter such as the following:
...
from("{{direct.split}}")
.split().method(splitter, "iterate").streaming()
.stopOnException()
.setHeader("{{header.index}}", simple("${property.CamelSplitIndex}++"))
// Other processing
.choice
.when(property(Ex
On Wed, Jan 9, 2013 at 1:15 PM, wxkevin wrote:
> I have an Apache Camel Splitter such as the following:
>
> ...
> from("{{direct.split}}")
> .split().method(splitter, "iterate").streaming()
> .stopOnException()
> .setHeader("{{header.index}}", simple("${property.CamelSplitIndex}++"))
>
It doesn't appear that Exchange.SPLIT_COMPLETE, Exchange.SPLIT_SIZE,
etc...are available outside the .splitter block. My original thought was to
use those provided properties.
I can try the always return 1 approach.
--
View this message in context:
http://camel.465427.n5.nabble.com/How-can-I-t
So I ended up using a class variable which is initially set to 0. If there
are elements to parse then when the splitter is complete it will update the
class variable through the use of a processor. Then after the splitter logic
I call another processor to get the number of elements parsed. If still
How can I keep the CamelContext running after I call start() in a
standalone java application? Thread.sleep(xxx) does not seem to be an
adequate solution for a production system.
On Tue, Jan 8, 2013 at 9:40 AM, Meriem wrote:
> I tried with :
>
> CamelContext context = new DefaultCamelContext()
Hi,
It may be architectural overkill for Camel to fail-over messages that are
inflight to another camel context with another identical route. The cost of
adding fail-over implies message persistence by the camel core and a degree
of stateful-ness which adds to cost per message for not enough value
Hi,
The CamelContext will be running once started until the context is stopped.
The example above is a rather trivial piece of main-line java code running
from the command line.
If you would like the context to run with more control on the life-cycle,
you need to either run it in a container (tom
Hi,
When I try to authenticate an HTTP request using WS-Security with camel-cxf
& wss4j interceptor, I get the following error :
org.apache.camel.spring.Main.main() INFO
[org.apache.camel.spring.SpringCamelContext] - Total 1 routes, of which 1
is started.
org.apache.camel.spring.Main.main() INFO
Willem,
Thanks, I read some of your posts in the past, they were very helpful. I
appreciate your advice.
My currently situation is: I used beans for complicated business logic, to
send different requests to different resources and to aggregate the results
in the past. But now our company is moving
I'm not using directly the BouncyCastle. It was imported by iText
dependency. I excluded the dependency to fix the problem.
Thanks
Best Regards
Leandro Franchi
On 08-01-2013 21:20, Christian Müller wrote:
Which version of BouncyCastle?
What is your runtime?
Can you share the complete stack t
Willem, thanks for the idea. Here is a resulting issue I have run into. The
1st route takes a message from queue/batch/ready, it throws it into the seda
queue. It basically takes every message it can and stuffs it into the seda
queue as fast as it can. The second route does process them as I would
Can you upgrade to wss4j 1.6.9? I had a similar issue...
Am 09.01.2013 17:31 schrieb "Charles Moulliard" :
> Hi,
>
> When I try to authenticate an HTTP request using WS-Security with camel-cxf
> & wss4j interceptor, I get the following error :
>
> org.apache.camel.spring.Main.main() INFO
> [org.ap
Will test with 1.6.9.
Until now in debug mode, I see that in the class WSS4JInInterceptor, when
we handle the message (handleMessage(SoapMessage msg) throws Fault), the
element is empty (Element elem =
WSSecurityUtil.getSecurityHeader(doc.getSOAPPart(), actor); ) even if a
SOAPHeader w
Get same issue even If I use camel with cxf 2.7.1 and wss4j 1.6.9.
Surprisingly the example that we have in camel project (that I created a
few years ago) including a unit test succeeds -->
https://github.com/apache/camel/blob/trunk/examples/camel-example-reportincident-wssecurity/src/test/java/or
http://camel.apache.org/loop.html
On Tue, Jan 8, 2013 at 1:45 PM, Kesireddy, Chandana (ITD) <
chandana.kesire...@state.ma.us> wrote:
> Following is the route :
>
> public class MyRouteBuilder extends RouteBuilder {
> @Override
> public void configure() throws Exception {
> // xnc route h
I tried producerTemplate for bean approach (in groovy) too. I got exception
when I tried to POST to an HTTP endpoint:
def template = context.createProducerTemplate()
def endpointUri = headers.END_POINT
def xheaders = ["Content-Type":"application/json",
"CamelHttpMethod":"PO
Find the issue. When we setup camel-cxf endpoint using as
DataFormat=MESSAGE, SOAP securityHeaders are removed.
On Wed, Jan 9, 2013 at 5:30 PM, Charles Moulliard wrote:
> Hi,
>
> When I try to authenticate an HTTP request using WS-Security with
> camel-cxf & wss4j interceptor, I get the followi
I just checked the camel-script code, it will bind the camel context within the
script context.
But it should be more easy to write a custom bean[1] and inject the camel
context to it, then you can get full control of it.
[1]http://camel.apache.org/bean.html
--
Willem Jiang
Red Hat, Inc.
F
Oh, you need to start the template before using it to send the request.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jn
On Thu, Jan 10, 2013 at 12:00 AM, Charles Moulliard wrote:
> Find the issue. When we setup camel-cxf endpoint using as
> DataFormat=MESSAGE, SOAP securityHeaders are removed.
>
I think there is a new CXF_MESSAGE or something. There was some new
formats added, but never documented.
I logged a tick
In the MESSAGE data format, camel-cxf will not let the interceptor which can
build the SOAP message from the input stream to be called.
So the WSS4JInInterceptor will not work any more.
I think that is why CXF_MESSAGE is introduced, I will dig the code to see if I
see the whole picture of it.
-
27 matches
Mail list logo
