common logging jar conflict with apache axis soap client

java axis2
Maneesh Kumar picture Maneesh Kumar · Feb 27, 2012 · Viewed 16.7k times · Source

I am getting this exception while trying to call SOAP webservice using axis. basically I have written a axis client.

org.apache.commons.discovery.DiscoveryException: Class org.apache.commons.logging.impl.SLF4JLogFactory does not implement org.apache.commons.logging.LogFactory.

When I remove the all the common-logging jars, I would able to remove these errors but these jars are coming from other apis, i dont have control on them.

Is there any way to overcome this problem?

Answer

sbridges picture sbridges · Feb 27, 2012

There is a pretty detailed explanation of what the issue may be and ways to debug it in the commons logging documentation. Your particular issue may be,

There is also another more unusual way in which this cast can fail: even when the binary is compatible, the implementation class loaded at runtime may be linked to a different instance of the LogFactory class. For more information, see the tech guide.

Related questions

Content is not allowed in Prolog SAXParserException

I am trying to call a web service but facing a strange behavior. we have a web-service running on my server but the code is not open to us so can not see what going on behind the wall The …

Read More
ORA-12516, TNS:listener could not find available handler

My error: java.sql.SQLException: Listener refused the connection with the following error: ORA-12516, TNS:listener could not find available handler with matching protocol stack The Connection descriptor used by the client was: //10.2.5.21:9001/XE at oracle.jdbc.driver.DatabaseError.throwSqlException(…

Read More
How do you Change a Package's Log Level using Log4j?

I've encountered the following bug: http://issues.apache.org/jira/browse/AXIS2-4363 It states the following: This error only occurs when log level for org.apache.axiom is DEBUG so a workaround is to set log level > DEBUG. …

Read More