Creates an installed contribution from a supplied root contribution and installed at a supplied base URI.
See section 10.5.1 of the Assembly Specification.
uri the base uri of where to install the contribution. May be null in which case a URI is derived from the contribution URL
contributionURL the URL where the contribution is located
metaDataURL the location of an optional generated Contribution Metadata Document. See section 10.2.2
of the Assembly Specification. May be null.
dependentContributionURIs specifies the contributions that are used to resolve the dependencies of the
root contribution and other dependent contributions. May be null.
startDeployables true if the composites defined as deployable in the contribution's sca-contribution.xml
file or supplied metaData file should be started, false if they should not be.
- the URI of the installed contribution
Creates an installed contribution from a supplied Contribution object.
See section 10.5.1 of the Assembly Specification.
Creates an installed contribution from a supplied root contribution URL.
See section 10.5.1 of the Assembly Specification. This method is the same
as calling installContribution(null, contributionURL, null, null, true)
4599 10.5.2 add Deployment Composite & update Deployment Composite
4600 Adds or updates a deployment composite using a supplied composite ("composite by value" - a data
4601 structure, not an existing resource in the Domain) to the contribution identified by a supplied contribution
4602 URI. The added or updated deployment composite is given a relative URI that matches the
contributionURI the URI of the installed contribution to add the composite to
compositeXML the composite to add to the contribution
- 4603 attribute of the composite, with a ".composite" suffix. Since all composites run within the context of a
4604 installed contribution (any component implementations or other definitions are resolved within that
4605 contribution), this functionality makes it possible for the deployer to create a composite with final
4606 configuration and wiring decisions and add it to an installed contribution without having to modify the
4607 contents of the root contribution.
4608 Also, in some use cases, a contribution might include only implementation code (e.g. PHP scripts). It is
4609 then possible for those to be given component names by a (possibly generated) composite that is added
4610 into the installed contribution, without having to modify the packaging. *
4611 11.4.310.5.3 remove Contribution
4612 Removes the deployed contribution identified by a supplied contribution URI.
4677 10.7.1 add To Domain-Level Composite
4678 This functionality adds the composite identified by a supplied URI to the Domain Level Composite. The
4679 supplied composite URI refers to a composite within an installed contribution. The composite's installed
4680 contribution determines how the composite's artifacts are resolved (directly and indirectly). The supplied
4681 composite is added to the domain composite with semantics that correspond to the domain-level
4683 components become top-level components and the component services become externally visible
4684 services (eg. they would be present in a WSDL description of the Domain). The meaning of any promoted
4685 services and references in the supplied composite is not defined; since there is no composite scope
4686 outside the domain composite, the usual idea of promotion has no utility.
4687 10.7.2 remove From Domain-Level Composite
4688 Removes from the Domain Level composite the elements corresponding to the composite identified by a
4689 supplied composite URI. This means that the removal of the components, wires, services and references
4690 originally added to the domain level composite by the identified composite.
10.7.3 get Domain-Level Composite
Returns a <composite> definition that has an <include> line for each composite that had been added to
the domain level composite. It is important to note that, in dereferencing the included composites, any
referenced artifacts are resolved in terms of that installed composite.
4695 10.7.4 get QName Definition
4696 In order to make sense of the domain-level composite (as returned by get Domain-Level Composite), it
4697 needs to be possible to get the definitions for named artifacts in the included composites. This
4698 functionality takes the supplied URI of an installed contribution (which provides the context), a supplied
4699 qualified name of a definition to look up, and a supplied symbol space (as a QName, e.g.
4700 wsdl:PortTypeportType). The result is a single definition, in whatever form is appropriate for that
4701 definition type.
4702 Note that this, like all the other domain-level operations, is a conceptual operation. Its capabilities need to
4703 exist in some form, but not necessarily as a service operation with exactly this signature.
Probably want to be able to stop it all at once so a method called stop or shutdown or destroy
Would also be convenient to get service proxys as from SCAClientFactory
Get the URIs of any composites that have been started for a contribution
contributionURI the contribution URI
- the List of started composite URIs
Get the URIs of all the contributions installed on this Node
- the list of installed contribution URIs
Get an installed Contribution
uri the URI of the contribution
- the Contribution