[
https://issues.apache.org/jira/browse/QPID-7372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorenz Quack updated QPID-7372:
-------------------------------
Description:
Currently the SystemConfig class has a hard dependency on LogBack, and forces
instantiation / resetting the logback config.
To allow for easier embedding of the broker we can move this instantiation out
of the core model and into the code use to bootstrap the broker instance. We
can also move the logback dependent model objects into a separate plugin. In
this way the System Config (and child Broker) will simply use whatever has
been set up for them in slf4j and an embedder of the broker could choose to use
a different logging provider or supply a logback configuration which is not
managed by the broker itself.
was:
Currently the SystemConfig class has a hard dependency on LogBack, and forces
instantiation / resetting the logback config.
To allow for easier embedding of the broker we can move this instantiation out
of the core model and into the code use to bootstrap the broker instance. We
can also move the logback dependent model objects into a separate plugin. In
this way the System Config (and child Broker) will simply use whatever has
been set up for them in slf4j and an embedder of the broker could choose to use
a different logging provider or simply a logback configuration which is not
managed by the broker itself.
> [Java Broker] Remove hard dependency on logback from broker-core
> ----------------------------------------------------------------
>
> Key: QPID-7372
> URL: https://issues.apache.org/jira/browse/QPID-7372
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Rob Godfrey
> Assignee: Rob Godfrey
> Fix For: qpid-java-6.1
>
>
> Currently the SystemConfig class has a hard dependency on LogBack, and forces
> instantiation / resetting the logback config.
> To allow for easier embedding of the broker we can move this instantiation
> out of the core model and into the code use to bootstrap the broker instance.
> We can also move the logback dependent model objects into a separate plugin.
> In this way the System Config (and child Broker) will simply use whatever
> has been set up for them in slf4j and an embedder of the broker could choose
> to use a different logging provider or supply a logback configuration which
> is not managed by the broker itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
