That's true. May have a look at the SmppConsumer [1] which is using a listener [2] to receive short messages (SMS), create an exchange and send this exchange the the next processor in the chain...
[1] https://git-wip-us.apache.org/repos/asf?p=camel.git;a=blob;f=components/camel-smpp/src/main/java/org/apache/camel/component/smpp/SmppConsumer.java;h=5f6e516b01b8d0f467d41ee46b4b8e4908fe9c6b;hb=HEAD [2] https://git-wip-us.apache.org/repos/asf?p=camel.git;a=blob;f=components/camel-smpp/src/main/java/org/apache/camel/component/smpp/MessageReceiverListenerImpl.java;h=c62c68790e2c532e0d8f511e827419e680985fa3;hb=HEAD Best, Christian ----------------- Software Integration Specialist Apache Member V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer Apache Incubator PMC Member https://www.linkedin.com/pub/christian-mueller/11/551/642 On Sat, Oct 19, 2013 at 7:36 PM, samslara <samsl...@yahoo.com> wrote: > Hi, > I'm trying to implement an event-driven consumer where the event-driver > is > a custom library we have developed. I was looking at various documentation > on the subject and I can't find any interface through which the > event-driver > notifies the consumer. From the following fusesource doc: > > > http://fusesource.com/docs/router/2.4/prog_guide/Component-Impl-Consumer.html > > it looks like the mechanism on how this works is completely up to the dev. > The event just needs to somehow be transformed into a Camel > Message/Exchange > and be sent to the next processor which is given to the consumer via its > constructor. > > Is this accurate? > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/event-driven-consumer-tp5741907.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
