Dunno about older versions of felix, but 3.0.1 doesn't have the org.osgi.framework.system.packages already listed out in the config.properties. So it wouldn't just be a case of commenting out a few pre-existing lines of config. Instead the user would have to copy a valid org.osgi.framework.system.packages setting from somewhere else (e.g. the SMX version).
Cheers, Eoghan On 28 June 2010 20:25, Sergey Beryozkin <sberyoz...@gmail.com> wrote: > I'd probably prefer updating the documentation and asking users to remove > the jaxws related entry in their own 1.6-related part of the config. They > will be appending the DOSGI fragment anyway and asking them to replace the > 1.6 related part (which already exists in their config) with what DOSGI RI > ships might be an extra hassle IMHO... > > cheers, Sergey > > > > > > A more long-term option might to ship an entire distro of karaf with > dOSGi, > > customized with some extra features in the internal system repo (that's > the > > approach I'm taking on another project that builds a CLI atop karaf, > works > > quite neatly with the features-maven-plugin to populate the internal > repo). > > The nice thing is that this is guaranteed to work out of the box, with > all > > external dependencies already resolved and all the versions lined up. > Makes > > the distro just a tad bigger tho' ;) > > > > Cheers, > > Eoghan > > > > On 28 June 2010 18:19, Sergey Beryozkin <sberyoz...@gmail.com> wrote: > > > > > Hi Eoghan > > > > > > ServiceMix is shipping the config.properties and they may be specific > to > > a > > > specific Felix version ? Similarly for Equinox (even though most of the > > > config.properties are probably reusable across diff versions) > > > DOSGI RI does only ship the fragments of config properties which are > > built > > > during the multi-bundle build... > > > > > > I'm just curious, why was the CXF import updated to include 0.0.0 ? > > > > > > cheers, Sergey > > > > > > > > > On Mon, Jun 28, 2010 at 5:55 PM, Eoghan Glynn <eogl...@gmail.com> > wrote: > > > > > > > Have you tried overriding the org.osgi.framework.system.packages > > property > > > > in > > > > felix/conf/config.properties, with a list of packages specifically > > > > excluding > > > > javax.xml.ws.*? > > > > > > > > This is the approach taken by SMX to get around these sort of issues. > > See > > > > for ex: > > > > > > > > wget > > > > > > > > > > > > > > https://www.apache.org/dist/servicemix/servicemix-4/4.2.0/apache-servicemix-4.2.0.tar.gz > > > > tar -xvzf apache-servicemix-4.2.0.tar.gz > > > > less apache-servicemix-4.2.0/etc/config.properties > > > > > > > > Note the packages in the jre-1.6 list that are specifically commented > > to > > > > avoid a 0.0.0.0 version dragged in from the system bundle upsetting > > > > version-constrained imports. > > > > > > > > Cheers, > > > > Eoghan > > > > > > > > On 28 June 2010 10:34, David Bosschaert <david.bosscha...@gmail.com> > > > > wrote: > > > > > > > > > Hi Sergey, > > > > > > > > > > I tried your patch on my machine and can confirm that it seems to > > > > > consistently hang in the multibundle system test. This wasn't the > > case > > > > > before. > > > > > > > > > > The good news is that it's hanging because the multi-bundle distro > is > > > > > actually broken - it's so good to have tests :) > > > > > > > > > > I just tried it manually with Felix 3.0.1 and it tells me this > > > > > org.apache.felix.framework.resolver.ResolveException: Constraint > > > > > violation for package 'javax.xml.ws' when resolving module 7.0 > > between > > > > > existing import 13.0.javax.xml.ws BLAMED ON [[7.0] package; > > > > > (&(package=javax.xml.ws)(version>=2.1.0))] and uses constraint > > > > > 0.javax.xml.ws BLAMED ON [[7.0] package; > > > > > (&(package=org.apache.cxf.jaxrs.provider)(version>=2.2.0)), [17.0] > > > > > package; (&(package=javax.xml.ws > > )(version>=0.0.0)(!(version>=3.0.0)))] > > > > > > > > > > Cheers, > > > > > > > > > > David > > > > > > > > > > g! lb > > > > > START LEVEL 85 > > > > > ID|State |Level|Name > > > > > 0|Active | 0|System Bundle (3.0.1) > > > > > 1|Active | 1|Apache Felix Bundle Repository (1.6.2) > > > > > 2|Active | 1|Apache Felix Gogo Command (0.6.0) > > > > > 3|Active | 1|Apache Felix Gogo Runtime (0.6.0) > > > > > 4|Active | 1|Apache Felix Gogo Shell (0.6.0) > > > > > 5|Active | 85|CXF dOSGi Topology Manager (1.2.0.SNAPSHOT) > > > > > 6|Active | 53|geronimo-javamail_1.4_spec (1.2.0) > > > > > 7|Installed | 84|CXF dOSGi Remote Service Admin > Implementation > > > > > (1.2.0.SNA > > > > > PSHOT) > > > > > 8|Active | 52|geronimo-activation_1.1_spec (1.0.2) > > > > > 9|Active | 83|CXF Local Discovery Service Bundle > > > > (1.2.0.SNAPSHOT) > > > > > 10|Active | 51|geronimo-annotation_1.0_spec (1.1.1) > > > > > 11|Active | 82|Apache ServiceMix Specs :: JSR311 API 1.0 > > > (1.3.0) > > > > > 12|Active | 50|osgi.compendium (4.1.0.build-200702212030) > > > > > 13|Active | 81|Apache ServiceMix Specs :: JAXWS API 2.1 > > (1.3.0) > > > > > 14|Active | 80|Apache ServiceMix Specs :: JAXB API 2.1 > > (1.3.0) > > > > > 15|Active | 79|Apache ServiceMix Specs :: STAX API 1.0 > > (1.3.0) > > > > > 16|Active | 78|Apache ServiceMix Specs :: SAAJ API 1.3 > > (1.3.0) > > > > > 17|Active | 77|Apache CXF Minimal Bundle Jar (2.2.9) > > > > > 18|Active | 76|Apache ServiceMix Bundles: > commons-pool-1.5.4 > > > > > (1.5.4.1) > > > > > 19|Active | 75|Apache ServiceMix Bundles: woodstox-3.2.7 > > > > (3.2.7.1) > > > > > 20|Active | 74|Apache ServiceMix Bundles: neethi-2.0.4 > > > (2.0.4.1) > > > > > 21|Active | 73|Apache ServiceMix Bundles: xmlresolver-1.2 > > > > (1.2.0.1) > > > > > 22|Active | 72|Apache ServiceMix Bundles: asm-2.2.3 > (2.2.3.1) > > > > > 23|Active | 71|Apache ServiceMix Bundles: xmlschema-1.4.3 > > > > (1.4.3.1) > > > > > 24|Active | 70|Apache ServiceMix Bundles: xmlsec-1.3.0 > > > (1.3.0.1) > > > > > 25|Active | 69|Apache ServiceMix Bundles: wsdl4j-1.6.1 > > > (1.6.1.1) > > > > > 26|Active | 68|Apache ServiceMix Bundles: jaxb-impl-2.1.6 > > > > (2.1.6.1) > > > > > 27|Active | 67|OPS4J Pax Web - Service (0.5.1) > > > > > 28|Active | 66|spring-osgi-extender (1.2.0) > > > > > 29|Active | 65|spring-osgi-core (1.2.0) > > > > > 30|Active | 64|spring-osgi-io (1.2.0) > > > > > 31|Active | 63|Spring AOP (2.5.6) > > > > > 32|Resolved | 62|SLF4J Jakarta Commons Logging Binding > (1.5.10) > > > > > 33|Active | 61|SLF4J API (1.5.10) > > > > > 34|Active | 60|AOP Alliance API (1.0.0) > > > > > 35|Active | 59|Spring Context (2.5.6) > > > > > 36|Active | 58|Spring Beans (2.5.6) > > > > > 37|Active | 57|Spring Core (2.5.6) > > > > > 38|Active | 56|JDOM DOM Processor (1.0.0) > > > > > 39|Active | 55|Apache Commons Logging (1.1.1) > > > > > 40|Active | 54|geronimo-ws-metadata_2.0_spec (1.1.2) > > > > > g! start 7 > > > > > RE: org.apache.felix.framework.resolver.ResolveException: > Constraint > > > > > violation f > > > > > or package 'javax.xml.ws' when resolving module 7.0 between > existing > > > > > import 13.0 > > > > > .javax.xml.ws BLAMED ON [[7.0] package; (&(package=javax.xml.ws > > > > > )(version>=2.1.0) > > > > > )] and uses constraint 0.javax.xml.ws BLAMED ON [[7.0] package; > > > > > (&(package=org.a > > > > > pache.cxf.jaxrs.provider)(version>=2.2.0)), [17.0] package; > > > > > (&(package=javax.xml > > > > > .ws)(version>=0.0.0)(!(version>=3.0.0)))] > > > > > org.osgi.framework.BundleException: Constraint violation for > package > > > > > 'javax.xml. > > > > > ws' when resolving module 7.0 between existing import > > > > 13.0.javax.xml.wsBLAMED O > > > > > N [[7.0] package; (&(package=javax.xml.ws)(version>=2.1.0))] and > > uses > > > > > constraint > > > > > 0.javax.xml.ws BLAMED ON [[7.0] package; > > > > > (&(package=org.apache.cxf.jaxrs.provid > > > > > er)(version>=2.2.0)), [17.0] package; (&(package=javax.xml.ws > > > > > )(version>=0.0.0)(! > > > > > (version>=3.0.0)))] > > > > > > > > > > On 26 June 2010 17:19, Sergey Beryozkin <sberyoz...@gmail.com> > > wrote: > > > > > > Hi > > > > > > > > > > > > I've attached a patch to [1] which I've tried locally, things > looks > > > ok > > > > > after > > > > > > updating to 2.2.9, i.e, I run two demos manually, greeter & > > > > greeter_rest, > > > > > > > > > > > > but the build itself is hanging in systests2/multi bundle tests. > > > > > > > > > > > > Can someone please try the patch as well and confirm it's > building > > ok > > > > or > > > > > > hanging ? DOSGI 1.1 uses 2.5 and moving to 2.2.9 need to be done > > IMHO > > > > > > > > > > > > cheers, Sergey > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/DOSGI-74 > > > > > > > > > > > > > > > > > > > > >
