On Mon, Jun 20, 2011 at 8:57 AM, Simon Laws <simonsl...@googlemail.com> wrote:
> > While I agree that you can attach to anywhere I doesn't seem to make > sense to applyTo anywhere but bindings and implementations. The spec > says.... > > 388 PolicySet authors need to be aware of the evaluation of the > @appliesTo attribute in order to designate > 389 meaningful values for this attribute. Although policySets can be > attached to any element in an SCA > 390 composite, the applicability of a policySet is not scoped by where > it is attached in the SCA framework. > 391 Rather, policySets always apply to either binding instances or > implementation elements regardless of where they are attached. > > So while technically you can describe and XPath statement that points > to anywhere in the composite I don't know what it means if the > appliesTo field doesn't point to an implementation or a binding. > The spec could certainly stand to be a bit more explicit here. :) It does seem to make more sense to limit it to bindings and implementations, so I agree that we should look into changing the appliesTo builder. I do notice there are several compliance tests using @appliesTo attributes that specify service, component, or composite, though (POL_4005 through 4009.) The compliance test failures seem to be a result of a change I made to avoid pushing implementation intents to endpoints. I've backed that change out and things seem to be OK now Brent
