[
http://issues.ops4j.org/browse/QI-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152#action_13152
]
Niclas Hedhman commented on QI-229:
-----------------------------------
Since the Activator class that handles this are used for many different
activation processes involved, it should also check if the Exception throw is
PassivationException, and from that aggregate all in a single
PassivationException, I think.
> Exception in passivate() halts the passivation process.
> -------------------------------------------------------
>
> Key: QI-229
> URL: http://issues.ops4j.org/browse/QI-229
> Project: Qi4j
> Issue Type: Bug
> Affects Versions: 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 1.0
> Reporter: Niclas Hedhman
> Assignee: Niclas Hedhman
> Fix For: 1.0
>
>
> The suggested solution is that passivate() will continue to try and shut down
> the services, and if additional Exceptions occur a special aggregated
> Exception is thrown, otherwise the single occurring Exception is thrown.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev