[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Usecases for External Policy Attachment
Here is my attempt to summarize the usecases for External Policy Attachment that we discussed on Monday's call. 1. Allow an External Policy file to be associated with a deployed composite. Michael Rowley says "I don’t know if we should generalize the addDeploymentComposite() to take multiple kinds of things, or add an explicit new operation like addExternalPolicy()." 2. Include the External Policy file in the sca-composite.xml file for a particular composite. 3. Once the External Policy file is associated with a domain by inclusion in a sca-composite.xml, statements within the file declare whether the file is to be associated with other composites in the domain. For example, a specific composite in a domain, all composites in the domain, composites in the domain whose name matches some regex. I must confess I don't really like the mechanism in 3. My preference would be to allow External Policy files to be associated with a domain and statements within the file to determine which composites within the domain it applies to. This requires a new mechanism to associate External Policy files with domains. -- All the best, Ashok
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]