diff --git a/html/tutorial/tutorial5/example.wsdl b/html/tutorial/tutorial5/example.wsdl
new file mode 100644
index 0000000000000000000000000000000000000000..5c394add4ba49fafa218b1935f37b3f4fded5dec
--- /dev/null
+++ b/html/tutorial/tutorial5/example.wsdl
@@ -0,0 +1,20 @@
+<?xml version='1.0' encoding='UTF-8'?><!-- Published by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.2-b05-. --><!-- Generated by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.2-b05-. --><definitions xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsp="http://www.w3.org/ns/ws-policy" xmlns:wsp1_2="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://tools.examples.omt.sealsproject.eu/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://tools.examples.omt.sealsproject.eu/" name="MMatchX3Service">
+<import namespace="http://matcher.ws.omt.sealsproject.eu/" location="http://mindblast.informatik.uni-mannheim.de:8080/testtools/mmatcherX3?wsdl=1" />
+<binding xmlns:ns1="http://matcher.ws.omt.sealsproject.eu/" name="MMatchX3PortBinding" type="ns1:AlignmentWS">
+<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc" />
+<operation name="align">
+<soap:operation soapAction="" />
+<input>
+<soap:body use="literal" namespace="http://matcher.ws.omt.sealsproject.eu/" />
+</input>
+<output>
+<soap:body use="literal" namespace="http://matcher.ws.omt.sealsproject.eu/" />
+</output>
+</operation>
+</binding>
+<service name="MMatchX3Service">
+<port name="MMatchX3Port" binding="tns:MMatchX3PortBinding">
+<soap:address location="http://mindblast.informatik.uni-mannheim.de:8080/testtools/mmatcherX3" />
+</port>
+</service>
+</definitions>
\ No newline at end of file
diff --git a/html/tutorial/tutorial5/index.html b/html/tutorial/tutorial5/index.html
index cf123cfb5eac473f9ab3456ced1d6aff35a87fe3..79b97c28d244b1cfdea2234ad44296e0705f7f13 100644
--- a/html/tutorial/tutorial5/index.html
+++ b/html/tutorial/tutorial5/index.html
@@ -34,9 +34,12 @@ margin-bottom: 10px;
<body style="background-color: #FFFFFF;">
<h1>Exposing a matcher as a web service</h1>
<dl>
- <dt>Author:</dt>
+ <dt>Authors:</dt>
<dd><a href="http://exmo.inrialpes.fr/people/trojahn/">Cássia Trojahn dos
Santos</a> & <a href="http://exmo.inrialpes.fr/people/euzenat/">Jérôme Euzenat</a>, INRIA & LIG </dd>
+ <dd>with contributions from <a href="http://ki.informatik.uni-mannheim.de/
+">Christian Meilicke</a>, University of Mannheim</dd>
+
</dl>
<p style="border-top: 2px solid #AAAAAA; padding-top: 15px;">This tutorial
@@ -232,6 +235,15 @@ public class AlignmentWSPublisher {
<p>To use the seals infrastructure you have to specify the class including its package specification (e.g. example.ws.matcher.AlignmentWSImpl or example.ws.matcher.MyAlignmentWS) and you have to specify the URL of the service endpoint (e.g. http://134.155.86.66:8080/matcherWS or http://134.155.86.66:8080/matcherWS?wsdl). </p>
+<p><b>Additional Note:</b> If you exactly follow these instructions to publish
+your wrapped matcher as a webservice, this will automatically generate a
+WSDL file that contains all required information. However, you can use
+also use another framework (e.g. axis) for publishing the webservice,
+but than you have to ensure to use the namespace
+"http://matcher.ws.omt.sealsproject.eu/" in the appropriate
+way. Take a look at <a href="example.wsdl">this file</a> as an example.</p>
+
+
<hr/>
<small>
<div style="text-align: center;">http://alignapi.gforge.inria.fr/tutorial/tutorial5/</div>