Hi Christian,

> In both cases a bndrun or similar is necessary. The bndrun file does not only 
> contain the runbundles which is the already resolved list. It also contains 
> the requirements. The minimum thing it would contain in your case is a 
> pointer to your application bundle. In many cases it will contain a list of 
> requirements for bundles and maybe other requirements.

Ok, so taking a different tack…

> The obr index is just the pool of bundles/resources to pick from.

Without reviewing the spec, I’ll take your word for it. :-)

> This part of the bndrun file is the input for the resolver. This is always 
> needed. […] It is the purpose of a feature file or a bndrun file. [...] You 
> need to give the resolver the initial hooks to pull the needed bundles out of 
> this pool.

What I understand from what you write is that the bndrun/feature file (call it 
a “runtime descriptor”?) is also nothing but a list of requirements and 
capabilities. If so, it seems to be essentially the same thing as an obr index: 
a list of resources with requirements and capabilities. The only difference I 
can see is that the obr index is for storing stuff and is ignorant of the 
runtime, while the the runtime descriptor only cares about what is required 
during a runtime, and doesn’t care if it contains all the stored resources or 
not. The contents otherwise seem very similar, if not identical.

Sounds like two different views on the same thing, maybe.

Or perhaps the features.xml file is itself nothing but a resource (having 
requirements and capabilities) that could be expressed in an obr index.


Also, I am still a bit stuck on the fact that the developers are the ones 
expected to create the runtime descriptor. I can understand if they want to 
immediately run something in a local test environment, but otherwise it seems 
to couple the devs to the deployment/runtime. Am I missing something, or is 
this related to the page of the yet-to-be-developers scenario you showed in 
your previous post (reposted below)?

> I have scoped such a scenario a long time ago here:
> http://liquid-reality.de/display/liquid/Software+Development+and+Deployment 
> <http://liquid-reality.de/display/liquid/Software+Development+and+Deployment>

Cheers,
=David


Reply via email to