A hint. The generated ANT tasks that get created when you use XMLBeans usually do everything necessary.
ADB is getting closer and closer to supporting as much Schema as is feasible. One approach is to identify any schema issues that ADB has with your WSDL and raise JIRAs - you might end up pretty close. The other option is JAXB 2.0 Reference Implementation. That's also a pretty good DB option. Paul On 5/10/07, Edward Bush <[EMAIL PROTECTED]> wrote:
That's not much of a work-around if a person is using Maven to build with. You can't just pause the build in the middle, fix things, and then let it continue ... maybe I can fix it with an ant task in process-sources ... Hey, thanks for helping me find that! I was having no luck! So, which data binding do folks use if they have moderate to complex schema-mapping requirements. My understanding is that ADB isn't the best choice in that case (seems to work _great_ and _easy_ for simple requirements though!), and I'm not sure I want to buy the complexity that I hear comes with JIBX. Thanks again for your help Robert! Eddie Bush Software Analyst Clinical Reference Laboratory bushe at crlcorp dot com ________________________________ From: robert lazarski [mailto:[EMAIL PROTECTED] Sent: Thursday, May 10, 2007 2:13 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] XMLBeans Implementation Seems like you've run into a common problem: http://ws.apache.org/axis2/tools/1_2/CodegenToolReference.html#invoking "An important detail is that an XMLBean class file is also generated by WSDL2Java, TypeSystemHolder.class. That file is placed into build/classes by the above ant task and will be needed to compile the generated sources. A frequent problem is users get an error such as: ClassNotFoundException : Cannot load SchemaTypeSystem. Unable to load class with name schemaorg_apache_xmlbeans.system.s68C41DB812F52C975439BA10FE4FEE54.TypeS ystemHolder. Make sure the generated binary files are on the classpath. The TypeSystemHolder.class generated by WSDL2Java must be placed in your classpath in order to avoid this error." wsdl2java created the class somewhere on your system - placing it in your classpath should fix the issue. HTH, Robert On 5/10/07, Edward Bush <[EMAIL PROTECTED]> wrote: That package isn't anywhere -- static or generated. Is the package name being incorrectly generated, or am I missing something here? Is it possible this is my error and not one of the Axis2 components? Anyone successfully using Axis2 1.2 + XMLBeans? With or without the wsdl2code and/or aar plugin? Anyone doing this with Maven2? Any feedback would be very appreciated! Thanks! Eddie Bush Software Analyst Clinical Reference Laboratory bushe at crlcorp dot com -----Original Message----- From: Edward Bush [mailto:[EMAIL PROTECTED] Sent: Thursday, May 10, 2007 12:29 PM To: axis-user@ws.apache.org Subject: [Axis2] XMLBeans Implementation All, I'm having some problems running a simple client. As indicated, I chose an XMLBeans implementation. Everything goes great -- I can deploy it fine, and the stand-alone Axis2 server starts up fine. I can check the deployed services and that looks good. I'm having a problem actually running my client though. It's acting like it can't find a class, which I find odd. I tracked-down the root package, and was traversing the package structure. When I got to the "system" level, I was lost -- there is not a package named s672D183626EBCBAE4E84BBAC56FF9CA9. Any suggestions? Here's the stack trace: Exception in thread "main" java.lang.ExceptionInInitializerError at com.crlcorp.ws.math.domain.EchoTextRequestDocument$Factory.newInstance(E choTextRequestDocument.java :92) at com.crlcorp.ws.math.service.TestServiceClientTest.main(TestServiceClient Test.java:19) Caused by: java.lang.RuntimeException: Cannot load SchemaTypeSystem. Unable to load class with name schemaorg_apache_xmlbeans.system.s672D183626EBCBAE4E84BBAC56FF9CA9.TypeS ystemHolder. Make sure the generated binary files are on the classpath. at org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:783) at com.crlcorp.ws.math.domain.EchoTextRequestDocument.<clinit>(EchoTextRequ estDocument.java:20) ... 2 more Caused by: java.lang.ClassNotFoundException: schemaorg_apache_xmlbeans.system.s672D183626EBCBAE4E84BBAC56FF9CA9.TypeS ystemHolder at java.net.URLClassLoader$1.run(URLClassLoader.java :200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass (Launcher.java:268) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:769) ... 3 more I'm building against Axis2 using the wsdl2code plugin and the aar plugin --- version 1.2 on all counts. My build system is Maven2. Thanks! Eddie Bush Software Analyst Clinical Reference Laboratory bushe at crlcorp dot com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
