Hi Bruno, I put together an example [1] how to embed Qpid broker-j without logback dependencies (It depends on log4j2). Logback broker loggers are completely optional. In order to avoid any Qpid logback dependency, you just need to add into your project a dependency to qpid-broker-core and any other required modules. Please check [2] for more details.
Kind Regards, Alex [1] https://github.com/alex-rufous/embedded-qpid-broker-j [2] https://cwiki.apache.org/confluence/display/qpid/How+to+embed+Qpid+Broker-J On Wed, 5 Feb 2020 at 19:40, queimadus <[email protected]> wrote: > Hi, I'm trying to use qpid-broker as an embedded broker for tests. > > Our project uses `log4j2` for logging and `log4j-slf4j-impl` for `slf4j` > compatibility, which clashes with the provided logback-classic. > I've tried to use `qpid-broker-core` and not use the > `qpid-broker-plugins-logging-logback` plugin in a effort to drop the > `logback-classic` dependency. > Unfortunately, doing that results in a exception: > `org.apache.qpid.server.model.NoFactoryForCategoryException: Unknown > category: BrokerLogger`. > > My question is: even if I don't defined any logger in the config, do I > still > need `BrokerLogger` implementations? A > `qpid-broker-plugins-logging-log4j2` > of sorts? Ideally, I'd like to consume the logs directly via the `slf4j` > interface or drop the logs altogether if the solution is easier. > > Thanks, > Bruno > > > > -- > Sent from: > http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
