Sx datastore soap client exceptions sxsoapinvokeexception error sending request

Разбор ошибок SOAP PHP WSDL: не удалось загрузить внешний объект?

Я пытаюсь запустить веб-службу с помощью PHP и SOAP, но пока все, что я получил, это:

Я пробовал изменить localhost на 127.0.0.1, но это не имеет значения. На самом деле логин — это файл wsdl, но если я помещаю login.wsdl в конструктор SOAPClient, вместо этого он говорит: «Похоже, у нас нет XML-документа».

Вот мой код для клиента SOAP (register_client.php):

А вот и файл login.wsdl:

И я не уверен, что это связано с этим, поэтому я предоставляю код для SOAP-сервера register.php:

Прошу прощения, если я даю ненужную информацию, но я новичок в этом — и я был бы очень признателен, если бы кто-нибудь мог указать, почему именно генерируется эта ошибка SOAP, и что я могу сделать, чтобы исправить Это.

Я использую WAMP Server версии 2.2 с mySQL 5.5.24 и PHP 5.3.13.

После перехода на PHP 5.6.5 мыло 1.2 перестало работать. Итак, я решил проблему, добавив необязательные параметры SSL.

failed to load external entity

Поместите этот код над любым вызовом Soap:

попробуй это. работает для меня

Получил аналогичный ответ с URL-адресом https WSDL с использованием php soapClient

SoapFault exception: [WSDL] SOAP-ERROR: Parsing WSDL: Couldn’t load from .

После обновления сервера с PHP 5.5.9-1ubuntu4.21 >> PHP 5.5.9-1ubuntu4.23 что-то пошло не так для моей клиентской машины osx 10.12.6 / PHP 5.6.30, но подключения клиентов MS Web Services могут быть выполнены без проблем.

В файле server_access.log Apache2 не было записей, когда я пытался загрузить WSDL, поэтому я добавил, ‘cache_wsdl’ => WSDL_CACHE_NONE чтобы предотвратить кеширование wsdl на стороне клиента, но все равно не получил записей. Наконец, я попытался загрузить wsdl на CURL -i проверенные ЗАГОЛОВКИ, но, похоже, все в порядке ..

Только libxml_get_last_error() предоставил некоторую информацию> SSL operation failed with code 1. OpenSSL Error messages: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

Поэтому я добавил к своему вызову несколько параметров ssl:

В моем случае все ‘allow_self_signed’ => true получилось!

Источник

Exception Handling In Spring Soap Client

In my last article — Spring Boot SOAP Client, we discussed about consuming SOAP web services through spring boot using WebServiceTemplate. Now, it’s time to implement a custom exception handling mechanism while consuming SOAP web services through Spring.

WebServiceTemplate already handles exception in a perfect way but sometimes it is required to add our custom logic while executing the exception callbacks as most of the web services are designed in a such a way that exceptions are thrown in a custom fashion. For example, many web services tend to provide a status of 200 even during exceptions and there is a nested status code which actually tells about the exception. In that case, default exception handling provided by WebServiceTemplate is unable to handle that.

Hence, in this article we will try provide some custom mechanism to handle esception while consuming SOAP web services.

Exception Flow in WebServiceTemplate

As discussed here in the spring documentation, WebServiceTemplate uses the following algorithm for sending and receiving.

First a coonection is created using createConnection().

Next a request message is created and doWithMessage() is invoked on the request callback.

Next interceptors are executed if any and then send() is invoked on the connection. In case, the connection has an error, handleError() is invoked and execution stops.

For a succesfull connection, receive() is invoked on the connection to read the response message.

Once, we have the response hasFault() is invokded to determine the fault and if there is any interceptor present then ClientInterceptor.handleFault(MessageContext) is executed.

Now, if we want to handle any custom exceptions, we need to intercept at this particular point and write our custom logic to handle it.For that we need to imple,ent a custom interceptor and tell WebServiceTemplate to use our custom interceptor. We can also use this custom interceptor to add custom headers.

Custom Interceptor to Handle Exception

For a custom interceptor, we need to implement ClientInterceptor and override the abstract methods. Make sure these methods return true for marshalling and unmarshalling the request and response further. This is the preferred way for performing any custom operations in the SOAP request or response. In the next article, we will see how custom header can be added using these interceptor.

Below is an implementation of handleFault() to log the fault string.

To register above class as an interceptor, we need little modifications in the bean config. Here we are using setInterceptors() to add our custom interceptors.

Sometimes, we encounter situation to handle custom exceptions such as one in below xml. In such cases, we can use TransformerFactory to log the fault response.

Exception Handling through WebServiceMessageCallback

We can also handle our custom exceptions by providing our own implementation of WebServiceMessageCallback. This is usefull when we have some nested excpetion code but the web service response status is 200. This implentation can also be used to alter the request, response or header. Below is the sample. You can visit my another article to add custom header in the SOAP request.

One thing to note here, the above implementation can also be achieved vis interceptors that we defined above. WebServiceMessageCallback is mostly used whenever we want to perform any specific actions for a particular web service call.

Conclusion

In this article, we discussed about exception handling while consuming SOAP web services using Spring SOAP client. We created our custom interceptor to define our custom exception handling logic.

If You Appreciate This, You Can Consider:

• We are thankful for your never ending support.

A technology savvy professional with an exceptional capacity to analyze, solve problems and multi-task. Technical expertise in highly scalable distributed systems, self-healing systems, and service-oriented architecture. Technical Skills: Java/J2EE, Spring, Hibernate, Reactive Programming, Microservices, Hystrix, Rest APIs, Java 8, Kafka, Kibana, Elasticsearch, etc.

Источник

Spring SOAP Web services – Add SOAP Fault Exception handling – Part III

In this post, we will learn how to add detail information to your exceptions. Spring WS enables easy translation of errors penetrated from business logic. Exceptions are automatically thrown up the chain with the use of EndpointExceptionResolvers . Rather than exposing the internals of your application by giving an exception and stack trace, you can handle the exceptions programmatically and add an appropriate error code and description. This example shows you how to add detailed information to your SoapFault Exception.

In this post, we will implement

• MovieNotFoundException – Throw this exception when we know if a movie not present in the database
• ServiceFaultException – Add Custom code and error messages

Here are the list of posts on SOAP web services using Spring framework for your reference

1. Publish SOAP web services – perform CRUD operation and consume SOAP web services using SOAP UI : We will explore these topic in this post – Publish SOAP Web services using Spring Boot – Part 1
2. Consume SOAP web services using client application – Consume Spring SOAP web services using client application – Part II
3. Exception handling in SOAP web services- We will learn about this topic in here
4. Exception handling in CRUD SOAP web services – Spring SOAP Web services – Add SOAP Fault Exception handling for CRUD operations – Part IV
5. Securing SOAP web services – In upcoming tutorial
6. Testing SOAP web services – In upcoming tutorial

List of Contents

1. Tools and Environment

Following tools and environments are used to consume SOAP web services in Spring Boot

• Spring Tool Suite (version: 3.9.4.RELEASE)
• Spring Boot (version: 2.0.4)
• Java version (version
• Maven (version 3.5.2)
• Mysql (version: 5.1.17)

2. Project Structure

3. Steps to create SOAP Server and SOAP Client with Exception handling

1. Create sample data in the database
2. New Spring Starter project
3. Add “movies.xsd” under /src/main/resources/xsd folder
4. Edit pom.xml
   1. Add “wsdl4j” dependency (The Web Services Description Language for Java Toolkit (WSDL4J) allows the creation, representation, and manipulation of WSDL documents)
   2. jaxb2- maven – plugin (to generate java source classes from XSD))
   3. Do Maven-> update project to generate java class files
5. Create SOAP Server related files
   1. Create Movie Service class to perform CRUD operations on Movie object – “MovieService.java”
   2. Create SOAP Server configuration file – “SoapServerConfig.java”
   3. Create SOAP Endpoint file – “MovieEndpoint.java”
   4. Create SOAP Server Exceptions – “MovieNotFoundException”, “ServiceFaultException”, “DetailSoapFaultDefinitionExceptionResolver”
   5. Create an executable server class to run the Server – “RunServer.java”
6. Run Server
   1. Right click on the “RunServer” and do Run As -> Java Application to start the server on default/specified port
7. Test WDSL on web browser
8. Test in SOAP UI or Create a Client application to test the exception

4. ScreenShots

Step 1: Create sample data in the database

Step 2: New Spring Starter project

Step 3: Add “movies.xsd” under /src/main/resources/xsd folder

movies.xsd

Step 4: Edit pom.xml to include wsdl4j and jaxb2-maven-plugin

Do Maven update project after saving pom.xml

pom.xml

Maven plugin will generate java source classes under “com.javaspringclub.gs_ws”. This package name is specified in pom.xml file

Alternatively, running the following command in parent directory, the Java Classes will be generated in the target/generated-sources/jaxb/

• We can produce Spring Ws Contract First Soap Endpoint by annotating the class with the @Endpoint annotation. This makes the class as a special sort of @Component , suitable for handling XML messages in Spring WS and eligible for component scanning
• The @PayloadRoot annotation informs Spring Ws that the getMovieById method is suitable for handling XML messages. This method can handle messages with localPart equal to getMovieByIdRequest with a namespace of http://www.javaspringclub.com/movies-ws
• @RequestPayload tells Spring Ws that a XML Payload of type GetMovieByIdRequest is needed as a parameter of the request

MovieNotFoundException.java

ServiceFaultException.java

Note: The ServiceFaultException extends from RuntimeException , so we don’t need to catch or add it to our method signature. With the ServiceStatus object we can add some detailed information about the error that occurred

ServiceStatus.java

This class either you implement on your own or specify in movies.xsd so that it generated by jaxb maven plugin. In our example, we took the second approach i.e specify in movies.xsd as shown below

and here is the class, if you would like to write

The ServiceStatus class is used to propagate the appropriate error code and description up the chain. Typically the code is used to map the exception on the client side and the message is just a description indicating the user/developer what exactly went wrong.

DetailSoapFaultDefinitionExceptionResolver.java

• DetailSoapFaultDefinitionExceptionResolver extends from the SoapFaultMappingExceptionResolver and is used for enhancing the SoapFault with detailed information about the error that occurred. We can override the customizeFault method to enhance the exception with detail information. We do this by calling the addFaultDetail method of the SoapFault class, and adding QName indicating the element with the addFaultDetailElement .

RunServer.java

Step 6: Run Server application.

Right click on “RunServer.java” and select Run As -> Java Application to run the Server and publish WSDL. In our application, Tomcat is started on port : 8080

Step 7: Test WSDL in web browser

You can view wsdl on http://localhost:8080/ws/movies.wsdl

Step 8: Test in SOAP UI or Create a Client application to test the exception

To run the client application:

All the required java classes are enclosed in the attached zip file in Download section

Источник

Не отправляются данные в ЕГАИС.

2019-03-06 18:44:45,856 ERROR es.programador.a.c - Ошибка отправки файла
com.sun.xml.internal.ws.protocol.soap.MessageCreationException: Couldn't create SOAP message due to exception: unexpected XML tag. expected: {http://schemas.xmlsoap.org/soap/envelope/}Envelope but found: {null}result
    at com.sun.xml.internal.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:304)
    at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.createResponsePacket(HttpTransportPipe.java:268)
    at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:217)
    at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:130)
    at com.sun.xml.internal.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:124)
    at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:1121)
    at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:1035)
    at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:1004)
    at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:862)
    at com.sun.xml.internal.ws.client.Stub.process(Stub.java:448)
    at com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(SEIStub.java:178)
    at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:93)
    at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:77)
    at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:147)
    at com.sun.proxy.$Proxy36.registerFile(Unknown Source)
    at es.programador.a.c.a(Unknown Source)
    at es.programador.a.c.a(Unknown Source)
    at es.programador.transport.o.a(Unknown Source)
    at es.programador.transport.o.a(Unknown Source)
    at es.programador.transport.o.a(Unknown Source)
    at es.programador.transport.i.d.execute(Unknown Source)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
    at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557)
Caused by: com.sun.xml.internal.ws.streaming.XMLStreamReaderException: unexpected XML tag. expected: {http://schemas.xmlsoap.org/soap/envelope/}Envelope but found: {null}result
    at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.verifyTag(XMLStreamReaderUtil.java:261)
    at com.sun.xml.internal.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:205)
    at com.oracle.webservices.internal.impl.encoding.StreamDecoderImpl.decode(StreamDecoderImpl.java:49)
    at com.sun.xml.internal.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:234)
    at com.sun.xml.internal.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:151)
    at com.sun.xml.internal.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:299)
    ... 22 more

Сообщений 4

Есть некий wsdl сервер, допустим «https://192.168.333.3/LNetworkServer/LNetworkServi…» (адрес для поста выдуманный).

В браузере открывается нормально.

Когда пробую использовать SOAP, выдает ошибку:

SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://sh333skd1-dev/LNetworkServer/LNetworkService.svc?wsdl=wsdl0' : failed to load external entity "https://sh333skd1-dev/LNetworkServer/LNetworkService.svc?wsdl=wsdl0"

Если пробую cURL, ошибок нет, спокойно получаю XML.

Разработчики молчат, дали мне такой код:

$wsdl = "https://192.168.333.3/LNetworkServer/LNetworkService.svc?wsdl";
    	$arrContextOptions=array(
		    'ssl'=>array(
		        'verify_peer'=>false,
		        'verify_peer_name'=>false,
		        'allow_self_signed' => true
		    ),
			'https' => array(
                'curl_verify_ssl_peer'  => false,
                'curl_verify_ssl_host'  => false)
		);
    	$options =array(
	    'trace' => 1,
    	'soap_version' => SOAP_1_1,
    	'location'=>'https://192.168.333.3/LNetworkServer/LNetworkService.svc',
    	'exceptions' => 1,
    	'cache_wsdl'=>WSDL_CACHE_NONE,
    	'verifypeer' => false,
        'verifyhost' => false,
    	'stream_context' => stream_context_create($arrContextOptions),
    	'login'=>'root', 'password'=>'1234' ,
    	'classmap' => array('AcsEmployeeSaveData' => "AcsEmployeeSaveData")
    	);
        //подключение 
	$client = new SoapClient($wsdl, $options);

Сам пробовал такой вариант:

try {
    $opts = array(
		    'ssl'=>array(
		        'verify_peer'=>false,
		        'verify_peer_name'=>false,
		        'allow_self_signed' => true
		    ),
			'https' => array(
                'curl_verify_ssl_peer'  => false,
                'curl_verify_ssl_host'  => false,
            	'user_agent' => 'PHPSoapClient',
                'allow_self_signed' => true
			)
    );
    $context = stream_context_create($opts);

    $wsdlUrl = 'https://192.168.333.3/LNetworkServer/LNetworkService.svc?wsdl';
    $soapClientOptions = array(
	    'trace' => 1,
    	'location'=>'https://192.168.333.3/LNetworkServer/LNetworkService.svc',
    	'exceptions' => 1,
    	'cache_wsdl'=>0,
    	'verifypeer' => false,
        'verifyhost' => false,
    	'stream_context' => $context,
    	'login'=>'root', 'password'=>'1234' ,
    	'classmap' => array('AcsEmployeeSaveData' => "AcsEmployeeSaveData")
    );

    $client = new SoapClient($wsdlUrl, $soapClientOptions);
}
catch(Exception $e) {
	echo $e->getMessage();
}

Оба варианта выдают одинаковую ошибку, описанную выше

SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://sh333skd1-dev/LNetworkServer/LNetworkService.svc?wsdl=wsdl0' : failed to load external entity "https://sh333skd1-dev/LNetworkServer/LNetworkService.svc?wsdl=wsdl0"

В чем проблема?

This XML file does not appear to have any style information associated with it. The document tree is shown below.

<wsdl:definitions xmlns:xsd=«http://www.w3.org/2001/XMLSchema» xmlns:wsdl=«http://schemas.xmlsoap.org/wsdl/» xmlns:tns=«http://soap.ws.javastudy.ru/» xmlns:soap=«http://schemas.xmlsoap.org/wsdl/soap/» xmlns:ns1=«http://schemas.xmlsoap.org/soap/http» name=«HelloSoap» targetNamespace=«http://soap.ws.javastudy.ru/»>

<wsdl:types>

<xs:schema xmlns:xs=«http://www.w3.org/2001/XMLSchema» xmlns:tns=«http://soap.ws.javastudy.ru/» attributeFormDefault=«unqualified» elementFormDefault=«unqualified» targetNamespace=«http://soap.ws.javastudy.ru/»>

<xs:element name=«exceptionTest» type=«tns:exceptionTest»/>

<xs:element name=«exceptionTestResponse» type=«tns:exceptionTestResponse»/>

<xs:element name=«getGoods» type=«tns:getGoods»/>

<xs:element name=«getGoodsResponse» type=«tns:getGoodsResponse»/>

<xs:element name=«goods» type=«tns:goods»/>

<xs:element name=«sayHelloTo» type=«tns:sayHelloTo»/>

<xs:element name=«sayHelloToResponse» type=«tns:sayHelloToResponse»/>

<xs:element name=«testService» type=«tns:testService»/>

<xs:element name=«testServiceResponse» type=«tns:testServiceResponse»/>

<xs:complexType name=«testService»>

<xs:sequence/>

</xs:complexType>

<xs:complexType name=«testServiceResponse»>

<xs:sequence>

<xs:element minOccurs=«0» name=«return» type=«xs:string»/>

</xs:sequence>

</xs:complexType>

<xs:complexType name=«getGoods»>

<xs:sequence/>

</xs:complexType>

<xs:complexType name=«getGoodsResponse»>

<xs:sequence>

<xs:element minOccurs=«0» name=«return» type=«tns:goods»/>

</xs:sequence>

</xs:complexType>

<xs:complexType name=«goods»>

<xs:sequence>

<xs:element name=«id» type=«xs:int»/>

<xs:element minOccurs=«0» name=«name» type=«xs:string»/>

</xs:sequence>

</xs:complexType>

<xs:complexType name=«sayHelloTo»>

<xs:sequence>

<xs:element minOccurs=«0» name=«text» type=«xs:string»/>

</xs:sequence>

</xs:complexType>

<xs:complexType name=«sayHelloToResponse»>

<xs:sequence>

<xs:element minOccurs=«0» name=«return» type=«xs:string»/>

</xs:sequence>

</xs:complexType>

<xs:complexType name=«exceptionTest»>

<xs:sequence>

<xs:element minOccurs=«0» name=«text» type=«xs:string»/>

</xs:sequence>

</xs:complexType>

<xs:complexType name=«exceptionTestResponse»>

<xs:sequence/>

</xs:complexType>

<xs:complexType name=«exceptionTrace»>

<xs:sequence>

<xs:element minOccurs=«0» name=«trace» type=«xs:string»/>

</xs:sequence>

</xs:complexType>

<xs:element name=«MyWebserviceException» type=«tns:MyWebserviceException»/>

<xs:complexType name=«MyWebserviceException»>

<xs:sequence>

<xs:element minOccurs=«0» name=«exceptionTrace» type=«tns:exceptionTrace»/>

<xs:element minOccurs=«0» name=«message» type=«xs:string»/>

</xs:sequence>

</xs:complexType>

</xs:schema>

</wsdl:types>

<wsdl:message name=«testService»>

<wsdl:part element=«tns:testService» name=«parameters»></wsdl:part>

</wsdl:message>

<wsdl:message name=«exceptionTestResponse»>

<wsdl:part element=«tns:exceptionTestResponse» name=«parameters»></wsdl:part>

</wsdl:message>

<wsdl:message name=«getGoods»>

<wsdl:part element=«tns:getGoods» name=«parameters»></wsdl:part>

</wsdl:message>

<wsdl:message name=«testServiceResponse»>

<wsdl:part element=«tns:testServiceResponse» name=«parameters»></wsdl:part>

</wsdl:message>

<wsdl:message name=«sayHelloTo»>

<wsdl:part element=«tns:sayHelloTo» name=«parameters»></wsdl:part>

</wsdl:message>

<wsdl:message name=«exceptionTest»>

<wsdl:part element=«tns:exceptionTest» name=«parameters»></wsdl:part>

</wsdl:message>

<wsdl:message name=«getGoodsResponse»>

<wsdl:part element=«tns:getGoodsResponse» name=«parameters»></wsdl:part>

</wsdl:message>

<wsdl:message name=«MyWebserviceException»>

<wsdl:part element=«tns:MyWebserviceException» name=«MyWebserviceException»></wsdl:part>

</wsdl:message>

<wsdl:message name=«sayHelloToResponse»>

<wsdl:part element=«tns:sayHelloToResponse» name=«parameters»></wsdl:part>

</wsdl:message>

<wsdl:portType name=«WebserviceSEI»>

<wsdl:operation name=«testService»>

<wsdl:input message=«tns:testService» name=«testService»></wsdl:input>

<wsdl:output message=«tns:testServiceResponse» name=«testServiceResponse»></wsdl:output>

</wsdl:operation>

<wsdl:operation name=«getGoods»>

<wsdl:input message=«tns:getGoods» name=«getGoods»></wsdl:input>

<wsdl:output message=«tns:getGoodsResponse» name=«getGoodsResponse»></wsdl:output>

</wsdl:operation>

<wsdl:operation name=«sayHelloTo»>

<wsdl:input message=«tns:sayHelloTo» name=«sayHelloTo»></wsdl:input>

<wsdl:output message=«tns:sayHelloToResponse» name=«sayHelloToResponse»></wsdl:output>

</wsdl:operation>

<wsdl:operation name=«exceptionTest»>

<wsdl:input message=«tns:exceptionTest» name=«exceptionTest»></wsdl:input>

<wsdl:output message=«tns:exceptionTestResponse» name=«exceptionTestResponse»></wsdl:output>

<wsdl:fault message=«tns:MyWebserviceException» name=«MyWebserviceException»></wsdl:fault>

</wsdl:operation>

</wsdl:portType>

<wsdl:binding name=«HelloSoapSoapBinding» type=«tns:WebserviceSEI»>

<soap:binding style=«document» transport=«http://schemas.xmlsoap.org/soap/http»/>

<wsdl:operation name=«testService»>

<soap:operation soapAction=«» style=«document»/>

<wsdl:input name=«testService»>

<soap:body use=«literal»/>

</wsdl:input>

<wsdl:output name=«testServiceResponse»>

<soap:body use=«literal»/>

</wsdl:output>

</wsdl:operation>

<wsdl:operation name=«getGoods»>

<soap:operation soapAction=«» style=«document»/>

<wsdl:input name=«getGoods»>

<soap:body use=«literal»/>

</wsdl:input>

<wsdl:output name=«getGoodsResponse»>

<soap:body use=«literal»/>

</wsdl:output>

</wsdl:operation>

<wsdl:operation name=«sayHelloTo»>

<soap:operation soapAction=«» style=«document»/>

<wsdl:input name=«sayHelloTo»>

<soap:body use=«literal»/>

</wsdl:input>

<wsdl:output name=«sayHelloToResponse»>

<soap:body use=«literal»/>

</wsdl:output>

</wsdl:operation>

<wsdl:operation name=«exceptionTest»>

<soap:operation soapAction=«» style=«document»/>

<wsdl:input name=«exceptionTest»>

<soap:body use=«literal»/>

</wsdl:input>

<wsdl:output name=«exceptionTestResponse»>

<soap:body use=«literal»/>

</wsdl:output>

<wsdl:fault name=«MyWebserviceException»>

<soap:fault name=«MyWebserviceException» use=«literal»/>

</wsdl:fault>

</wsdl:operation>

</wsdl:binding>

<wsdl:service name=«HelloSoap»>

<wsdl:port binding=«tns:HelloSoapSoapBinding» name=«HelloSoapPort»>

<soap:address location=«http://localhost:8080/soap/webserviceSEI»/>

</wsdl:port>

</wsdl:service>

</wsdl:definitions>