[
https://issues.apache.org/jira/browse/FELIX-4066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Schurman updated FELIX-4066:
-----------------------------------
Attachment: example.tar.gz
Attached an example project which exposes the problem. Use
mvn verify
to create the bundles and an OBR repo using maven-bundle-plugin and spin up a
felix instance for testing. Use
obr:deploy importer
in felix to show the resolution problem. You can use
mvn verify -Pfix
with the same felix command if you want to run with a possible workaround
described below.
I believe (1) should be fixed by exposing all interfaces in the manifest
Export-Service tag instead of just the first. As for (2), one possible fix
would be to add the bean id of each service as an attribute to the
Export-Service tag. Removing the comp-name attribute from the importer may fix
the resolution issue in OBR, but may cause runtime errors when blueprint tries
to wire in services.
> Unable to load blueprint augmented jars with OBR
> ------------------------------------------------
>
> Key: FELIX-4066
> URL: https://issues.apache.org/jira/browse/FELIX-4066
> Project: Felix
> Issue Type: Bug
> Components: Bundle Repository (OBR), Manifest Generator (mangen),
> Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.3.7
> Reporter: Andrew Schurman
> Attachments: example.tar.gz
>
>
> There appear to be 2 somewhat related issues regarding consuming blueprint
> augmented bundles in OBR. Both stem from the generated manifest:
> 1) when exporting a service bean with 2 or more interfaces, only the first is
> exposed in the manifest
> 2) when importing a service via interface and component-name, you never find
> the service as the component-name is never exposed on the exporting side
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
