On Wed, Aug 29, 2012 at 9:47 PM, garrydias wrote:
> Hy guys
>
> I wrote the route below to perform this behavior:
> 1) call onExchangeBegin once
> 2) call onExchangeDone /body.envelopeList.size()/ times
>
> routePolicyRef="loggingRoutePolicy">
>
>
>
> ${
Hi Gershaw,
I want to use the camel quickFIX/J component which uses the QuickFIX/J FIX
engine. This component uses the standard Financial Interchange (FIX) protocol
for message transport.
Regards,
Shadab
-Original Message-
From: Gershaw, Geoffrey [mailto:geoffrey.gers...@credit-suisse
Hi All,
I have a question about how to configure time out for camel route
transaction. I am using servicemix 4.4.1 and Camel 2.8.0. I am trying to set
a time out to the transactions used by my camel routes so if any step in
route take too long time, the transaction can roll back and message could
Hi Garry,
No worries, if you are looking to do something each time a message is sent to
the ActiveMQ Endpoint you could just stick a processor in.
Thanks
Graham
${body.envelopeList}
> Date:
Hi Graham
Thanx a lot for your replies.
I´ll try another approach to do what I want.
The localSmsDeliveryEntry is an activemq endpoint. I thought that splited
Exchanges could fire onExchangeDone because they heir its parent Exchange
headers, including correlationID, and localSmsDeliveryEntry is
Hi Again,
Just in case you are interested you can see the workings of the
MulticastProcessor class here
(http://svn.apache.org/viewvc/camel/trunk/camel-core/src/main/java/org/apache/camel/processor/MulticastProcessor.java?view=markup)
thanks
Graham
> From: graham.lit...@outlook.com
> To: u
Hi,
Isn't the behaviour of the splitter that the it splits the message and not the
exchange, therefore the message is split at the point of the call put on hold
whilst all the messages are sent to localSmsDeliveryEntry. Once this process is
complete the single message is allowed to cotinue, in
It's a semi-Jetty issue. If you use Keep-Alive connections (the default),
Jetty has issues shutting down the port for some reason. It holds the port in
some sort of strange semi-open state that accepts connections but doesn't
properly process things. Never really had time to investigate a
Hy guys
I wrote the route below to perform this behavior:
1) call onExchangeBegin once
2) call onExchangeDone /body.envelopeList.size()/ times
${body.envelopeList}
But the current behavior is:
1) call
Have tried that. Doesn't fix it if I remember right.
--
View this message in context:
http://camel.465427.n5.nabble.com/Issue-using-camel-cxf-in-an-unit-test-tp5718310p5718324.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Maybe @*DirtiesContext*(classMode = ClassMode.AFTER_EACH_TEST_METHOD) at
the level of the class can help ?
On Wed, Aug 29, 2012 at 9:16 PM, Preben.Asmussen wrote:
> I can confirm this behavior also exists on Camel 2.10
>
> /Preben
>
>
>
> --
> View this message in context:
> http://camel.465427.
I can confirm this behavior also exists on Camel 2.10
/Preben
--
View this message in context:
http://camel.465427.n5.nabble.com/Issue-using-camel-cxf-in-an-unit-test-tp5718310p5718322.html
Sent from the Camel - Users mailing list archive at Nabble.com.
On Wed, Aug 29, 2012 at 6:17 PM, Claus Ibsen wrote:
> On Wed, Aug 29, 2012 at 2:10 PM, Alexey wrote:
>> Sorry, I moved the discussion to another topic.
>> You don't quite understand me. My xpath expression is correct. I tested this
>> xpath expr. with my xml using online xpath selector, it's work
On Wed, Aug 29, 2012 at 2:10 PM, Alexey wrote:
> Sorry, I moved the discussion to another topic.
> You don't quite understand me. My xpath expression is correct. I tested this
> xpath expr. with my xml using online xpath selector, it's work normal. The
> problem is that xpath must select from my h
Hi Hom,
Did you enable proxy support?
etc/org.ops4j.pax.url.mvn.cfg --> org.ops4j.pax.url.mvn.proxySupport=true
If not make sure you have it set up correctly in your Maven settings.xml
and then uncomment the line above.
Best Regards,
Scott ES
On Wed, Aug 29, 2012 at 9:28 AM, hom wrote:
> Hi,
Just as a future reference to others with the same issue:
Using a depends-on from the broker to camel didn't work by itself without
useShutdownHook set to true.
I am now using both the shutdown hook and a depends-on to make completely
sure stuff is dismantled in the correct order.
This is my wo
On Wed, Aug 29, 2012 at 5:39 PM, Muenkel, Markus wrote:
> Hi,
>
> the documentation at http://camel.apache.org/bean-binding.html describes the
> parameter binding feature that supports invoking a Java bean method with
> specified parameter values (literals or simple expressions) and gives
> exa
Hi,
the documentation at http://camel.apache.org/bean-binding.html describes the
parameter binding feature that supports invoking a Java bean method with
specified parameter values (literals or simple expressions) and gives examples
in the Java DSL.
AFAIK this feature is not supported in bluep
Problem solved!!!
I had "useShutdownHook" set to false in my embedded broker. Setting that to
true solved it. Now everything works like a charm.
I will add the depends-on as well to have them shutdown in the correct
order.
Thank you very much for your help!
Claus Ibsen-2 wrote
>
> Yeah good
On Wed, Aug 29, 2012 at 5:12 PM, towe wrote:
> I think you are on to something here! :-)
>
> One major difference I spotted between your test and mine is the standalone
> broker.
>
> When I run my own test against an external broker everything works as
> expected, the message is still there after
I think you are on to something here! :-)
One major difference I spotted between your test and mine is the standalone
broker.
When I run my own test against an external broker everything works as
expected, the message is still there after camel shutdown!
But when I run with an embedded broker st
thank you for your comment, Willem.
then it's like I figured out and I will develop a custom solution...
--
View this message in context:
http://camel.465427.n5.nabble.com/Exec-component-get-stdout-streaming-while-not-finished-tp5718201p5718270.html
Sent from the Camel - Users mailing list arch
Hi,
We are building a custom Karaf distribution using the feature descriptor:
mvn:org.apache.camel.karaf/apache-camel/${camel.version}/xml/features
It contains some bundles with repo definitions as part of the Maven url.
For instance:
mvn:http://scriptengines.googlecode.com/svn/m2-repo/!co
Could you share the bean code with us?
Sent from a mobile device
Am 29.08.2012 10:29 schrieb "me.mehta" :
> I am using following xml configuration for defining a custom bean for
> splitter.
>
>
>
>
>
>
>
>
> It doesn't run and gives an error:
>
> 12:31:28.770 [main] WARN
Hi
I created an unit test trying to reproduce an issue
http://svn.apache.org/viewvc?rev=1378526&view=rev
It works for me. I start up a remote AMQ broker first. In this case
Apache ActiveMQ 5.6.0.
Running the test ensures the message is rolled back, and using the AMQ
web console I can see the mess
Sorry, I moved the discussion to another topic.
You don't quite understand me. My xpath expression is correct. I tested this
xpath expr. with my xml using online xpath selector, it's work normal. The
problem is that xpath must select from my header, but not in the body.
For example that expressio
Also I have other beans within the same context where splitterBean is
defined, and those are referred from the camel routes. Working fine. Not
able to find out why this bean is not working.
--
View this message in context:
http://camel.465427.n5.nabble.com/Using-custom-bean-for-splitter-using-
Hi Yogesh,
thanks for your reply.
I am tried based on your reply.
but I am not getting the output file.
It thrwoing the following error.
*ShutdownTask] DefaultShutdownStrategyINFO Waiting as there are still 2
inflight and pending exchanges to complete, timeout in 299 seconds.
[el-1)
I am using camel 2.6, and running it through spring
--
View this message in context:
http://camel.465427.n5.nabble.com/Using-custom-bean-for-splitter-using-spring-camel-tp5718236p5718245.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi,
Given that its working without the use of the custom bean, I would say that
your bean is either not registered, or is registered but in another context.
Thanks
Graham
--
View this message in context:
http://camel.465427.n5.nabble.com/Using-custom-bean-for-splitter-using-spring-camel-tp5
Hi
What Camel version do you use?
Also how do you run this. Do you use Spring or OSGi or what?
On Wed, Aug 29, 2012 at 10:24 AM, me.mehta wrote:
> I am using following xml configuration for defining a custom bean for
> splitter.
>
>
>
>
>
>
>
>
> It doesn't run and give
Hi,
How do you deploy your project (war in tomcat, ...) ? Which version of CXF
are you using ? Which cxf xml files do you import ? Are you using the Jetty
HTTP server to register the web service or tomcat ?
I think that your issue is described here :
http://cxf.547215.n5.nabble.com/address-in-sp
I am using following xml configuration for defining a custom bean for
splitter.
It doesn't run and gives an error:
12:31:28.770 [main] WARN org.apache.camel.util.ObjectHelper - Cannot find
class: splitterBean.
If I use body instead of the custome bean, it
works fine
Hi Sushil,
Here is a basic example for you in the Java DSL, you can create and check as
many exchanges as you want. I would say just make sure that you are handling
any exceptions that may happen gracefully. A custom exchange handler is nearly
always needed to handle what to do in event of a c
On Wed, Aug 29, 2012 at 9:12 AM, Mohammad Shadab Ali
wrote:
> Hi,
>
> I am new to Quickfix. I want to use camel quickfix component to take input
> from FIX simulator and pass on to Active MQ.
>
> Routes as :-
> Quickfix --> ActiveMQ
>
> ActiveMQ --> Quickfix
>
> Can anybody please provide me a p
Hi
You can use a producer template to send a message to any endpoint.
And then create a "child route" using a direct/seda endpoint and use
the produce template to send the message to this route.
And in your custom processor, you can just wait until they are
complete before existing the method.
O
Hi
Use a header to set the UUID if it has to be per message specific.
The property is shared on a single Exchange which is used during the
entire routing of the incoming message that started it all.
On Wed, Aug 29, 2012 at 7:43 AM, sushil_vsk5 wrote:
> I have a route which has a splitter which
Hi,
I am new to Quickfix. I want to use camel quickfix component to take input from
FIX simulator and pass on to Active MQ.
Routes as :-
Quickfix --> ActiveMQ
ActiveMQ --> Quickfix
Can anybody please provide me a pointer for how to use Quickfix component and
camel test case for Quickfix comp
38 matches
Mail list logo