Versions Compared

Key

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

...

The following diagram shows the different entities that ACE knows:

Image Added

For each entity we will now list and explain the properties:

Artifact

Artifacts contain the metadata for the different types of artifacts that can be provisioned to targets. Artifacts can be bundles, configuration data or any other type you've defined yourself.

  • artifactName
  • artifactDescription
  • url
  • mimetype
  • processorPid
  • Bundle-Name
  • Bundle-SymbolicName
  • Bundle-Version

Artifact2Feature

Associates artifacts to features. Associations have a left and right hand side. Both can be expressed as filter conditions, and both have a cardinality.

  • leftEndpoint
  • leftCardinality
  • rightEndpoint
  • rightCardinality

Feature

A feature is a grouping mechanism for artifacts. It is commonly used to group together a set of artifacts that together represent some kind of feature to the application.

  • name
  • description

Feature2Distribution

Associates features to distributions. Associations have a left and right hand side. Both can be expressed as filter conditions, and both have a cardinality.

  • leftEndpoint
  • leftCardinality
  • rightEndpoint
  • rightCardinality

Distribution

A feature is a grouping mechanism for features. It is commonly used to group together a set of features that together represent some kind of distribution. Distributions are the things you can associate with targets, so you can look at them as the licensable configurations of your software.

  • name
  • description

Distribution2Target

Associates distributions to targets. Associations have a left and right hand side. Both can be expressed as filter conditions, and both have a cardinality.

  • leftEndpoint
  • leftCardinality
  • rightEndpoint
  • rightCardinality

Target

A target receives the artifacts you provision to it. Most of the time, a target is an OSGi container and provisioning means you'll actually install the artifacts in the container, but there can be other types of targets (non-OSGi containers, or something completely different).

  • id
  • autoapprove

Checkout and commit

Similar to the web based UI, this API also works with the concept of checking out a copy to a local working area, altering it in that working area and then committing it back to the server.

...