[
https://issues.apache.org/jira/browse/QPID-7747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15971121#comment-15971121
]
Lorenz Quack commented on QPID-7747:
------------------------------------
My guess is that you are trying to embed the broker in your Java application
and you are using things from the {{qpid-broker}} module.
This is a relatively thin wrapper that starts up the broker and adds dependency
to logback. This is by design.
For the embedded use case you should not be using {{qpid-broker}}. Instead you
should use classes from {{qpid-broker-core}} which should not depend on logback
(caveat: QPID-7733).
If this does not help please specify how you are trying to use the broker and
where the problems arise.
We know that we need better documentation on how to embed the broker. We just
did not get around to writing it.
I believe [~alex.rufous] might have some example code he might be able to share.
I'll ask him to comment on this JIRA.
> Logging: Depend only on slf4j and remove logback dependencies
> -------------------------------------------------------------
>
> Key: QPID-7747
> URL: https://issues.apache.org/jira/browse/QPID-7747
> Project: Qpid
> Issue Type: Improvement
> Reporter: Tomas Klimavicius
>
> Qpid is depending on logback as it's log implementation, but this makes it
> horrible to use inside projects that already use log4j or slf4j-jdk14.
> It would be much easier for users if the source code would only depened on
> slf4j. Now if we exclude logback and expect qpid to use our provided logger
> the code does not compile since qpid actually depends on logback -
> ch.qos.logback.classic.Logger logger =
> (ch.qos.logback.classic.Logger)LoggerFactory.getLogger("ROOT");
> And if you use something else you get a class cast exception.
> Also slf4j complains on every startup when you have multiple implementations
> in your classpath
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
