You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "John Ross (JIRA)" <ji...@apache.org> on 2012/07/31 15:53:35 UTC
[jira] [Created] (ARIES-895) Missing filter directive on
Require-Capability does not translate to a filter value of =*.
John Ross created ARIES-895:
-------------------------------
Summary: Missing filter directive on Require-Capability does not translate to a filter value of <namespace>=*.
Key: ARIES-895
URL: https://issues.apache.org/jira/browse/ARIES-895
Project: Aries
Issue Type: Bug
Components: Subsystem
Reporter: John Ross
Assignee: John Ross
Currently, Subsystems translates a bundle's missing Require-Capability filter directive as <namespace>=* for the purpose of computing the subsystem's Require-Capability header. For example,
Require-Capability: y
in a bundle's manifest, would translate to
Require-Capability: y;filter:=(y=*)
in the subsystem's manifest. This is incorrect because (1) a requirement with a missing filter directive should match any capability from the same namespace and (2) capabilities are not required to use the namespace as an attribute. The current translation would not match a capability from the same namespace if said capability did not use the namespace as an attribute.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (ARIES-895) Missing filter directive on
Require-Capability does not translate to a filter value of =*.
Posted by "John Ross (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Ross resolved ARIES-895.
-----------------------------
Resolution: Fixed
Missing filter directives are no longer translated. Null values are anticipated and treated accordingly. For example, null filter directives result in RegionFilterBuilder.allowAll(<namespace>) being called when setting up the sharing policy in Region Digraph. Otherwise, RegionFilterBuilder.allow(<namespace>, <filter>) is called.
> Missing filter directive on Require-Capability does not translate to a filter value of <namespace>=*.
> -----------------------------------------------------------------------------------------------------
>
> Key: ARIES-895
> URL: https://issues.apache.org/jira/browse/ARIES-895
> Project: Aries
> Issue Type: Bug
> Components: Subsystem
> Reporter: John Ross
> Assignee: John Ross
>
> Currently, Subsystems translates a bundle's missing Require-Capability filter directive as <namespace>=* for the purpose of computing the subsystem's Require-Capability header. For example,
> Require-Capability: y
> in a bundle's manifest, would translate to
> Require-Capability: y;filter:=(y=*)
> in the subsystem's manifest. This is incorrect because (1) a requirement with a missing filter directive should match any capability from the same namespace and (2) capabilities are not required to use the namespace as an attribute. The current translation would not match a capability from the same namespace if said capability did not use the namespace as an attribute.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira