<?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-. --><definitionsxmlns: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">
@@ -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 <ahref="example.wsdl">this file</a> as an example.</p>