You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (JIRA)" <ji...@apache.org> on 2016/12/07 17:22:58 UTC
[jira] [Resolved] (QPID-7486) [Java Broker] Refactor broker startup
code, remove BrokerOptions
[ https://issues.apache.org/jira/browse/QPID-7486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy resolved QPID-7486.
------------------------------
Resolution: Fixed
I reviewed the changes committed against this JIRA. They look Ok to me but I made a small improvement in [ https://svn.apache.org/r1773056 ] to initialize and upgrade configuration store on activation rather then doing it twice on activation and stop
> [Java Broker] Refactor broker startup code, remove BrokerOptions
> ----------------------------------------------------------------
>
> Key: QPID-7486
> URL: https://issues.apache.org/jira/browse/QPID-7486
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Rob Godfrey
> Assignee: Rob Godfrey
> Fix For: qpid-java-6.2
>
>
> The code relating to the initial construction of the broker has evolved over time leaving functionality spread across a number of different classes with no clear division of responsibilities.
> Refactor so that Main in the broker module has responsibility for parsing of command line arguments and conversion into SystemConfig attributes, as well as providing the hooks into the desired logging provider.
> SystemLauncher (renamed from Broker) provides a thin layer of state management (shutdown/startup) on top of the SystemConfig configured object.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org