diff options
Diffstat (limited to 'docs/org.eclipse.wst.wsi.ui.doc.user/tasks')
6 files changed, 0 insertions, 488 deletions
diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.dita b/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.dita deleted file mode 100644 index d1f2204a5..000000000 --- a/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.dita +++ /dev/null @@ -1,88 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd"> -<task id="tmonitor" xml:lang="en-us"> -<title>Using the TCP/IP Monitor to test Web services</title> -<titlealts> -<searchtitle>Using the TCP/IP or SOAP monitor to test Web services</searchtitle> -</titlealts> -<shortdesc>Once you have created your Web service and Web service client, -you can monitor the Web service's SOAP traffic using the TCP/IP Monitor.</shortdesc> -<taskbody> -<prereq><p> Prerequisites: </p><ul> -<li>Generate a Web service</li> -<li>Generate a Proxy and a sample application</li> -</ul></prereq> -<context><p>When creating a Web service using the Web service or Web service -client wizards, you can select to set up and run the TCP/IP Monitor automatically. -Alternately, you can set up the TCP/IP Monitor manually by completing the -following steps:</p></context> -<steps> -<step><cmd>In the sample application, invoke the getEndPoint method. Record -this endpoint. The default endpoint for a Web service is: http://localhost:<port>/<web -module context root>/services/<port></cmd></step><?Pub Caret1?> -<step><cmd>Create a server to act as the TCP/IP Monitor:</cmd> -<substeps> -<substep><cmd>From the Window menu, select <uicontrol>Preferences</uicontrol>. </cmd> -</substep> -<substep><cmd>In the Preferences window, expand Internet and then select <uicontrol>TCP/IP -Monitor</uicontrol>. </cmd></substep> -<substep><cmd>Select the <uicontrol>Show TCP/IP Monitor View when there is -activity</uicontrol> check box. </cmd></substep> -<substep><cmd>Under the TCP/IP Monitors lists, click <uicontrol>Add</uicontrol>. -A New Monitor dialog opens.</cmd></substep> -<substep><cmd>Specify the following settings: </cmd></substep> -</substeps> -<choicetable> -<chhead><choptionhd>Option</choptionhd><chdeschd>Description</chdeschd></chhead> -<chrow><choption>Local monitoring port</choption><chdesc>Specify a unique -port number on your local machine.</chdesc></chrow> -<chrow><choption>Host name</choption><chdesc>Specify the host name or IP address -of the machine where the server is running.</chdesc></chrow> -<chrow><choption>Port</choption><chdesc>Specify the port number of the remote -server.</chdesc></chrow> -<chrow><choption>Type</choption><chdesc>Specify whether the request type from -the Web browser are sent by HTTP or TCP/IP. If the HTTP option is selected -the requests from the Web browser are modified so that the HTTP header points -to the remote machine and separated if multiple HTTP requests are received -in the same connection. If the TCP/IP option is selected, all the requests -are sent byte for byte. </chdesc></chrow> -</choicetable> -</step> -<step><cmd>In order to route the Web service through the monitor, the endpoint -of the Web service client needs to be changed. The TCP/IP Monitor listens -on port 9081. In the Web browser window used in step 1, invoke the setEndPoint -method, and change the endpoint so that it directs to port 9081. For example, -the default would be: <codeph>http://localhost:9081/web_module_context_root/servlet/rpcrouter</codeph> Invoke -the getEndPoint method again to ensure that your change has been implemented.</cmd> -</step> -<step><cmd>Select a Web service method in the Methods pane. Invoke this method.</cmd> -</step> -<step><cmd>Change to the TCP/IP Monitor view by selecting the TCP/IP Monitor -tab in the Servers view. This will display request and response pairs that -are being routed through the TCP/IP Monitor. It will look similar to the following -picture: <image alt="Screen capture of request and response traffic" href="../images/traffic.gif" -placement="break"></image></cmd></step> -<step><cmd>To ensure that your Web service SOAP traffic is WS-I compliant, -you can generate a log file by clicking the <image alt="WS-I validation icon" -href="../images/wsivalico.gif"></image> icon. In the dialog box that opens, -select a name for the log file and specify where you want it to be stored. </cmd> -</step> -</steps> -<result>This log file will be validated for WS-I compliance. You can open -the log file in an XML editor to examine its contents.</result> -</taskbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/csoap.dita" scope="peer"> -<linktext>SOAP</linktext></link> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsiover.dita" scope="peer"> -<linktext>WS-I</linktext></link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.dita" scope="peer"> -<linktext>Setting the level of WS-I compliance</linktext></link> -</linklist> -</related-links> -</task> -<?Pub *0000004710?> diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.html b/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.html deleted file mode 100644 index 8f5a2275e..000000000 --- a/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.html +++ /dev/null @@ -1,145 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Using the TCP/IP Monitor to test Web services" /> -<meta name="abstract" content="Once you have created your Web service and Web service client, you can monitor the Web service's SOAP traffic using the TCP/IP Monitor." /> -<meta name="description" content="Once you have created your Web service and Web service client, you can monitor the Web service's SOAP traffic using the TCP/IP Monitor." /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/csoap.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsiover.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tmonitor" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Using the TCP/IP or SOAP monitor to test Web services</title> -</head> -<body id="tmonitor"><a name="tmonitor"><!-- --></a> - - -<h1 class="topictitle1">Using the TCP/IP Monitor to test Web services</h1> - - - -<div><p>Once you have created your Web service and Web service client, -you can monitor the Web service's SOAP traffic using the TCP/IP Monitor.</p> - -<div class="p"><p> Prerequisites: </p> -<ul> -<li>Generate a Web service</li> - -<li>Generate a Proxy and a sample application</li> - -</ul> -</div> - -<div class="section"><p>When creating a Web service using the Web service or Web service -client wizards, you can select to set up and run the TCP/IP Monitor automatically. -Alternately, you can set up the TCP/IP Monitor manually by completing the -following steps:</p> -</div> - -<ol> -<li><span>In the sample application, invoke the getEndPoint method. Record -this endpoint. The default endpoint for a Web service is: http://localhost:<port>/<web -module context root>/services/<port></span></li> - -<li><span>Create a server to act as the TCP/IP Monitor:</span> -<ol type="a"> -<li><span>From the Window menu, select <span class="uicontrol">Preferences</span>. </span> -</li> - -<li><span>In the Preferences window, expand Internet and then select <span class="uicontrol">TCP/IP -Monitor</span>. </span></li> - -<li><span>Select the <span class="uicontrol">Show TCP/IP Monitor View when there is -activity</span> check box. </span></li> - -<li><span>Under the TCP/IP Monitors lists, click <span class="uicontrol">Add</span>. -A New Monitor dialog opens.</span></li> - -<li><span>Specify the following settings: </span></li> - -</ol> - - -<table class="choicetableborder" summary="" cellspacing="0" cellpadding="4" rules="rows" frame="hsides" border="1"> -<thead><tr><th valign="bottom" id="N100BA-option">Option</th> -<th valign="bottom" id="N100BA-desc">Description</th></tr></thead> -<tbody> - -<tr><td valign="top" headers="N100BA-option" id="N100D3"><strong>Local monitoring port</strong></td> -<td valign="top" headers="N100BA-desc N100D3">Specify a unique -port number on your local machine.</td> -</tr> - -<tr><td valign="top" headers="N100BA-option" id="N100E2"><strong>Host name</strong></td> -<td valign="top" headers="N100BA-desc N100E2">Specify the host name or IP address -of the machine where the server is running.</td> -</tr> - -<tr><td valign="top" headers="N100BA-option" id="N100F1"><strong>Port</strong></td> -<td valign="top" headers="N100BA-desc N100F1">Specify the port number of the remote -server.</td> -</tr> - -<tr><td valign="top" headers="N100BA-option" id="N10100"><strong>Type</strong></td> -<td valign="top" headers="N100BA-desc N10100">Specify whether the request type from -the Web browser are sent by HTTP or TCP/IP. If the HTTP option is selected -the requests from the Web browser are modified so that the HTTP header points -to the remote machine and separated if multiple HTTP requests are received -in the same connection. If the TCP/IP option is selected, all the requests -are sent byte for byte. </td> -</tr> - -</tbody></table> - -</li> - -<li><span>In order to route the Web service through the monitor, the endpoint -of the Web service client needs to be changed. The TCP/IP Monitor listens -on port 9081. In the Web browser window used in step 1, invoke the setEndPoint -method, and change the endpoint so that it directs to port 9081. For example, -the default would be: <samp class="codeph">http://localhost:9081/web_module_context_root/servlet/rpcrouter</samp> Invoke -the getEndPoint method again to ensure that your change has been implemented.</span> -</li> - -<li><span>Select a Web service method in the Methods pane. Invoke this method.</span> -</li> - -<li><span>Change to the TCP/IP Monitor view by selecting the TCP/IP Monitor -tab in the Servers view. This will display request and response pairs that -are being routed through the TCP/IP Monitor. It will look similar to the following -picture: <br /><img src="../images/traffic.gif" alt="Screen capture of request and response traffic" /><br /></span></li> - -<li><span>To ensure that your Web service SOAP traffic is WS-I compliant, -you can generate a log file by clicking the <img src="../images/wsivalico.gif" alt="WS-I validation icon" /> icon. In the dialog box that opens, -select a name for the log file and specify where you want it to be stored. </span> -</li> - -</ol> - -<div class="section">This log file will be validated for WS-I compliance. You can open -the log file in an XML editor to examine its contents.</div> - -</div> - -<div> -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/csoap.html">SOAP</a></div> -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsiover.html">WS-I</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.html">Setting the level of WS-I compliance</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsdlval.dita b/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsdlval.dita deleted file mode 100644 index ae708f129..000000000 --- a/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsdlval.dita +++ /dev/null @@ -1,50 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd"> -<task id="twsdlval" xml:lang="en-us"> -<title>Validating WSDL files</title> -<titlealts> -<searchtitle>Validating WSDL files</searchtitle> -</titlealts> -<shortdesc>If you have created a WSDL file through the Web services wizard -the WSDL that is generated should be valid. However, if you have imported -a WSDL file, or if you are creating a WSDL file, you should validate the WSDL -to ensure it is valid.</shortdesc> -<taskbody> -<context><?Pub Caret?><p>If you have selected Require or Suggest WS-I Compliance -on the WS-I Compliance preference page, the validation also checks WS-I compliance. -If you have selected Ignore WS-I Compliance the validator will only check -the validity of the WSDL. For more information on setting WS-I compliance -levels, refer to: <xref href="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.dita" -scope="peer"> Setting the level of WS-I compliance</xref>.</p><p>The WSDL -Validator compares the WSDL file in your project to the W3C <xref format="html" -href="http://www.w3.org/TR/wsdl" scope="external">Web Services Description -Language (WSDL) 1.1</xref> specifications, and the WS-I compliance settings -that you have selected.</p><p>To validate your WSDL, complete the following -steps:</p></context> -<steps> -<step><cmd>Select a WSDL file in the <b>Project Navigator</b> view.</cmd> -</step> -<step><cmd>Right-click the WSDL file, and select <b>Validate WSDL file.</b></cmd> -</step> -</steps> -<result>Any problems encountered while validating the file will be shown in -the <b>Tasks</b> view.<p>When you rebuild a project or save a resource, the -WSDL Validator can be set to run automatically. To do this, from the Window -menu, select <b>Preferences</b> > <b>Validation</b>. Ensure that the check -box beside WSDL Validator is selected.</p></result> -</taskbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.dita" scope="peer"> -<linktext>WSDL</linktext></link> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsiover.dita" scope="peer"> -<linktext>WS-I</linktext></link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.dita" scope="peer"> -<linktext>Setting WS-I compliance</linktext></link> -</linklist> -</related-links> -</task> -<?Pub *0000002471?> diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsdlval.html b/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsdlval.html deleted file mode 100644 index 8eb6d2b23..000000000 --- a/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsdlval.html +++ /dev/null @@ -1,77 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Validating WSDL files" /> -<meta name="abstract" content="If you have created a WSDL file through the Web services wizard the WSDL that is generated should be valid. However, if you have imported a WSDL file, or if you are creating a WSDL file, you should validate the WSDL to ensure it is valid." /> -<meta name="description" content="If you have created a WSDL file through the Web services wizard the WSDL that is generated should be valid. However, if you have imported a WSDL file, or if you are creating a WSDL file, you should validate the WSDL to ensure it is valid." /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsiover.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="twsdlval" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Validating WSDL files</title> -</head> -<body id="twsdlval"><a name="twsdlval"><!-- --></a> - - -<h1 class="topictitle1">Validating WSDL files</h1> - - - -<div><p>If you have created a WSDL file through the Web services wizard -the WSDL that is generated should be valid. However, if you have imported -a WSDL file, or if you are creating a WSDL file, you should validate the WSDL -to ensure it is valid.</p> - -<div class="section"><p>If you have selected Require or Suggest WS-I Compliance -on the WS-I Compliance preference page, the validation also checks WS-I compliance. -If you have selected Ignore WS-I Compliance the validator will only check -the validity of the WSDL. For more information on setting WS-I compliance -levels, refer to: <a href="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.html">Setting the level of WS-I compliance</a>.</p> -<p>The WSDL -Validator compares the WSDL file in your project to the W3C <a href="http://www.w3.org/TR/wsdl" target="_blank">Web Services Description Language (WSDL) 1.1</a> specifications, and the WS-I compliance settings -that you have selected.</p> -<p>To validate your WSDL, complete the following -steps:</p> -</div> - -<ol> -<li><span>Select a WSDL file in the <strong>Project Navigator</strong> view.</span> -</li> - -<li><span>Right-click the WSDL file, and select <strong>Validate WSDL file.</strong></span> -</li> - -</ol> - -<div class="section">Any problems encountered while validating the file will be shown in -the <strong>Tasks</strong> view.<p>When you rebuild a project or save a resource, the -WSDL Validator can be set to run automatically. To do this, from the Window -menu, select <strong>Preferences</strong> > <strong>Validation</strong>. Ensure that the check -box beside WSDL Validator is selected.</p> -</div> - -</div> - -<div> -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.html">WSDL</a></div> -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsiover.html">WS-I</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.html">Setting WS-I compliance</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsival.dita b/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsival.dita deleted file mode 100644 index 462bbbbaf..000000000 --- a/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsival.dita +++ /dev/null @@ -1,47 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd"> -<task id="twsival" xml:lang="en-us"> -<title>Validating WS-I Web service traffic compliance</title> -<titlealts> -<searchtitle>Validating WS-I Web service traffic compliance</searchtitle> -</titlealts> -<shortdesc>As well as setting the level of WS-I compliance during Web services -creation, you can validate WS-I compliance of the SOAP traffic a Web service -produces through the TCP/IP Monitor.</shortdesc> -<taskbody> -<prereq> Prerequisites: Before you can use the validation tool to ensure that -your Web service SOAP traffic is WS-I compliant, you must have completed the -following steps:<ul> -<li>Generate a Web service.</li> -<li> <xref href="twsdlval.dita">Validate the WSDL that is produced.</xref> </li> -<li>Generate a Proxy and a sample application. </li> -<li> <xref href="tmonitor.dita">Set up the TCP/IP Monitor.</xref> Ensure that -your Web service sample application traffic is directed through the TCP/IP -Monitor.</li> -</ul></prereq> -<context><p>To validate your Web service, complete the following steps:</p></context> -<steps> -<step><cmd>Invoke a method in your Web service sample application to generate -traffic through the TCP/IP Monitor.</cmd></step> -<step><cmd>To ensure that your Web service SOAP traffic is WS-I compliant, -you can generate a log file by clicking the <image alt="Validate icon" href="../images/wsivalico.gif"> -</image> icon.</cmd></step> -<step><cmd>In the dialog box that opens, select a name for the log file and -specify where you want it to be stored.</cmd></step> -</steps> -<result> This log file will show whether or not messages sent to and from -your Web service are WS-I compliant, and list any non-compliant elements. -You can open the log file in an XML editor to examine its contents.</result> -</taskbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsiover.dita" scope="peer"> -<linktext>WS-I</linktext></link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.dita" scope="peer"> -<linktext>Setting the level of WS-I compliance</linktext></link> -</linklist> -</related-links> -</task> diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsival.html b/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsival.html deleted file mode 100644 index 3896d2721..000000000 --- a/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsival.html +++ /dev/null @@ -1,81 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Validating WS-I Web service traffic compliance" /> -<meta name="abstract" content="As well as setting the level of WS-I compliance during Web services creation, you can validate WS-I compliance of the SOAP traffic a Web service produces through the TCP/IP Monitor." /> -<meta name="description" content="As well as setting the level of WS-I compliance during Web services creation, you can validate WS-I compliance of the SOAP traffic a Web service produces through the TCP/IP Monitor." /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsiover.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="twsival" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Validating WS-I Web service traffic compliance</title> -</head> -<body id="twsival"><a name="twsival"><!-- --></a> - - -<h1 class="topictitle1">Validating WS-I Web service traffic compliance</h1> - - - -<div><p>As well as setting the level of WS-I compliance during Web services -creation, you can validate WS-I compliance of the SOAP traffic a Web service -produces through the TCP/IP Monitor.</p> - -<div class="p"> Prerequisites: Before you can use the validation tool to ensure that -your Web service SOAP traffic is WS-I compliant, you must have completed the -following steps:<ul> -<li>Generate a Web service.</li> - -<li> <a href="twsdlval.html">Validate the WSDL that is produced.</a> </li> - -<li>Generate a Proxy and a sample application. </li> - -<li> <a href="tmonitor.html">Set up the TCP/IP Monitor.</a> Ensure that -your Web service sample application traffic is directed through the TCP/IP -Monitor.</li> - -</ul> -</div> - -<div class="section"><p>To validate your Web service, complete the following steps:</p> -</div> - -<ol> -<li><span>Invoke a method in your Web service sample application to generate -traffic through the TCP/IP Monitor.</span></li> - -<li><span>To ensure that your Web service SOAP traffic is WS-I compliant, -you can generate a log file by clicking the <img src="../images/wsivalico.gif" alt="Validate icon" /> icon.</span></li> - -<li><span>In the dialog box that opens, select a name for the log file and -specify where you want it to be stored.</span></li> - -</ol> - -<div class="section"> This log file will show whether or not messages sent to and from -your Web service are WS-I compliant, and list any non-compliant elements. -You can open the log file in an XML editor to examine its contents.</div> - -</div> - -<div> -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsiover.html">WS-I</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.html">Setting the level of WS-I compliance</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file |