Environment: linux+weblogic10.3.0.0
In the project's Web-inf directory, there are the following weblogic.xml files
<?xml version= "1.0" encoding= "UTF-8"?> <weblogic-web-app xmlns=
"http://www.bea.com/ns/weblogic/" Weblogic-web-app "
xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance "
xsi:schemalocation=" http:// Java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd ">
< container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</ Container-descriptor>
</weblogic-web-app>
WebLogic after the successful release of the Code, run a feature, the following error occurred:
<2016-3-10 11:49 A.M. 51 sec cst> <Error> <HTTP> <BEA-101017> <[servletcontext@16524584[app:
Ceaccsvr module:ceaccsvr path:/ceaccsvr Spec-version:null]] Root cause of servletexception. Java.lang.LinkageError:loader constraint violation in interface itable Initialization:when-Resolving method "Org.apache . axis. Messagecontext.getmessage () ljavax/xml/soap/soapmessage; "The class loader (instance of weblogic/utils/classloaders/ Changeawareclassloader) of the current class, Org/apache/axis/messagecontext,and the class loader (instance of SUN/MISC/L Auncher$appclassloader) for interface Javax/xml/rpc/handler/soap/soapmessagecontext have different Class objects for The type javax/xml/soap/soapmessage used in the signature at org.apache.axis.AxisFault.setFaultCodeAsString (AXISFA ult.java:422) at org.apache.axis.axisfault.<init> (axisfault.java:228) at Com.eastrobot.wsserver.serv Ice.impl.AirportsMsgServiceSoapBindingStub.createCall (Airportsmsgservicesoapbindingstub.java:138) at Com.eastrobot.wsserver.service.impl.AirportsMsgServiceSoapBindingStub.search ( airportsmsgservicesoapbindingstub.java:146) at Com.cea.callcenter.action.baseinfo.SearchAirportsMsgI.execute ( searchairportsmsgi.java:23) truncated. The log file for complete StackTrace
Package conflict, delete the following few packages, it's OK.
Saaj-api-1.3.jar uses the jar required by axis
Saaj-impl-1.3.2.jar uses the jar required by axis
Saaj.jar methods for creating point-to-point connections to endpoints, methods for creating and processing SOAP messages and attachments, and methods of receiving and handling soap errors.