Thank you guys for your help! Here's a simple example that works for me:
DataToPOJOProcessor:
exchange.setProperty("MyProperty", myObject); // assume method
myObject.getName();
Camel.xml:
--
View this message in context:
http://came
Cool thanks, this helps!
How would I access this the property via Spring XML?
Processor:
exchange.setProperty("MyProperty", myObject); // assume method
myObject.getName();
Camel.xml:
This doesn't work.
--
View this message in context:
http://camel.465427.n5.nabble.com/Passing-several-POJ
Hi,
I converted data from a file into several POJOs which should be available in
different routes for further processing. I tried to store them in the
message header (implements Serializable) but they are just available within
one route. After passing them to the next they are lost. Do I miss some
Hi,
I have got a POJO which contains values for two sequential SQL inserts. How
can I achieve this?
I tried something like this, but it fails due to the fact that named query
parameters (:#column) just work for HashMaps. I cannot find any
documentation how to proceed with my POJO. The conversion
Thanks for your answer!
Indeed, my concern to manage all exclusive topics might be a question for
the ActiveMQ mailing list. I was hoping to get around exclusive topics
sending the response directly after the camel route like in this description
(didn't work for me):
Reference:
http://camel.4654
Hi,
I'm trying to figure out the best practice for the communication between a
client and a broker over mqtt. I assume n different clients sending data to
my broker expecting to send a custom response for every received message in
return.
My current understanding is that every client must publish
Hi Claus,
I'm still not sure if the way I'm trying to access the java.util.Map
resultset with :#Position is the right way. It seems that nobody is using
this feature at all (at least I cannot find any other samples on the
internet).
--
View this message in context:
http://camel.465427.n5.nabb
Is it a bug?
Under http://camel.apache.org/sql-example.html at the very bottom it says:
Notice in the SQL queries below we use named parameters which must start
with prefix ':#' and then the name, eg :#amount. Then Camel will bind that
parameter with the given name, from the
message body (if its
