I don't think that's a good idea to import the osgi api.
It may lead to problems if multiple blueprint implementations are
deployed for some reason.
To support such a case, the blueprint bundles are supposed to import
the org.osgi.blueprint package iirc, so that the osgi framework wiring
will be
[
https://issues.apache.org/jira/browse/ARIES-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved ARIES-809.
---
Resolution: Fixed
Not possible to configure transaction timeout
[
https://issues.apache.org/jira/browse/ARIES-846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved ARIES-846.
---
Resolution: Fixed
The Aries transaction manager does not recover transactions correctly
[
https://issues.apache.org/jira/browse/ARIES-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved ARIES-663.
---
Resolution: Fixed
Assignee: Guillaume Nodet
ConfigurationAdminMBean registered
I'm otherwise done with all the changes in that branch and they are
all also in trunk now.
On Tue, May 22, 2012 at 12:43 AM, Guillaume Nodet gno...@gmail.com wrote:
I don't think that's a good idea to import the osgi api.
It may lead to problems if multiple blueprint implementations are