If you are sure that all classes/JARs are there, then it means that some classes are loaded by the wrong class loader in the class loader hierarchy. This is something that is difficult to solve on a mailing list. My recommendations:
1) Start with a fresh server + Axis2 WAR or Axis2 binary distribution, deploy the service and check if it works. 2) Try to familiarize yourself a bit more with how class loading works in Java, especially in the context of an application/Web server. This will help you to understand and debug this kind of problems. Andreas On Thu, Aug 20, 2009 at 04:40, Clara<[email protected]> wrote: > > Hi, > My xmlbeans JAR is located at C:\xmlbeans-2.4.0\lib. I also placed this in > my classpath (CLASSPATH environment variable) but I am still getting the > below error. What could be causing this? > --- On Wed, 8/19/09, Andreas Veithen <[email protected]> wrote: > > From: Andreas Veithen <[email protected]> > Subject: Re: Help! Error when testing Axis2 client > To: [email protected] > Date: Wednesday, August 19, 2009, 11:10 AM > > Which classloader is the xmlbeans JAR loaded from (i.e. where is the > xmlbeans JAR located)? Idem for the TypeSystemHolder class. > > Andreas > > On Wed, Aug 19, 2009 at 11:43, Clara<[email protected]> wrote: >> >> Hi Andreas, >> Thank you for your very helpful response. You are right, my jar files from >> 2 >> different axis2 versions got mixed up. I was using axis2 v1.4 but i used >> axis2.jar of axis2 v1.5. The error was resolved by using axis2 v1.5. >> However, when I tried running my sample client code, I got the below error >> during runtime: >> >> [17:10:23.500] java.lang.ExceptionInInitializerError >> [17:10:23.500] at com.sample.LoginRequestDocument$Factory >> .parse(LoginRequestDocument.java:86) >> [17:10:23.500] at com.sample.Axis2SampleMessageR >> eceiverInOut.fromOM(Axis2SampleMessageReceiverInOut.java:2540) >> . >> . >> . >> [17:10:23.500] Caused by: java.lang.RuntimeException: Cannot load >> SchemaTypeSyst >> em. Unable to load class with name >> schemaorg_apache_xmlbeans.system.s23B9B2646D7 >> 77B890CFC862E67D5196A.TypeSystemHolder. Make sure the generated binary >> files >> are >> on the classpath. >> [17:10:23.500] at >> org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBean >> s.java:783) >> [17:10:23.500] at com.sample.LoginRequestDocument.<clinit >>>(LoginRequestDocument.java:19) >> [17:10:23.500] ... 21 more >> [17:10:23.500] Caused by: java.lang.ClassNotFoundException: >> schemaorg_apache_xml >> beans.system.s23B9B2646D777B890CFC862E67D5196A.TypeSystemHolder >> [17:10:23.500] at >> com.caucho..loader.DynamicClassLoader.loadClass(DynamicClassLo >> ader.java:1133) >> [17:10:23.500] at >> com.caucho.loader.DynamicClassLoader.loadClass(DynamicClassLo >> ader.java:1113) >> [17:10:23.500] at >> org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBean >> s.java:769) >> [17:10:23.500] ... 22 more >> I already placed the schemaorg_apache_xml >> beans.system.s23B9B2646D777B890CFC862E67D5196A.TypeSystemHolder in the >> classpath. Is there something that I might be missing? >> >> thanks, >> >> Clara >> --- On Tue, 8/18/09, Andreas Veithen <[email protected]> wrote: >> >> From: Andreas Veithen <[email protected]> >> Subject: Re: Help! Error when testing Axis2 client >> To: [email protected] >> Date: Tuesday, August 18, 2009, 2:45 AM >> >> This probably means that you have a mix of JARs from different Axis2 >> versions (maybe at different locations in the class loader hierarchy). >> >> Andreas >> >> >> > >
