2009/9/4 Guillaume Nodet <gno...@gmail.com> > Right, and you can do that already. > There is obr url handler [1] that can be installed in OSGi, so that you > could write a features file with: > <bundle>obr:activemq-core/5.2.0</bundle> > > There are two real problems I have with OBR. > The first one is that those repository descriptors are *huge*. Here is a > list of existing repositories for example: > http://www.osgi.org/repository/repository.xml > http://www.knopflerfish.org/repo/bindex.xml > http://sigil.codecauldron.org/spring-external.obr > http://download.eclipse.org/releases/ganymede/repository.zip > http://dz.prosyst.com/pdoc/repository.xml > http://sigil.codecauldron.org/spring-release.obr > > The spring-external repository is more than 5Mb to download. And you need > to parse this xml ! > > The other problem is that locations in those descriptors are usually > absolute locations, thus you need to have access to the internet to be able > to leverage those (unless you want to rewrite them all). This means that > some companies can't use them at all.
or you could use a local repository manager (like Nexus) to cache the OBR content as it's requested and rewrite the descriptors so they use the locally cached bundles - that's what we do in Nexus Pro, and it solves a lot of the performance issues > We therefore usually use maven style > urls, where you can actually change the maven repositories list in > etc/org.ops4j.pax.url.mvn.cfg, which means you can point to an internal > repository easily. > which is actually very similar to OBR, it's just a different form of metadata - in fact there's no reason why you can't have many small OBR files which are referenced from a top-level OBR, it's just that most people use a single index file. Those two things lead me to think that OBR is just unusable at runtime > (though it could really help at dev time with the right tools). This lead > the path to the so called "features" in karaf. > the OBR spec is being updated so this might improve, but even so I still think the current OBR format is perfectly usable at runtime if you use a local/internal server (this is effectively what you're doing with the maven urls and an internal repository) [1] http://wiki.ops4j.org/display/paxurl/Obr+Protocol > > On Fri, Sep 4, 2009 at 15:58, J Aaron Farr <fa...@apache.org> wrote: > > > > > On Fri 04 Sep 2009 21:38, Guillaume Nodet <gno...@gmail.com> wrote: > > > > > There are multiple solutions to this problem, but the easiest one is to > > make > > > sure that the system bundle does not export those packages. > > > That's what i've done at [2] where you can see that the > javax.transaction > > > packages are commented, thus not exported. > > > > > > Hopes this help! > > > > It does. I figured someone was working on updating the > > features/bundles, but I thought my notes might help. > > > > Speaking of making this simpler, while I really like the karaf > > "features" feature, shouldn't this sort of install be possible via OBR? > > That is, I install/activate the activemq bundle and OBR takes care of > > the rest? > > > > I've been out of osgi development for almost 2 years, so I'm still > > getting back up to speed on what's changed. > > > > -- > > J. Aaron Farr > > 馮傑仁 > > www.cubiclemuses.com > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@felix.apache.org > > For additional commands, e-mail: users-h...@felix.apache.org > > > > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com > -- Cheers, Stuart
