Petals and Apache Camel

Specifications and User Documentation

See the Petals Wiki page on the component.

Continuous Integration

• Component
• Integration Tests

Issues Reporting

• Bug
• New Feature
• Improvement Request

Architecture

There is two main projects in this repository.

camel-petals

It implements a Camel Component that can be used in Camel in order to consumes (with from("petals:...") and produces (with to("petals:...") messages from and to Petals.

It needs to be provided with an implementation on how to communicate with Petals. Currently there is only one implementation, that is petals-se-camel (see next section).

In the future, it could be possible to use Camel from outside Petals and be able to contact and existing Petals Container.

petals-se-camel

It is a Petals Service Engine that embeds Apache Camel inside Petals. It obviously uses (and implements parts of) camel-petals for the integration into Camel.

Examples

There is currently three examples.

su-camel-hello-proxy-java

A simple proxy that forwards a request to another service. It is written in Java by implementing a Camel RouteBuilder.

su-camel-hello-proxy-xml

A simple proxy that forwards a request to another service. It is written in XML using the Camel Spring XML schema (but without using Spring itself).

su-camel-datamapping

Again a proxy (in Java) but more advanced, it exploits the following features of Camel :

• Marshmalling and unmarshalling using JAXB.
• Mapping between two different service descriptions using a Java bean for the transformation.
• Logging inside the routes.
• Streamcaching (Petals uses stream to store exchange content).