[
https://issues.jboss.org/browse/WFLY-557?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler resolved WFLY-557.
---------------------------------
Resolution: Won't Fix
Won't Fix - OSGi is going to get removed
Complete support for Bundle update
----------------------------------
Key: WFLY-557
URL:
https://issues.jboss.org/browse/WFLY-557
Project: WildFly
Issue Type: Sub-task
Components: OSGi, Server
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 9.0.0.CR1
A Bundle can have multiple revisions. A call to Bundle.update(…) creates a new revision.
There is only ever one current revision (the latest update) associated with a Bundle.
Stale revisions continue to exist in the runtime until an explicit refresh of the
transitive dependency graph.
Approach #1 - bundle revisions are represented as individual deployments
Each bundle update deploys the revision as a new deployment
The association of revisions to bundle happens in the OSGi layer only
Management sees disconnected deployments with no notion of stale/current or belonging
together
Approach #2 - deployment API supports the notion of multiple revisions
deployments, their revisions and respective mapping would be modelled more closely on
OSGi requirements
some deployment types might not support revisions
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira