It seems Weblogic 6.1 sp2 or higher does manifest file validation on jars loaded in a
webapp.
Thank goodness. The offending jar is commons-logging.jar.
Manifest-Version: 1.0
Extension-Name: org.apache.commons.logging
Specification-Vendor: Apache Software Foundation
Created-By: Ant 1.4
Implemen
This is exactly my current work around. Actually, I'm only building XMLUtils and placing the class files (there is an inner class) in my WEB-INF/classes. This ensures that this version of the classes are loaded before those in the lib directory.
Also, I am using Crimson, and crimson.jar is in my
I have been having some difficulty using Axis beta3 with Weblogic 6.0, and have seen
others having
similar problems in the mailing list archive - without resolution.
http://marc.theaimsgroup.com/?l=axis-user&m=101068604131056&w=2
I was getting an AbstractMethodError on the server from line 199
I have also had this symptom. I'm sure there could be many other causes, but
here is mine.
The example in the "Axis User's Guide" under "Consuming Web Services with Axis"
contains the following code.
call.setOperationName(new QName("http://soapinterop.org/";, "echoString"));
I found that this
