[
https://issues.apache.org/jira/browse/FELIX-4184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719605#comment-13719605
]
Marcel Offermans commented on FELIX-4184:
-----------------------------------------
I'm hesitant to go that way Bram, as ultimately it would have to exactly
simulate what the resolver does. In the case I had, it was a uses constraint
that failed. Also, unlike what Jan Willem said, we're currently NOT stopping
any bundles. We leave everything running and invoke update on the active
bundles.
> Temporary resolver errors while updating bundles with deploymentadmin
> ---------------------------------------------------------------------
>
> Key: FELIX-4184
> URL: https://issues.apache.org/jira/browse/FELIX-4184
> Project: Felix
> Issue Type: Bug
> Components: Deployment Admin
> Affects Versions: deploymentadmin-0.9.4
> Reporter: Marcel Offermans
>
> When you use the system property to not stop the world during an update,
> updating a running bundle might cause a (temporary) resolver error (I've seen
> it throw exceptions related to uses constraints). According to the spec, if
> we get an exception here, we should rollback. If you stop the world, this
> never happens, but here such temporary exceptions are probably resolved when
> we refresh packages at the end. That does not happen though, since we never
> get there. We should consider covering this use case, letting the deployment
> continue and deal with errors when resolving (and maybe then rolling back).
--
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
