Versions Compared

Old Version 7

changes.mady.by.user James Strachan

Saved on

compared with

New Version Current

changes.mady.by.user Carl Edstrom

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

Architecture

Excerpt

Camel

is based around

uses a Java based Routing Domain Specific Language (DSL) or an Xml Configuration to configure

the

routing and mediation

you require using type-safe Java code which has IDE smart completion without the need for reams of XML

rules which are added to a CamelContext to implement the various Enterprise Integration Patterns.

At a high level Camel consists of a CamelContext which contains a collection of Component instances. A Component is essentially a factory of Endpoint instances.

You can explicitly configure Component instances in Java code or an IoC container like Spring or Guice, or they can be auto-discovered using URIs.

A Component is essentially a factory of Endpoint instances. An individual

An Endpoint acts rather like a URI or URL in a web application or a Destination in a JMS system; you can communicate with an endpoint; either sending messages to it or consuming messages from it. You can then create a Producer or Consumer

of

on an Endpoint to exchange messages with it.

The

Java Domain Specific Language (DSL) or Xml Configuration then adds Routes to a CamelContext which implement the various Enterprise Integration Patterns.

...

DSL makes heavy use of pluggable Languages to create an Expression or Predicate to make a truly powerful DSL which is extensible to the most suitable language depending on your needs. The following languages are supported

Include Page
Languages Supported
Languages Supported

Contents

The following links are to the individual parts of the Architecture.

Children Display
sorttitle

Diagram

Image Added