[
https://issues.apache.org/jira/browse/DOSGI-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15490202#comment-15490202
]
Christian Schneider commented on DOSGI-155:
-------------------------------------------
I think the reason why equinox works without the config is that they delegate
all class loading to the boot classloader as a fallback.
Btw. I was able to run the SOAP and RS examples using bndrun and only needed
these configs:
org.osgi.framework.bootdelegation=com.sun.*,\
org.osgi.framework.system.packages.extra='sun.misc,javax.xml.bind.annotation;version=2.2.1,javax.xml.bind;version=2.2.1'
This is not directly applicable to the multi bundle distro though as bndtools
resolves different bundles.
In mid term I plan to deprecate the mutli bundle distro and instead recommend
to use bndtools for non karaf purposes.
This does not help for eclipse RCP though. So I hope we can provide a distro
for RCP too - maybe in the form of a p2 repo and feature. I am not sure how
important this is though as I only know one of our customers who uses CXF in
Eclipse RCP.
> Felix Multi-Bundle distro should not set org.osgi.framework.system.packages
> property
> ------------------------------------------------------------------------------------
>
> Key: DOSGI-155
> URL: https://issues.apache.org/jira/browse/DOSGI-155
> Project: CXF Distributed OSGi
> Issue Type: Bug
> Components: Product
> Affects Versions: 1.4.0
> Reporter: David Bosschaert
> Priority: Minor
>
> The multi-bundle distribution contains 2 felix configuration files:
> * conf/felix.config.properties.append
> * conf/felix.discovery.config.properties.append
> Both these files specify the *org.osgi.framework.system.packages* framework
> property:
> {noformat}org.osgi.framework.system.packages=org.osgi.framework;
> version=1.5.0, \
> org.osgi.framework.launch; version=1.0.0, \
> org.osgi.framework.hooks.service; version=1.0.0, \
> org.osgi.service.packageadmin; version=1.2.0, \
> org.osgi.service.startlevel; version=1.1.0, \
> org.osgi.service.url; version=1.0.0, \
> org.osgi.util.tracker; version=1.4.0, \
> org.apache.karaf.jaas.boot; version=2.2.9, \
> org.apache.karaf.version; version=2.2.9, \
> javax.crypto, \
> javax.crypto.spec, \
> {noformat}
> and so on...
> This property should really be left specified by the framework itself as its
> value will depend on the version of the OSGi framework and the Java runtime
> used. The values specified are very likely incorrect in a number of cases
> (for example if you use the latest version of Felix, the org.osgi.* values
> are incomplete and the versions incorrect).
> It looks like the main thing here is to add the *org.apache.karaf* packages
> to the framework packages. This should really be done via the
> *org.osgi.framework.system.packages.extra* property, without specifying any
> of the packages provided by the framework or the JRE. E.g.
> {noformat}org.osgi.framework.system.packages.extra=\
> org.apache.karaf.jaas.boot; version=2.2.9, \
> org.apache.karaf.version; version=2.2.9{noformat}
> I briefly tried this but it seems there is an issue with resolving the
> javax.xml.stream package, and I noticed that in the current configuration it
> was actually removed from the list.
> So in order to fix this situation some work will need to be done make sure
> that the default value of the *org.osgi.framework.system.packages* property
> will work.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
