Jax ws:Java SOAP异常:MustUnderstand头:[{http://www.w3.org/2005/08/addressing}行动
我正在使用Jax ws实现Onvif IP camera的客户端应用程序,我正在向camera发送一个创建PullPointSubscription的请求,看起来camera理解该请求并处理该请求并发送正确的响应,但是客户端Jax ws代码抛出了一个异常Jax ws:Java SOAP异常:MustUnderstand头:[{http://www.w3.org/2005/08/addressing}行动,java,web-services,soap,jax-ws,soap-client,Java,Web Services,Soap,Jax Ws,Soap Client,我正在使用Jax ws实现Onvif IP camera的客户端应用程序,我正在向camera发送一个创建PullPointSubscription的请求,看起来camera理解该请求并处理该请求并发送正确的响应,但是客户端Jax ws代码抛出了一个异常 MustUnderstand headers:[{http://www.w3.org/2005/08/addressing}Action] are not understood 我不明白到底是什么问题?任何人都可以解释问题是什么以及如何解决
MustUnderstand headers:[{http://www.w3.org/2005/08/addressing}Action] are not understood
我不明白到底是什么问题?任何人都可以解释问题是什么以及如何解决
异常详细信息
an 29, 2012 11:43:48 AM com.sun.xml.ws.protocol.soap.MUTube getMisUnderstoodHeaders
INFO: Element not understood={http://www.w3.org/2005/08/addressing}Action
javax.xml.ws.soap.SOAPFaultException: MustUnderstand headers:[{http://www.w3.org/2005/08/addressing}Action] are not understood
at com.sun.xml.ws.protocol.soap.MUTube.createMUSOAPFaultException(MUTube.java:148)
at com.sun.xml.ws.protocol.soap.ClientMUTube.processResponse(ClientMUTube.java:109)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:651)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:600)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:585)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:482)
at com.sun.xml.ws.client.Stub.process(Stub.java:323)
at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:161)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:113)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:93)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:144)
at $Proxy46.createPullPointSubscription(Unknown Source)
at Test.SubInEventLast(Test.java:173)
at Test.main(Test.java:139)
请求soap消息是
<?xml version='1.0' encoding='UTF-8'?>
<S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope">
<S:Body>
<ns6:CreatePullPointSubscription xmlns:ns2="http://www.w3.org/2005/08/addressing"
xmlns:ns3="http://docs.oasis-open.org/wsn/b-2"
xmlns:ns4="http://docs.oasis-open.org/wsrf/bf-2"
xmlns:ns5="http://docs.oasis-open.org/wsn/t-1"
xmlns:ns6="http://www.onvif.org/ver10/events/wsdl"
xmlns:ns7="http://www.onvif.org/ver10/schema"
xmlns:xmime="http://www.w3.org/2005/05/xmlmime"
xmlns:ns9="http://www.w3.org/2004/08/xop/include"
xmlns:ns10="http://docs.oasis-open.org/wsrf/r-2">
<ns6:Filter>
<ns3:TopicExpression xmlns="http://docs.oasis-open.org/wsn/b-2"
xmlns:tns1="http://www.onvif.org/ver10/topics"
Dialect="http://www.onvif.org/ver10/tev/topicExpression/ConcreteSet">
tns1:Device
</ns3:TopicExpression>
</ns6:Filter>
<ns3:InitialTerminationTime>PT1M</ns3:InitialTerminationTime>
</ns6:CreatePullPointSubscription>
</S:Body>
</S:Envelope>
tns1:设备
PT1M
这是soap响应
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope"
xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:c14n="http://www.w3.org/2001/10/xml-exc-c14n#"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
xmlns:wsa5="http://www.w3.org/2005/08/addressing"
xmlns:xmime5="http://www.w3.org/2005/05/xmlmime"
xmlns:wsrf-bf="http://docs.oasis-open.org/wsrf/bf-2"
xmlns:wstop="http://docs.oasis-open.org/wsn/t-1"
xmlns:tt="http://www.onvif.org/ver10/schema"
xmlns:wsrf-r="http://docs.oasis-open.org/wsrf/r-2"
xmlns:tan1="http://www.onvif.org/ver10/analytics/wsdl/RuleEngineBinding"
xmlns:tan="http://www.onvif.org/ver10/analytics/wsdl"
xmlns:tan2="http://www.onvif.org/ver10/analytics/wsdl/AnalyticsEngineBinding"
xmlns:tds="http://www.onvif.org/ver10/device/wsdl"
xmlns:tev1="http://www.onvif.org/ver10/events/wsdl/NotificationProducerBinding"
xmlns:tev2="http://www.onvif.org/ver10/events/wsdl/EventBinding"
xmlns:tev3="http://www.onvif.org/ver10/events/wsdl/SubscriptionManagerBinding"
xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2"
xmlns:tev4="http://www.onvif.org/ver10/events/wsdl/PullPointSubscriptionBinding"
xmlns:tev="http://www.onvif.org/ver10/events/wsdl"
xmlns:timg="http://www.onvif.org/ver10/imaging/wsdl"
xmlns:tptz="http://www.onvif.org/ver10/ptz/wsdl"
xmlns:trt="http://www.onvif.org/ver10/media/wsdl"
xmlns:ter="http://www.onvif.org/ver10/error"
xmlns:tns1="http://www.onvif.org/ver10/topics"
xmlns:tnsaxis="http://www.axis.com/2009/event/topics">
<SOAP-ENV:Header>
<wsa5:Action SOAP-ENV:mustUnderstand="true">http://docs.oasis-open.org/wsn/bw-2/SubscriptionManager/CreatePullPointSubscriptionResponse</wsa5:Action>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<tev:CreatePullPointSubscriptionResponse>
<tev:SubscriptionReference>
<wsa5:Address>http://192.168.0.151/onvif/services</wsa5:Address>
<wsa5:ReferenceParameters><dom0:SubscriptionId xmlns:dom0="http://www.axis.com/2009/event">3</dom0:SubscriptionId>
</wsa5:ReferenceParameters>
</tev:SubscriptionReference>
<wsnt:CurrentTime>2010-10-27T09:11:42Z</wsnt:CurrentTime>
<wsnt:TerminationTime>2010-11-24T09:11:42Z</wsnt:TerminationTime></tev:CreatePullPointSubscriptionResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
http://docs.oasis-open.org/wsn/bw-2/SubscriptionManager/CreatePullPointSubscriptionResponse
http://192.168.0.151/onvif/services
3.
2010-10-27T09:11:42Z
2010-11-24T09:11:42Z
我在一个特定的设备上遇到了同样的问题,我花了几天的搜索和反复试验才找到了一个解决方案(几乎完全是偶然的)。我可以通过向端口添加自定义处理程序来解决这个问题。处理程序只需要为WS-Addressing操作头提供QName(调用handleMessage时不需要执行任何操作)
这就是我的工作原理:
public class ActionHandler implements SOAPHandler<SOAPMessageContext>
{
@Override
public boolean handleMessage(SOAPMessageContext context)
{
// Auto-generated method stub
return true;
}
@Override
public boolean handleFault(SOAPMessageContext context)
{
// Auto-generated method stub
return false;
}
@Override
public void close(MessageContext context)
{
// Auto-generated method stub
}
@Override
public Set<QName> getHeaders()
{
Set<QName> set = new HashSet<QName>();
// Make sure the '[{http://www.w3.org/2005/08/addressing}]Action' header
// is handled in case the device set the 'MustUnderstand' attribute to '1'
set.add(new QName("http://www.w3.org/2005/08/addressing", "Action"));
return set;
}
}
public类ActionHandler实现SOAPHandler
{
@凌驾
公共布尔handleMessage(SOAPMessageContext上下文)
{
//自动生成的方法存根
返回true;
}
@凌驾
公共布尔handleFault(SOAPMessageContext上下文)
{
//自动生成的方法存根
返回false;
}
@凌驾
公共无效关闭(MessageContext上下文)
{
//自动生成的方法存根
}
@凌驾
公共集getHeaders()
{
Set=newhashset();
//确保[{http://www.w3.org/2005/08/addressing}]“动作”标题
//在设备将“MustUnderstand”属性设置为“1”时处理
set.add(新的QName(“http://www.w3.org/2005/08/addressing“,”行动“);
返回集;
}
}
然后将处理程序添加到绑定的处理程序链:
BindingProvider bindingProvider = (BindingProvider) eventPortType;
final Binding binding = bindingProvider.getBinding();
List<Handler> handlerList = binding.getHandlerChain();
if (handlerList == null)
handlerList = new ArrayList<Handler>();
handlerList.add(new ActionHandler());
binding.setHandlerChain(handlerList);
BindingProvider BindingProvider=(BindingProvider)事件端口类型;
final Binding Binding=bindingProvider.getBinding();
List handlerList=binding.getHandlerChain();
if(handlerList==null)
handlerList=新的ArrayList();
add(newactionHandler());
绑定。setHandlerChain(handlerList);
解决此问题的另一种方法是向wsimport命令添加“-xaadditionalHeaders”参数。这将向服务方法添加请求/响应头参数
wsimport HelloWorld.wsdl -keep -d ./src/main/java -p com.trial.helloworld -XadditionalHeaders
就我而言,这有助于:
getPort(QName portName,
Class<T> serviceEndpointInterface, WebServiceFeature... features)
getPort(QName-portName,
类serviceEndpointInterface、WebServiceFeature…功能)
将newjavax.xml.ws.soap.AddressingFeature()
作为WebServiceFeature
解决方案传递到修复
- “MustUnderstand标头:[{}操作]未被理解”
- “服务器发送了HTTP状态代码415:无法处理该消息,因为内容类型为'application/soap+xml;charset=“utf-8;””
WSService service = new WSService();
IWSService wcf = service.getWSHttpBindingIWSService(new AddressingFeature(true));
如果您正在使用其中一种批注@WebService,@WebServiceProvider
或者@webservicef,那么也可以通过添加javax.xml.ws.soap中的@Addressing注释来解决此问题。恐怕您所指的名称空间()JAX-WS不支持。当您生成JAX-WS工件时,
wsimport
是否有任何警告?我也有同样的问题。当我运行wsimport
时,显示以下警告:未知扩展性元素或属性“EndpointReference”(在命名空间中)添加功能帮助。谢谢!
WSService service = new WSService();
IWSService wcf = service.getWSHttpBindingIWSService(new AddressingFeature(true));