You might want to have a look at deploymentadmin (in the R4.1 compendium). We have an implementation in trunk (not released yet but works).
I'm sure others have more to say about this topic (I know I do but I don't have the time right now :-). regards, Karl On Thu, Jun 19, 2008 at 6:58 AM, Mark Derricutt <[EMAIL PROTECTED]> wrote: > Hey all, > > I was wondering if anyone has written up any thoughts on best-practices for > deploying apps based on Felix/OSGi and for updating/deploying a set of > bundles? > > Along with some issues withs updating our bundles, I'm trying to work out > the best of automated, or making easier updating a system with multiple > bundles (we only have 5 so far, but its already showing some growing pains > (which could just be misunderstandings on my part)). > > Currently I have a custom Felix launcher that starts a JNDI server outside > of OSGi (Objectweb's Carol) which I was having all manner of pain getting it > to start/stop from a bundle, along with all manner of class loading issues, > but then I also have a block of code in my launcher which installs the 10 or > so bundles we have (5 of our own, 5 standard ones). > > I've had a look at the Felix File-install bundle which worked well, other > than starting bundles in random orders (not really a big issue, but seemed > to annoy some of the devs due to seemingly random changing behaviour). > > I understand the new Spring OSGi server contains some form of "bundle of > bundles" setup (an uber jar), is there anything similar for Felix? > > I think at its core, I think I'm looking for some form of dependency tree in > my bundles, so that when I stop/update bundle X, bundles Y and Z stop, then > restart aswell (and maybe optionally attempt to update themseves as well). > > > I'm almost thinking it'd be easier to rework my app so its pretty much just > one huge uber-bundle, but I like the small bundles... > > Mark > > > > -- > "It is easier to optimize correct code than to correct optimized code." -- > Bill Harlan > -- Karl Pauls [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
