[
https://issues.apache.org/jira/browse/QPID-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Conway resolved QPID-2223.
-------------------------------
Resolution: Not A Problem
> Controlling order of plug-in initialization.
> --------------------------------------------
>
> Key: QPID-2223
> URL: https://issues.apache.org/jira/browse/QPID-2223
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Broker
> Affects Versions: 0.5
> Reporter: Alan Conway
> Assignee: Alan Conway
> Priority: Minor
>
> The specific use case for this is as follows:
> The cluster plug-in needs to know in earlyInitialize whether or not the
> broker has a store so it can correctly advertise itself as
> persistent/transient when joining the cluster.
> The current solution is
> /**
>
> * Initialization order. If a plugin does not override this, it
>
> * returns DEFAULT_INIT_ORDER. Plugins that need to be initialized
>
> * earlier/later than normal can override initOrder to return
>
> * a lower/higher value than DEFAULT_INIT_ORDER.
>
> */
> QPID_COMMON_EXTERN virtual int initOrder() const;
> The cluster plugin sets a higher initOrder so it will initialize after the
> store and can test whether broker.getStore() is a null store.
> This feature was added without sufficient discussion. The goal of this JIRA
> is to determine if there's a better solution that would apply more generally.
> If so we'll implement that instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
