As given by the explanation this happens because both qpid-client and the HelloWorld app expose slf4j configuration. I don't think we can avoid slf4j config in qpid-client because qpid-client still uses in other products. Further as explained this warning is harmless and slf4j will still bind to a one of the logging configurations.
Rajika On Wed, Apr 27, 2011 at 6:01 PM, Afkham Azeez <az...@wso2.com> wrote: > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in > [jar:file:/Users/azeez/projects/wso2/org/trunk/carbon/products/appserver/modules/distribution/product/target/wso2appserver-4.1.0-SNAPSHOT/lib/core/WEB-INF/lib/qpid-client-0.11.0.wso2v1.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in > [jar:file:/Users/azeez/projects/wso2/org/trunk/carbon/products/appserver/modules/distribution/product/target/wso2appserver-4.1.0-SNAPSHOT/lib/tomcat/work/Tomcat/defaulthost/HelloWorld-1.3.7/WEB-INF/lib/slf4j-log4j12-1.5.8.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > explanation. > > > -- > *Afkham Azeez* > Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, > * > * > *Member; Apache Software Foundation; > **http://www.apache.org/*<http://www.apache.org/> > * > email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 > blog: **http://blog.afkham.org* <http://blog.afkham.org>* > twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> > * > linked-in: **http://lk.linkedin.com/in/afkhamazeez* > * > * > *Lean . Enterprise . Middleware* > > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
