soapfault

问题 My web service method returns a collection object, this will serialize nicely, thanks to the way C# web services work! But if my code throws an uncaught exception, I want to instead return a custom error object. Is this possible using C# ASP.NET v2? For example, Normal Operation should return: <Books> <book>Sample</book> <book>Sample</book> </Books> But on error I want <error> <errorMessage></errorMessage> </error> 回答1: Yes, this is possible. What you'll need to look into is the SoapException

问题 I've been using Apache CXF wsdl2java generated code to call methods from a webservice for some time now, which so far has been working fine.. The problem I'm having is that when the webservice (implemented just down the hall from me) legitimately throws a soap exception, CXF comes up with the following Error message: Could not initialize class com.sun.xml.internal.ws.fault.SOAPFaultBuilder I'm using Ubuntu 9.04, OpenJDK (IcedTea6 1.4.1) 6b14-1.1.1-0ubuntu11, Maven2 and CXF 2.2.3. I'm

问题 I am very new to Android and ksoap2 development. I have been searching on the forums for an answer to my error and still have not found a fix. Hopefully someone will be able to figure how to fix the error. I am calling a Webservice with 10 parameters in my sample android app using the Ksoap2-Android-assembly-2.4 jar library. The error from the responsedump call: <?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www

问题 I am working on creating a web service using Spring-WS. And i am using the validation framework provided by Spring-WS to validate the request. When there are validation errors, the web service returns a SOAP fault with the validation errors in the detail element of the SOAP Fault. I'd like to know if there is a way we can send a custom response(message with my own schema) instead of a SOAP Fault response? If so, i'd be grateful if you can describe how i can achieve this. I have checked the

问题 I wrote a custom CXF interceptor to log all the SOAP request and responses into the database and it seems to be working fine with positive test cases and server errors. But when a SOAP Fault occurs it just neglects my interceptor and nothing is logged. Custom CXF interceptors. public class DbLogOutInterceptor extends AbstractSoapInterceptor { public void handleMessage(SoapMessage message) { logger.info("Handling outbound request"); String transaction = MDC.get(mdcKey); logger.info("OutBound

问题 I would like to add some SOAP Faults to my JAX-WS web service, but I would like not to change content of WSDL schema. As far as I read I would have to use annotation @WebFault to define SOAP Fault and it automatically causes changes in WSDL during next build. Is there any way to use SOAP Faults without changing content of WSDL scheme? 回答1: When you throw an Exception from your code it will be automatically mapped to a SOAP fault by JAX-WS in the response. There's no need to define a fault in

问题 I am trying to hit a web service with an android application. I am getting following exception about which I don't have any Idea. Please help: 09-01 11:21:29.873: WARN/System.err(921): SoapFault - faultcode: 'soapenv:Server' faultstring: 'com.hello.service.DataStore' faultactor: 'null' detail: org.kxml2.kdom.Node@44e9a320 09-01 11:21:29.883: WARN/System.err(921): at org.ksoap2.serialization.SoapSerializationEnvelope.parseBody(SoapSerializationEnvelope.java:112) 09-01 11:21:29.883: WARN/System

问题 I am a begginer in android,here I have activity that use web service: SoapObject request = new SoapObject(NAMESPACE, METHOD_NAME); GetBoundData val = new GetBoundData() { }; PropertyInfo pi = new PropertyInfo(); pi.setName("GetBoundData"); pi.setValue(val); pi.setType(GetBoundData.class); request.addProperty(pi); SoapSerializationEnvelope envelope = new SoapSerializationEnvelope(SoapEnvelope.VER11); envelope.setOutputSoapObject(request); Marshal floatMarshal = new MarshalFloat(); envelope

问题 I'm using the Enterprise Library Validation Application Block for my WCF service. All is fine, and .Net consumers can catch the FaultException<ValidationFault> exception to get a collection of human-readable business errors. However, it doesn't look quite as great for non-.Net consumers, especially those that are going to be looking at the raw SOAP message. The SOAP Reason text is always " The creator of this fault did not specify a Reason. " This isn't very helpful, as there is a reason, it

问题 I am using spring-ws-2.3.1, While creating client for webservices sometime i am getting SoapFaultClientException like below, <SOAP-ENV:Body> <SOAP-ENV:Fault> <faultcode>SOAP-ENV:Server</faultcode> <faultstring>There was a problem with the server so the message could not proceed</faultstring> <faultactor>InvalidAPI</faultactor> <detail> <ns0:serviceException xmlns:ns0="http://www.books.com/interface/v1"> <ns1:messageId xmlns:ns1="http://www.books.org/schema/common/v3_1">5411</ns1:messageId>