I noticed that an error occurs during jboss startup. A conflict between SL4J (embedded in jboss) and SL4J required by Camel is printed: /2012-04-10 10:05:06,424 ERROR [STDERR] (main) SLF4J: Class path contains multiple SLF4J bindings. 2012-04-10 10:05:06,424 ERROR [STDERR] (main) SLF4J: Found binding in [vfszip:/C:/dev/servers/jboss-5.1.0.GA/common/lib/slf4j-jboss-logging.jar/org/slf4j/impl/StaticLoggerBinder.class] 2012-04-10 10:05:06,424 ERROR [STDERR] (main) SLF4J: Found binding in [vfszip:/C:/dev/servers/jboss-5.1.0.GA/server/all-infosender/deploy/_projects/project1-1.0.0.ear/project1-web-1.0.0.war/WEB-INF/lib/com.springsource.slf4j.log4j-1.6.1.jar/org/slf4j/impl/StaticLoggerBinder.class] 2012-04-10 10:05:06,424 ERROR [STDERR] (main) SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation./
If I remove SL4J (1.6.1 version) from pom.xml Camel is not deployed because it depends on *org.slf4j.impl.StaticLoggerBinder* and this exception is thrown at server startup: / ... Caused by: org.springframework.beans.FatalBeanException: Invalid NamespaceHandler class [org.apache.camel.spring.handler.CamelNamespaceHandler] for namespace [http://camel.apache.org/schema/spring]: problem with handler class file or dependent class; nested exception is java.lang.NoSuchMethodError: org.slf4j.impl.StaticLoggerBinder.getSingleton()Lorg/slf4j/impl/StaticLoggerBinder; at org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.resolve(DefaultNamespaceHandlerResolver.java:139) at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1333) at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1328) at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:135) at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:93) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:493) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:390) ... 83 more Caused by: java.lang.NoSuchMethodError: org.slf4j.impl.StaticLoggerBinder.getSingleton()Lorg/slf4j/impl/StaticLoggerBinder; at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121) at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111) at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:268) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254) at org.apache.camel.spring.handler.CamelNamespaceHandler.<clinit>(CamelNamespaceHandler.java:74) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:126) at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:104)/ I don´t know if these conflicts are related to original post but... who knows?? thanks -- View this message in context: http://camel.465427.n5.nabble.com/Apparent-Duplicated-Log-Log4J-tp5630011p5630138.html Sent from the Camel - Users mailing list archive at Nabble.com.
