You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Thomas Watson (JIRA)" <ji...@apache.org> on 2015/01/08 14:41:35 UTC
[jira] [Commented] (ARIES-1283) Subsystem import/export service
header parsing is incorrect
[ https://issues.apache.org/jira/browse/ARIES-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14269298#comment-14269298 ]
Thomas Watson commented on ARIES-1283:
--------------------------------------
Taking ownership from David. I plan to get Sam Bratton to have a look and provide a patch that I can review.
> Subsystem import/export service header parsing is incorrect
> -----------------------------------------------------------
>
> Key: ARIES-1283
> URL: https://issues.apache.org/jira/browse/ARIES-1283
> Project: Aries
> Issue Type: Bug
> Components: Subsystem
> Environment: All
> Reporter: Thomas Watson
> Assignee: Thomas Watson
>
> ARIES-1263 introduced a bug in the parsing of the Subsystem import/export service headers. It appears the wildcard matching is causing the regular expressions used to parse the headers to match too much. If you modify test file:
> subsystem/subsystem-itests/src/test/resources/composite2/OSGI-INF/SUBSYSTEM.MF
> To have the following the test will fail:
> Subsystem-ExportService: *;filter:="(test=tb4)", does.not.exist; filter:="(a=b)"
> It appears the parsing converts the above to be something like
> Subsystem-ExportService: *;filter:="(a=b)"
> Basically collapsing the elements into one and using the last filter. This is causing Subsystem OSGi CT failures.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)