Versions Compared

Old Version 2

changes.mady.by.user James Strachan

Saved on

compared with

New Version 3

changes.mady.by.user Gordon Dickens

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

ServiceMix has mainly two deployment modelmodels:

  • you use the JBI compliant way, which is you install component at run-time and deploy service assemblies onto into them
  • you use a static configuration (servicemix.xml) file.  This mainly happens when you will run a single application for testing purposes, or when you embed servicemix ServiceMix in a web application for example.

Components in ServiceMix comes in two different flavours:

  • standard JBI compliants compliant components (servicemix-jms, servicemix-http, servicemix-jsr181, ...) that can accept servicemix ServiceMix unit deployments and are in the JBI spec spirit (they are containers).  These components are implemented using the servicemix-common module and are packaged as JBI components (with a jbi.xml descriptor file in the zip file)
  • lightweight components (or pojo components) are JBI components (they implement the needed interfaces) but can not be deployed at runtime (no packaging) and do not support service unit deployments.  These components usually inherit the ComponentSupport class (maybe indirectly) and are mainly in the servicemix-components module.

...