Thanks for the quick response, Clarance. Double checking, we do have the xsb's in the jars.
I neglected to mention that we have these objects working in a java console only tester application. It's when we bring them into a Dynamic web project and attempt to call them through our main web application that these errors occur. If you're running in a Dynamic Web Project, did you have to do anything special or specific with the class path, server entry, library loading order, etc.? I can provide more detailed information on our specific usage if anyone thinks it's necessary. Just let me know what to send... Thanks, Dave "Clarance Howatt" <[EMAIL PROTECTED]> Thu 04/17/2008 01:44 PM Please respond to user@xmlbeans.apache.org To <user@xmlbeans.apache.org> cc Subject RE: NoSuchMethod error in WebSphere 6.0 Although I can not be of much help to you, I can tell you that we are running WebSphere 6.1 and are not having any issues (at least with XMLBeans) I have experienced something similar to this when the xsb files were not included in the jar file. C. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, April 17, 2008 11:40 AM To: user@xmlbeans.apache.org Subject: NoSuchMethod error in WebSphere 6.0 Hi, new to the list, looking for a little help, please. Running IBM WebSphere 6.0.23 and xmlbeans 2.3.0. Getting errors as follows: "java.lang.ClassCastException: org/apache/xmlbeans/impl/values/XmlComplexContentImpl incompatible with com/prudential/sct/service/entries/ServiceEntries" where: com.prudential.sct.service.entries.ServiceEntries extends java.lang.Object implements org.apache.xmlbeans.XmlObject error code line: doc.addNewServiceEntries(); thows: java.lang.NoSuchMethodException where doc is ServiceEntriesDocument where ServiceEntriesDocument is com.prudential.sct.service.entries.ServiceEntriesDocument extends extends java.lang.Object implements org.apache.xmlbeans.XmlObject Does anyone know of any issues using xmlbeans with websphere 6? I've seen several issues where the QName method in websphere conflicts with QName in xmlbeans, that seem to be resolvable with setting classpath correctly. Up to now I've not been able to get this to work. Can someone familiar with both xmlbeans and websphere 6 please provide some guidence here? thanks, dave milbut (david dot milbut at prudential dot com) --------------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
