xfire Web服务客户端获得null响应

时间:2014-07-07 06:36:03

标签: java web-services xfire

我使用xfire在Spring 3.x项目中开发Web服务客户端,以下是我的代码

WebServiceClient wClient = new WebServiceClient();
WebServiceSoap soap = wClient.getWebServiceSoap(Commons.VD_INFO_WSDL);

com.webservice.object.GetVDInfo input = new com.webservice.object.GetVDInfo();
input.setPASSWORD(Commons.VD_INFO_PASSWORD);
com.webservice.object.GetVDInfoResponse response = soap.getVDInfo(input);
System.out.println(response==null ? "response=null" : "response not null,");

当我在服务器上运行这些时,我可以看到wsdl在我的Eclipse控制台上运行,但是#34;响应"对象是null .... 这是下面的最后一部分日志,任何人都可以给我一个提示或建议吗? 如果没有足够的信息,请告诉我...... 太多了......

DEBUG: httpclient.wire.content - << "   <wsdl:service name="ToServiceImplService">[\r][\n]"
DEBUG: httpclient.wire.content - << "[\n]"
DEBUG: httpclient.wire.content - << "      <wsdl:port binding="impl:ToServiceImplSoapBinding" name="ToServiceImpl">[\r][\n]"
DEBUG: httpclient.wire.content - << "[\n]"
DEBUG: httpclient.wire.content - << "         <wsdlsoap:address location="http://xx.xx.10.77/TO_SERVICE/services/ToServiceImpl"/>[\r][\n]"
DEBUG: httpclient.wire.content - << "[\n]"
DEBUG: httpclient.wire.content - << "      </wsdl:port>[\r][\n]"
DEBUG: httpclient.wire.content - << "[\n]"
DEBUG: httpclient.wire.content - << "   </wsdl:service>[\r][\n]"
DEBUG: httpclient.wire.content - << "[\n]"
DEBUG: httpclient.wire.content - << "</wsdl:definitions>[\r][\n]"
DEBUG: org.apache.commons.httpclient.HttpMethodBase - Resorting to protocol version default close connection policy
DEBUG: org.apache.commons.httpclient.HttpMethodBase - Should NOT close connection, using HTTP/1.1
DEBUG: org.apache.commons.httpclient.HttpConnection - Releasing connection back to connection manager.
DEBUG: org.apache.commons.httpclient.MultiThreadedHttpConnectionManager - Freeing connection, hostConfig=HostConfiguration[host=http://61.60.10.77]
DEBUG: org.apache.commons.httpclient.util.IdleConnectionHandler - Adding connection at: 1404713700948
DEBUG: org.apache.commons.httpclient.MultiThreadedHttpConnectionManager - Notifying no-one, there are no waiting threads
DEBUG: org.codehaus.xfire.handler.HandlerPipeline - Invoking phase pre-dispatch
DEBUG: org.codehaus.xfire.handler.HandlerPipeline - Invoking handler org.codehaus.xfire.client.CorrelatorHandler in phase pre-dispatch
DEBUG: org.codehaus.xfire.client.Client - Correlating context with ID 14047137002771-1400602077
DEBUG: org.codehaus.xfire.client.Client - Found correlated context with ID 14047137002771-1400602077
DEBUG: org.codehaus.xfire.handler.HandlerPipeline - adding handler org.codehaus.xfire.client.ClientReceiveHandler@37e80c87 to phase service
DEBUG: org.codehaus.xfire.handler.HandlerPipeline - Invoking phase dispatch
DEBUG: org.codehaus.xfire.handler.HandlerPipeline - Invoking handler org.codehaus.xfire.handler.LocateBindingHandler in phase dispatch
DEBUG: org.codehaus.xfire.handler.HandlerPipeline - Invoking handler org.codehaus.xfire.soap.handler.SoapBodyHandler in phase dispatch
DEBUG: org.codehaus.xfire.handler.HandlerPipeline - Invoking handler org.codehaus.xfire.soap.handler.SoapActionInHandler in phase dispatch
DEBUG: org.codehaus.xfire.handler.HandlerPipeline - Invoking phase policy
DEBUG: org.codehaus.xfire.handler.HandlerPipeline - Invoking phase user
DEBUG: org.codehaus.xfire.handler.HandlerPipeline - Invoking phase pre-invoke
DEBUG: org.codehaus.xfire.handler.HandlerPipeline - Invoking handler org.codehaus.xfire.soap.handler.ValidateHeadersHandler in phase pre-invoke
DEBUG: org.codehaus.xfire.handler.HandlerPipeline - Invoking phase service
DEBUG: org.codehaus.xfire.handler.HandlerPipeline - Invoking handler org.codehaus.xfire.client.ClientReceiveHandler in phase service
DEBUG: org.codehaus.xfire.client.XFireProxy - Result [null]
response=null

0 个答案:

没有答案