JOnAS / Camel

JOnAS Camel

Java EE / OSGi / EIP for high performance

JOnAS Camel relies on the Open Source and standard Java EE Entreprise OSGi JOnAS platform enhanced with the powerful EIP (Enterprise Integration Pattern) Apache Camel framework. It paves the road towards the convergence of the application server and the ESB with a flexible, efficient and robust mediation system and without expense of proprietary software. JOnAS Camel is provided with the LGPL License.

Nowadays Java EE application servers are widespread in the Enterprise Information System by reaching to reduce costs in development and administration tasks. The new generation of application server embeds the OSGi technology to improve modularity and dynamicity within the platform. In JOnAS, OSGi was put directly in the kernel at the lowest layer and Java EE and others technical services are deployed as OSGi services on top. That permits to build some 'à la carte' middlewares whose the functionalities fits well with the application requirements and which can evolve at runtime for optimizing the resource consumption. The high adaptability of the server is aligned with the profiles introduced in Java EE 6 specifications. The OSGi powerful can also be used at the application layer in JOnAS, in one hand to solve dynamically some dependencies and in another hand to navigate between the OSGi and Java paradigms.

With the advent of SOA principles, the lightweight mediation framework is pretty used to implement and integrate the applications. They provide a large library of connectors and processors for the routing, aggregation and transformation and a DSL to ease the expression. The OSGi version of Apache Camel ensures a fine integration in the JOnAS server with a maximum reuse of the technical services which guarantees the scalability and the robustness of the solution.

JOnAS users can leverage the Java EE/OSGi/Camel integrated technologies to deal with new SOA use cases such as the applications integration, reuse of legacy assets or application modernization.


Camel comes with

  • A large number of EIP patterns, such as message channel, message transport, point-topoint, publish, dead letter, aggregator, splitter, multicast, ...
  • Tens of components (i.e., protocol connectors): Java Bean, File (local and remote), FTP, SFTP, POP3, IMAP, SMTP, HTTP, SOAP, Web Services via CXF, EJB (2 and 3), JDBC, SQL, JMS, TCP, UDP, Nagios, Google App Engine, ... See here for a full list.
  • Tens of data formats: CSV, XML, JSON, Zip, ... See here for a whole list.
  • Programmability via multiple languages: Java, Spring XML, DSL, SQL, XPath, many scripting languages such as Groovy or Python, ...
  • Extensibility: you can add your own components, data formats and data converters.
  • Compatible with Presto WS stack
  • Logging with jdklog
  • JMX support
  • Comprehensive management solution with JASMINe
  • OSGi integration: all these components can be used in a “standalone” mode as well as in an OSGi framework.
    When used in an OSGi framework (such as JOnAS), CAMEL:
  • Reuses all existing JOnAS capabilities:
    • Existing services (HTTP service, JDBC, remote JMX, etc.)
    • Thread pool
    • Libraries (CXF, Spring, etc.)
    • Registries (OSGi, JNDI, etc.)
    • Dynamic class and component loading
    • and so on
  • Enriches the platform with its routing, transformation and other processing capabilities.