[
https://issues.apache.org/jira/browse/FELIX-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed FELIX-217.
-----------------------------------
Resolution: Won't Fix
Discussion on this issue took place but the implementation has stuck. Moreover,
this project is currently part of the newly incubating Apache Sling project.
Finally, it is probably even dead end given the addition of the Deployment
Package Service Specification in R 4.1 of the Compendium Specs.
Therefore, I close this bug as won't fix and suggest we write it off.
> Assembly Bundle
> ---------------
>
> Key: FELIX-217
> URL: https://issues.apache.org/jira/browse/FELIX-217
> Project: Felix
> Issue Type: New Feature
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Priority: Trivial
> Attachments: assembly.jar
>
>
> There are different threads on the dev list, which discuss around installing
> bundles of bundles ([1], [2]). In this discussion, I presented the ideas
> behind a bundle we built to manage the installation/update of a new system we
> are building. To show more, how it is being done, I attach the code for this
> bundle here. I put it under ASL 2 and would also agree to add it to Felix as
> a contribution.
> The goals behind this bundle are:
> (1) In our system, we have potentially more than one source of
> installation/upgrade order. So we had to find a solution of making these
> processes thread safe in a sense, that another thread should not
> install/update/remove bundles while another thread is for example trying to
> deploy bundles through OBR. This is solved by having an InstallerService,
> which should be used instead of directly doing BundleContext.installBundle,
> etc.
> (2) Likewise we had to "serialize" uses of the OBR, which is also solved by
> the InstallerService mentioned above.
> (3) We defined the Assembly Bundle, which defines a set of bundles to be
> installed together.
> Any comments here or on the list are very welcome.
> [1] http://www.mail-archive.com/[EMAIL PROTECTED]/msg03809.html
> [2] http://www.mail-archive.com/[EMAIL PROTECTED]/msg04005.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.