Petals Distribution

A service assembly does not contain only a set of service units. It contains also:

• their identification
• the component on which each service unit must be deployed.

So we can't deploy a service unit as-is.

We introduced the deployable service unit that is a service unit with a JBI descriptor extended by:

• an identification part,
• and another part to define the target component name.

  <jbi:jbi xmlns:jbi="http://java.sun.com/xml/ns/jbi"
     xmlns:petals-jbi="http://petals.ow2.org/extensions/jbi/1.0"
     xmlns:petals.ow2.org="http://petals.ow2.org/" version="1.0">
     <jbi:services binding-component="false">
        ...
        <petals-jbi:identification>
           <jbi:name>su-name</jbi:name>
           <jbi:description>A Service Unit deployable directly</jbi:description>
        </petals-jbi:identification>
        <petals-jbi:component-name>target-component-id</petals-jbi:component-name>
     </jbi:services>
  </jbi:jbi>

To keep Petals ESB compliant with JBI, and to avoid to update the Petals ESB server side, we choose:

• to create automatically a temporary SA during such a service unit deployment,
• the temporary SA creation is done on Petals ESB client side (into Petals Administration API) or Petals ESB Autoloader extension.

Impacted Petals components:

• PETALSSTUD-317: Petals Studio will be improved to add the both new parts of the service unit JBI descriptor in the service unit wizard.
• PETALSESBCLI-99: Petals CLI will be improved to support deployment of such service units.
• MAVPETALSPLUG-22: Maven Petals Plugin will be improved to add both new parts when updating the JBI descriptor of a service unit
• PETALSESBCONT-305: Petals ESB autoloader will be improved to support deployment of such service units.

This issue should be closed when PETALSSTUD-317 will be closed