docs/org.eclipse.jst.ws.doc.user/tasks/twsicomply.html - webservices/webtools.webservices - Git at Google

 <?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="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
 <meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
 <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="Setting the level of WS-I compliance" />
 <meta name="abstract" content="The Web services WS-I validation tools support the level of WS-I compliance outlined in the WS-I Basic Profile 1.1, the WS-I Simple SOAP Binding Profile 1.0 (WS-I SSBP), and the WS-I Attachments Profile 1.0 (WS-I AP). You can choose to make your Web service compliant or non-compliant, depending on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols are not WS-I compliant." />
 <meta name="description" content="The Web services WS-I validation tools support the level of WS-I compliance outlined in the WS-I Basic Profile 1.1, the WS-I Simple SOAP Binding Profile 1.0 (WS-I SSBP), and the WS-I Attachments Profile 1.0 (WS-I AP). You can choose to make your Web service compliant or non-compliant, depending on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols are not WS-I compliant." />
 <meta content="Web services, interoperability compliance, WSI, setting compliance" name="DC.subject" />
 <meta content="Web services, interoperability compliance, WSI, setting compliance" name="keywords" />
 <meta content="XHTML" name="DC.Format" />
 <meta content="twsicomply" name="DC.Identifier" />
 <meta content="en-us" name="DC.Language" />
 <link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
 <title>Setting the level of WS-I compliance</title>
 </head>
 <body id="twsicomply"><a name="twsicomply"><!-- --></a>


 <h1 class="topictitle1">Setting the level of WS-I compliance</h1>


 <div><p>The Web services WS-I validation tools support the level of WS-I
 compliance outlined in the WS-I Basic Profile 1.1, the WS-I Simple SOAP Binding
 Profile 1.0 (WS-I SSBP), and the WS-I Attachments Profile 1.0 (WS-I AP). You
 can choose to make your Web service compliant or non-compliant, depending
 on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols
 are not WS-I compliant.</p>

 <div class="section"><p>You can set the level of compliance for either the Basic Profile
 and the Simple SOAP Binding Profile, or for the Attachments Profile. You can
 select from three levels of compliance with WS-I specifications:</p>
 <ul>
 <li>Require WS-I compliance - this level prevents you from creating a non-compliant
 Web service.</li>

 <li>Suggest WS-I compliance - this level allows you to create a non-compliant
 Web service, but provides a visible warning stating how the service is non-compliant.</li>

 <li>Ignore WS-I compliance - this level allows you to create a non-compliant
 Web service and does not notify you of non-compliance.</li>

 </ul>
 <p>You can set the level of WS-I compliance at the workspace level, or
 at the project level.</p>
 </div>

 </div>

 <div class="nested1" xml:lang="en-us" id="sdgfsdgs"><a name="sdgfsdgs"><!-- --></a>
 <h2 class="topictitle2">Set the level of WS-I compliance for the workspace</h2>

 <div>
 <div class="section"><p>To set the level of WS-I compliance for the workspace:</p>
 </div>

 <ol>
 <li><span>From the  <strong>Window</strong> menu, select  <strong>Preferences</strong>.</span>
 </li>

 <li><span>Select  <strong>Web Services</strong> from the component tree on the left-hand
 side of the panel.</span></li>

 <li><span>Under <strong>Profile Compliance and Validation</strong>, select the level
 of compliance you want from the drop-down lists.</span></li>

 <li><span>Click  <strong>Apply</strong>, then click  <strong>OK</strong>.</span></li>

 </ol>

 </div>

 </div>

 <div class="nested1" xml:lang="en-us" id="xvgdsgfsg"><a name="xvgdsgfsg"><!-- --></a>
 <h2 class="topictitle2">Set the level of WS-I compliance for a project</h2>

 <div>
 <div class="section"><p>To set the level of WS-I compliance for a project:</p>
 </div>

 <ol>
 <li><span>In the Project Navigator, right click and select  <strong>Properties</strong>.</span>
 </li>

 <li><span>Select  <strong>Profile Compliance and Validation</strong> from the component
 tree on the left-hand side of the panel.</span></li>

 <li><span>Select the level of compliance you want from the drop-down lists,
 or select to have the project share the same level of WS-I compliance as the
 workspace</span></li>

 <li><span>Click  <strong>Apply</strong>, then click  <strong>OK</strong>.</span></li>

 </ol>

 </div>

 <div>
 <div class="linklist"><strong>Related Concepts</strong><br />

 <div><a href="../concepts/cwsiover.html" title="WS-I is an organization designed to promote Web service interoperability across platforms, operating systems, and programming languages.">Web services interoperability (WS-I)</a></div></div>
 </div>
 </div>


 </body>
 </html>
	<?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="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
	<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
	<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="Setting the level of WS-I compliance" />
	<meta name="abstract" content="The Web services WS-I validation tools support the level of WS-I compliance outlined in the WS-I Basic Profile 1.1, the WS-I Simple SOAP Binding Profile 1.0 (WS-I SSBP), and the WS-I Attachments Profile 1.0 (WS-I AP). You can choose to make your Web service compliant or non-compliant, depending on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols are not WS-I compliant." />
	<meta name="description" content="The Web services WS-I validation tools support the level of WS-I compliance outlined in the WS-I Basic Profile 1.1, the WS-I Simple SOAP Binding Profile 1.0 (WS-I SSBP), and the WS-I Attachments Profile 1.0 (WS-I AP). You can choose to make your Web service compliant or non-compliant, depending on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols are not WS-I compliant." />
	<meta content="Web services, interoperability compliance, WSI, setting compliance" name="DC.subject" />
	<meta content="Web services, interoperability compliance, WSI, setting compliance" name="keywords" />
	<meta content="XHTML" name="DC.Format" />
	<meta content="twsicomply" name="DC.Identifier" />
	<meta content="en-us" name="DC.Language" />
	<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
	<title>Setting the level of WS-I compliance</title>
	</head>
	<body id="twsicomply"><a name="twsicomply"><!-- --></a>


	<h1 class="topictitle1">Setting the level of WS-I compliance</h1>



	<div><p>The Web services WS-I validation tools support the level of WS-I
	compliance outlined in the WS-I Basic Profile 1.1, the WS-I Simple SOAP Binding
	Profile 1.0 (WS-I SSBP), and the WS-I Attachments Profile 1.0 (WS-I AP). You
	can choose to make your Web service compliant or non-compliant, depending
	on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols
	are not WS-I compliant.</p>

	<div class="section"><p>You can set the level of compliance for either the Basic Profile
	and the Simple SOAP Binding Profile, or for the Attachments Profile. You can
	select from three levels of compliance with WS-I specifications:</p>
	<ul>
	<li>Require WS-I compliance - this level prevents you from creating a non-compliant
	Web service.</li>

	<li>Suggest WS-I compliance - this level allows you to create a non-compliant
	Web service, but provides a visible warning stating how the service is non-compliant.</li>

	<li>Ignore WS-I compliance - this level allows you to create a non-compliant
	Web service and does not notify you of non-compliance.</li>

	</ul>
	<p>You can set the level of WS-I compliance at the workspace level, or
	at the project level.</p>
	</div>

	</div>

	<div class="nested1" xml:lang="en-us" id="sdgfsdgs"><a name="sdgfsdgs"><!-- --></a>
	<h2 class="topictitle2">Set the level of WS-I compliance for the workspace</h2>

	<div>
	<div class="section"><p>To set the level of WS-I compliance for the workspace:</p>
	</div>

	<ol>
	<li><span>From the <strong>Window</strong> menu, select <strong>Preferences</strong>.</span>
	</li>

	<li><span>Select <strong>Web Services</strong> from the component tree on the left-hand
	side of the panel.</span></li>

	<li><span>Under <strong>Profile Compliance and Validation</strong>, select the level
	of compliance you want from the drop-down lists.</span></li>

	<li><span>Click <strong>Apply</strong>, then click <strong>OK</strong>.</span></li>

	</ol>

	</div>

	</div>

	<div class="nested1" xml:lang="en-us" id="xvgdsgfsg"><a name="xvgdsgfsg"><!-- --></a>
	<h2 class="topictitle2">Set the level of WS-I compliance for a project</h2>

	<div>
	<div class="section"><p>To set the level of WS-I compliance for a project:</p>
	</div>

	<ol>
	<li><span>In the Project Navigator, right click and select <strong>Properties</strong>.</span>
	</li>

	<li><span>Select <strong>Profile Compliance and Validation</strong> from the component
	tree on the left-hand side of the panel.</span></li>

	<li><span>Select the level of compliance you want from the drop-down lists,
	or select to have the project share the same level of WS-I compliance as the
	workspace</span></li>

	<li><span>Click <strong>Apply</strong>, then click <strong>OK</strong>.</span></li>

	</ol>

	</div>

	<div>
	<div class="linklist"><strong>Related Concepts</strong><br />

	<div><a href="../concepts/cwsiover.html" title="WS-I is an organization designed to promote Web service interoperability across platforms, operating systems, and programming languages.">Web services interoperability (WS-I)</a></div></div>
	</div>
	</div>


	</body>
	</html>