On Sat, May 24, 2014 at 2:19 PM, romain.guay romain.g...@gmail.com wrote:
Hi,
I wonder why Camel supports JMSXGroupID and not JMSXGroupSeq properties. I
find it useful sometimes to set a message sequence inside a group and I
would expect to be able to rely on this property. Unless there is
Hello Claus,
Do you need anything else to have a more precise idea of my issue ?
Otherwise, do you have advice to make a workaround ?
Thanks.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-gracefull-shutdown-with-exec-tp5751510p5751578.html
Sent from the Camel -
On Mon, May 26, 2014 at 10:15 AM, Jey350 jey...@hotmail.com wrote:
Hello Claus,
Do you need anything else to have a more precise idea of my issue ?
Otherwise, do you have advice to make a workaround ?
I dont know what is the problem. You have provided limited
information. Also as you have
Hi,
I'm deploying some camel stuff in the last Karaf and noticed that the
camel-spring bundle have a Spring range that does not allow Spring 4
([3.2,4)).
Servicemix has wrapped Spring 4 jars so it would be nice to handle them.
Do you want that I fill a ticket on it? Make a pull request with bnd
Hi again
I need to clarify that I want to access members of the Object in the body,
which is a HashMap, from within the DSL. From a Processor I can access the
Object as such:
// works
exchange.getIn().getBody(Map.class).get(user_name));
In the fluent builder, like in the following
I'm having problems working out how to write my output to file.
I'm wanting something that can work with the File component so that I
get the benefit of its flexibility (and can use FTP etc.).
But the problem is that I need to write the data using a class that uses
a File or OutputStream. Its
Conclusion:
I have solved the issue few days ago by using Spring
CachingConnectionFactory which wraps MQQueueConnectionFactory - I was aware
of this possibility but I could not believe it can create memory leak. I
still don´t understand it and IMO this is bug (MQ?).
--
View this message in
Hi
My understanding is that the JMS connection factories were built for use in a
J2EE container and if you are using them outside of one, which sounds like you
are, then it must be wrapped in either Spring's CachingConnectionFactory or
ActiveMQ's PooledConnectionFactory. Though I have read in
In the Processor you define the access path during runtime:
you have one exchange as input.
In the RouteBuilder you define the access path during design time:
what is to do for _every_ incoming exchange (and some may not have a hashmap
as body...).
But i am sure that you could use simple
