Apache ServiceMix NMR #usernavbar() #printableicon() #pdficon() #feedicon()  
When you contribute content to this Wiki, you grant a license to the ASF for inclusion in ASF works (as per the Apache Software License).
  3. Deploying JBI components without the JBI packaging

Versions Compared

Old Version 8

changes.mady.by.user Guillaume Nodet

Saved on

compared with

New Version 9

changes.mady.by.user Guillaume Nodet

Saved on

Key

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

...

For each endpoint defined in the application context, the EndpointExporter will create and register in the OSGi registry an object implementing org.apache.servicemix.common.osgi.EndpointWrapper. Those objects are tracked by each individual ServiceMix JBI component. When a given component knows how to handle a given endpoint, it will internally create a service unit, deploy it, and inform the endpoint wrapper that it has been successfully deployed. The EndpointExporter waits for all endpoint to be deployed and once this is done, will register a org.apache.servicemix.jbi.deployer.DeployedAssembly object representing a JBI Service Assembly composed of all the deployed service units. Those DeployedAssembly objects are tracked by the NMR JBI layer which can then handle those as standard JBI service assemblies.

At this point, the service units have been deployed, but not initialized and started, so that no JBI / NMR endpoint has been created yet. This will be done when the Service Assembly is actually initialized and started.

This quite complicated flow is necessary to be able to handle the JBI lifecycle of the Service Assembly in a nice way (starting, stopping, shutting down), because all service units lifecycle have to be managed through a service assembly in an atomic way.

...