[jira] [Commented] (ARIES-1590) Subsystem install fails due to unexpected resolve conflict
[
https://issues.apache.org/jira/browse/ARIES-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412190#comment-15412190
]
John Ross commented on ARIES-1590:
--
Can you try using the latest version of the Felix Resolver, apparently 1.8?
http://felix.apache.org/downloads.cgi
> Subsystem install fails due to unexpected resolve conflict
> --
>
> Key: ARIES-1590
> URL: https://issues.apache.org/jira/browse/ARIES-1590
> Project: Aries
> Issue Type: Bug
> Components: Subsystem
>Reporter: Tom De Wolf
>Priority: Blocker
> Fix For: subsystem-2.1.0
>
> Attachments: reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
> reproduce-subsystem-4.1.2-SNAPSHOT.esa
>
>
> When we use the 2.0.9-SNAPSHOT version currently in development we get an
> unexpected resolve conflict:
> {panel}
> DEBUG: Candidate permutation failed due to a conflict between imports; will
> try another if possible. (org.osgi.service.resolver.ResolutionException: Uses
> constraint violation. Unable to resolve resource
> org.apache.servicemix.bundles.spring-core [116.0] because it is exposed to
> package 'org.aspectj.bridge' from resources
> com.reproduce.reproduce-base-subsystem
> [org.apache.aries.subsystem.core.internal.BasicSubsystem: children=0,
> constituents=60, id=3,
> location=file:///Users/tom/Documents/code/aca-common/osgi-subsystem-support/reproduce-base-subsystem/target/reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
> parents=1, state=INSTALLED,
> symbolicName=com.reproduce.reproduce-base-subsystem,
> type=osgi.subsystem.feature, version=4.1.2.SNAPSHOT] and
> org.apache.servicemix.bundles.aspectj [111.0] via two dependency chains.
> Chain 1:
> org.apache.servicemix.bundles.spring-core [116.0]
> import:
> (&(osgi.wiring.package=org.aspectj.bridge)(version>=1.7.1)(!(version>=2.0.0)))
> |
> export: osgi.wiring.package: org.aspectj.bridge
> com.reproduce.reproduce-base-subsystem
> [org.apache.aries.subsystem.core.internal.BasicSubsystem: children=0,
> constituents=60, id=3,
> location=file:///Users/tom/Documents/code/aca-common/osgi-subsystem-support/reproduce-base-subsystem/target/reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
> parents=1, state=INSTALLED,
> symbolicName=com.reproduce.reproduce-base-subsystem,
> type=osgi.subsystem.feature, version=4.1.2.SNAPSHOT]
> Chain 2:
> org.apache.servicemix.bundles.spring-core [116.0]
> import:
> (&(osgi.wiring.package=org.aspectj.weaver)(version>=1.7.1)(!(version>=2.0.0)))
> |
> export: osgi.wiring.package=org.aspectj.weaver;
> uses:=org.aspectj.weaver.patterns
> com.reproduce.reproduce-base-subsystem
> [org.apache.aries.subsystem.core.internal.BasicSubsystem: children=0,
> constituents=60, id=3,
> location=file:///Users/tom/Documents/code/aca-common/osgi-subsystem-support/reproduce-base-subsystem/target/reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
> parents=1, state=INSTALLED,
> symbolicName=com.reproduce.reproduce-base-subsystem,
> type=osgi.subsystem.feature, version=4.1.2.SNAPSHOT]
> import:
> (&(osgi.wiring.package=org.aspectj.weaver.patterns)(&(version>=1.7.1)(!(version>=2.0.0
> |
> export: osgi.wiring.package: org.aspectj.weaver.patterns;
> uses:=org.aspectj.bridge
> export: osgi.wiring.package=org.aspectj.bridge
> org.apache.servicemix.bundles.aspectj [111.0])
> {panel}
> It is unexpected because 1 of the 2 chains points to the actual bundle that
> exports the package and the other of the 2 chains points to the base
> subsystem already installed in the runtime. In fact the bundle is part of
> that subsystem so it should consider both as exactly the same and not
> consider it as 2 chains he cannot resolve.
> Not sure if it is related to ARIES-1588 and the commit mentioned there but
> that commit does affect how already installed subsystems are taken into
> account in the resolve process.
> Note: we are using the felix resolver 1.4.0
> Steps to reproduce:
> 1. start clean felix
> 2. install the attached reproduce-base-subsystem-4.1.2-SNAPSHOT.esa, do not
> start it
> 3. install the attached reproduce-subsystem-4.1.2-SNAPSHOT.esa
> Step 3 will start failing in DEBUG logging with chain errors like above. It
> will try a number of permutations but it will not get out of it.
> Note: which bundles and packages are shown in the example log above are less
> important as we have multiple such kind of errors for which only the package
> and bundles differ.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ARIES-1588) Installation of subsystems fails due to uses constraint violation after exposing feature capabilities.
[
https://issues.apache.org/jira/browse/ARIES-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412117#comment-15412117
]
Tom De Wolf commented on ARIES-1588:
[~jwr...@us.ibm.com] tried to compose subsystems for this specific issue and
encountered possibly related problems, equally blocking the 2.1.0 release with
the perf improvements. Can you have a look?
> Installation of subsystems fails due to uses constraint violation after
> exposing feature capabilities.
> --
>
> Key: ARIES-1588
> URL: https://issues.apache.org/jira/browse/ARIES-1588
> Project: Aries
> Issue Type: Bug
> Components: Subsystem
>Affects Versions: subsystem-2.1.0
>Reporter: Wouter Bancken
> Fix For: subsystem-2.1.0
>
> Attachments: pax-web-jetty-bundle-4.2.5.jar
>
>
> h4. Setup
> Two feature subsystems
> 1. Feature subsystem with fragment-hosts and fragments
> 2. Feature subsystem with other bundles
> Installation of the second subsystem fails
> h4. Issue
> Installation of the second subsystem fails with the message
> {quote}
> gogo: SubsystemException: org.osgi.service.resolver.ResolutionException: Uses
> constraint violation. Unable to resolve resource
> org.ops4j.pax.web.pax-web-jetty-bundle [124.0] because it exports package
> 'org.apache.xbean.finder.archive' and is also exposed to it from resource
> org.apache.xbean.finder [98.0] via the following dependency chain:
> org.ops4j.pax.web.pax-web-jetty-bundle [124.0]
> import: (osgi.wiring.package=org.apache.xbean.finder)
> export: osgi.wiring.package: org.apache.xbean.finder;
> uses:=org.apache.xbean.finder.archive
> export: osgi.wiring.package=org.apache.xbean.finder.archive
> org.apache.xbean.finder [98.0]
> {quote}
> Before failing a lot of similar messages are logged with the message "DEBUG:
> Candidate permutation failed due to a conflict between an export and import;
> will try another if possible."
> This is especially weird since pax-web-jetty-bundle does not expose the
> org.apache.xbean.finder.archive package (see attached Jar). Both
> pax-web-jetty-bundle and org.apache.xbean.finder are only present in the
> first subsystem.
> In our setup pax-web-jetty-bundle is a fragment-host for a fragment which is
> in the same (first) subsystem. Similar DEBUG statements are printed for other
> fragment-hosts in the first subsystem.
> The issue occurs since commit 4c0437de06f34321909a6132a7f2be163b2f6d5
> (ARIES-1443). In earlier versions, we had no issues for these subsystems.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ARIES-1591) Subsystem install fails due to ArrayIndexOutofBoundsException
[
https://issues.apache.org/jira/browse/ARIES-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom De Wolf updated ARIES-1591:
---
Description:
When we use the 2.0.9-SNAPSHOT version currently in development we get an
ArrayIndexOutOfBoundsException as soon as our base subsystem contains a
fragment bundle:
{panel}
Caused by: org.osgi.service.subsystem.SubsystemException:
java.lang.ArrayIndexOutOfBoundsException: -1
at
org.apache.aries.subsystem.core.internal.Utils.handleTrowable(Utils.java:117)
at
org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:398)
at
org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:363)
at
org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:101)
at
org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:91)
at
org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:60)
at
org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:27)
at java.security.AccessController.doPrivileged(Native Method)
at
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:738)
at
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:791)
at
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:365)
at
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:70)
... 30 more
Caused by: java.lang.ArrayIndexOutOfBoundsException: -1
at
org.apache.felix.resolver.util.CopyOnWriteList.set(CopyOnWriteList.java:53)
at org.apache.felix.resolver.Candidates.prepare(Candidates.java:1052)
at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:173)
at
org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:393)
... 41 more
{panel}
Attached are 2 subsystems that allow to reproduce it. Note that the ONLY
difference between these subsystem esa's and the onces attached at ARIES-1590
is the fragment bundle osgi-pax-web-jetty-config.
So the problem might be related to the same commit, but another effect.
Note: we are using the felix resolver 1.4.0
Steps to reproduce:
1. start clean felix
2. install the attached reproduce-base-subsystem-4.1.2-SNAPSHOT.esa, do not
start it
3. install the attached reproduce-subsystem-4.1.2-SNAPSHOT.esa
was:
When we use the 2.0.9-SNAPSHOT version currently in development we get an
ArrayIndexOutOfBoundsException as soon as our base subsystem contains a
fragment bundle:
{panel}
Caused by: org.osgi.service.subsystem.SubsystemException:
java.lang.ArrayIndexOutOfBoundsException: -1
at
org.apache.aries.subsystem.core.internal.Utils.handleTrowable(Utils.java:117)
at
org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:398)
at
org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:363)
at
org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:101)
at
org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:91)
at
org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:60)
at
org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:27)
at java.security.AccessController.doPrivileged(Native Method)
at
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:738)
at
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:791)
at
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:365)
at
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:70)
... 30 more
Caused by: java.lang.ArrayIndexOutOfBoundsException: -1
at
org.apache.felix.resolver.util.CopyOnWriteList.set(CopyOnWriteList.java:53)
at org.apache.felix.resolver.Candidates.prepare(Candidates.java:1052)
at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:173)
at
org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:393)
... 41 more
{panel}
Attached are 2 subsystems that allow to reproduce it. Note that the ONLY
difference between these subsystem esa's and the onces attached at ARIES-1590
is the fragment bundle osgi-pax-web-jetty-config.
So the problem might be related to the same commit, but another effect.
> Subsystem install fails due to ArrayIndexOutofBoundsException
>
[jira] [Updated] (ARIES-1591) Subsystem install fails due to ArrayIndexOutofBoundsException
[
https://issues.apache.org/jira/browse/ARIES-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom De Wolf updated ARIES-1591:
---
Attachment: reproduce-subsystem-4.1.2-SNAPSHOT.esa
reproduce-base-subsystem-4.1.2-SNAPSHOT.esa
> Subsystem install fails due to ArrayIndexOutofBoundsException
> -
>
> Key: ARIES-1591
> URL: https://issues.apache.org/jira/browse/ARIES-1591
> Project: Aries
> Issue Type: Bug
> Components: Subsystem
>Reporter: Tom De Wolf
>Priority: Blocker
> Fix For: subsystem-2.1.0
>
> Attachments: reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
> reproduce-subsystem-4.1.2-SNAPSHOT.esa
>
>
> When we use the 2.0.9-SNAPSHOT version currently in development we get an
> ArrayIndexOutOfBoundsException as soon as our base subsystem contains a
> fragment bundle:
> {panel}
> Caused by: org.osgi.service.subsystem.SubsystemException:
> java.lang.ArrayIndexOutOfBoundsException: -1
> at
> org.apache.aries.subsystem.core.internal.Utils.handleTrowable(Utils.java:117)
> at
> org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:398)
> at
> org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:363)
> at
> org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:101)
> at
> org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:91)
> at
> org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:60)
> at
> org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:27)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:738)
> at
> org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:791)
> at
> org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:365)
> at
> org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:70)
> ... 30 more
> Caused by: java.lang.ArrayIndexOutOfBoundsException: -1
> at
> org.apache.felix.resolver.util.CopyOnWriteList.set(CopyOnWriteList.java:53)
> at org.apache.felix.resolver.Candidates.prepare(Candidates.java:1052)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:173)
> at
> org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:393)
> ... 41 more
> {panel}
> Attached are 2 subsystems that allow to reproduce it. Note that the ONLY
> difference between these subsystem esa's and the onces attached at ARIES-1590
> is the fragment bundle osgi-pax-web-jetty-config.
> So the problem might be related to the same commit, but another effect.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ARIES-1591) Subsystem install fails due to ArrayIndexOutofBoundsException
Tom De Wolf created ARIES-1591:
--
Summary: Subsystem install fails due to
ArrayIndexOutofBoundsException
Key: ARIES-1591
URL: https://issues.apache.org/jira/browse/ARIES-1591
Project: Aries
Issue Type: Bug
Components: Subsystem
Reporter: Tom De Wolf
Priority: Blocker
Fix For: subsystem-2.1.0
When we use the 2.0.9-SNAPSHOT version currently in development we get an
ArrayIndexOutOfBoundsException as soon as our base subsystem contains a
fragment bundle:
{panel}
Caused by: org.osgi.service.subsystem.SubsystemException:
java.lang.ArrayIndexOutOfBoundsException: -1
at
org.apache.aries.subsystem.core.internal.Utils.handleTrowable(Utils.java:117)
at
org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:398)
at
org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:363)
at
org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:101)
at
org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:91)
at
org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:60)
at
org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:27)
at java.security.AccessController.doPrivileged(Native Method)
at
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:738)
at
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:791)
at
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:365)
at
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:70)
... 30 more
Caused by: java.lang.ArrayIndexOutOfBoundsException: -1
at
org.apache.felix.resolver.util.CopyOnWriteList.set(CopyOnWriteList.java:53)
at org.apache.felix.resolver.Candidates.prepare(Candidates.java:1052)
at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:173)
at
org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:393)
... 41 more
{panel}
Attached are 2 subsystems that allow to reproduce it. Note that the ONLY
difference between these subsystem esa's and the onces attached at ARIES-1590
is the fragment bundle osgi-pax-web-jetty-config.
So the problem might be related to the same commit, but another effect.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ARIES-1591) Subsystem install fails due to ArrayIndexOutofBoundsException
[
https://issues.apache.org/jira/browse/ARIES-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom De Wolf updated ARIES-1591:
---
Description:
When we use the 2.0.9-SNAPSHOT version currently in development we get an
ArrayIndexOutOfBoundsException as soon as our base subsystem contains a
fragment bundle:
{panel}
Caused by: org.osgi.service.subsystem.SubsystemException:
java.lang.ArrayIndexOutOfBoundsException: -1
at
org.apache.aries.subsystem.core.internal.Utils.handleTrowable(Utils.java:117)
at
org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:398)
at
org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:363)
at
org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:101)
at
org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:91)
at
org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:60)
at
org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:27)
at java.security.AccessController.doPrivileged(Native Method)
at
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:738)
at
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:791)
at
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:365)
at
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:70)
... 30 more
Caused by: java.lang.ArrayIndexOutOfBoundsException: -1
at
org.apache.felix.resolver.util.CopyOnWriteList.set(CopyOnWriteList.java:53)
at org.apache.felix.resolver.Candidates.prepare(Candidates.java:1052)
at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:173)
at
org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:393)
... 41 more
{panel}
Attached are 2 subsystems that allow to reproduce it. Note that the ONLY
difference between these subsystem esa's and the onces attached at ARIES-1590
is the fragment bundle osgi-pax-web-jetty-config.
So the problem might be related to the same commit, but another effect.
Note: we are using the felix resolver 1.4.0
Steps to reproduce:
1. start clean felix
2. install the attached reproduce-base-subsystem-4.1.2-SNAPSHOT.esa, do not
start it
3. install the attached reproduce-subsystem-4.1.2-SNAPSHOT.esa
Step 3 fails with the above exception.
was:
When we use the 2.0.9-SNAPSHOT version currently in development we get an
ArrayIndexOutOfBoundsException as soon as our base subsystem contains a
fragment bundle:
{panel}
Caused by: org.osgi.service.subsystem.SubsystemException:
java.lang.ArrayIndexOutOfBoundsException: -1
at
org.apache.aries.subsystem.core.internal.Utils.handleTrowable(Utils.java:117)
at
org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:398)
at
org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:363)
at
org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:101)
at
org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:91)
at
org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:60)
at
org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:27)
at java.security.AccessController.doPrivileged(Native Method)
at
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:738)
at
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:791)
at
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:365)
at
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:70)
... 30 more
Caused by: java.lang.ArrayIndexOutOfBoundsException: -1
at
org.apache.felix.resolver.util.CopyOnWriteList.set(CopyOnWriteList.java:53)
at org.apache.felix.resolver.Candidates.prepare(Candidates.java:1052)
at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:173)
at
org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:393)
... 41 more
{panel}
Attached are 2 subsystems that allow to reproduce it. Note that the ONLY
difference between these subsystem esa's and the onces attached at ARIES-1590
is the fragment bundle osgi-pax-web-jetty-config.
So the problem might be related to the same commit, but another effect.
Note: we are using the felix resolver 1.4.0
Steps to reproduce:
1. start
[jira] [Commented] (ARIES-1588) Installation of subsystems fails due to uses constraint violation after exposing feature capabilities.
[
https://issues.apache.org/jira/browse/ARIES-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411829#comment-15411829
]
Tom De Wolf commented on ARIES-1588:
ARIES-1590 might be related, I came across it trying to compose a set of
subsystems which can reproduce this issue (have to clean them out as I cannot
share all company bundles).
The problem in ARIES-1590 also seems to linked to the commit mentioned in the
description of this issue.
> Installation of subsystems fails due to uses constraint violation after
> exposing feature capabilities.
> --
>
> Key: ARIES-1588
> URL: https://issues.apache.org/jira/browse/ARIES-1588
> Project: Aries
> Issue Type: Bug
> Components: Subsystem
>Affects Versions: subsystem-2.1.0
>Reporter: Wouter Bancken
> Fix For: subsystem-2.1.0
>
> Attachments: pax-web-jetty-bundle-4.2.5.jar
>
>
> h4. Setup
> Two feature subsystems
> 1. Feature subsystem with fragment-hosts and fragments
> 2. Feature subsystem with other bundles
> Installation of the second subsystem fails
> h4. Issue
> Installation of the second subsystem fails with the message
> {quote}
> gogo: SubsystemException: org.osgi.service.resolver.ResolutionException: Uses
> constraint violation. Unable to resolve resource
> org.ops4j.pax.web.pax-web-jetty-bundle [124.0] because it exports package
> 'org.apache.xbean.finder.archive' and is also exposed to it from resource
> org.apache.xbean.finder [98.0] via the following dependency chain:
> org.ops4j.pax.web.pax-web-jetty-bundle [124.0]
> import: (osgi.wiring.package=org.apache.xbean.finder)
> export: osgi.wiring.package: org.apache.xbean.finder;
> uses:=org.apache.xbean.finder.archive
> export: osgi.wiring.package=org.apache.xbean.finder.archive
> org.apache.xbean.finder [98.0]
> {quote}
> Before failing a lot of similar messages are logged with the message "DEBUG:
> Candidate permutation failed due to a conflict between an export and import;
> will try another if possible."
> This is especially weird since pax-web-jetty-bundle does not expose the
> org.apache.xbean.finder.archive package (see attached Jar). Both
> pax-web-jetty-bundle and org.apache.xbean.finder are only present in the
> first subsystem.
> In our setup pax-web-jetty-bundle is a fragment-host for a fragment which is
> in the same (first) subsystem. Similar DEBUG statements are printed for other
> fragment-hosts in the first subsystem.
> The issue occurs since commit 4c0437de06f34321909a6132a7f2be163b2f6d5
> (ARIES-1443). In earlier versions, we had no issues for these subsystems.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ARIES-1590) Subsystem install fails due to unexpected resolve conflict
[
https://issues.apache.org/jira/browse/ARIES-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom De Wolf updated ARIES-1590:
---
Attachment: reproduce-subsystem-4.1.2-SNAPSHOT.esa
> Subsystem install fails due to unexpected resolve conflict
> --
>
> Key: ARIES-1590
> URL: https://issues.apache.org/jira/browse/ARIES-1590
> Project: Aries
> Issue Type: Bug
> Components: Subsystem
>Reporter: Tom De Wolf
>Priority: Blocker
> Fix For: subsystem-2.1.0
>
> Attachments: reproduce-subsystem-4.1.2-SNAPSHOT.esa
>
>
> When we use the 2.0.9-SNAPSHOT version currently in development we get an
> unexpected resolve conflict:
> {panel}
> DEBUG: Candidate permutation failed due to a conflict between imports; will
> try another if possible. (org.osgi.service.resolver.ResolutionException: Uses
> constraint violation. Unable to resolve resource
> com.reproduce.reproduce-bundle
> [/var/folders/9b/nqy6w5xs6gz1m1q4g6gpfr_cgn/T/inputStreamExtract8165788265469364064.zip/reproduce-bundle-4.1.2-SNAPSHOT.jar]
> because it is exposed to package 'org.springframework.beans' from resources
> com.reproduce.reproduce-base-subsystem
> [org.apache.aries.subsystem.core.internal.BasicSubsystem: children=0,
> constituents=70, id=1,
> location=file:///Users/tom/Documents/code/aca-common/osgi-subsystem-support/reproduce-base-subsystem/target/reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
> parents=1, state=INSTALLED,
> symbolicName=com.reproduce.reproduce-base-subsystem,
> type=osgi.subsystem.feature, version=4.1.2.SNAPSHOT] and
> org.apache.servicemix.bundles.spring-beans [73.0] via two dependency chains.
> Chain 1:
> com.reproduce.reproduce-bundle
> [/var/folders/9b/nqy6w5xs6gz1m1q4g6gpfr_cgn/T/inputStreamExtract8165788265469364064.zip/reproduce-bundle-4.1.2-SNAPSHOT.jar]
> import: (&(osgi.wiring.package=org.springframework.beans)(version>=0.0.0))
> |
> export: osgi.wiring.package: org.springframework.beans
> com.reproduce.reproduce-base-subsystem
> [org.apache.aries.subsystem.core.internal.BasicSubsystem: children=0,
> constituents=70, id=1,
> location=file:///Users/tom/Documents/code/aca-common/osgi-subsystem-support/reproduce-base-subsystem/target/reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
> parents=1, state=INSTALLED,
> symbolicName=com.reproduce.reproduce-base-subsystem,
> type=osgi.subsystem.feature, version=4.1.2.SNAPSHOT]
> Chain 2:
> com.reproduce.reproduce-bundle
> [/var/folders/9b/nqy6w5xs6gz1m1q4g6gpfr_cgn/T/inputStreamExtract8165788265469364064.zip/reproduce-bundle-4.1.2-SNAPSHOT.jar]
> import:
> (&(osgi.wiring.package=org.springframework.beans.factory.annotation)(version>=0.0.0))
> |
> export: osgi.wiring.package:
> org.springframework.beans.factory.annotation; uses:=org.springframework.beans
> export: osgi.wiring.package=org.springframework.beans
> org.apache.servicemix.bundles.spring-beans [73.0])
> {panel}
> It is unexpected because 1 of the 2 chains points to the actual bundle that
> exports the package and the other of the 2 chains points to the base
> subsystem already installed in the runtime. In fact the bundle is part of
> that subsystem so it should consider both as exactly the same and not
> consider it as 2 chains he cannot resolve.
> Not sure if it is related to ARIES-1588 and the commit mentioned there but
> that commit does affect how already installed subsystems are taken into
> account in the resolve process.
> Note: we are using the felix resolver 1.4.0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ARIES-1590) Subsystem install fails due to unexpected resolve conflict
[
https://issues.apache.org/jira/browse/ARIES-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom De Wolf updated ARIES-1590:
---
Attachment: reproduce-base-subsystem-4.1.2-SNAPSHOT.esa
> Subsystem install fails due to unexpected resolve conflict
> --
>
> Key: ARIES-1590
> URL: https://issues.apache.org/jira/browse/ARIES-1590
> Project: Aries
> Issue Type: Bug
> Components: Subsystem
>Reporter: Tom De Wolf
>Priority: Blocker
> Fix For: subsystem-2.1.0
>
> Attachments: reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
> reproduce-subsystem-4.1.2-SNAPSHOT.esa
>
>
> When we use the 2.0.9-SNAPSHOT version currently in development we get an
> unexpected resolve conflict:
> {panel}
> DEBUG: Candidate permutation failed due to a conflict between imports; will
> try another if possible. (org.osgi.service.resolver.ResolutionException: Uses
> constraint violation. Unable to resolve resource
> org.apache.servicemix.bundles.spring-core [116.0] because it is exposed to
> package 'org.aspectj.bridge' from resources
> com.reproduce.reproduce-base-subsystem
> [org.apache.aries.subsystem.core.internal.BasicSubsystem: children=0,
> constituents=60, id=3,
> location=file:///Users/tom/Documents/code/aca-common/osgi-subsystem-support/reproduce-base-subsystem/target/reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
> parents=1, state=INSTALLED,
> symbolicName=com.reproduce.reproduce-base-subsystem,
> type=osgi.subsystem.feature, version=4.1.2.SNAPSHOT] and
> org.apache.servicemix.bundles.aspectj [111.0] via two dependency chains.
> Chain 1:
> org.apache.servicemix.bundles.spring-core [116.0]
> import:
> (&(osgi.wiring.package=org.aspectj.bridge)(version>=1.7.1)(!(version>=2.0.0)))
> |
> export: osgi.wiring.package: org.aspectj.bridge
> com.reproduce.reproduce-base-subsystem
> [org.apache.aries.subsystem.core.internal.BasicSubsystem: children=0,
> constituents=60, id=3,
> location=file:///Users/tom/Documents/code/aca-common/osgi-subsystem-support/reproduce-base-subsystem/target/reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
> parents=1, state=INSTALLED,
> symbolicName=com.reproduce.reproduce-base-subsystem,
> type=osgi.subsystem.feature, version=4.1.2.SNAPSHOT]
> Chain 2:
> org.apache.servicemix.bundles.spring-core [116.0]
> import:
> (&(osgi.wiring.package=org.aspectj.weaver)(version>=1.7.1)(!(version>=2.0.0)))
> |
> export: osgi.wiring.package=org.aspectj.weaver;
> uses:=org.aspectj.weaver.patterns
> com.reproduce.reproduce-base-subsystem
> [org.apache.aries.subsystem.core.internal.BasicSubsystem: children=0,
> constituents=60, id=3,
> location=file:///Users/tom/Documents/code/aca-common/osgi-subsystem-support/reproduce-base-subsystem/target/reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
> parents=1, state=INSTALLED,
> symbolicName=com.reproduce.reproduce-base-subsystem,
> type=osgi.subsystem.feature, version=4.1.2.SNAPSHOT]
> import:
> (&(osgi.wiring.package=org.aspectj.weaver.patterns)(&(version>=1.7.1)(!(version>=2.0.0
> |
> export: osgi.wiring.package: org.aspectj.weaver.patterns;
> uses:=org.aspectj.bridge
> export: osgi.wiring.package=org.aspectj.bridge
> org.apache.servicemix.bundles.aspectj [111.0])
> {panel}
> It is unexpected because 1 of the 2 chains points to the actual bundle that
> exports the package and the other of the 2 chains points to the base
> subsystem already installed in the runtime. In fact the bundle is part of
> that subsystem so it should consider both as exactly the same and not
> consider it as 2 chains he cannot resolve.
> Not sure if it is related to ARIES-1588 and the commit mentioned there but
> that commit does affect how already installed subsystems are taken into
> account in the resolve process.
> Note: we are using the felix resolver 1.4.0
> Steps to reproduce:
> 1. start clean felix
> 2. install the attached reproduce-base-subsystem-4.1.2-SNAPSHOT.esa, do not
> start it
> 3. install the attached reproduce-subsystem-4.1.2-SNAPSHOT.esa
> Step 3 will start failing in DEBUG logging with chain errors like above. It
> will try a number of permutations but it will not get out of it.
> Note: which bundles and packages are shown in the example log above are less
> important as we have multiple such kind of errors for which only the package
> and bundles differ.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ARIES-1590) Subsystem install fails due to unexpected resolve conflict
[
https://issues.apache.org/jira/browse/ARIES-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom De Wolf updated ARIES-1590:
---
Description:
When we use the 2.0.9-SNAPSHOT version currently in development we get an
unexpected resolve conflict:
{panel}
DEBUG: Candidate permutation failed due to a conflict between imports; will try
another if possible. (org.osgi.service.resolver.ResolutionException: Uses
constraint violation. Unable to resolve resource
org.apache.servicemix.bundles.spring-core [116.0] because it is exposed to
package 'org.aspectj.bridge' from resources
com.reproduce.reproduce-base-subsystem
[org.apache.aries.subsystem.core.internal.BasicSubsystem: children=0,
constituents=60, id=3,
location=file:///Users/tom/Documents/code/aca-common/osgi-subsystem-support/reproduce-base-subsystem/target/reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
parents=1, state=INSTALLED,
symbolicName=com.reproduce.reproduce-base-subsystem,
type=osgi.subsystem.feature, version=4.1.2.SNAPSHOT] and
org.apache.servicemix.bundles.aspectj [111.0] via two dependency chains.
Chain 1:
org.apache.servicemix.bundles.spring-core [116.0]
import:
(&(osgi.wiring.package=org.aspectj.bridge)(version>=1.7.1)(!(version>=2.0.0)))
|
export: osgi.wiring.package: org.aspectj.bridge
com.reproduce.reproduce-base-subsystem
[org.apache.aries.subsystem.core.internal.BasicSubsystem: children=0,
constituents=60, id=3,
location=file:///Users/tom/Documents/code/aca-common/osgi-subsystem-support/reproduce-base-subsystem/target/reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
parents=1, state=INSTALLED,
symbolicName=com.reproduce.reproduce-base-subsystem,
type=osgi.subsystem.feature, version=4.1.2.SNAPSHOT]
Chain 2:
org.apache.servicemix.bundles.spring-core [116.0]
import:
(&(osgi.wiring.package=org.aspectj.weaver)(version>=1.7.1)(!(version>=2.0.0)))
|
export: osgi.wiring.package=org.aspectj.weaver;
uses:=org.aspectj.weaver.patterns
com.reproduce.reproduce-base-subsystem
[org.apache.aries.subsystem.core.internal.BasicSubsystem: children=0,
constituents=60, id=3,
location=file:///Users/tom/Documents/code/aca-common/osgi-subsystem-support/reproduce-base-subsystem/target/reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
parents=1, state=INSTALLED,
symbolicName=com.reproduce.reproduce-base-subsystem,
type=osgi.subsystem.feature, version=4.1.2.SNAPSHOT]
import:
(&(osgi.wiring.package=org.aspectj.weaver.patterns)(&(version>=1.7.1)(!(version>=2.0.0
|
export: osgi.wiring.package: org.aspectj.weaver.patterns;
uses:=org.aspectj.bridge
export: osgi.wiring.package=org.aspectj.bridge
org.apache.servicemix.bundles.aspectj [111.0])
{panel}
It is unexpected because 1 of the 2 chains points to the actual bundle that
exports the package and the other of the 2 chains points to the base subsystem
already installed in the runtime. In fact the bundle is part of that subsystem
so it should consider both as exactly the same and not consider it as 2 chains
he cannot resolve.
Not sure if it is related to ARIES-1588 and the commit mentioned there but that
commit does affect how already installed subsystems are taken into account in
the resolve process.
Note: we are using the felix resolver 1.4.0
Steps to reproduce:
1. start clean felix
2. install the attached reproduce-base-subsystem-4.1.2-SNAPSHOT.esa, do not
start it
3. install the attached reproduce-subsystem-4.1.2-SNAPSHOT.esa
Step 3 will start failing in DEBUG logging with chain errors like above. It
will try a number of permutations but it will not get out of it.
Note: which bundles and packages are shown in the example log above are less
important as we have multiple such kind of errors for which only the package
and bundles differ.
was:
When we use the 2.0.9-SNAPSHOT version currently in development we get an
unexpected resolve conflict:
{panel}
DEBUG: Candidate permutation failed due to a conflict between imports; will try
another if possible. (org.osgi.service.resolver.ResolutionException: Uses
constraint violation. Unable to resolve resource com.reproduce.reproduce-bundle
[/var/folders/9b/nqy6w5xs6gz1m1q4g6gpfr_cgn/T/inputStreamExtract8165788265469364064.zip/reproduce-bundle-4.1.2-SNAPSHOT.jar]
because it is exposed to package 'org.springframework.beans' from resources
com.reproduce.reproduce-base-subsystem
[org.apache.aries.subsystem.core.internal.BasicSubsystem: children=0,
constituents=70, id=1,
location=file:///Users/tom/Documents/code/aca-common/osgi-subsystem-support/reproduce-base-subsystem/target/reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
parents=1, state=INSTALLED,
symbolicName=com.reproduce.reproduce-base-subsystem,
type=osgi.subsystem.feature, version=4.1.2.SNAPSHOT] and
org.apache.servicemix.bundles.spring-beans [73.0] via two dependency chains.
Chain 1:
com.reproduce.reproduce-bundle
[jira] [Created] (ARIES-1590) Subsystem install fails due to unexpected resolve conflict
Tom De Wolf created ARIES-1590:
--
Summary: Subsystem install fails due to unexpected resolve conflict
Key: ARIES-1590
URL: https://issues.apache.org/jira/browse/ARIES-1590
Project: Aries
Issue Type: Bug
Components: Subsystem
Reporter: Tom De Wolf
Priority: Blocker
Fix For: subsystem-2.1.0
When we use the 2.0.9-SNAPSHOT version currently in development we get an
unexpected resolve conflict:
{panel}
DEBUG: Candidate permutation failed due to a conflict between imports; will try
another if possible. (org.osgi.service.resolver.ResolutionException: Uses
constraint violation. Unable to resolve resource com.reproduce.reproduce-bundle
[/var/folders/9b/nqy6w5xs6gz1m1q4g6gpfr_cgn/T/inputStreamExtract8165788265469364064.zip/reproduce-bundle-4.1.2-SNAPSHOT.jar]
because it is exposed to package 'org.springframework.beans' from resources
com.reproduce.reproduce-base-subsystem
[org.apache.aries.subsystem.core.internal.BasicSubsystem: children=0,
constituents=70, id=1,
location=file:///Users/tom/Documents/code/aca-common/osgi-subsystem-support/reproduce-base-subsystem/target/reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
parents=1, state=INSTALLED,
symbolicName=com.reproduce.reproduce-base-subsystem,
type=osgi.subsystem.feature, version=4.1.2.SNAPSHOT] and
org.apache.servicemix.bundles.spring-beans [73.0] via two dependency chains.
Chain 1:
com.reproduce.reproduce-bundle
[/var/folders/9b/nqy6w5xs6gz1m1q4g6gpfr_cgn/T/inputStreamExtract8165788265469364064.zip/reproduce-bundle-4.1.2-SNAPSHOT.jar]
import: (&(osgi.wiring.package=org.springframework.beans)(version>=0.0.0))
|
export: osgi.wiring.package: org.springframework.beans
com.reproduce.reproduce-base-subsystem
[org.apache.aries.subsystem.core.internal.BasicSubsystem: children=0,
constituents=70, id=1,
location=file:///Users/tom/Documents/code/aca-common/osgi-subsystem-support/reproduce-base-subsystem/target/reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
parents=1, state=INSTALLED,
symbolicName=com.reproduce.reproduce-base-subsystem,
type=osgi.subsystem.feature, version=4.1.2.SNAPSHOT]
Chain 2:
com.reproduce.reproduce-bundle
[/var/folders/9b/nqy6w5xs6gz1m1q4g6gpfr_cgn/T/inputStreamExtract8165788265469364064.zip/reproduce-bundle-4.1.2-SNAPSHOT.jar]
import:
(&(osgi.wiring.package=org.springframework.beans.factory.annotation)(version>=0.0.0))
|
export: osgi.wiring.package: org.springframework.beans.factory.annotation;
uses:=org.springframework.beans
export: osgi.wiring.package=org.springframework.beans
org.apache.servicemix.bundles.spring-beans [73.0])
{panel}
It is unexpected because 1 of the 2 chains points to the actual bundle that
exports the package and the other of the 2 chains points to the base subsystem
already installed in the runtime. In fact the bundle is part of that subsystem
so it should consider both as exactly the same and not consider it as 2 chains
he cannot resolve.
Not sure if it is related to ARIES-1588 and the commit mentioned there but that
commit does affect how already installed subsystems are taken into account in
the resolve process.
Note: we are using the felix resolver 1.4.0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (ARIES-1589) Blueprint-maven-plugin does not handle service reference filter correctly
[ https://issues.apache.org/jira/browse/ARIES-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominik Przybysz reassigned ARIES-1589: --- Assignee: Dominik Przybysz > Blueprint-maven-plugin does not handle service reference filter correctly > - > > Key: ARIES-1589 > URL: https://issues.apache.org/jira/browse/ARIES-1589 > Project: Aries > Issue Type: Bug > Components: Blueprint >Affects Versions: blueprint-maven-plugin-1.4.0 >Reporter: Charlie Mordant >Assignee: Dominik Przybysz > Original Estimate: 24h > Remaining Estimate: 24h > > When trying to reference a filtered service with pax-cdi-api annotation i.e.: > [code] > @OsgiService(filter="(component-type=jmsXA)") > private ConnectionFactory connectionFactory > [/code] > The generated blueprint adds the filter as a 'component-name' attribute > instead of filling the 'filter' attribute. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ARIES-1589) Blueprint-maven-plugin does not handle service reference filter correctly
[ https://issues.apache.org/jira/browse/ARIES-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominik Przybysz resolved ARIES-1589. - Resolution: Works for Me > Blueprint-maven-plugin does not handle service reference filter correctly > - > > Key: ARIES-1589 > URL: https://issues.apache.org/jira/browse/ARIES-1589 > Project: Aries > Issue Type: Bug > Components: Blueprint >Affects Versions: blueprint-maven-plugin-1.4.0 >Reporter: Charlie Mordant >Assignee: Dominik Przybysz > Original Estimate: 24h > Remaining Estimate: 24h > > When trying to reference a filtered service with pax-cdi-api annotation i.e.: > [code] > @OsgiService(filter="(component-type=jmsXA)") > private ConnectionFactory connectionFactory > [/code] > The generated blueprint adds the filter as a 'component-name' attribute > instead of filling the 'filter' attribute. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ARIES-1589) Blueprint-maven-plugin does not handle service reference filter correctly
[ https://issues.apache.org/jira/browse/ARIES-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411755#comment-15411755 ] Dominik Przybysz commented on ARIES-1589: - I have checked it on blueprint-maven-plugin in version 1.4.0: I have field: [code] @OsgiService(filter="(component-type=jmsXA)") @Inject private ConnectionFactory connectionFactory; [/code] and in generated blueprint I have [code] [/code] and [code] [/code] You have missed @Inject annotation. Maybe you have defined this service without parentheses in another bean? Then component-name could be used. > Blueprint-maven-plugin does not handle service reference filter correctly > - > > Key: ARIES-1589 > URL: https://issues.apache.org/jira/browse/ARIES-1589 > Project: Aries > Issue Type: Bug > Components: Blueprint >Affects Versions: blueprint-maven-plugin-1.4.0 >Reporter: Charlie Mordant > Original Estimate: 24h > Remaining Estimate: 24h > > When trying to reference a filtered service with pax-cdi-api annotation i.e.: > [code] > @OsgiService(filter="(component-type=jmsXA)") > private ConnectionFactory connectionFactory > [/code] > The generated blueprint adds the filter as a 'component-name' attribute > instead of filling the 'filter' attribute. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ARIES-1589) Blueprint-maven-plugin does not handle service reference filter correctly
Charlie Mordant created ARIES-1589: -- Summary: Blueprint-maven-plugin does not handle service reference filter correctly Key: ARIES-1589 URL: https://issues.apache.org/jira/browse/ARIES-1589 Project: Aries Issue Type: Bug Components: Blueprint Affects Versions: blueprint-maven-plugin-1.4.0 Reporter: Charlie Mordant When trying to reference a filtered service with pax-cdi-api annotation i.e.: [code] @OsgiService(filter="(component-type=jmsXA)") private ConnectionFactory connectionFactory [/code] The generated blueprint adds the filter as a 'component-name' attribute instead of filling the 'filter' attribute. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
