{maturity:experimental}

EasyESB is a lightweight services bus. Unlike [PetalsDSB|petalsdsb:PetalsDSB Overview] is not really integration oriented but more oriented on advanced SOA notions. It is based on MDA (Model Driven Architecture) approaches.

It is composed of several modules and under modules:
* *exchange data model*:
** _+exchange10-api+_ : provides XSD schema to modelize an exchange
** _+exchange10-impl+_ : implementation of exchange models
* *soa data and service model*:
** _+soa10-api+_ : provides XSD schema to modelize the basics concepts of SOA and ESB paradigm such as endpoint, service, node, registry, components, listeners, senders... etc.
** _+soa10-impl+_ : implements these basics concepts from soa model
** _+ws-binding-soa+_ : provides WSDL description of basic operations that must offered endpoint, node and registry concept.
** _+soa-core-api+_ : wraps the preceeding WSDL description into a JAVA API.
** _+soa-core-impl+_ : implements the basic operations that must offered endpoint, node ... etc (The implementation of registry service is implemented in anothers module: technical-service-registry-impl ).
* *transporter service model* :
** _+ws-binding-transporter+_ : provides a WSDL description providing the basic operation of transporter based on exchange data model.
** _+transporter-api+_ : wraps the preceeding WSDL description into a JAVA API.
** _+transporter-soap-impl+_ : proposes an implementation of a transporter based on SOAP protocol.
* *integration model*:
** _+external-listener-soap+_ :
** _+external-sender-soap+_ :
* *component model*:
** _+ws-binding-bpel-component+_ :
** _+component-bpel+_ :
* *technical service model* :
** _+technical-service-registry-impl+_ :
** _+ws-binding-admin+_ :
** _+technical-service-admin-api+_ :
** _+technical-service-admin-impl+_ :
** _+ws-binding-client+_ :

If you have any questions, please use the [{report-info:page:space > space:name} contact form|Contact].