Weblogic webservices question

[Billy Fence]

Hi, trying to create a client call using stubs generated by weblogic (7) tool clientgen on a wasp 4.6 wsdl. I'm stuck with the following error:
java.lang.NoSuchMethodError
at weblogic.xml.schema.binding.internal.TypeMappingEntryImpl.<init>(TypeMappingEntryImpl.java:61)
at weblogic.xml.schema.binding.internal.XSDTypeMapping.addEntries(XSDTypeMapping.java:724)
at weblogic.xml.schema.binding.internal.XSDTypeMapping.createPrimaryMapping(XSDTypeMapping.java:149)
at weblogic.xml.schema.binding.internal.XSDTypeMapping.createInstance(XSDTypeMapping.java:135)
at weblogic.xml.schema.binding.internal.XSDTypeMapping.<clinit>(XSDTypeMapping.java:116)
at weblogic.xml.schema.binding.internal.TypeMappingFactoryBase.createDefaultMapping(TypeMappingFactoryBase.java:18)
at weblogic.webservice.core.encoding.DefaultRegistry.<init>(DefaultRegistry.java:77)
at weblogic.webservice.core.rpc.ServiceImpl.<init>(ServiceImpl.java:68)
at weblogic.webservice.core.rpc.ServiceImpl.<init>(ServiceImpl.java:57)
at weblogic.webservice.core.rpc.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:36)
Anyone any ideas? It looks like I'm missing a jar in my classpath but which? I'm using the ones recommended by weblogic to make client calls.
Thanks for the help.
B

[Zkr Ryz]

Did anyone find the solution for this?
Re-posting the question.
How can I use a weblogic8.1 webservice from a jdk1.3 client?

I think using the generated client is not useful since this exception is thrown. The only difference I have been able to identify is the jdk version.


Thanks a lot.

[John Cattanach]

Hi, came across this thread will spending a miserable couple hours tracking down something similar.
Our problem turned out to be classpath - ensure that webserviceclient.jar from same weblogic server version is being used. Should suffice, but if weblogicservice.jar and weblogic.jar are required for some reason, ensure they follow the former in that order.
The context of our problem was running client within Eclipse, and there was a weblogic.jar of unknown provenance in the JRE path.
Removed this and problem went away.