[ 
https://issues.apache.org/jira/browse/QPID-7747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974133#comment-15974133
 ] 

Tomas Klimavicius edited comment on QPID-7747 at 4/19/17 6:04 AM:
------------------------------------------------------------------

Thanks [~alex.rufous], the example works. Since logback dependency is done by 
design for qpid-broker then the ticket can be closed.
And maybe [~alex.rufous] can give an exmaple of how to disable secure only 
mechanisms as documented 
[here|https://qpid.apache.org/releases/qpid-java-6.0.2/java-broker/book/Java-Broker-Security.html#Java-Broker-Security-Authentication-Providers]
 in the fully programmatic config approach? 


was (Author: tomasklimavicius):
Thanks [~alex.rufous], the example works. Since logback dependency is done by 
design for qpid-broker then the ticket can be closed.
And maybe [~alex.rufous] can give an exmaple of how to disable secure only 
mechanisms as documented 
[Here|https://qpid.apache.org/releases/qpid-java-6.0.2/java-broker/book/Java-Broker-Security.html#Java-Broker-Security-Authentication-Providers]
 in the programmatic approach? 

> 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
>         Attachments: embedded-broker-example.tar.gz
>
>
> 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]

Reply via email to