> I use castor to generate the xml file and convert into a byte array and
> make a call to a remote service using axis. Now the webservice tries to
[quoted text clipped - 3 lines]
> But when I try to unmarshall the byte array, I get the
> following error
[...]
> java.lang.ExceptionInInitializerError
> at
> org.exolab.castor.xml.Unmarshaller.initConfig(Unmarshaller.java:272)
> at
> org.exolab.castor.xml.Unmarshaller.<init>(Unmarshaller.java:225)
> at
A variable initializer of class org.exolab.castor.xml.Unmarshaller threw
an exception. Specifically:
[...]
> Caused by: org.apache.commons.logging.LogConfigurationException:
> org.apache.comm
[quoted text clipped - 10 lines]
> Impl.java:272)
> at
[...]
Since it seems exceedingly unlikely that one of the Commons Logging's
own loggers would fail to implement its Log interface, the most likely
scenario is multiple versions of the Commons Logging package in the
classpath. This sort of thing sometimes happens when an application or
package, such as Axis, Castor, or Tomcat comes packaged with various
external libraries, such as Commons Logging. It is possible for
multiple versions of the same package to coexist peacefully, but it is
necessary to exercise some care to get it right. In short, look into
the server configuration.

Signature
John Bollinger
jobollin@indiana.edu
Ravi M - 29 Apr 2005 19:38 GMT
Hi John,
Thank you very much for reply. I forgot to remove the
commons-loging.jar that comes with axis, thus had two versions of
commons-loging.jar in both tomcat/lib and
tomcat/webapps/axis/web-inf/lib. Once I remove the commons-logging.jar
from the tomcat/webapps/axis/web-inf/lib it worked.
Thanks again.
Ravi
> > I use castor to generate the xml file and convert into a byte array and
> > make a call to a remote service using axis. Now the webservice tries to
[quoted text clipped - 8 lines]
> > java.lang.ExceptionInInitializerError
> > at
org.exolab.castor.xml.Unmarshaller.initConfig(Unmarshaller.java:272)
> > at
> > org.exolab.castor.xml.Unmarshaller.<init>(Unmarshaller.java:225)
[quoted text clipped - 13 lines]
> > t Log
> > at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactory
> > Impl.java:532)
> > at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance
> > (LogFactory
> > Impl.java:272)
[quoted text clipped - 3 lines]
>
> Since it seems exceedingly unlikely that one of the Commons Logging's
> own loggers would fail to implement its Log interface, the most likely
> scenario is multiple versions of the Commons Logging package in the
[quoted text clipped - 3 lines]
> multiple versions of the same package to coexist peacefully, but it is
> necessary to exercise some care to get it right. In short, look into
> the server configuration.
Ravi M - 29 Apr 2005 20:00 GMT
Hi John,
Thank you very much for reply. I forgot to remove the
commons-loging.jar that comes with axis, thus had two versions of
commons-loging.jar in both tomcat/lib and
tomcat/webapps/axis/web-inf/lib. Once I remove the commons-logging.jar
from the tomcat/webapps/axis/web-inf/lib it worked.
Thanks again.
Ravi
> > I use castor to generate the xml file and convert into a byte array and
> > make a call to a remote service using axis. Now the webservice tries to
[quoted text clipped - 8 lines]
> > java.lang.ExceptionInInitializerError
> > at
org.exolab.castor.xml.Unmarshaller.initConfig(Unmarshaller.java:272)
> > at
> > org.exolab.castor.xml.Unmarshaller.<init>(Unmarshaller.java:225)
[quoted text clipped - 13 lines]
> > t Log
> > at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactory
> > Impl.java:532)
> > at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance
> > (LogFactory
> > Impl.java:272)
[quoted text clipped - 3 lines]
>
> Since it seems exceedingly unlikely that one of the Commons Logging's
> own loggers would fail to implement its Log interface, the most likely
> scenario is multiple versions of the Commons Logging package in the
[quoted text clipped - 3 lines]
> multiple versions of the same package to coexist peacefully, but it is
> necessary to exercise some care to get it right. In short, look into
> the server configuration.