Yeah, maybe we need to tidy up the terminology a bit and come to agreement on that, I think Guillaume's clarification helps.
In my opinion it would be nice if Aries could provide both models. The shared subsystem building block one as well as the more isolated application one. Since I tend to think about Applications as a specialization of a subsystem it should be possible to do this quite naturally. Just my thoughts, David On 15 February 2010 22:21, Guillaume Nodet <[email protected]> wrote: > Are you talking about nested framework instead of subsystems ? > Subsystems are currently defined by RFC 152 and nested frameworks by RFC 138. > > My understanding is that applications as they stand are meant to be > self-contained (or mostly) and isolated, > whereas subsystems can be considered more as building blocks with > sharing capabilities > > The way applications or subsystems can be isolated could be done using > nested frameworks or manifest rewriting for example. > > On Mon, Feb 15, 2010 at 22:58, David Jencks <[email protected]> wrote: >> >> On Feb 15, 2010, at 1:34 PM, Guillaume Nodet wrote: >> >>> Aries applications model is quite similar to the subsytem model being >>> discussed in the OSGi EEG. >>> I'd like to think that subsytems are more generic than applications, >>> or said another way, that applications >>> are specialization of subsystems. Subsystems allow reference to other >>> subsystems, scoping, etc... >>> >>> I'd like to see how we can make both fits together. I guess the first >>> question to solve it whether we want >>> to keep applications the way they are, without advanced features >>> provided by subsystems such as >>> sharing / scoping, dependencies on other subsytems, etc... >>> >>> Once we've answered that, we can think about the way we want to support >>> both. >>> >>> Thoughts ? >>> >> >> My point of view.... perhaps shared by no one else.... is that an >> application would be deployed or installed into a particular subsystem, but >> that several apps and plain bundles can all be installed into a single >> subsystem. I'm thinking of an application as a way to deploy a set of >> bundles at once, where the "maven-like" dependencies aren't specified, and >> where the framework has a way to resolve the osgi dependencies into >> maven-like dependencies. >> >> I don't think this idea is expressed in the current code in any way. >> >> thanks >> david jencks >> >>> -- >>> Cheers, >>> Guillaume Nodet >>> ------------------------ >>> Blog: http://gnodet.blogspot.com/ >>> ------------------------ >>> Open Source SOA >>> http://fusesource.com >> >> > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com >
