FWIW, currently if the deployment.mf is provided in the archive, it has to be transitively closed, i.e. the resolver is not called at all. The list of bundles to be installed comes either from the deployment manifest or the resolver at the moment.
On Tue, Feb 16, 2010 at 17:12, David Bosschaert <[email protected]> wrote: > On 16 February 2010 13:28, Alasdair Nottingham <[email protected]> wrote: >> So the Application-Content in the Application.mf is isolated content, >> but the Deployment.mf contains additional shared bundles that are >> required to support the application. >> >> What do you think? >> Alasdair > > So this allows one to describe the transitive closure of all the > dependencies without forcing them all into the application. Maybe some > of the shareable dependencies are already there in your framework, in > which case they're ignored from the Deployment.mf file, right? > This sounds like a very useful approach to me, especially if you put > everything in a single .zip file - like the .eba. Just download the > .eba, install and your done. > > Although I also think that in some deployments the Deployment.mf file > may not be required as all the transitive dependencies could be > resolved from OBR (I know - OBR doesn't really exist yet, but > hopefully it will soon). If your system is hooked up to an OBR, the > dependencies from your application could be resolved from there. > I guess it depends on how dynamic you want your deployment to be, but > to me these are both valid scenarios... > > Best regards, > > David > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
