cxf-dosgi-ri-singlebundle-distribution-1.2.jar does not play well with other
bundles
------------------------------------------------------------------------------------
Key: DOSGI-84
URL: https://issues.apache.org/jira/browse/DOSGI-84
Project: CXF Distributed OSGi
Issue Type: Bug
Affects Versions: 1.2
Reporter: Sven Zethelius
singlebundle is registering OSGI services and listening to the OSGi Service
registry without importing/exporting all the packages involved. The particular
case I ran into is with the org.apache.felix.cm.PersistenceManager services.
When the org.apache.felix.configadmin is included in the OSGi runtime, the
ConfigurationAdminImpl/ConfigurationManager instances created by singlebundle's
felix.configadmin sees the PersistanceManager registered by the external
felix.configadmin.
Setup:
org.eclipse.osgi-3.6.0.v20100517.jar
cxf-dosgi-ri-singlebundle-distribution-1.2.jar
org.apache.felix.configadmin-1.2.4.jar
Other bundles using ConfigurationAdmin interface
Our bundle, via a ServiceTracker ends up using the ConfigurationAdmin service
being provided by singlebundle. A call to ConfigurationAdmin.getConfiguration
triggers a call to look up PersistenceManager instances. The singlebundle's
felix.configadmin is somehow seeing ALL registered instances of
PersistenceManager even though the class loaders are incompatible. It may have
to do with the copy of ServiceTracker included in the felix.configadmin, and
using an old version of the felix.configadmin.
In terms of resolutions:
ConfigurationAdmin was resolved to the external org.apache.felix.configadmin,
and both my bundle and the singlebundle agrees on classloaders, hence why I am
seeing the singlebundle's instance of ConfigurationAdmin
PersistenceManager is split, with the FilePersistenceManager for singlebundle
using singlebundle's definition, and the external felix.configadmin having it's
own.
P.S. You might want to update the Bug form, it shows 1.2 as "Unreleased
Versions" even though its under the release page
http://cxf.apache.org/dosgi-releases.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
