diff options
Diffstat (limited to 'docs/org.eclipse.wst.wsdl.ui.doc.user/tasks')
24 files changed, 0 insertions, 2349 deletions
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddmess.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddmess.dita deleted file mode 100644 index 7b2e59c9e..000000000 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddmess.dita +++ /dev/null @@ -1,108 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2006, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" - "task.dtd"> -<task id="addingamessage" xml:lang="en-us"> -<title>Adding a message</title> -<shortdesc>Messages represent an abstract definition of the data being transmitted. -A message consists of logical parts, each of which is associated with a definition -within some type system. WSDL messages are top level objects that can be referenced -by an operation's input, output and fault elements (within a port type).</shortdesc> -<prolog><metadata> -<keywords><indexterm keyref="taddmess|1|WebservicesaddingWSDLmessages" status="unchanged">Web -services<indexterm>adding WSDL messages</indexterm></indexterm><indexterm -keyref="taddmess|2|WSDLmessages" status="unchanged">WSDL files<indexterm>messages</indexterm></indexterm> -</keywords> -</metadata></prolog> -<taskbody> -<prereq></prereq> -<context><p>You can create a message using the Outline view by right-clicking -the <b>Messages</b> folder and clicking <b>Add Message</b>.</p><p>To create -a new message for your input, output, or fault element, complete the following -steps:</p></context> -<steps> -<step><cmd>In the Design view, right-click your input, output, or fault element -and click <b>Set Message > New Message.</b></cmd></step> -<step><cmd>Type the name of the message in the <uicontrol>General</uicontrol> pane -of the Properties view.</cmd><info>This name should be a unique amongst all -messages defined within the enclosing WSDL document.</info></step> -<step><cmd>The new message will appear in the Design view within the port -type.</cmd></step> -</steps> -<postreq><p> <b>Note</b>: Messages are referenced within a port type (specifically -by an operation's input, output and fault objects). The input, output and -fault objects within a binding do not reference messages. Hence you cannot -create a new message by right clicking on a input, output, or fault within -a binding (these are also known as binding input, binding output and binding -faults).</p><note type="tip">You can also create a new message for your input, -output, or fault element using the Outline view. Under the <b>Port Types</b> folder, -right-click your element and click <b>Set Message > Add Message</b>. Your -message will appear in the Outline view under the <b>Messages</b> folder.</note></postreq> -</taskbody> -<task id="reusingamessage" xml:lang="en-us"> -<title>Reusing a message</title> -<taskbody> -<prereq>To reuse a message for your input, output, or fault element, complete -the following steps:</prereq> -<steps> -<step><cmd>In the Design view, right-click your input, output, or fault element -and click <b>Set Message > Existing Message.</b></cmd></step> -<step><cmd>In the <b>Name</b> field, type a search string to filter the list -or leave the field blank to view all</cmd></step> -<step><cmd>You can change the scope of the list by selecting one of the following -options:</cmd><info><ul> -<li><b>Workspace</b>: lists the messages available in your workspace.</li> -<li><b>Enclosing Project</b>: lists the messages available in the project -that contains your file.</li> -<li><b>Current Resource</b>: lists the messages available in your current -file.</li> -<li><b>Working Sets</b>: lists the messages available in a specified set of -files. To specify a working set, click <b>Choose</b>. You can select files -from an existing working set or create a new working set. Once you have selected -the files, click <b>OK</b>.</li> -</ul></info></step> -<step><cmd>The existing messages will be listed. Select one and click <b>OK</b>.</cmd> -</step> -</steps> -<postreq></postreq> -</taskbody> -</task> -<task id="importingamessage" xml:lang="en-us"> -<title>Importing a message</title> -<taskbody> -<prereq>If you want to import an existing message for your input, output, -or fault element, follow these steps:</prereq> -<steps> -<step><cmd>In the Design view, right-click your input, output, or fault element -and click <b>Set Message > Existing Message.</b></cmd></step> -<step><cmd>In the <b>Name</b> field, type a search string to filter the list -or leave the field blank to view all.</cmd></step> -<step><cmd>You can import a message by selecting one of the following options:</cmd> -<info><ul> -<li><b>Workspace</b>: lists the messages available in your workspace.</li> -<li><b>Enclosing Project</b>: lists the messages available in the project -that contains your file.</li> -<li><b>Working Sets</b>: lists the messages available in a specified set of -files. To specify a working set, click <b>Choose</b>. You can select files -from an existing working set or create a new working set. Once you have selected -the files, click <b>OK</b>.</li> -</ul></info></step> -<step><cmd>The messages will be listed. Select one and click <b>OK</b>.</cmd> -</step> -</steps> -<postreq>You can now add parts to your message. Parts are a flexible mechanism -for describing the logical abstract content of a message. For more information, -see <xref format="html" href="../tasks/taddpart.dita" scope="peer">Adding -a part to a message</xref>.</postreq> -</taskbody> -<related-links> -<linklist><title>Related concepts</title> -<link href="../concepts/cwsdled.dita" scope="local"></link> -</linklist> -<linklist><title>Related tasks</title> -<link href="tcrtwsdl.dita" scope="local"></link> -<link href="tedtwsdl.dita" scope="local"></link> -</linklist> -</related-links> -</task> -</task> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddmess.html b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddmess.html deleted file mode 100644 index 1be49ace7..000000000 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddmess.html +++ /dev/null @@ -1,167 +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="Copyright (c) 2000, 2008 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, 2008" /> -<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="Adding a message" /> -<meta name="abstract" content="Messages represent an abstract definition of the data being transmitted. A message consists of logical parts, each of which is associated with a definition within some type system. WSDL messages are top level objects that can be referenced by an operation's input, output and fault elements (within a port type)." /> -<meta name="description" content="Messages represent an abstract definition of the data being transmitted. A message consists of logical parts, each of which is associated with a definition within some type system. WSDL messages are top level objects that can be referenced by an operation's input, output and fault elements (within a port type)." /> -<meta content="Web services, adding WSDL messages, WSDL files, messages" name="DC.subject" /> -<meta content="Web services, adding WSDL messages, WSDL files, messages" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="addingamessage" 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>Adding a message</title> -</head> -<body id="addingamessage"><a name="addingamessage"><!-- --></a> - - -<h1 class="topictitle1">Adding a message</h1> - - - -<div><p>Messages represent an abstract definition of the data being transmitted. -A message consists of logical parts, each of which is associated with a definition -within some type system. WSDL messages are top level objects that can be referenced -by an operation's input, output and fault elements (within a port type).</p> - -<div class="p" /> - -<div class="section"><p>You can create a message using the Outline view by right-clicking -the <strong>Messages</strong> folder and clicking <strong>Add Message</strong>.</p> -<p>To create -a new message for your input, output, or fault element, complete the following -steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>In the Design view, right-click your input, output, or fault element -and click <strong>Set Message > New Message.</strong></span></li> - -<li class="stepexpand"><span>Type the name of the message in the <span class="uicontrol">General</span> pane -of the Properties view.</span> This name should be a unique amongst all -messages defined within the enclosing WSDL document.</li> - -<li class="stepexpand"><span>The new message will appear in the Design view within the port -type.</span></li> - -</ol> - -<div class="section"><p> <strong>Note</strong>: Messages are referenced within a port type (specifically -by an operation's input, output and fault objects). The input, output and -fault objects within a binding do not reference messages. Hence you cannot -create a new message by right clicking on a input, output, or fault within -a binding (these are also known as binding input, binding output and binding -faults).</p> -<div class="tip"><span class="tiptitle">Tip:</span> You can also create a new message for your input, -output, or fault element using the Outline view. Under the <strong>Port Types</strong> folder, -right-click your element and click <strong>Set Message > Add Message</strong>. Your -message will appear in the Outline view under the <strong>Messages</strong> folder.</div> -</div> - -</div> - -<div class="nested1" xml:lang="en-us" id="reusingamessage"><a name="reusingamessage"><!-- --></a> -<h2 class="topictitle2">Reusing a message</h2> - -<div> -<div class="p">To reuse a message for your input, output, or fault element, complete -the following steps:</div> - -<ol> -<li class="stepexpand"><span>In the Design view, right-click your input, output, or fault element -and click <strong>Set Message > Existing Message.</strong></span></li> - -<li class="stepexpand"><span>In the <strong>Name</strong> field, type a search string to filter the list -or leave the field blank to view all</span></li> - -<li class="stepexpand"><span>You can change the scope of the list by selecting one of the following -options:</span> <ul> -<li><strong>Workspace</strong>: lists the messages available in your workspace.</li> - -<li><strong>Enclosing Project</strong>: lists the messages available in the project -that contains your file.</li> - -<li><strong>Current Resource</strong>: lists the messages available in your current -file.</li> - -<li><strong>Working Sets</strong>: lists the messages available in a specified set of -files. To specify a working set, click <strong>Choose</strong>. You can select files -from an existing working set or create a new working set. Once you have selected -the files, click <strong>OK</strong>.</li> - -</ul> -</li> - -<li class="stepexpand"><span>The existing messages will be listed. Select one and click <strong>OK</strong>.</span> -</li> - -</ol> - -<div class="section" /> - -</div> - -</div> - -<div class="nested1" xml:lang="en-us" id="importingamessage"><a name="importingamessage"><!-- --></a> -<h2 class="topictitle2">Importing a message</h2> - -<div> -<div class="p">If you want to import an existing message for your input, output, -or fault element, follow these steps:</div> - -<ol> -<li class="stepexpand"><span>In the Design view, right-click your input, output, or fault element -and click <strong>Set Message > Existing Message.</strong></span></li> - -<li class="stepexpand"><span>In the <strong>Name</strong> field, type a search string to filter the list -or leave the field blank to view all.</span></li> - -<li class="stepexpand"><span>You can import a message by selecting one of the following options:</span> - <ul> -<li><strong>Workspace</strong>: lists the messages available in your workspace.</li> - -<li><strong>Enclosing Project</strong>: lists the messages available in the project -that contains your file.</li> - -<li><strong>Working Sets</strong>: lists the messages available in a specified set of -files. To specify a working set, click <strong>Choose</strong>. You can select files -from an existing working set or create a new working set. Once you have selected -the files, click <strong>OK</strong>.</li> - -</ul> -</li> - -<li class="stepexpand"><span>The messages will be listed. Select one and click <strong>OK</strong>.</span> -</li> - -</ol> - -<div class="section">You can now add parts to your message. Parts are a flexible mechanism -for describing the logical abstract content of a message. For more information, -see <a href="taddpart.html">Adding a part to a message</a>.</div> - -</div> - -<div> -<div class="linklist"><strong>Related concepts</strong><br /> - -<div><a href="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></div></div> - -<div class="linklist"><strong>Related tasks</strong><br /> - -<div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div> -<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> -</div> -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddoper.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddoper.dita deleted file mode 100644 index 8c1c383e3..000000000 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddoper.dita +++ /dev/null @@ -1,56 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2006, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" - "task.dtd"> -<task id="taddoper" xml:lang="en-us"> -<title>Adding an operation</title> -<shortdesc>An operation names the operation and lists the expected inputs -and outputs. The operation element may also contain a fault sub-element that -describes any error data the operation may return.</shortdesc> -<prolog><metadata> -<keywords><indexterm>Web services<indexterm>adding WSDL operations</indexterm></indexterm> -<indexterm>WSDL files<indexterm>operations</indexterm></indexterm></keywords> -</metadata></prolog> -<taskbody> -<context>Using these, you can declare four transmission primitives that an -endpoint can support:<ul> -<li> <b>One-way</b>: the endpoint receives a message.</li> -<li> <b>Request-response</b>: the endpoint receives a message, and sends a -correlated message.</li> -<li> <b>Solicit-response</b>: the endpoint sends a message, and receives a -correlated message.</li> -<li> <b>Notification</b>: the endpoint sends a message.</li> -</ul><p>You can add an operation to a port type or a port binding.</p><p>To -add an operation to a port type, complete the following steps:</p></context> -<steps> -<step><cmd>In the Design view, right-click your port type.</cmd><info>Click <b>Add -Operation</b>. To select the new operation, click the operation in the port -type object.</info></step> -<step><cmd>In the Properties view, click the <b>General</b> pane.</cmd></step> -<step><cmd>In the <b>Name</b> field, type the name of the operation.</cmd> -</step> -<step><cmd>Right click on the operation to add input, output or fault objects.</cmd> -<info>Depending on an operation's inputs and outputs it can be classified -as follows:<ul> -<li><b>One way operation</b>: input </li> -<li><b>Request response operation</b>: input, output </li> -<li><b> Solicit response operation</b>: output, input </li> -<li><b>Notification operation</b>: output</li> -</ul></info></step> -<step><cmd>In the Properties view, type any information about the operation -you wish the user to read in the <b>Documentation</b> pane.</cmd></step> -</steps> -<result><p> <b>Tip</b>: You can also create a new operation for your port -type using the Outline view. Right click on a port type in the <uicontrol>Port -Type</uicontrol> folder and select <uicontrol>Add Operation</uicontrol>.</p></result> -</taskbody> -<related-links> -<linklist><title>Related concepts</title> -<link href="../concepts/cwsdled.dita" scope="local"></link> -</linklist> -<linklist><title>Related tasks</title> -<link href="tcrtwsdl.dita" scope="local"></link> -<link href="tedtwsdl.dita" scope="local"></link> -</linklist> -</related-links> -</task> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddoper.html b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddoper.html deleted file mode 100644 index d7914b36d..000000000 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddoper.html +++ /dev/null @@ -1,102 +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="Copyright (c) 2000, 2008 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, 2008" /> -<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="Adding an operation" /> -<meta name="abstract" content="An operation names the operation and lists the expected inputs and outputs. The operation element may also contain a fault sub-element that describes any error data the operation may return." /> -<meta name="description" content="An operation names the operation and lists the expected inputs and outputs. The operation element may also contain a fault sub-element that describes any error data the operation may return." /> -<meta content="Web services, adding WSDL operations, WSDL files, operations" name="DC.subject" /> -<meta content="Web services, adding WSDL operations, WSDL files, operations" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cwsdled.html" /> -<meta scheme="URI" name="DC.Relation" content="tcrtwsdl.html" /> -<meta scheme="URI" name="DC.Relation" content="tedtwsdl.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddoper" 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>Adding an operation</title> -</head> -<body id="taddoper"><a name="taddoper"><!-- --></a> - - -<h1 class="topictitle1">Adding an operation</h1> - - - -<div><p>An operation names the operation and lists the expected inputs -and outputs. The operation element may also contain a fault sub-element that -describes any error data the operation may return.</p> - -<div class="section">Using these, you can declare four transmission primitives that an -endpoint can support:<ul> -<li> <strong>One-way</strong>: the endpoint receives a message.</li> - -<li> <strong>Request-response</strong>: the endpoint receives a message, and sends a -correlated message.</li> - -<li> <strong>Solicit-response</strong>: the endpoint sends a message, and receives a -correlated message.</li> - -<li> <strong>Notification</strong>: the endpoint sends a message.</li> - -</ul> -<p>You can add an operation to a port type or a port binding.</p> -<p>To -add an operation to a port type, complete the following steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>In the Design view, right-click your port type.</span> Click <strong>Add -Operation</strong>. To select the new operation, click the operation in the port -type object.</li> - -<li class="stepexpand"><span>In the Properties view, click the <strong>General</strong> pane.</span></li> - -<li class="stepexpand"><span>In the <strong>Name</strong> field, type the name of the operation.</span> -</li> - -<li class="stepexpand"><span>Right click on the operation to add input, output or fault objects.</span> - Depending on an operation's inputs and outputs it can be classified -as follows:<ul> -<li><strong>One way operation</strong>: input </li> - -<li><strong>Request response operation</strong>: input, output </li> - -<li><strong> Solicit response operation</strong>: output, input </li> - -<li><strong>Notification operation</strong>: output</li> - -</ul> -</li> - -<li class="stepexpand"><span>In the Properties view, type any information about the operation -you wish the user to read in the <strong>Documentation</strong> pane.</span></li> - -</ol> - -<div class="section"><p> <strong>Tip</strong>: You can also create a new operation for your port -type using the Outline view. Right click on a port type in the <span class="uicontrol">Port -Type</span> folder and select <span class="uicontrol">Add Operation</span>.</p> -</div> - -</div> - -<div> -<div class="linklist"><strong>Related concepts</strong><br /> - -<div><a href="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></div></div> - -<div class="linklist"><strong>Related tasks</strong><br /> - -<div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div> -<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddpart.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddpart.dita deleted file mode 100644 index 3c287bc8c..000000000 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddpart.dita +++ /dev/null @@ -1,48 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2006, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" - "task.dtd"> -<task id="taddpart" xml:lang="en-us"> -<title>Adding a part to a message</title> -<shortdesc>All messages contain one or more parts. Parts are a flexible mechanism -for describing the logical abstract content of a message. The message definition -associates each part with a type using a message-typing attribute.</shortdesc> -<prolog><metadata> -<keywords><indexterm>Web services<indexterm>adding WSDL message parts</indexterm></indexterm> -<indexterm>WSDL files<indexterm>message parts</indexterm></indexterm></keywords> -</metadata></prolog> -<taskbody> -<context><p>To add a part to a message, complete the following steps:</p></context> -<steps> -<step><cmd>In Design view, right-click an input, output, or fault object and -click <b>Add Part</b>.</cmd><stepresult>The part is added to the input, output, -or fault's message reference. To select the part, click the part in the port -type object.</stepresult></step> -<step><cmd>In the Properties view, click the <b>General</b> pane.</cmd></step> -<step><cmd>In the <b>Name</b> field, type the name of the part.</cmd></step> -<step><cmd>Your part can refer to either a <b>Type</b> or an <b>Element</b>.</cmd> -<info>Select the appropriate option as the <b>Reference Kind</b> .</info> -</step> -<step><cmd>If you selected <b>Type</b>, you now have the option of selecting -an XML schema data type from the <b>Type</b> drop down list.</cmd><info>The -list of types comes from any available referenced XML schemas.</info></step> -<step><cmd>If you selected <b>Element</b> , you now have the option of selecting -an XML schema element from the <b>Element</b> drop down list.</cmd><info>The -list of elements comes from any available referenced XML schemas.</info></step> -</steps> -<result><note type="tip"> You can also create a new part for your message -using the Outline view. Under the <b>Messages</b> folder, right-click your -element and click <b>Add Part</b>. Your part will automatically appear in -the Outline view (under the <b>Messages</b> folder), but it will only appear -in the Design view if the message you added it to currently does.</note></result> -</taskbody> -<related-links> -<linklist><title>Related concepts</title> -<link href="../concepts/cwsdled.dita" scope="local"></link> -</linklist> -<linklist><title>Related tasks</title> -<link href="tcrtwsdl.dita" scope="local"></link> -<link href="tedtwsdl.dita" scope="local"></link> -</linklist> -</related-links> -</task> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddpart.html b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddpart.html deleted file mode 100644 index 737160658..000000000 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddpart.html +++ /dev/null @@ -1,84 +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="Copyright (c) 2000, 2008 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, 2008" /> -<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="Adding a part to a message" /> -<meta name="abstract" content="All messages contain one or more parts. Parts are a flexible mechanism for describing the logical abstract content of a message. The message definition associates each part with a type using a message-typing attribute." /> -<meta name="description" content="All messages contain one or more parts. Parts are a flexible mechanism for describing the logical abstract content of a message. The message definition associates each part with a type using a message-typing attribute." /> -<meta content="Web services, adding WSDL message parts, WSDL files, message parts" name="DC.subject" /> -<meta content="Web services, adding WSDL message parts, WSDL files, message parts" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cwsdled.html" /> -<meta scheme="URI" name="DC.Relation" content="tcrtwsdl.html" /> -<meta scheme="URI" name="DC.Relation" content="tedtwsdl.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddpart" 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>Adding a part to a message</title> -</head> -<body id="taddpart"><a name="taddpart"><!-- --></a> - - -<h1 class="topictitle1">Adding a part to a message</h1> - - - -<div><p>All messages contain one or more parts. Parts are a flexible mechanism -for describing the logical abstract content of a message. The message definition -associates each part with a type using a message-typing attribute.</p> - -<div class="section"><p>To add a part to a message, complete the following steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>In Design view, right-click an input, output, or fault object and -click <strong>Add Part</strong>.</span> The part is added to the input, output, -or fault's message reference. To select the part, click the part in the port -type object.</li> - -<li class="stepexpand"><span>In the Properties view, click the <strong>General</strong> pane.</span></li> - -<li class="stepexpand"><span>In the <strong>Name</strong> field, type the name of the part.</span></li> - -<li class="stepexpand"><span>Your part can refer to either a <strong>Type</strong> or an <strong>Element</strong>.</span> - Select the appropriate option as the <strong>Reference Kind</strong> . -</li> - -<li class="stepexpand"><span>If you selected <strong>Type</strong>, you now have the option of selecting -an XML schema data type from the <strong>Type</strong> drop down list.</span> The -list of types comes from any available referenced XML schemas.</li> - -<li class="stepexpand"><span>If you selected <strong>Element</strong> , you now have the option of selecting -an XML schema element from the <strong>Element</strong> drop down list.</span> The -list of elements comes from any available referenced XML schemas.</li> - -</ol> - -<div class="section"><div class="tip"><span class="tiptitle">Tip:</span> You can also create a new part for your message -using the Outline view. Under the <strong>Messages</strong> folder, right-click your -element and click <strong>Add Part</strong>. Your part will automatically appear in -the Outline view (under the <strong>Messages</strong> folder), but it will only appear -in the Design view if the message you added it to currently does.</div> -</div> - -</div> - -<div> -<div class="linklist"><strong>Related concepts</strong><br /> - -<div><a href="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></div></div> - -<div class="linklist"><strong>Related tasks</strong><br /> - -<div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div> -<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddport.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddport.dita deleted file mode 100644 index bae01dc09..000000000 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddport.dita +++ /dev/null @@ -1,62 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2006, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" - "task.dtd"> -<task id="taddport" xml:lang="en-us"> -<title>Adding a port to a service</title> -<shortdesc>A port defines an individual endpoint by specifying a single address -for a binding. The port contains a 'binding' attribute that references a binding -and an address element that provides a specification for the endpoint.</shortdesc> -<prolog><metadata> -<keywords><indexterm>Web services<indexterm>adding WSDL ports</indexterm></indexterm> -<indexterm>WSDL files<indexterm>ports</indexterm></indexterm></keywords> -</metadata></prolog> -<taskbody> -<context><p>Services are used to group sets of related ports together. Ports -within a service have the following relationship:</p><ul> -<li>None of the ports communicate with each other (for example, the output -of one port is not the input of another).</li> -<li>If a service has several ports that share a port type, but employ different -bindings or addresses, the ports are alternatives. Each port provides semantically -equivalent behavior (within the transport and message format limitations imposed -by each binding).</li> -<li>You can determine a service's port types by examining its ports. Using -this information, a user can determine if a given machine supports all the -operations needed to complete a given task.</li> -</ul><p>To add a port to a service, complete the following steps:</p></context> -<steps> -<step><cmd>In the Design view, right-click the service you want to add a port -to, then click <b>Add Port.</b> </cmd></step> -<step><cmd>Fill in the <b>Name</b> for the port.</cmd><info>The name of the -port should provide it with a unique name amongst all the ports defined within -the service.</info></step> -<step><cmd>Select a <b>Binding</b> and <uicontrol>Protocol</uicontrol> for -the port, and enter the address of the port into the <uicontrol>Address</uicontrol> field. -Click <uicontrol>Finish</uicontrol>.</cmd><info>To select the new port, click -the port in the service object. You can change the information you entered -about this port any time in the <uicontrol>General</uicontrol> pane.</info> -</step> -<step><cmd>Type any information about the port you want the user to read in -the <b>Documentation</b> pane of the Properties view.</cmd></step> -<step><cmd>To manage extensions, click the <b>Extensions</b> pane. You can -either add, sort, or remove extensions. </cmd></step> -</steps> -<result><p>You can create a new binding for your port, re-use an existing -one, or import one. A <b>Binding</b> defines the message format and protocol -details for operations and messages defined by a particular port type. For -more information, see <xref format="html" href="../tasks/tsetbind.dita" scope="peer">Setting -a binding</xref> .</p><p>You can also create a port using the Outline view -by right-clicking your service under the <b>Services</b> folder and clicking <b>Add -Port</b>. Your port (regardless of which view you create it in) will appear -in both the Design view and the Outline view.</p></result> -</taskbody> -<related-links> -<linklist><title>Related concepts</title> -<link href="../concepts/cwsdled.dita" scope="local"></link> -</linklist> -<linklist><title>Related tasks</title> -<link href="tcrtwsdl.dita" scope="local"></link> -<link href="tedtwsdl.dita" scope="local"></link> -</linklist> -</related-links> -</task> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddport.html b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddport.html deleted file mode 100644 index 1c52f98cc..000000000 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddport.html +++ /dev/null @@ -1,102 +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="Copyright (c) 2000, 2008 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, 2008" /> -<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="Adding a port to a service" /> -<meta name="abstract" content="A port defines an individual endpoint by specifying a single address for a binding. The port contains a 'binding' attribute that references a binding and an address element that provides a specification for the endpoint." /> -<meta name="description" content="A port defines an individual endpoint by specifying a single address for a binding. The port contains a 'binding' attribute that references a binding and an address element that provides a specification for the endpoint." /> -<meta content="Web services, adding WSDL ports, WSDL files, ports" name="DC.subject" /> -<meta content="Web services, adding WSDL ports, WSDL files, ports" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cwsdled.html" /> -<meta scheme="URI" name="DC.Relation" content="tcrtwsdl.html" /> -<meta scheme="URI" name="DC.Relation" content="tedtwsdl.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddport" 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>Adding a port to a service</title> -</head> -<body id="taddport"><a name="taddport"><!-- --></a> - - -<h1 class="topictitle1">Adding a port to a service</h1> - - - -<div><p>A port defines an individual endpoint by specifying a single address -for a binding. The port contains a 'binding' attribute that references a binding -and an address element that provides a specification for the endpoint.</p> - -<div class="section"><p>Services are used to group sets of related ports together. Ports -within a service have the following relationship:</p> -<ul> -<li>None of the ports communicate with each other (for example, the output -of one port is not the input of another).</li> - -<li>If a service has several ports that share a port type, but employ different -bindings or addresses, the ports are alternatives. Each port provides semantically -equivalent behavior (within the transport and message format limitations imposed -by each binding).</li> - -<li>You can determine a service's port types by examining its ports. Using -this information, a user can determine if a given machine supports all the -operations needed to complete a given task.</li> - -</ul> -<p>To add a port to a service, complete the following steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>In the Design view, right-click the service you want to add a port -to, then click <strong>Add Port.</strong> </span></li> - -<li class="stepexpand"><span>Fill in the <strong>Name</strong> for the port.</span> The name of the -port should provide it with a unique name amongst all the ports defined within -the service.</li> - -<li class="stepexpand"><span>Select a <strong>Binding</strong> and <span class="uicontrol">Protocol</span> for -the port, and enter the address of the port into the <span class="uicontrol">Address</span> field. -Click <span class="uicontrol">Finish</span>.</span> To select the new port, click -the port in the service object. You can change the information you entered -about this port any time in the <span class="uicontrol">General</span> pane. -</li> - -<li class="stepexpand"><span>Type any information about the port you want the user to read in -the <strong>Documentation</strong> pane of the Properties view.</span></li> - -<li class="stepexpand"><span>To manage extensions, click the <strong>Extensions</strong> pane. You can -either add, sort, or remove extensions. </span></li> - -</ol> - -<div class="section"><p>You can create a new binding for your port, re-use an existing -one, or import one. A <strong>Binding</strong> defines the message format and protocol -details for operations and messages defined by a particular port type. For -more information, see <a href="tsetbind.html">Sethtml a binding</a> .</p> -<p>You can also create a port using the Outline view -by right-clicking your service under the <strong>Services</strong> folder and clicking <strong>Add -Port</strong>. Your port (regardless of which view you create it in) will appear -in both the Design view and the Outline view.</p> -</div> - -</div> - -<div> -<div class="linklist"><strong>Related concepts</strong><br /> - -<div><a href="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></div></div> - -<div class="linklist"><strong>Related tasks</strong><br /> - -<div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div> -<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddsrvc.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddsrvc.dita deleted file mode 100644 index 193f226f5..000000000 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddsrvc.dita +++ /dev/null @@ -1,43 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2006, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" - "task.dtd"> -<task id="taddsrvc" xml:lang="en-us"> -<title>Adding a service</title> -<shortdesc>The <systemoutput>service</systemoutput> element is a collection -of related ports and specifies the location of the service.</shortdesc> -<prolog><metadata> -<keywords><indexterm>Web services<indexterm>adding services to WSDL</indexterm></indexterm> -<indexterm>WSDL files<indexterm>services</indexterm></indexterm></keywords> -</metadata></prolog> -<taskbody> -<context><p>To create a new service, complete the following steps:</p></context> -<steps> -<step><cmd>In the Design view, right-click in any blank space and click <b>Add -Service</b>. To select the new service, click the service object.</cmd></step> -<step><cmd>In the Properties view, click the <b>General</b> pane. In the <b>Name</b> field, -type the name of the service.</cmd><info>The name of the service provides -it with a unique name amongst all the services defined within in the enclosing -WSDL document.</info></step> -<step><cmd>Type any information about the service you want the user to read -in the <b>Documentation</b> pane.</cmd></step> -<step><cmd>To manage extensions, click the <b>Extensions</b> pane. You can -either add, sort, or remove extensions.<draft-comment> Refer to the related -tasks for more details. Add link to the XSD Editor plugin topic for "Adding -extension components"</draft-comment></cmd></step> -</steps> -<result><p> <b>Tip</b>: You can also create a service using the Outline view -by right-clicking the <b>Services</b> folder and clicking <b>Add Service</b>.</p><p>You -can now add a port to your service. A port defines an individual endpoint -by specifying a single address for a binding.</p></result> -</taskbody> -<related-links> -<linklist><title>Related concepts</title> -<link href="../concepts/cwsdled.dita" scope="local"></link> -</linklist> -<linklist><title>Related tasks</title> -<link href="tcrtwsdl.dita" scope="local"></link> -<link href="tedtwsdl.dita" scope="local"></link> -</linklist> -</related-links> -</task> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddsrvc.html b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddsrvc.html deleted file mode 100644 index 3493106bb..000000000 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddsrvc.html +++ /dev/null @@ -1,76 +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="Copyright (c) 2000, 2008 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, 2008" /> -<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="Adding a service" /> -<meta name="abstract" content="The service element is a collection of related ports and specifies the location of the service." /> -<meta name="description" content="The service element is a collection of related ports and specifies the location of the service." /> -<meta content="Web services, adding services to WSDL, WSDL files, services" name="DC.subject" /> -<meta content="Web services, adding services to WSDL, WSDL files, services" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cwsdled.html" /> -<meta scheme="URI" name="DC.Relation" content="tcrtwsdl.html" /> -<meta scheme="URI" name="DC.Relation" content="tedtwsdl.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddsrvc" 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>Adding a service</title> -</head> -<body id="taddsrvc"><a name="taddsrvc"><!-- --></a> - - -<h1 class="topictitle1">Adding a service</h1> - - - -<div><p>The <tt class="sysout">service</tt> element is a collection -of related ports and specifies the location of the service.</p> - -<div class="section"><p>To create a new service, complete the following steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>In the Design view, right-click in any blank space and click <strong>Add -Service</strong>. To select the new service, click the service object.</span></li> - -<li class="stepexpand"><span>In the Properties view, click the <strong>General</strong> pane. In the <strong>Name</strong> field, -type the name of the service.</span> The name of the service provides -it with a unique name amongst all the services defined within in the enclosing -WSDL document.</li> - -<li class="stepexpand"><span>Type any information about the service you want the user to read -in the <strong>Documentation</strong> pane.</span></li> - -<li class="stepexpand"><span>To manage extensions, click the <strong>Extensions</strong> pane. You can -either add, sort, or remove extensions.</span></li> - -</ol> - -<div class="section"><p> <strong>Tip</strong>: You can also create a service using the Outline view -by right-clicking the <strong>Services</strong> folder and clicking <strong>Add Service</strong>.</p> -<p>You -can now add a port to your service. A port defines an individual endpoint -by specifying a single address for a binding.</p> -</div> - -</div> - -<div> -<div class="linklist"><strong>Related concepts</strong><br /> - -<div><a href="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></div></div> - -<div class="linklist"><strong>Related tasks</strong><br /> - -<div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div> -<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtimpt.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtimpt.dita deleted file mode 100644 index abdaff536..000000000 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtimpt.dita +++ /dev/null @@ -1,51 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2006, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" - "task.dtd"> -<task id="tcrtimpt" xml:lang="en-us"> -<title>Creating an import statement</title> -<shortdesc>The import statement is used to import other WSDL documents or -XML schemas into your WSDL document. This enables you to have more modular -WSDL documents. The use of the <b>import</b> statement allows the separation -of the different elements of a service definition into independent documents, -which can then be imported as needed. This technique helps in writing clearer -service definitions, by separating the definitions according to their level -of abstraction.</shortdesc> -<prolog><metadata> -<keywords><indexterm>Web services<indexterm>adding WSDL import statements</indexterm></indexterm> -<indexterm>WSDL files<indexterm>import statements</indexterm></indexterm> -</keywords> -</metadata></prolog> -<taskbody> -<context><p>To create an import statement, complete the following steps:</p></context> -<steps> -<step><cmd>In the Outline view, right-click the <b>Imports</b> folder and -click <b>Add Import.</b> Select your new import statement.</cmd></step> -<step><cmd>In the Properties view, click the <b>General</b> pane.</cmd></step> -<step><cmd>Click the icon to the right of the <b>Location</b> field to open -the Select File window.<uicontrol></uicontrol>.</cmd></step> -<step><cmd>Select a WSDL file or XML Schema to import by doing one of the -following:</cmd><info><ul> -<li>Select a file from another project in the workspace in the <uicontrol>Workspace -Files</uicontrol> section.</li> -<li>Click <uicontrol>Import Files</uicontrol> and then <uicontrol>Browse</uicontrol> to -find and select files outside the workspace. Click <uicontrol>Finish</uicontrol> after -completing this Import wizard.</li> -</ul>Click <uicontrol>OK</uicontrol>.</info></step> -<step><cmd>Type any information about the import statement you want the user -to read in the <b>Documentation</b> pane.</cmd></step> -</steps> -<result>Once you specify the location of the document you wish to import, -the import object's label changes to reflect the specified location. Imported -WSDL components may now be visible within the editor.</result> -</taskbody> -<related-links> -<linklist><title>Related concepts</title> -<link href="../concepts/cwsdled.dita" scope="local"></link> -</linklist> -<linklist><title>Related tasks</title> -<link href="tcrtwsdl.dita" scope="local"></link> -<link href="tedtwsdl.dita" scope="local"></link> -</linklist> -</related-links> -</task> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtimpt.html b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtimpt.html deleted file mode 100644 index ca7f9c29d..000000000 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtimpt.html +++ /dev/null @@ -1,87 +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="Copyright (c) 2000, 2008 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, 2008" /> -<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="Creating an import statement" /> -<meta name="abstract" content="The import statement is used to import other WSDL documents or XML schemas into your WSDL document. This enables you to have more modular WSDL documents. The use of the import statement allows the separation of the different elements of a service definition into independent documents, which can then be imported as needed. This technique helps in writing clearer service definitions, by separating the definitions according to their level of abstraction." /> -<meta name="description" content="The import statement is used to import other WSDL documents or XML schemas into your WSDL document. This enables you to have more modular WSDL documents. The use of the import statement allows the separation of the different elements of a service definition into independent documents, which can then be imported as needed. This technique helps in writing clearer service definitions, by separating the definitions according to their level of abstraction." /> -<meta content="Web services, adding WSDL import statements, WSDL files, import statements" name="DC.subject" /> -<meta content="Web services, adding WSDL import statements, WSDL files, import statements" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cwsdled.html" /> -<meta scheme="URI" name="DC.Relation" content="tcrtwsdl.html" /> -<meta scheme="URI" name="DC.Relation" content="tedtwsdl.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tcrtimpt" 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>Creating an import statement</title> -</head> -<body id="tcrtimpt"><a name="tcrtimpt"><!-- --></a> - - -<h1 class="topictitle1">Creating an import statement</h1> - - - -<div><p>The import statement is used to import other WSDL documents or -XML schemas into your WSDL document. This enables you to have more modular -WSDL documents. The use of the <strong>import</strong> statement allows the separation -of the different elements of a service definition into independent documents, -which can then be imported as needed. This technique helps in writing clearer -service definitions, by separating the definitions according to their level -of abstraction.</p> - -<div class="section"><p>To create an import statement, complete the following steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>In the Outline view, right-click the <strong>Imports</strong> folder and -click <strong>Add Import.</strong> Select your new import statement.</span></li> - -<li class="stepexpand"><span>In the Properties view, click the <strong>General</strong> pane.</span></li> - -<li class="stepexpand"><span>Click the icon to the right of the <strong>Location</strong> field to open -the Select File window.<span class="uicontrol" />.</span></li> - -<li class="stepexpand"><span>Select a WSDL file or XML Schema to import by doing one of the -following:</span> <ul> -<li>Select a file from another project in the workspace in the <span class="uicontrol">Workspace -Files</span> section.</li> - -<li>Click <span class="uicontrol">Import Files</span> and then <span class="uicontrol">Browse</span> to -find and select files outside the workspace. Click <span class="uicontrol">Finish</span> after -completing this Import wizard.</li> - -</ul> -Click <span class="uicontrol">OK</span>.</li> - -<li class="stepexpand"><span>Type any information about the import statement you want the user -to read in the <strong>Documentation</strong> pane.</span></li> - -</ol> - -<div class="section">Once you specify the location of the document you wish to import, -the import object's label changes to reflect the specified location. Imported -WSDL components may now be visible within the editor.</div> - -</div> - -<div> -<div class="linklist"><strong>Related concepts</strong><br /> - -<div><a href="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></div></div> - -<div class="linklist"><strong>Related tasks</strong><br /> - -<div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div> -<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrttype.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrttype.dita deleted file mode 100644 index a3cfdecba..000000000 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrttype.dita +++ /dev/null @@ -1,37 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2006, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" - "task.dtd"> -<task id="tcrttype" xml:lang="en-us"> -<title>Creating a new type for your WSDL file</title> -<shortdesc>Types describe all the data types used between the client and server. -WSDL is not tied exclusively to a specific typing system, but it uses the -W3C XML Schema specification as its default choice.</shortdesc> -<prolog><metadata> -<keywords><indexterm>Web services<indexterm>creating WSDL types</indexterm></indexterm> -<indexterm>WSDL files<indexterm>types</indexterm></indexterm></keywords> -</metadata></prolog> -<taskbody> -<context><p>WSDL allows type systems to be added via extensibility elements. -An extensibility element may appear under the <b>types</b> element to identify -the type definition system being used and to provide an XML container element -for the type definitions.</p><p>To add an XSD type or element to your WSDL -file: </p></context> -<steps-unordered> -<step><cmd>In the Design view, click the arrow icon to the right of the port -type object to open that operation in the XML schema editor.</cmd></step> -</steps-unordered> -<result><p>For more information about XML schemas, see the <xref format="html" -href="/../../org.eclipse.wst.xsdeditor.doc.user/topics/cxmlsced.dita" scope="peer">XML -schema editor documentation</xref> for links to online resources.</p></result> -</taskbody> -<related-links> -<linklist><title>Related concepts</title> -<link href="../concepts/cwsdled.dita" scope="local"></link> -</linklist> -<linklist><title>Related tasks</title> -<link href="tcrtwsdl.dita" scope="local"></link> -<link href="tedtwsdl.dita" scope="local"></link> -</linklist> -</related-links> -</task> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrttype.html b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrttype.html deleted file mode 100644 index 250d89a1f..000000000 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrttype.html +++ /dev/null @@ -1,66 +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="Copyright (c) 2000, 2008 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, 2008" /> -<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="Creating a new type for your WSDL file" /> -<meta name="abstract" content="Types describe all the data types used between the client and server. WSDL is not tied exclusively to a specific typing system, but it uses the W3C XML Schema specification as its default choice." /> -<meta name="description" content="Types describe all the data types used between the client and server. WSDL is not tied exclusively to a specific typing system, but it uses the W3C XML Schema specification as its default choice." /> -<meta content="Web services, creating WSDL types, WSDL files, types" name="DC.subject" /> -<meta content="Web services, creating WSDL types, WSDL files, types" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cwsdled.html" /> -<meta scheme="URI" name="DC.Relation" content="tcrtwsdl.html" /> -<meta scheme="URI" name="DC.Relation" content="tedtwsdl.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tcrttype" 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>Creating a new type for your WSDL file</title> -</head> -<body id="tcrttype"><a name="tcrttype"><!-- --></a> - - -<h1 class="topictitle1">Creating a new type for your WSDL file</h1> - - - -<div><p>Types describe all the data types used between the client and server. -WSDL is not tied exclusively to a specific typing system, but it uses the -W3C XML Schema specification as its default choice.</p> - -<div class="section"><p>WSDL allows type systems to be added via extensibility elements. -An extensibility element may appear under the <strong>types</strong> element to identify -the type definition system being used and to provide an XML container element -for the type definitions.</p> -<p>To add an XSD type or element to your WSDL -file: </p> -</div> - - -<div class="p"><span>In the Design view, click the arrow icon to the right of the port -type object to open that operation in the XML schema editor.</span></div> - - -<div class="section"><p>For more information about XML schemas, see the <a href="/../../org.eclipse.wst.xsdeditor.doc.user/topics/cxmlsced.dita">XML schema editor documentation</a> for links to online resources.</p> -</div> - -</div> - -<div> -<div class="linklist"><strong>Related concepts</strong><br /> - -<div><a href="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></div></div> - -<div class="linklist"><strong>Related tasks</strong><br /> - -<div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div> -<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtwsdl.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtwsdl.dita deleted file mode 100644 index 8292a70e8..000000000 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtwsdl.dita +++ /dev/null @@ -1,95 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2006, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" - "task.dtd"> -<task id="tcrtwsdl" xml:lang="en-us"> -<title>Creating a new WSDL file</title> -<shortdesc>You can create a new, empty WSDL file, then edit it using the WSDL -editor.</shortdesc> -<prolog><metadata> -<keywords><indexterm>WSDL files<indexterm>creating</indexterm></indexterm> -<indexterm>Web services<indexterm>creating WSDL files</indexterm></indexterm> -</keywords> -</metadata></prolog> -<taskbody> -<context><p>To create a WSDL file, complete the following steps:</p></context> -<steps> -<step><cmd>Create a project to contain the WSDL document.</cmd><info>It does -not matter what kind of project you create.</info></step> -<step><cmd>In the workbench, click <menucascade><uicontrol>File</uicontrol> -<uicontrol>New</uicontrol><uicontrol>Other</uicontrol></menucascade> and select <menucascade> -<uicontrol>Web Services</uicontrol><uicontrol>WSDL</uicontrol></menucascade>.</cmd> -<info>Click <uicontrol>Next</uicontrol>.</info></step> -<step><cmd>Select the project or folder that will contain the WSDL file.</cmd> -<info>In the <uicontrol>File name</uicontrol> field, type the name of the -WSDL file. The name of your XML file must end in <systemoutput>.wsdl</systemoutput></info> -</step> -<step><cmd>Click <uicontrol>Next</uicontrol> and enter the following information -on the next page of the wizard:</cmd> -<substeps> -<substep><cmd>A <uicontrol>Target namespace</uicontrol> for the WSDL file -or accept the default (<codeph>http://www.example.org/<i>MyWSDLFile</i>/</codeph>).</cmd> -<info>The target namespace is used for the names of messages and the port -type, binding and service defined in the WSDL file. The value must take the -form of a valid URI (for example, <codeph>http://www.mycompany.com/myservice/</codeph>)</info> -</substep> -<substep><cmd>The <uicontrol>Prefix</uicontrol> associated with the target -namespace.</cmd></substep> -<substep><cmd>Select <uicontrol>Create WSDL Skeleton</uicontrol> if you want -the wizard to create the skeleton of the WSDL file.</cmd><info>This will generate -the WSDL elements required for your service, including bindings, ports and -messages. You can then modify these to meet the requirements of your Web service -.</info></substep> -<substep><cmd>If you have chosen to create a WSDL skeleton, select the binding -options you want to use in the <uicontrol>Protocol</uicontrol> drop down. -The options are SOAP and HTTP. Use the SOAP protocol when you want to exchange -structured and typed information. Use the HTTP protocol when you want your -application client to just request or update information.</cmd></substep> -<substep><cmd></cmd><info>If you select SOAP you can then select the encoding -style you want to use:<ul> -<li><uicontrol>document literal</uicontrol>. Document style messages, literal -encoding. Use this style of binding when you want to send SOAP messages that -can be validated by an XML validator. All the data types in the SOAP message -body are defined in a schema, so the WSDL parts must point to schema elements. </li> -<li><uicontrol>rpc literal</uicontrol>. RPC style messages, literal encoding. -Use this style of binding when you want to specify the operation method names -in your SOAP messages so a server can dispatch the specified methods. Data -types must be defined, so the WSDL parts must point to XSD types.</li> -<li><uicontrol>rpc encoded</uicontrol>. RPC style messages and SOAP encoding. -Use this style of binding when you want to encode data graphs in your SOAP -messages so a server can deserialize the object data. Data types must be -defined, so the WSDL parts must point to XSD types.</li> -</ul></info></substep> -<substep><cmd></cmd><info>If you select HTTP you can select whether to create -an HTTP getter or setter.<ul> -<li><uicontrol>HTTP GET</uicontrol>. A GET request fetches data from a Web -server based on an URL value and a set of HTTP headers. Use this method when -you want to retrieve information specified in the request. </li> -<li><uicontrol>HTTP POST</uicontrol>. A POST request sends additional data -to the server, specified after the URL and the headers. Use this method when -you want to send data enclosed in the body of the request.</li> -</ul></info></substep> -</substeps> -</step> -<step><cmd>Click <uicontrol>Finish</uicontrol>.</cmd><info>The WSDL file -opens in the WSDL editor.</info></step> -</steps> -<result><p>If you created a WSDL file with a skeleton using SOAP bindings, -it should look similar to the following:</p><p><image alt="Image of a WSDL skeleton using SOAP bindings" -href="../images/soapskel.gif" placement="break"></image></p><p>If you created -a WSDL file with a skeleton using HTTP bindings, it should look similar to -the following:</p><p><image alt="Image of a WSDL skeleton using HTTP bindings" -href="../images/httpskel.gif" placement="break"></image></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="../concepts/cwsdled.dita" scope="local"></link> -</linklist> -<linklist><title>Related tasks</title> -<link href="timpwsdl.dita" scope="local"></link> -<link href="tedtwsdl.dita" scope="local"></link> -</linklist> -</related-links> -</task> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtwsdl.html b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtwsdl.html deleted file mode 100644 index 4fe908b52..000000000 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtwsdl.html +++ /dev/null @@ -1,144 +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="Copyright (c) 2000, 2008 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, 2008" /> -<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="Creating a new WSDL file" /> -<meta name="abstract" content="You can create a new, empty WSDL file, then edit it using the WSDL editor." /> -<meta name="description" content="You can create a new, empty WSDL file, then edit it using the WSDL editor." /> -<meta content="WSDL files, creating, Web services, creating WSDL files" name="DC.subject" /> -<meta content="WSDL files, creating, Web services, creating WSDL files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.html" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cwsdled.html" /> -<meta scheme="URI" name="DC.Relation" content="timpwsdl.html" /> -<meta scheme="URI" name="DC.Relation" content="tedtwsdl.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tcrtwsdl" 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>Creating a new WSDL file</title> -</head> -<body id="tcrtwsdl"><a name="tcrtwsdl"><!-- --></a> - - -<h1 class="topictitle1">Creating a new WSDL file</h1> - - - -<div><p>You can create a new, empty WSDL file, then edit it using the WSDL -editor.</p> - -<div class="section"><p>To create a WSDL file, complete the following steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>Create a project to contain the WSDL document.</span> It does -not matter what kind of project you create.</li> - -<li class="stepexpand"><span>In the workbench, click <span class="menucascade"><span class="uicontrol">File</span> - > <span class="uicontrol">New</span> > <span class="uicontrol">Other</span></span> and select <span class="menucascade"> -<span class="uicontrol">Web Services</span> > <span class="uicontrol">WSDL</span></span>.</span> - Click <span class="uicontrol">Next</span>.</li> - -<li class="stepexpand"><span>Select the project or folder that will contain the WSDL file.</span> - In the <span class="uicontrol">File name</span> field, type the name of the -WSDL file. The name of your XML file must end in <tt class="sysout">.wsdl</tt> -</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Next</span> and enter the following information -on the next page of the wizard:</span> -<ol type="a"> -<li class="substepexpand"><span>A <span class="uicontrol">Target namespace</span> for the WSDL file -or accept the default (<samp class="codeph">http://www.example.org/<em>MyWSDLFile</em>/</samp>).</span> - The target namespace is used for the names of messages and the port -type, binding and service defined in the WSDL file. The value must take the -form of a valid URI (for example, <samp class="codeph">http://www.mycompany.com/myservice/</samp>) -</li> - -<li class="substepexpand"><span>The <span class="uicontrol">Prefix</span> associated with the target -namespace.</span></li> - -<li class="substepexpand"><span>Select <span class="uicontrol">Create WSDL Skeleton</span> if you want -the wizard to create the skeleton of the WSDL file.</span> This will generate -the WSDL elements required for your service, including bindings, ports and -messages. You can then modify these to meet the requirements of your Web service -.</li> - -<li class="substepexpand"><span>If you have chosen to create a WSDL skeleton, select the binding -options you want to use in the <span class="uicontrol">Protocol</span> drop down. -The options are SOAP and HTTP. Use the SOAP protocol when you want to exchange -structured and typed information. Use the HTTP protocol when you want your -application client to just request or update information.</span></li> - -<li class="substepexpand"><span /> If you select SOAP you can then select the encoding -style you want to use:<ul> -<li><span class="uicontrol">document literal</span>. Document style messages, literal -encoding. Use this style of binding when you want to send SOAP messages that -can be validated by an XML validator. All the data types in the SOAP message -body are defined in a schema, so the WSDL parts must point to schema elements. </li> - -<li><span class="uicontrol">rpc literal</span>. RPC style messages, literal encoding. -Use this style of binding when you want to specify the operation method names -in your SOAP messages so a server can dispatch the specified methods. Data -types must be defined, so the WSDL parts must point to XSD types.</li> - -<li><span class="uicontrol">rpc encoded</span>. RPC style messages and SOAP encoding. -Use this style of binding when you want to encode data graphs in your SOAP -messages so a server can deserialize the object data. Data types must be -defined, so the WSDL parts must point to XSD types.</li> - -</ul> -</li> - -<li class="substepexpand"><span /> If you select HTTP you can select whether to create -an HTTP getter or setter.<ul> -<li><span class="uicontrol">HTTP GET</span>. A GET request fetches data from a Web -server based on an URL value and a set of HTTP headers. Use this method when -you want to retrieve information specified in the request. </li> - -<li><span class="uicontrol">HTTP POST</span>. A POST request sends additional data -to the server, specified after the URL and the headers. Use this method when -you want to send data enclosed in the body of the request.</li> - -</ul> -</li> - -</ol> - -</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Finish</span>.</span> The WSDL file -opens in the WSDL editor.</li> - -</ol> - -<div class="section"><p>If you created a WSDL file with a skeleton using SOAP bindings, -it should look similar to the following:</p> -<p><br /><img src="../images/soapskel.gif" alt="Image of a WSDL skeleton using SOAP bindings" /><br /></p> -<p>If you created -a WSDL file with a skeleton using HTTP bindings, it should look similar to -the following:</p> -<p><br /><img src="../images/httpskel.gif" alt="Image of a WSDL skeleton using HTTP bindings" /><br /></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="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></div></div> - -<div class="linklist"><strong>Related tasks</strong><br /> - -<div><a href="timpwsdl.html" title="You can import WSDL files into the workbench and open them in the WSDL editor. Opening them in the WSDL editor provides you with an opportunity to have a structured viewing of the WSDL file.">Importing a WSDL file</a></div> -<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tedtwsdl.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tedtwsdl.dita deleted file mode 100644 index d8809d013..000000000 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tedtwsdl.dita +++ /dev/null @@ -1,100 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2006, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" - "task.dtd"> -<task id="tedtwsdl" xml:lang="en-us"> -<title>Editing WSDL files</title> -<shortdesc>Once you have created a WSDL file, you can edit it in the WSDL -editor. You can also import WSDL files you have created into the workbench -and edit them in the WSDL editor.</shortdesc> -<prolog><metadata> -<keywords><indexterm>WSDL files<indexterm>editing</indexterm></indexterm> -<indexterm>Web services<indexterm>editing WSDL files</indexterm></indexterm> -</keywords> -</metadata></prolog> -<taskbody> -<context><p>To open a WSDL file in the WSDL editor, double-click it in the -Navigator view or right-click it and click <b>Open With > WSDL Editor.</b></p></context> -</taskbody> -<task id="editisourceview"> -<title>Editing in the Source view</title> -<taskbody> -<context>To edit a WSDL file in the Source view, complete the following steps:</context> -<steps> -<step><cmd>Open your WSDL file in the WSDL editor.</cmd></step> -<step><cmd>Click the <uicontrol>Source</uicontrol> tab.</cmd></step> -<step><cmd>Select the source code you want to edit.</cmd></step> -</steps> -<result><p>At any time, you can switch to the Source view to review the source -code of the WSDL file. You can also edit your WSDL file directly in the Source -view.</p></result> -</taskbody> -</task> -<task id="editeditview"> -<title>Editing in the Design view</title> -<taskbody> -<context><p>The Design view provides a graphical way to browse and edit your -WSDL file. Each type of top level WSDL object is shown within a tabular view -(for example, service, binding, port type). Each tabular view contains one -or more rows that represent the structure of the object. The service, binding, -and port type objects are 'linked'. A line displays to denote a reference -(or association) between these objects.</p><p> <image alt="Image of a WSDL file open in the WSDL editor" -href="../images/wsdleditor.gif" placement="break"></image></p></context> -</taskbody> -</task> -<task id="editpropertiesview"> -<title>Editing in the Properties view</title> -<taskbody> -<context><p>The Properties view displays a list of attributes and editable -attribute values of a selected WSDL object and contains the following panes -to edit:</p><ul> -<li> <uicontrol>General</uicontrol> pane, which displays a list of object -attributes.</li> -<li> <uicontrol>Documentation</uicontrol> pane, which specifies the information -you want the user to read.</li> -<li> <uicontrol>Extensions</uicontrol> pane, which is used to add extension -components.</li> -</ul><draft-comment> [Legacy Title] Showing Bindings in the Design [Legacy -Context]By default bindings are shown in the Design View. Select the show/hide -binding button at the top left of the Design View to hide the bindings. With -the bindings hidden a service can be browsed from a purely abstract level -without showing binding information. When the need arises to understand the -concrete details represented by the binding, select the show/hide binding -button again to make them visible. view [Writer comments] Remove topic "Showing -bindings..." because there is no show/hide binding function in the new GUI</draft-comment></context> -</taskbody> -</task> -<task id="editoutlineview" xml:lang="en-us"> -<title>Editing in the Outline view</title> -<taskbody> -<context><p>The Outline view will show you all the items in your WSDL file -as you add them. In this view, you can both create and delete WSDL components.</p><p>The -Outline view contains the following folders you can use (by right-clicking -and selecting the appropriate option) to edit your WSDL file:</p><ul> -<li> <b>Imports</b> statements, which are used to associate a namespace -with a document location.</li> -<li> <b>Types</b>, which provide data type definitions used to describe the -messages exchanged. You cannot edit any types directly using this folder.</li> -<li> <b>Services</b>, which are used to aggregate a set of related ports.</li> -<li> <b>Bindings</b>, which specify concrete protocol and data format specifications -for the operations and messages defined by a particular port type.</li> -<li> <b>Port Type</b>, which is a set of abstract operations. Each operation -refers to an input message and output messages. </li> -<li> <b>Messages</b>, which represent an abstract definition of the data being -transmitted. A message consists of logical parts, each of which is associated -with a definition within some type system.</li> -</ul></context> -</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="../concepts/cwsdled.dita" scope="local"></link> -</linklist> -<linklist><title>Related tasks</title> -<link href="tcrtwsdl.dita" scope="local"></link> -<link href="timpwsdl.dita" scope="local"></link> -</linklist> -</related-links> -</task> -</task> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tedtwsdl.html b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tedtwsdl.html deleted file mode 100644 index a9e16c89c..000000000 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tedtwsdl.html +++ /dev/null @@ -1,161 +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="Copyright (c) 2000, 2008 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, 2008" /> -<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="Editing WSDL files" /> -<meta name="abstract" content="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor." /> -<meta name="description" content="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor." /> -<meta content="WSDL files, editing, Web services, editing WSDL files" name="DC.subject" /> -<meta content="WSDL files, editing, Web services, editing WSDL files" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tedtwsdl" 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>Editing WSDL files</title> -</head> -<body id="tedtwsdl"><a name="tedtwsdl"><!-- --></a> - - -<h1 class="topictitle1">Editing WSDL files</h1> - - - -<div><p>Once you have created a WSDL file, you can edit it in the WSDL -editor. You can also import WSDL files you have created into the workbench -and edit them in the WSDL editor.</p> - -<div class="section"><p>To open a WSDL file in the WSDL editor, double-click it in the -Navigator view or right-click it and click <strong>Open With > WSDL Editor.</strong></p> -</div> - -</div> - -<div class="nested1" id="editisourceview"><a name="editisourceview"><!-- --></a> -<h2 class="topictitle2">Editing in the Source view</h2> - -<div> -<div class="section">To edit a WSDL file in the Source view, complete the following steps:</div> - -<ol> -<li><span>Open your WSDL file in the WSDL editor.</span></li> - -<li><span>Click the <span class="uicontrol">Source</span> tab.</span></li> - -<li><span>Select the source code you want to edit.</span></li> - -</ol> - -<div class="section"><p>At any time, you can switch to the Source view to review the source -code of the WSDL file. You can also edit your WSDL file directly in the Source -view.</p> -</div> - -</div> - -<div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></div> -</div> -</div> -</div> - -<div class="nested1" id="editeditview"><a name="editeditview"><!-- --></a> -<h2 class="topictitle2">Editing in the Design view</h2> - -<div> -<div class="section"><p>The Design view provides a graphical way to browse and edit your -WSDL file. Each type of top level WSDL object is shown within a tabular view -(for example, service, binding, port type). Each tabular view contains one -or more rows that represent the structure of the object. The service, binding, -and port type objects are 'linked'. A line displays to denote a reference -(or association) between these objects.</p> -<p> <br /><img src="../images/wsdleditor.gif" alt="Image of a WSDL file open in the WSDL editor" /><br /></p> -</div> - -</div> - -</div> - -<div class="nested1" id="editpropertiesview"><a name="editpropertiesview"><!-- --></a> -<h2 class="topictitle2">Editing in the Properties view</h2> - -<div> -<div class="section"><p>The Properties view displays a list of attributes and editable -attribute values of a selected WSDL object and contains the following panes -to edit:</p> -<ul> -<li> <span class="uicontrol">General</span> pane, which displays a list of object -attributes.</li> - -<li> <span class="uicontrol">Documentation</span> pane, which specifies the information -you want the user to read.</li> - -<li> <span class="uicontrol">Extensions</span> pane, which is used to add extension -components.</li> - -</ul> -</div> - -</div> - -</div> - -<div class="nested1" xml:lang="en-us" id="editoutlineview"><a name="editoutlineview"><!-- --></a> -<h2 class="topictitle2">Editing in the Outline view</h2> - -<div> -<div class="section"><p>The Outline view will show you all the items in your WSDL file -as you add them. In this view, you can both create and delete WSDL components.</p> -<p>The -Outline view contains the following folders you can use (by right-clicking -and selecting the appropriate option) to edit your WSDL file:</p> -<ul> -<li> <strong>Imports</strong>Â statements, which are used to associate a namespace -with a document location.</li> - -<li> <strong>Types</strong>, which provide data type definitions used to describe the -messages exchanged. You cannot edit any types directly using this folder.</li> - -<li> <strong>Services</strong>, which are used to aggregate a set of related ports.</li> - -<li> <strong>Bindings</strong>, which specify concrete protocol and data format specifications -for the operations and messages defined by a particular port type.</li> - -<li> <strong>Port Type</strong>, which is a set of abstract operations. Each operation -refers to an input message and output messages. </li> - -<li> <strong>Messages</strong>, which represent an abstract definition of the data being -transmitted. A message consists of logical parts, each of which is associated -with a definition within some type system.</li> - -</ul> -</div> - -</div> - -<div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></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="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></div></div> - -<div class="linklist"><strong>Related tasks</strong><br /> - -<div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div> -<div><a href="timpwsdl.html" title="You can import WSDL files into the workbench and open them in the WSDL editor. Opening them in the WSDL editor provides you with an opportunity to have a structured viewing of the WSDL file.">Importing a WSDL file</a></div></div> -</div> -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/timpwsdl.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/timpwsdl.dita deleted file mode 100644 index 6d2eb586c..000000000 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/timpwsdl.dita +++ /dev/null @@ -1,70 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2006, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" - "task.dtd"> -<task id="timpwsdl" xml:lang="en-us"> -<title>Importing a WSDL file</title> -<titlealts> -<searchtitle>Importing WSDL files</searchtitle> -</titlealts> -<shortdesc>You can import WSDL files into the workbench and open them in the -WSDL editor. Opening them in the WSDL editor provides you with an opportunity -to have a structured viewing of the WSDL file.</shortdesc> -<prolog><metadata> -<keywords><indexterm>WSDL files<indexterm>importing</indexterm></indexterm> -<indexterm>Web services<indexterm>importing WSDL files</indexterm></indexterm> -</keywords> -</metadata></prolog> -<taskbody> -<context><p>The Web Service wizard assists you in creating a new Web service -from a WSDL file. You must first create or import a WSDL file. A WSDL file -can be created using the WSDL editor. This is described in: <xref href="../tasks/tcrtwsdl.dita" -scope="peer">Creating a new WSDL file</xref>. To import a WSDL file follow -the instructions below.</p><p> <uicontrol>Prerequisite:</uicontrol> Create -a project. It is recommend that you create a Web project so that the WSDL -can be easily used to generate additional artifacts and deployed.</p><p>For -more information on creating a Web project, refer to the Web application development -documentation.</p><p>To import a WSDL file to your Web project, complete the -following steps:</p></context> -<steps> -<step><cmd>Select your project in the Java EE Navigator pane, and from the <uicontrol>File</uicontrol> menu, -select <uicontrol>Import</uicontrol>.</cmd></step> -<step><cmd>Select <menucascade><uicontrol>General</uicontrol><uicontrol>File -System</uicontrol></menucascade> and click <uicontrol>Next</uicontrol>.</cmd> -</step> -<step><cmd>Click <uicontrol>Browse</uicontrol> on the next page of the wizard -to select the directories from which you would like to add the WSDL.</cmd> -</step> -<step><cmd>In the import selection panes, use the following methods to select -exactly the resources you want to add: </cmd><info><ul> -<li>Expand the hierarchies in the left pane and select or clear the checkboxes -that represent the folders in the selected directory. Then in the right pane, -select or clear check boxes for individual files.</li> -<li>Click <uicontrol>Filter Types</uicontrol> to filter the current selection -for files of a specific type.</li> -<li>Click <uicontrol>Select All</uicontrol> to select all resources in the -directory, then go through and deselect the ones that you do not want to add.</li> -<li>Click <uicontrol>Deselect All</uicontrol> to deselect all resources in -the directory, then go through and choose individual resources to add.</li> -</ul></info></step> -<step><cmd>Specify the Workbench project or folder that will be the import -destination.</cmd></step> -<step><cmd>When you have finished specifying your import options, click <uicontrol>Finish.</uicontrol></cmd> -</step> -</steps> -<result><p>Alternately, you can import a WSDL file using the WSDL Explorer. -For more information, refer to: <xref href="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdlexp.dita" -scope="peer"> Using the WSDL Explorer</xref>. </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="../concepts/cwsdled.dita" scope="local"></link> -</linklist> -<linklist><title>Related tasks</title> -<link href="tcrtwsdl.dita" scope="local"></link> -<link href="tedtwsdl.dita" scope="local"></link> -</linklist> -</related-links> -</task> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/timpwsdl.html b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/timpwsdl.html deleted file mode 100644 index b28b73afb..000000000 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/timpwsdl.html +++ /dev/null @@ -1,109 +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="Copyright (c) 2000, 2008 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, 2008" /> -<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="Importing a WSDL file" /> -<meta name="abstract" content="You can import WSDL files into the workbench and open them in the WSDL editor. Opening them in the WSDL editor provides you with an opportunity to have a structured viewing of the WSDL file." /> -<meta name="description" content="You can import WSDL files into the workbench and open them in the WSDL editor. Opening them in the WSDL editor provides you with an opportunity to have a structured viewing of the WSDL file." /> -<meta content="WSDL files, importing, Web services, importing WSDL files" name="DC.subject" /> -<meta content="WSDL files, importing, Web services, importing WSDL files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.html" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cwsdled.html" /> -<meta scheme="URI" name="DC.Relation" content="tcrtwsdl.html" /> -<meta scheme="URI" name="DC.Relation" content="tedtwsdl.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="timpwsdl" 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>Importing WSDL files</title> -</head> -<body id="timpwsdl"><a name="timpwsdl"><!-- --></a> - - -<h1 class="topictitle1">Importing a WSDL file</h1> - - - - -<div><p>You can import WSDL files into the workbench and open them in the -WSDL editor. Opening them in the WSDL editor provides you with an opportunity -to have a structured viewing of the WSDL file.</p> - -<div class="section"><p>The Web Service wizard assists you in creating a new Web service -from a WSDL file. You must first create or import a WSDL file. A WSDL file -can be created using the WSDL editor. This is described in: <a href="../tasks/tcrtwsdl.html">Creating a new WSDL file</a>. To import a WSDL file follow -the instructions below.</p> -<p> <span class="uicontrol">Prerequisite:</span> Create -a project. It is recommend that you create a Web project so that the WSDL -can be easily used to generate additional artifacts and deployed.</p> -<p>For -more information on creating a Web project, refer to the Web application development -documentation.</p> -<p>To import a WSDL file to your Web project, complete the -following steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>Select your project in the Java EE Navigator pane, and from the <span class="uicontrol">File</span> menu, -select <span class="uicontrol">Import</span>.</span></li> - -<li class="stepexpand"><span>Select <span class="menucascade"><span class="uicontrol">General</span> > <span class="uicontrol">File -System</span></span> and click <span class="uicontrol">Next</span>.</span> -</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Browse</span> on the next page of the wizard -to select the directories from which you would like to add the WSDL.</span> -</li> - -<li class="stepexpand"><span>In the import selection panes, use the following methods to select -exactly the resources you want to add: </span> <ul> -<li>Expand the hierarchies in the left pane and select or clear the checkboxes -that represent the folders in the selected directory. Then in the right pane, -select or clear check boxes for individual files.</li> - -<li>Click <span class="uicontrol">Filter Types</span> to filter the current selection -for files of a specific type.</li> - -<li>Click <span class="uicontrol">Select All</span> to select all resources in the -directory, then go through and deselect the ones that you do not want to add.</li> - -<li>Click <span class="uicontrol">Deselect All</span> to deselect all resources in -the directory, then go through and choose individual resources to add.</li> - -</ul> -</li> - -<li class="stepexpand"><span>Specify the Workbench project or folder that will be the import -destination.</span></li> - -<li class="stepexpand"><span>When you have finished specifying your import options, click <span class="uicontrol">Finish.</span></span> -</li> - -</ol> - -<div class="section"><p>Alternately, you can import a WSDL file using the WSDL Explorer. -For more information, refer to: <a href="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdlexp.html">Using the WSDL Explorer</a>. </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="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></div></div> - -<div class="linklist"><strong>Related tasks</strong><br /> - -<div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div> -<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetbind.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetbind.dita deleted file mode 100644 index 11d0589ba..000000000 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetbind.dita +++ /dev/null @@ -1,111 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2006, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" - "task.dtd"> -<task id="tsetbind" xml:lang="en-us"> -<title>Setting a binding</title> -<shortdesc>A binding is a top level WSDL object that provides a concrete specification -regarding the transmission of messages to and from a web service. A binding -references exactly one port type. The structure of a binding corresponds very -closely to that of the port type. The binding contains extensibility elements -(for example, SOAP, http, and mime) that specify protocol specific details. -Each port within a service references exactly one binding.</shortdesc> -<prolog><metadata> -<keywords><indexterm>Web services<indexterm>bindings<indexterm>creating</indexterm></indexterm><indexterm>setting -WSDL bindings</indexterm></indexterm><indexterm>WSDL files<indexterm>bindings</indexterm></indexterm> -</keywords> -</metadata></prolog> -<taskbody> -<context><p>You can create a binding by right clicking in any blank space -in the Design view and selecting <uicontrol>Add Binding</uicontrol>. You can -create a new binding, reuse an existing one, or import one. </p></context> -</taskbody> -<task id="createnewbind"> -<title>Creating a new binding</title> -<taskbody> -<context><p>To create a new binding for your port, complete the following -steps:</p></context> -<steps> -<step><cmd>In the Design view, right-click your port and click <b>Set Binding -> New Binding</b>.</cmd></step> -<step><cmd>In the <b>Name</b> field, type the name of the binding.</cmd><info>The -name should be unique among all bindings defined within the enclosing WSDL -document. Click <b>OK.</b> To select the new binding, click the binding object.</info> -</step> -<step><cmd>Type any information about the binding you want the user to read -in the <b>Documentation</b> pane.</cmd></step> -</steps> -<result><note>A <b>PortType</b> is a named set of abstract operations and -the abstract messages involved. You can either create a new port type for -your binding, reuse an existing one, or import one. For more information, -see <xref format="html" href="../tasks/tsetprtt.dita" scope="peer">Setting -a Port Type</xref>.</note><note type="tip">You can also create a new binding -for your port using the Outline view. Right click on the <uicontrol>Bindings</uicontrol> folder -and select <uicontrol>Add Binding</uicontrol>.</note></result> -</taskbody> -</task> -<task id="reusebinding"> -<title>Reusing a binding for a port</title> -<taskbody> -<context><p>To reuse a binding for your port, complete the following steps:</p></context> -<steps> -<step><cmd>In the Design view, select your port.</cmd></step> -<step><cmd>In the Properties view, click the <b>General</b> pane.</cmd></step> -<step><cmd>From the <b>Binding</b> drop down list, select the binding you -want to use.</cmd></step> -</steps> -</taskbody> -</task> -<task id="regeneratingabinding"> -<title>Regenerating a binding</title> -<taskbody> -<context>To regenerate a binding, complete the following steps:</context> -<steps> -<step><cmd>Right-click the binding you want to regenerate.</cmd></step> -<step><cmd>Select <uicontrol>Generate Binding Content</uicontrol>.</cmd></step> -<step><cmd>Specify the required binding information. If you are modifying -an existing binding, select the <uicontrol>Overwrite existing binding information</uicontrol> check -box.</cmd></step> -</steps> -</taskbody> -</task> -<task id="impbinding"> -<title>Import an existing binding</title> -<taskbody> -<context>To import an existing binding for your port, complete the following -steps:</context> -<steps> -<step><cmd>In the Design view, right-click your port and click <b>Set Binding -> Existing Binding.</b></cmd></step> -<step importance="optional"><cmd>In the <b>Name</b> field, type a search string -to filter the list or leave the field blank to view all.</cmd></step> -<step><cmd>You can import a binding by selecting one of the following options:</cmd> -<choices> -<choice><b>Workspace</b>: lists the bindings available in your workspace.</choice> -<choice><b>Enclosing Project</b>: lists the bindings available in the project -that contains your file.</choice> -<choice><b>Current Resource</b>: lists the binding types available in your -current file.</choice> -<choice><b>Working Sets</b>: lists the bindings available in a specified set -of files. To specify a working set, click <b>Choose</b>. You can select files -from an existing working set or create a new working set. Once you have selected -the files, click <b>OK</b>.</choice> -</choices> -</step> -<step><cmd>The bindings will be listed. Select one and click <b>OK</b>. In -the Design view, click the binding object.</cmd></step> -<step><cmd>In the Properties view, type any information about the binding -you wish the user to read in the <b>Documentation</b> pane.</cmd></step> -</steps> -</taskbody> -<related-links> -<linklist><title>Related concepts</title> -<link href="../concepts/cwsdled.dita" scope="local"></link> -</linklist> -<linklist><title>Related tasks</title> -<link href="tcrtwsdl.dita" scope="local"></link> -<link href="tedtwsdl.dita" scope="local"></link> -</linklist> -</related-links> -</task> -</task> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetbind.html b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetbind.html deleted file mode 100644 index 83a646157..000000000 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetbind.html +++ /dev/null @@ -1,177 +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="Copyright (c) 2000, 2008 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, 2008" /> -<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 a binding" /> -<meta name="abstract" content="A binding is a top level WSDL object that provides a concrete specification regarding the transmission of messages to and from a web service. A binding references exactly one port type. The structure of a binding corresponds very closely to that of the port type. The binding contains extensibility elements (for example, SOAP, http, and mime) that specify protocol specific details. Each port within a service references exactly one binding." /> -<meta name="description" content="A binding is a top level WSDL object that provides a concrete specification regarding the transmission of messages to and from a web service. A binding references exactly one port type. The structure of a binding corresponds very closely to that of the port type. The binding contains extensibility elements (for example, SOAP, http, and mime) that specify protocol specific details. Each port within a service references exactly one binding." /> -<meta content="Web services, bindings, creating, setting WSDL bindings, WSDL files" name="DC.subject" /> -<meta content="Web services, bindings, creating, setting WSDL bindings, WSDL files" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tsetbind" 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 a binding</title> -</head> -<body id="tsetbind"><a name="tsetbind"><!-- --></a> - - -<h1 class="topictitle1">Setting a binding</h1> - - - -<div><p>A binding is a top level WSDL object that provides a concrete specification -regarding the transmission of messages to and from a web service. A binding -references exactly one port type. The structure of a binding corresponds very -closely to that of the port type. The binding contains extensibility elements -(for example, SOAP, http, and mime) that specify protocol specific details. -Each port within a service references exactly one binding.</p> - -<div class="section"><p>You can create a binding by right clicking in any blank space -in the Design view and selecting <span class="uicontrol">Add Binding</span>. You can -create a new binding, reuse an existing one, or import one. </p> -</div> - -</div> - -<div class="nested1" id="createnewbind"><a name="createnewbind"><!-- --></a> -<h2 class="topictitle2">Creating a new binding</h2> - -<div> -<div class="section"><p>To create a new binding for your port, complete the following -steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>In the Design view, right-click your port and click <strong>Set Binding -> New Binding</strong>.</span></li> - -<li class="stepexpand"><span>In the <strong>Name</strong> field, type the name of the binding.</span> The -name should be unique among all bindings defined within the enclosing WSDL -document. Click <strong>OK.</strong> To select the new binding, click the binding object. -</li> - -<li class="stepexpand"><span>Type any information about the binding you want the user to read -in the <strong>Documentation</strong> pane.</span></li> - -</ol> - -<div class="section"><div class="note"><span class="notetitle">Note:</span> A <strong>PortType</strong> is a named set of abstract operations and -the abstract messages involved. You can either create a new port type for -your binding, reuse an existing one, or import one. For more information, -see <a href="tsetprtt.html">Setting a Port Type</a>.</div> -<div class="tip"><span class="tiptitle">Tip:</span> You can also create a new binding -for your port using the Outline view. Right click on the <span class="uicontrol">Bindings</span> folder -and select <span class="uicontrol">Add Binding</span>.</div> -</div> - -</div> - -</div> - -<div class="nested1" id="reusebinding"><a name="reusebinding"><!-- --></a> -<h2 class="topictitle2">Reusing a binding for a port</h2> - -<div> -<div class="section"><p>To reuse a binding for your port, complete the following steps:</p> -</div> - -<ol> -<li><span>In the Design view, select your port.</span></li> - -<li><span>In the Properties view, click the <strong>General</strong> pane.</span></li> - -<li><span>From the <strong>Binding</strong> drop down list, select the binding you -want to use.</span></li> - -</ol> - -</div> - -</div> - -<div class="nested1" id="regeneratingabinding"><a name="regeneratingabinding"><!-- --></a> -<h2 class="topictitle2">Regenerating a binding</h2> - -<div> -<div class="section">To regenerate a binding, complete the following steps:</div> - -<ol> -<li><span>Right-click the binding you want to regenerate.</span></li> - -<li><span>Select <span class="uicontrol">Generate Binding Content</span>.</span></li> - -<li><span>Specify the required binding information. If you are modifying -an existing binding, select the <span class="uicontrol">Overwrite existing binding information</span> check -box.</span></li> - -</ol> - -</div> - -</div> - -<div class="nested1" id="impbinding"><a name="impbinding"><!-- --></a> -<h2 class="topictitle2">Import an existing binding</h2> - -<div> -<div class="section">To import an existing binding for your port, complete the following -steps:</div> - -<ol> -<li><span>In the Design view, right-click your port and click <strong>Set Binding -> Existing Binding.</strong></span></li> - -<li><strong>Optional: </strong><span>In the <strong>Name</strong> field, type a search string -to filter the list or leave the field blank to view all.</span></li> - -<li><span>You can import a binding by selecting one of the following options:</span> -<ul> -<li><strong>Workspace</strong>: lists the bindings available in your workspace.</li> - -<li><strong>Enclosing Project</strong>: lists the bindings available in the project -that contains your file.</li> - -<li><strong>Current Resource</strong>: lists the binding types available in your -current file.</li> - -<li><strong>Working Sets</strong>: lists the bindings available in a specified set -of files. To specify a working set, click <strong>Choose</strong>. You can select files -from an existing working set or create a new working set. Once you have selected -the files, click <strong>OK</strong>.</li> - -</ul> - -</li> - -<li><span>The bindings will be listed. Select one and click <strong>OK</strong>. In -the Design view, click the binding object.</span></li> - -<li><span>In the Properties view, type any information about the binding -you wish the user to read in the <strong>Documentation</strong> pane.</span></li> - -</ol> - -</div> - -<div> -<div class="linklist"><strong>Related concepts</strong><br /> - -<div><a href="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></div></div> - -<div class="linklist"><strong>Related tasks</strong><br /> - -<div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div> -<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> -</div> -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetprtt.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetprtt.dita deleted file mode 100644 index 98973fa00..000000000 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetprtt.dita +++ /dev/null @@ -1,114 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2006, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" - "task.dtd"> -<task id="tsetprtt" xml:lang="en-us"> -<title>Setting a port type</title> -<shortdesc>A port type is a named set of abstract operations and the abstract -messages involved. Each operation refers to an input message and output messages. -A port type is referenced by a binding object. Each binding references exactly -one port type. Since each port refers to exactly one binding, each port has -exactly one port type.</shortdesc> -<prolog><metadata> -<keywords><indexterm>WSDL files<indexterm>setting port types</indexterm></indexterm> -<indexterm>Web services<indexterm>setting port types</indexterm></indexterm> -</keywords> -</metadata></prolog> -<taskbody> -<context><p>You can create a port type by right clicking in any blank space -in the Design view and selecting <uicontrol>Add PortType</uicontrol>. As a -convenience you can also add a port type via a binding. This allows you to -create a port type and modify the binding to reference the new port type in -one action. You can either create a new port type for your binding, re-use -an existing one, or import one.</p></context> -</taskbody> -<task id="createporttype"> -<title>Create a new port type for a binding</title> -<taskbody> -<context><p>If you want to create a new port type for your binding, complete -the following steps:</p></context> -<steps> -<step><cmd>In the Design view, right-click on a binding object (note that -port must reference a binding) and click <b>Set PortType > New PortType</b>.</cmd> -</step> -<step><cmd>Type the name of the port type in the <b>Name</b> field and click <b>OK</b>.</cmd> -<info>The name should be unique name among all port types defined within in -the enclosing WSDL document. To select the new port type, click the port type -object.</info></step> -<step><cmd>In the Properties view, type any information about the port type -you wish the user to read in the <b>Documentation</b> pane.</cmd></step> -</steps> -<result> <note type="tip">You can also create a new port type for your binding -using the Outline view.</note><p>Once you have created a port type, you can -add operations to it, which can send and receive messages.</p></result> -</taskbody> -</task> -<task id="reuseporttype"> -<title>Reuse a port type for a binding</title> -<taskbody> -<context><p>If you want to reuse a port type for your binding, complete the -following steps:</p></context> -<steps> -<step><cmd>In the Design view, right-click on a binding object (note that -port must reference a binding) and click <b>Set Port Type > Existing PortType</b>.</cmd> -</step> -<step importance="optional"><cmd>In the <b>Name</b> field, type a search string -to filter the list or leave the field blank to view all.</cmd></step> -<step><cmd>You can change the scope of the list by selecting one of the following -options:</cmd> -<choices> -<choice><b>Workspace</b>: lists the port types available in your workspace.</choice> -<choice><b>Enclosing Project</b>: lists the port types available in the project -that contains your file.</choice> -<choice><b>Current Resource</b>: lists the port types available in your current -file.</choice> -<choice><b>Working Sets</b>: lists the port types available in a specified -set of files. To specify a working set, click <b>Choose</b>. You can select -files from an existing working set or create a new working set. Once you have -selected the files, click <b>OK</b>.</choice> -</choices> -</step> -<step><cmd>The existing port types will be listed. Select one and click <b>OK</b>.</cmd> -</step> -</steps> -</taskbody> -</task> -<task id="importporttype"> -<title>Import a port type for a binding</title> -<taskbody> -<context><p>If you want to import an existing port type for your binding, -complete the following steps:</p></context> -<steps> -<step><cmd>In the Design view, right-click on a binding object (note that -port must reference a binding) and click <b>Set Port Type > Existing PortType.</b></cmd> -</step> -<step importance="optional"><cmd>In the <b>Name</b> field, type a search string -to filter the list or leave the field blank to view all.</cmd></step> -<step><cmd>You can import a port type by selecting one of the following options:</cmd> -<choices> -<choice><b>Workspace</b>: lists the port types available in your workspace.</choice> -<choice><b>Enclosing Project</b>: lists the port types available in the project -that contains your file.</choice> -<choice><b>Working Sets</b>: lists the port types available in a specified -set of files. To specify a working set, click <b>Choose</b>. You can select -files from an existing working set or create a new working set. Once you have -selected the files, click <b>OK</b>.</choice> -</choices> -</step> -<step><cmd>The port types will be listed. Select one and click <b>OK</b>. -In the Design view, click the port type object.</cmd></step> -<step><cmd>In the Properties view, type any information about the port type -you wish the user to read in the <b>Documentation</b> pane.</cmd></step> -</steps> -</taskbody> -<related-links> -<linklist><title>Related concepts</title> -<link href="../concepts/cwsdled.dita" scope="local"></link> -</linklist> -<linklist><title>Related tasks</title> -<link href="tcrtwsdl.dita" scope="local"></link> -<link href="tedtwsdl.dita" scope="local"></link> -</linklist> -</related-links> -</task> -</task> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetprtt.html b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetprtt.html deleted file mode 100644 index 8e29bb397..000000000 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetprtt.html +++ /dev/null @@ -1,179 +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="Copyright (c) 2000, 2008 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, 2008" /> -<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 a port type" /> -<meta name="abstract" content="A port type is a named set of abstract operations and the abstract messages involved. Each operation refers to an input message and output messages. A port type is referenced by a binding object. Each binding references exactly one port type. Since each port refers to exactly one binding, each port has exactly one port type." /> -<meta name="description" content="A port type is a named set of abstract operations and the abstract messages involved. Each operation refers to an input message and output messages. A port type is referenced by a binding object. Each binding references exactly one port type. Since each port refers to exactly one binding, each port has exactly one port type." /> -<meta content="WSDL files, setting port types, Web services" name="DC.subject" /> -<meta content="WSDL files, setting port types, Web services" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tsetprtt" 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 a port type</title> -</head> -<body id="tsetprtt"><a name="tsetprtt"><!-- --></a> - - -<h1 class="topictitle1">Setting a port type</h1> - - - -<div><p>A port type is a named set of abstract operations and the abstract -messages involved. Each operation refers to an input message and output messages. -A port type is referenced by a binding object. Each binding references exactly -one port type. Since each port refers to exactly one binding, each port has -exactly one port type.</p> - -<div class="section"><p>You can create a port type by right clicking in any blank space -in the Design view and selecting <span class="uicontrol">Add PortType</span>. As a -convenience you can also add a port type via a binding. This allows you to -create a port type and modify the binding to reference the new port type in -one action. You can either create a new port type for your binding, re-use -an existing one, or import one.</p> -</div> - -</div> - -<div class="nested1" id="createporttype"><a name="createporttype"><!-- --></a> -<h2 class="topictitle2">Create a new port type for a binding</h2> - -<div> -<div class="section"><p>If you want to create a new port type for your binding, complete -the following steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>In the Design view, right-click on a binding object (note that -port must reference a binding) and click <strong>Set PortType > New PortType</strong>.</span> -</li> - -<li class="stepexpand"><span>Type the name of the port type in the <strong>Name</strong> field and click <strong>OK</strong>.</span> - The name should be unique name among all port types defined within in -the enclosing WSDL document. To select the new port type, click the port type -object.</li> - -<li class="stepexpand"><span>In the Properties view, type any information about the port type -you wish the user to read in the <strong>Documentation</strong> pane.</span></li> - -</ol> - -<div class="section"> <div class="tip"><span class="tiptitle">Tip:</span> You can also create a new port type for your binding -using the Outline view.</div> -<p>Once you have created a port type, you can -add operations to it, which can send and receive messages.</p> -</div> - -</div> - -</div> - -<div class="nested1" id="reuseporttype"><a name="reuseporttype"><!-- --></a> -<h2 class="topictitle2">Reuse a port type for a binding</h2> - -<div> -<div class="section"><p>If you want to reuse a port type for your binding, complete the -following steps:</p> -</div> - -<ol> -<li><span>In the Design view, right-click on a binding object (note that -port must reference a binding) and click <strong>Set Port Type > Existing PortType</strong>.</span> -</li> - -<li><strong>Optional: </strong><span>In the <strong>Name</strong> field, type a search string -to filter the list or leave the field blank to view all.</span></li> - -<li><span>You can change the scope of the list by selecting one of the following -options:</span> -<ul> -<li><strong>Workspace</strong>: lists the port types available in your workspace.</li> - -<li><strong>Enclosing Project</strong>: lists the port types available in the project -that contains your file.</li> - -<li><strong>Current Resource</strong>: lists the port types available in your current -file.</li> - -<li><strong>Working Sets</strong>: lists the port types available in a specified -set of files. To specify a working set, click <strong>Choose</strong>. You can select -files from an existing working set or create a new working set. Once you have -selected the files, click <strong>OK</strong>.</li> - -</ul> - -</li> - -<li><span>The existing port types will be listed. Select one and click <strong>OK</strong>.</span> -</li> - -</ol> - -</div> - -</div> - -<div class="nested1" id="importporttype"><a name="importporttype"><!-- --></a> -<h2 class="topictitle2">Import a port type for a binding</h2> - -<div> -<div class="section"><p>If you want to import an existing port type for your binding, -complete the following steps:</p> -</div> - -<ol> -<li><span>In the Design view, right-click on a binding object (note that -port must reference a binding) and click <strong>Set Port Type > Existing PortType.</strong></span> -</li> - -<li><strong>Optional: </strong><span>In the <strong>Name</strong> field, type a search string -to filter the list or leave the field blank to view all.</span></li> - -<li><span>You can import a port type by selecting one of the following options:</span> -<ul> -<li><strong>Workspace</strong>: lists the port types available in your workspace.</li> - -<li><strong>Enclosing Project</strong>: lists the port types available in the project -that contains your file.</li> - -<li><strong>Working Sets</strong>: lists the port types available in a specified -set of files. To specify a working set, click <strong>Choose</strong>. You can select -files from an existing working set or create a new working set. Once you have -selected the files, click <strong>OK</strong>.</li> - -</ul> - -</li> - -<li><span>The port types will be listed. Select one and click <strong>OK</strong>. -In the Design view, click the port type object.</span></li> - -<li><span>In the Properties view, type any information about the port type -you wish the user to read in the <strong>Documentation</strong> pane.</span></li> - -</ol> - -</div> - -<div> -<div class="linklist"><strong>Related concepts</strong><br /> - -<div><a href="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></div></div> - -<div class="linklist"><strong>Related tasks</strong><br /> - -<div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div> -<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> -</div> -</div> - - -</body> -</html>
\ No newline at end of file |