On 10/8/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: <snip>
> > > Does the spec say anywhere that when there is no sca-contribution.xmlthen > > composites in a contribution must not be added by default? > > > > Assembly specification V1.0 > > 2867 The contribution optionally contains a document that declares > runnable composites, exported > 2868 definitions and imported definitions. > ... > 2887 deployable element: Identifies a composite which is a composite > within the contribution that is > 2888 a composite intended for potential inclusion into the virtual > domain-level composite. Other > 2889 composites in the contribution are not intended for inclusion but > only for use by other > 2890 composites. New composites can be created for a contribution after > it is installed, by using the > 2891 add Deployment Composite capability and the add To Domain Level > Composite capability. > > This tells me that: > > - sca-contribution.xml is optional > - composites not listed as deployables are not intended for inclusion > - composites can be included in the domain after contribution, manually > using the addDeploymentComposite and addToDomainLevel operations > - the spec says "potential inclusion" and does not even imply that > deployable composites should be included in the domain by default But thats all about when the IS an sca-contribution.xml not what happens when there is NOT one. Including all composites in the domain by default when there's no > sca-contribution.xml is going to be pretty inconvenient and confusing as > it'll force people to ship an empty sca-contribution.xml file in all > contributions containing only composites intended for use by other > composites (aka implementations). How common will that be? If you look at all the dozens and dozens of composites we have in the Tuscany tests and samples the vast majority (all?) of them are intended to get deployed. Maybe those are 'simple' cases but aren't those the cases we should try to keep the API as simple as possible for? Along with the add methods if there's also remove methods then composites could still be removed so in those less common simple cases where having things added by default is inconvenient then you can simply remove them. ...ant
