using reactive-streams with Apache Camel Saga - apache-camel

I would like to know if it is possible to use reactive streams in Apache Camel. I know reactive-streams is a component from Apache but I couldn't get it to work the way they explain in the documentation. I would like to know if there is any possible solutions available in github that could help me understand apache camel along with reactive-streams except the one's from apache.
I could possibly use Producer Template with reactor-core but the route logic that sits in RouteBuilder configure method would still be blocking I/O. Any helps would be appreciated?


External Service through Component Bindings in Camel (Similar To Mule binding interface)

I'm new in Apache Camel world and currently looking to understand how to use camel endpoints to Java interface methods. As per my requirement, I want to use an external service while the component(bean or transform or a process) is still processing the message. In Mule world - this is how it is implemented -
<component class="org.mule.examples.bindings.InvokerComponent">
<binding interface="org.mule.examples.bindings.HelloInterface"
Here in this example - The binding causes the sayHello method in HelloInterface to call out to the external HelloWeb service when sayHello is called when InvokerComponent is in execution.
Currently, I'm reading about camel CXF-RS but not sure if this is way to implement this type of use case in Camel. Can anyone please help me or guide me to implement this? Any code example will be great. Thank you so much!!
It’s quite an old unanswered question so sharing some ideas. You can use aggregator EIP for this situation.
The Aggregator from the EIP patterns allows you to combine a number of messages together into a single message.
How to use Aggregator EIP using Spring and Apache Camel?

What is the CamelContext in apache?

I searched in web but did not find any explanation that what is the exactly CamelContext? where and how to use ?
I gone through below links also but not satisfied with explanation.
There are many comparision for CamelContext with others, but what I am looking for is the what is it? I want some conceptual explanation.
Please help me to understand this.
It's roughly an instance of a Camel environment, or at least it's a reference to it. Most apps would only have one CamelContext, but you can have several if needed. Looking at the referenced document, it shows how the context has a lifecycle.
In most cases, the context will start and stop along with the application.
After seeing the videos in YouTube, I knew about the Apache camel framework,
and from that I got the answer that camelcontext is nothing but context of the 'apache camel framework' framework.
As many framework have context like Spring have an applicationcontext, Ninja have a context, same the 'Apache camel framework' have a context and that is called 'camelcontext'.
So, it is the run-time system of Apache Camel (framework) and it connects its different concepts such as routes, components or endpoints.
Reference :
Basic Apache Camel Tutorial

Can I use Camel and WMQ without JMS?

I am currently learning Camel, and have a specific project in mind that requires a Websphere MQ back-end, but I can't use JMS components, since I need a lot of non-jms headers, like MQIIH.
I found the camel-wmq project.
Is it the recommended solution ? Is it any good ?
You don't need to use jms. WMQ has a client API. Just download the wmq client jars and put them in your project and use them together with your Camel routes. You will probably put the wmq client code in a processor class or something similar. Off course best to test to put a message on a queue manually via RFHUTIL or something similar as a client so you are sure the environment setup is correct.
The suggested way of working with WMQ has always been through the JMS component since it enables you to painlessly switch to other providers if the need arises.
However, if you need to use some WMQ-specific function then my suggestion would be to extend the camel-wmq library - it contains only a subset of features supported by WMQ and does not support MQIIH headers that you need. Adding functionality to a component would probably involve more work than the solution Souciance Eqdam Rashti suggested but it would be a cleaner solution and more in line with Camel's philosophy. Also, you'd be giving back to the community and thus help make Camel a better tool for everyone :)
I would also suggest you go through the IBM MQ discussions on the Camel's official user group mailing list and see if you can salvage anything.

Camel-restdsl and fabric8 http-gateway

I got a camel-restdsl route (among others) running on JBoss Fuse 6.2, I'd like to know if it is possible to have it gateway'ed by the fabri8 http-gateway. I know that is would work for CXF rest services implemented there but don't see any documentation about REST services implemented with RestDSL.
The route relies on on the restlet component (though I may have it changed to jetty or whatever other it may work).
Any pointers will be much appreciated!

Difference between processor , component and end point

I am studying Apache Camel.
Could some one please explain the difference between a processor, component and endpoint with regard to Apache Camel.
A component allows you to talk with other systems. It allows you to send or receive messages and encapsulates the protocol to deal with another system. For e.g. jms-component allows to talk with JMS brokers.
An endpoint is nothing but the channel by which you send or receive a message through component e.g. "jms:queue:order" this defines a jms endpoint which is a queue from where your (jms) component will either consume or publish a message.
While a processor is piece of code which goes in between routes. There you write code to manipulate (transform/enrich/extract etc.) the message or have some integration logic.
For more details refer to camel's documentation
All whom are new to Apache Camel I suggest to read this article which explains really well what Camel is, and has an example to go along.
Another great piece is chatper 1 of the Camel in Action book, which can be freely downloaded from here:
Disclaimer: I am co-author of that book.
And there is this old by good tutorial that still applies today:
And you can find more tutorials / examples on the Camel website
And there is also some links to 3rd party blogs/articles/videos about Camel, where you can find some great information: