| Key: |
POLICY-42
|
| Type: |
Improvement
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Michael Rowley (BEA)
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
|
| Component/s: |
None
|
| Affects Version/s: |
1.1
|
| Fix Version/s: |
1.1
|
|
|
Environment:
|
Policy Framework Specification section 3.3 Policy Sets
|
|
Issue Links:
|
Relates to
|
|
This issue relates to:
|
|
POLICY-15
External mechanism for attaching inte...
|
|
|
|
|
|
|
|
In the existing policy framework specification, the @appliesTo attribute is described as being executed against the composite file as it was written. However, the composite contains bindings, targets and policies that may be overridden by the component that uses that composite (with implementation.composite). In this case, the writer of the policySet usually wants the @appliesTo expression to be evaluated against the effective description of the components/bindings/etc.
PROPOSAL:
@appliesTo should be applied to a pre-processed infoset. The processing step should modify the composite file by applying any overrides, reference targets or property values that are specified by the component that uses the composite.
|
|
Description
|
In the existing policy framework specification, the @appliesTo attribute is described as being executed against the composite file as it was written. However, the composite contains bindings, targets and policies that may be overridden by the component that uses that composite (with implementation.composite). In this case, the writer of the policySet usually wants the @appliesTo expression to be evaluated against the effective description of the components/bindings/etc.
PROPOSAL:
@appliesTo should be applied to a pre-processed infoset. The processing step should modify the composite file by applying any overrides, reference targets or property values that are specified by the component that uses the composite.
|
Show » |
|
This issue should be marked as depending on issue 15 (external attachment of policy sets). The issue 15 resolution is likely going to make use of an XPath expression that runs on a post-processed infoset. The infoset that policySet/@appliesTo is executed on should be the same infoset as is used for issue 15, unless there is a good reason not to. The use cases are almost identical so the arguments for post-processing are the same. The main difference, in my way of thinking, is that external attachment is "pushing" policySets onto the infoset, whereas @appliesTo is "pulling" them onto the infoset based on intents.
One possible exception to this would be that the policySet algorithm can't be applied to the infoset prior to executing @appliesTo, since @appliesTo evaluation is part of that policySet algorithm (it would be a circular definition).
- Michael