[
https://issues.apache.org/jira/browse/QPID-7547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall closed QPID-7547.
----------------------------
Resolution: Duplicate
Fixed by QPID-8066
> [Java Broker] Refactor closing and deletion of AbstractConfiguredObjects
> ------------------------------------------------------------------------
>
> Key: QPID-7547
> URL: https://issues.apache.org/jira/browse/QPID-7547
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
> Reporter: Lorenz Quack
> Priority: Major
> Fix For: Future
>
>
> Currently deletion and closing of objects are completely independent.
> It seems reasonable that an object that is being deleted should be closed
> before hand to ensure resources are being cleaned up and to reduce code
> duplication.
> In fact many implementations of ConfiguredObjects already do this.
> This JIRA suggests to do this in a generic way in AbstractConfiguredObject.
> The suggested order would be:
> ACO.deleteAsync
> * calls delete on all children
> * closes itself
> * deletes itself
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
