我在一个抛出的独立应用程序中有一个JAXWS客户端:
Caused by: java.lang.UnsupportedOperationException: WSWS4104E: SOAP 1.2 Protocol is not supported by SAAJ 1.2.
at com.ibm.ws.webservices.engine.xmlsoap.SOAPFactory.setSOAPConstants(SOAPFactory.java:143)
at com.ibm.ws.webservices.engine.xmlsoap.SOAPFactory.<init>(SOAPFactory.java:111)
at com.ibm.ws.webservices.engine.soap.SAAJMetaFactoryImpl.newSOAPFactory(SAAJMetaFactoryImpl.java:68)
at javax.xml.soap.SOAPFactory.newInstance(SOAPFactory.java:297)
at com.sun.xml.internal.ws.api.SOAPVersion.<init>(SOAPVersion.java:176)
at com.sun.xml.internal.ws.api.SOAPVersion.<clinit>(SOAPVersion.java:94)
我添加了以下jar com.ibm.jaxws.thinclient_8.0.0.jar但仍然会抛出同样的错误。
还尝试添加这些依赖项:
<dependency>
<groupId>com.sun.xml.messaging.saaj</groupId>
<artifactId>saaj-impl</artifactId>
<version>1.3.25</version>
</dependency>
<dependency>
<groupId>javax.xml.soap</groupId>
<artifactId>saaj-api</artifactId>
<version>1.3.5</version>
</dependency>
甚至在Oracle的JDK 1.8和IBM JDK 1.7下运行。
这让我发疯,不知道它为什么不起作用?
答案 0 :(得分:1)
在遭遇这种情况之后,我终于明白了发生了什么:
使用SOAP 1.2时,瘦客户端会尝试确定SAAJ 1.3是否可用。
com.ibm.ws.webservices.engine.xmlsoap.Utils
private static final boolean isSAAJ13Available = discoverSAAJ13Availability();
discoverSAAJ13Availability()
最终尝试加载不在类路径上的com.ibm.ws.webservices.engine.xmlsoap.saaj13only.SOAPDynamicConstants
并最终引发异常。
要解决此问题,您还必须添加包含该类的jar:com.ibm.jaxws.thinclient_8.0.0.jar
。