I agree with Romain that processor is good thing to look at. Here are some resources that maybe useful:
https://stackoverflow.com/questions/20578756/apache-camel-processor-purpose https://camel.apache.org/manual/processor.html https://www.youtube.com/watch?v=s_6ip_9Yz5M https://access.redhat.com/documentation/ko-kr/red_hat_fuse/7.3/html/apache_camel_development_guide/processors https://medium.com/p/56c9249d5b24 Good luck, Raymond On Wed, Nov 16, 2022 at 7:51 PM Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > Hi John, > > Last time I implemented this bridge i moved from the templates to directly > using the processor (advantage being able to use sync or async send > depending how you integrate it with beam - in multicast mode if you have > only async processors you can call them all and await all to finish without > having to block or use a tons of threads which is great). > On the producing side (source in beam) the killer advantage is to not have > to poll the source but just react to the emittion and send them through the > PCollection directly when they are popping up - like beam does - so IMHO > the best is to get the consumer instance and set a custom "beam processor" > which just forwards the exchange in the PCollection (unbounded source or a > plain DoFn works). > > Hope it helps. > > Romain Manni-Bucau > @rmannibucau <https://twitter.com/rmannibucau> | Blog > <https://rmannibucau.metawerx.net/> | Old Blog > <http://rmannibucau.wordpress.com> | Github < > https://github.com/rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > < > https://www.packtpub.com/application-development/java-ee-8-high-performance > > > > > Le mer. 16 nov. 2022 à 19:15, John Casey <theotherj...@google.com.invalid> > a écrit : > > > And an hour after I send this, I stumble upon ProducerTemplate and > > ConsumerTemplate, which I'm pretty sure are exactly what I'm looking for. > > > > On Wed, Nov 16, 2022 at 11:56 AM John Casey <theotherj...@google.com> > > wrote: > > > > > Hi Camel, > > > > > > I'm John, working on the Apache Beam project. I'm looking to write a > Beam > > > wrapper for some Camel components, as Camel has a very well developed > > > ecosystem of connectors that we are looking to borrow. > > > > > > I essentially want to inject messages into camel, or extract them, > > > directly. > > > > > > Examples would be: > > > > > > from(something1?).to(some:existing:camel:component) > > > > > > from(some:existing:camel:component?with=config).to(something2?) > > > > > > Critically, I want to have my java process manually add data to > > > something1, and have it be routed to the existing component properly. > > > > > > I'm mailing to ask if there is an existing component or technique I can > > > use to get data into and out of Camel, or if this would be a new > > component > > > of some kind. > > > > > > Thanks, > > > John > > > > > > > > >
