Chapter 3. Apache Camel Issues
3.1. Summary of Apache Camel 2.10 to Apache Camel 2.12 Migration
Overview
Red Hat JBoss Fuse 6.1.0.redhat-379 uses Apache Camel 2.12. Since the last release, Apache Camel has been upgraded from version 2.10 to version 2.12. This introduces a few migration issues.
Spring framework
Spring 3.0.x and Spring 3.1.x are no longer supported. You must use Spring 3.2.x.
You should also note that Maven 3.0.4 or better is required to build the source.
Apache MINA components are deprecated
In Apache Camel 2.12, both the MINA component and the MINA2 component are deprecated. Use the Camel Netty component instead.
New Camel components
Many new Camel components have been added in Apache Camel versions 2.11 and 2.12. In particular, note the following new components:
- SAP component
- The SAP Component enables outbound and inbound communication to and from SAP systems using synchronous remote function calls, sRFC. The component uses the SAP Java Connector (SAP JCo) library to facilitate bidirectional communication with SAP. The component supports two types of endpoints: destination endpoints and server endpoints.
- SAP Netweaver component
- The SAP Netweaver component integrates with the SAP NetWeaver Gateway using HTTP transports.
- Netty HTTP component
- The Netty HTTP component is an extension of the Netty component that can be used to create HTTP sockets with Netty.
- Yammer component
- The Yammer component enables you to interact with the Yammer enterprise social network.
- Facebook component
- The Facebook component provides access to all of the Facebook APIs accessible using Facebook4J.
