Objectives and prerequisites

compared with
Current by Vincent Zurczak
on Jun 17, 2011 14:15.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (9)

View Page History
{section}
{column}
{column}This section aims at describing how to create a Petals component from scratch.
This section aims at describing how to create a Petals component from scratch. It also explains some technical details on how Petals ESB works and manages components.

A Petals ESB component can be a _binding component_, that is to say a connector between Petals ESB and an external system, an application or the rest of the world. Or it can be a _service engine_, which provides a meaningful service inside the bus. The creation of both kinds of components is discussed in this document.
\\
A Petals component can be a _binding component_, that is to say a connector between Petals and an external system, an application or the rest of the world. . Or, it can be a service engine, which provides a reusable and customizable feature inside the bus. The creation of both kinds of components is discussed in this document.

\\
Understanding how a Petals component is made can ease the use of Petals components and help in the management and the configuration of a Petals platform.

This document is intended for a wide audience of Java developers, willing to develop components for the Petals platform. A good knowledge of Apache Maven is a plus, but is not mandatory. Petals beginners are encouraged to read this tutorial, as it was written with the objective of making the development of components easy.
\\
This document is intended for Java developers who need or want to develop components for the Petals platform. A good knowledge of Apache Maven is a plus, but is not mandatory. Petals beginners are encouraged to read this tutorial, as it was written with the objective of making the development of components as much easy as possible.
{column}
{column:width=350px}