LibraryToggle FramesPrintFeedback

Each URI scheme maps to a Apache Camel component. A Apache Camel component is an endpoint factory. To use a particular type of endpoint, you must deploy the corresponding Apache Camel component along with the route. For example, to use JMS endpoints, you would deploy the JMS component.

Apache Camel provides a large variety of different components that enable you to integrate your application with various transport protocols and third-party products. For example, some of the more commonly used components are: File, JMS, CXF (Web services), HTTP, Jetty, Direct, and Mock. For the full list of supported components, see Component Reference.

Most of the Apache Camel components are packaged separately to the Camel core. If you use Maven to build your application, you can easily add a component (and its third-party dependencies) to your application simply by adding a dependency on the relevant component artifact. Example 1.4 shows the dependency needed to include the HTTP component to a project.

The following components are built-in to the the camel-core artifact, so they are always available:

  • Bean

  • Browse

  • Dataset

  • Direct

  • File

  • Log

  • Mock

  • Properties

  • Ref

  • SEDA

  • Timer

  • VM

Comments powered by Disqus
loading table of contents...