Skip to end of metadata
Go to start of metadata
Apache Camel ™ is a versatile open-source integration framework based on known Enterprise Integration Patterns.

Camel empowers you to define routing and mediation rules in a variety of domain-specific languages, including a Java-based Fluent API, Spring or Blueprint XML Configuration files, and a Scala DSL. This means you get smart completion of routing rules in your IDE, whether in a Java, Scala or XML editor.

Apache Camel uses URIs to work directly with any kind of Transport or messaging model such as HTTP, ActiveMQ, JMS, JBI, SCA, MINA or CXF, as well as pluggable Components and Data Format options. Apache Camel is a small library with minimal dependencies for easy embedding in any Java application. Apache Camel lets you work with the same API regardless which kind of Transport is used - so learn the API once and you can interact with all the Components provided out-of-box.

Apache Camel provides support for Bean Binding and seamless integration with popular frameworks such as CDISpring, Blueprint and Guice. Camel also has extensive support for unit testing your routes.

The following projects can leverage Apache Camel as a routing and mediation engine:

  • Apache ServiceMix - a popular distributed open source ESB and JBI container
  • Apache ActiveMQ - a mature, widely used open source message broker
  • Apache CXF - a smart web services suite (JAX-WS and JAX-RS)
  • Apache Karaf - a small OSGi based runtime in which applications can be deployed
  • Apache MINA - a high-performance NIO-driven networking framework

So don't get the hump - try Camel today! (smile)

Too many buzzwords - what exactly is Camel?

Okay, so the description above is technology focused.
There's a great discussion about Camel at Stack Overflow. We suggest you view the post, read the comments, and browse the suggested links for more details.

News

Today marks a very special day as it was exactly 10 years ago the first commit of Apache Camel was done by its creator James Strachan.

 
Added Mon Mar 19 10:54:57 2007 UTC (10 years ago) by jstrachan
Initial checkin of Camel routing library

The project was created as a sub-project to Apache ActiveMQ and back then github did not exists, so its using good old subversion.

In summer 2007 the first release of Apache Camel was published, which happened on July 2nd so lets wait until the summer to celebrate it's 10 years birthday.

The Camel community announces the immediate availability of the new patch release Camel 2.18.3. This release contains 38 fixes applied in the past few weeks by the community on the Camel 2.18.x maintenance branch.

The artifacts are published and ready for you to download either from the Apache mirrors or from the Central Maven repository. For more details please take a look at the release notes.

Many thanks to all who made this release possible.

On behalf of the Camel PMC,

Gregor Zurowski

The Camel community announces the immediate availability of the new patch release Camel 2.17.6. This release contains 17 fixes applied in the past few weeks by the community on the Camel 2.17.x maintenance branch.

The artifacts are published and ready for you to download either from the Apache mirrors or from the Central Maven repository. For more details please take a look at the release notes.

Many thanks to all who made this release possible.

On behalf of the Camel PMC,

Gregor Zurowski

The Apache Camel logo is a bit out dated so we have discussed in the Camel PMC and community to come up with a new one.
We encourage anyone to participate by submitting a logo proposal and/or share thoughts

The logo can be submitted by either:

And each logo should be:

  • images should be added to docs/img
  • each PR should contains a single logo

We are looking for a new logo that has two parts

  • graphical logo
  • name: Apache Camel

So we can use the logo without the word Apache Camel, but also as a combination of the two of them, eg as logo on the Camel front page.
Also if the logo can be vector based it would be a benefit, so it can scale up and down nicely.

You can find details here how to contribute to the project and how to work on the source code.
Such as how to do a github PR: http://camel.apache.org/contributing

The period is open until Monday 27th March 2017

After the period the submitted logos will be in a public vote, and the outcome of that vote will influence the decision on which logo to use as the official Apache Camel logo.

At this time of writing there are two proposals submitted at PRs:

https://github.com/apache/camel/pull/1369
https://github.com/apache/camel/pull/1494

More information and questions can be asked at the JIRA ticket:
https://issues.apache.org/jira/browse/CAMEL-10543

A weeks ago the Camel PMC voted another one of the very active and talented contributors to become a committer.

Zoran Regvart was actively involved with Apache Camel for about 8 month contributing code and helping other users, especially for the Camel Salesforce component.

Likewise he helped upgrade Jetty to support Jetty 9.3 which is not trivial work because Jetty keeps breaking their APIs and we have many components that rely on Jetty so its often a pain/more work to upgrade/maintain.

On behalf of the Camel PMC, welcome aboard Zoran and keep up the great work!
Claus Ibsen

The Camel community announces the immediate availability of the new patch release Camel 2.18.2. This release contains 68 fixes applied in the past few weeks by the community on the Camel 2.18.x maintenance branch.

The artifacts are published and ready for you to download either from the Apache mirrors or from the Central Maven repository. For more details please take a look at the release notes.

Many thanks to all who made this release possible.

On behalf of the Camel PMC,
Gregor Zurowski

RSS Feed

  • No labels

0 Comments