diff options
Diffstat (limited to 'docs/org.eclipse.jst.ws.consumption.ui.doc.user')
98 files changed, 0 insertions, 4654 deletions
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/.cvsignore b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/.cvsignore deleted file mode 100644 index c9d32abd5..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/.cvsignore +++ /dev/null @@ -1,3 +0,0 @@ -org.eclipse.jst.ws.consumption.ui.doc.user_1.0.0.jar -bak -temp diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/.project b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/.project deleted file mode 100644 index 0b3dcb141..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/.project +++ /dev/null @@ -1,22 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<projectDescription> - <name>org.eclipse.jst.ws.consumption.ui.doc.user</name> - <comment></comment> - <projects> - </projects> - <buildSpec> - <buildCommand> - <name>org.eclipse.pde.ManifestBuilder</name> - <arguments> - </arguments> - </buildCommand> - <buildCommand> - <name>org.eclipse.pde.SchemaBuilder</name> - <arguments> - </arguments> - </buildCommand> - </buildSpec> - <natures> - <nature>org.eclipse.pde.PluginNature</nature> - </natures> -</projectDescription> diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/META-INF/MANIFEST.MF b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/META-INF/MANIFEST.MF deleted file mode 100644 index b169c0be0..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/META-INF/MANIFEST.MF +++ /dev/null @@ -1,8 +0,0 @@ -Manifest-Version: 1.0 -Bundle-ManifestVersion: 2 -Bundle-Name: %pluginName -Bundle-SymbolicName: org.eclipse.jst.ws.consumption.ui.doc.user; singleton:=true -Bundle-Version: 1.0.1.qualifier -Bundle-Vendor: %pluginProvider -Bundle-Localization: plugin -Eclipse-LazyStart: true diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/about.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/about.html deleted file mode 100644 index 4c99086f8..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/about.html +++ /dev/null @@ -1,22 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> -<html> -<head> -<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"> -<title>About</title> -</head> -<body lang="EN-US"> -<h2>About This Content</h2> - -<p>February 24, 2005</p> -<h3>License</h3> - -<p>The Eclipse Foundation makes available all content in this plug-in ("Content"). Unless otherwise indicated below, the Content is provided to you under the terms and conditions of the -Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>. -For purposes of the EPL, "Program" will mean the Content.</p> - -<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is being redistributed by another party ("Redistributor") and different terms and conditions may -apply to your use of any object code in the Content. Check the Redistributor's license that was provided with the Content. If no such license exists, contact the Redistributor. Unless otherwise -indicated below, the terms and conditions of the EPL still apply to any source code in the Content.</p> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/build.properties b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/build.properties deleted file mode 100644 index 72b92f537..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/build.properties +++ /dev/null @@ -1,11 +0,0 @@ -bin.includes = plugin.properties,\ - plugin.xml,\ - wsconsumptionbuild_toc.xml,\ - wsconsumptiont_toc.xml,\ - about.html,\ - images/,\ - concepts/,\ - tasks/,\ - ref/,\ - META-INF/ -src.includes = build.properties diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/build.xml b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/build.xml deleted file mode 100644 index ae96a16ad..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/build.xml +++ /dev/null @@ -1,59 +0,0 @@ -<?xml version="1.0" encoding="UTF-8" ?> -<!-- - - This script build the Help plug-in by transforming the DITA source files into HTML. - - To use this script, you must install DITA-OT on your machine in the directory - defined by the dita.ot.dir property. - - Run the default target after you edit the DITA source files to regenerate the HTML. - - To customize this script for other Help plug-ins, modify the value of the args.input property - to be the DITA map file for the plug-in. - - NOTE: This script assumes that links to sibling Help plug-ins have scope="peer", otherwise the - output directory structure will be shifted incorrectly. - - NOTE: This script assumes that you hand code your plugin.xml file in myplugin.xml. This file - will be copied over the generated plugin.xml which is currently not being generated correctly - by DITA-OT. - - ChangeLog: - 2006-04-05 Arthur Ryman <ryman@ca.ibm.com> - - Created. - ---> -<project name="eclipsehelp" default="all"> - - <property name="dita.ot.dir" location="C:/DITA-OT1.2.1" /> - - <path id="dost.class.path"> - <pathelement location="${dita.ot.dir}${file.separator}lib${file.separator}dost.jar" /> - </path> - - <taskdef name="integrate" classname="org.dita.dost.platform.IntegratorTask"> - <classpath refid="dost.class.path" /> - </taskdef> - <target name="all" depends="integrate, eclipsehelp"> - </target> - <target name="integrate"> - <integrate ditadir="${dita.ot.dir}" /> - </target> - - <!-- revise below here --> - <target name="eclipsehelp"> - <ant antfile="${dita.ot.dir}${file.separator}conductor.xml" target="init" dir="${dita.ot.dir}"> - <property name="args.copycss" value="no" /> - <property name="args.csspath" value="org.eclipse.wst.doc.user" /> - <property name="args.eclipse.provider" value="Eclipse.org" /> - <property name="args.eclipse.version" value="1.5.0" /> - <property name="args.input" location="wsconsumptionbuild_toc.ditamap" /> - <property name="clean.temp" value="true" /> - <property name="dita.extname" value=".dita" /> - <property name="dita.temp.dir" location="temp" /> - <property name="output.dir" location=".." /> - <property name="transtype" value="eclipsehelp" /> - </ant> - <copy file="myplugin.xml" tofile="plugin.xml" overwrite="yes" /> - </target> -</project> diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cuddi.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cuddi.dita deleted file mode 100644 index 49df34fa1..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cuddi.dita +++ /dev/null @@ -1,88 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> -<concept id="cuddi" xml:lang="en-us"> -<title>Universal Description, Discovery, and Integration (UDDI)</title> -<titlealts> -<searchtitle>Universal Description, Discovery, and Integration (UDDI)</searchtitle> -</titlealts> -<shortdesc>Universal Description, Discovery, and Integration (UDDI) specification -defines a way to publish and discover information about Web services.</shortdesc> -<conbody> -<p>UDDI has two functions: <ul> -<li>It is a SOAP-based protocol that defines how clients communicate with -UDDI registries.</li> -<li>It is a particular set of global replicated registries.</li> -</ul></p> -<p>UDDI includes an XML schema for SOAP messages that defines a set of documents -to describe business and services information, a common set of APIs for querying -and publishing information to the directories, and an API for replicating -directory entries between peer UDDI nodes.</p> -<p>For more information on UDDI refer to <xref format="html" href="http://www.uddi.org" -scope="external">www.uddi.org</xref></p> -<section><title>UDDI registries</title><p>UDDI manages the discovery of Web -services by relying on a distributed registry of businesses and their service -descriptions implemented in a common XML format. Before you can publish your -business entity and Web service to a public registry, you must first register -your business entity with a UDDI registry.</p><p>UDDI registries come in two -forms: public and private. Both types comply to the same specifications. -A private registry enables you to publish and test your internal e-business -applications in a secure, private environment.</p><p>A public registry -is a collection of peer directories that contain information about businesses -and services. It locates services that are registered at one of its peer nodes -and facilitates the discovery of published Web services. Data is replicated -at each of the registries on a regular basis. This ensures consistency in -service description formats and makes it easy to track changes as they occur. <tm -tmclass="ibm" tmowner="IBM Corporation" tmtype="reg" trademark="IBM">IBM</tm> maintains -two public registries called the <tm tmclass="ibm" tmowner="IBM Corporation" -tmtype="reg" trademark="IBM">IBM</tm> UDDI Business Registry and the <tm tmclass="ibm" -tmowner="IBM Corporation" tmtype="reg" trademark="IBM">IBM</tm> UDDI Test -Registry. The <tm tmclass="ibm" tmowner="IBM Corporation" tmtype="reg" trademark="IBM">IBM</tm> UDDI -Test Registry allows you to develop your Web service and experience the UDDI -registration process without placing your Web service in an official registry. -Use the <tm tmclass="ibm" tmowner="IBM Corporation" tmtype="reg" trademark="IBM">IBM</tm> UDDI -Test Registry to experiment with UDDI, and to test and validate your Web service. -For more information on the IBM's public registries, refer to <xref format="html" -href="http://uddi.ibm.com" scope="external">http://uddi.ibm.com</xref> For -a list of public registries, refer to <xref href="http://www.uddi.org/register.html" -scope="external">http://www.uddi.org/register.html</xref></p><p>A private -registry allows you to publish and test your internal applications in a secure, -private environment.</p><p>The UDDI Business Registry acts as a B2B directory -linking marketplaces, buyers, and sellers. The information provided in the -registry consists of three components: white pages, yellow pages, and green -pages. White pages include the business name, contact information, and a text -description of the business's services. Yellow pages include industrial categorizations -based on standard taxonomies such as NAICS, ISO 3166, and UNSPSC. Green pages -include references to specifications for Web services and pointers to various -file and URL-based discovery mechanisms. This makes it easy for businesses -to integrate across marketplaces. Because it is registered, information is -made available across all applications. For more information on NAICS refer -to <xref format="html" href="http://www.naics.com" scope="external">www.naics.com</xref> For -more information on UNSPSC refer to <xref format="html" href="http://www.unspsc.org" -scope="external">www.unspsc.org</xref> For more information on ISO 3166 refer -to <xref format="html" href="http://www.iso.org/iso/en/prods-services/iso3166ma/index.html" -scope="external">http://www.iso.org/iso/en/prods-services/iso3166ma/index.html</xref></p><p>Businesses -populate the registry with descriptions of the services that they support. -UDDI assigns a unique identifier to each service description and business -registration. These become the service and business keys respectively. Search -engines, and applications query the registry to discover services. UDDI servers -are a directory of available services and service providers.</p></section> -</conbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cws.dita" scope="peer"> -<linktext>Web services development</linktext></link> -<link href="cwsdlud.dita"></link> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsilud.dita" scope="peer"> -<linktext>Relationship between UDDI and WSIL</linktext></link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="../tasks/tuddiexp.dita"></link> -<link href="../../org.eclipse.jst.ws.uddi.registry.doc.user/tasks/tuddiwiz.dita" -scope="peer"><linktext> Configuring a Unit Test UDDI Registry</linktext></link> -</linklist> -<linklist><title>Related Reference</title> -<link href="../ref/ruddi.dita"></link> -</linklist> -</related-links> -</concept> diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cuddi.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cuddi.html deleted file mode 100644 index 33969e148..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cuddi.html +++ /dev/null @@ -1,119 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Universal Description, Discovery, and Integration (UDDI)" /> -<meta name="abstract" content="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services." /> -<meta name="description" content="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services." /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cws.html" /> -<meta scheme="URI" name="DC.Relation" content="cwsdlud.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsilud.html" /> -<meta scheme="URI" name="DC.Relation" content="../tasks/tuddiexp.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.uddi.registry.doc.user/tasks/tuddiwiz.html" /> -<meta scheme="URI" name="DC.Relation" content="../ref/ruddi.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="cuddi" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Universal Description, Discovery, and Integration (UDDI)</title> -</head> -<body id="cuddi"><a name="cuddi"><!-- --></a> - - -<h1 class="topictitle1">Universal Description, Discovery, and Integration (UDDI)</h1> - - - -<div><p>Universal Description, Discovery, and Integration (UDDI) specification -defines a way to publish and discover information about Web services.</p> - -<div class="p">UDDI has two functions: <ul> -<li>It is a SOAP-based protocol that defines how clients communicate with -UDDI registries.</li> - -<li>It is a particular set of global replicated registries.</li> - -</ul> -</div> - -<p>UDDI includes an XML schema for SOAP messages that defines a set of documents -to describe business and services information, a common set of APIs for querying -and publishing information to the directories, and an API for replicating -directory entries between peer UDDI nodes.</p> - -<p>For more information on UDDI refer to <a href="http://www.uddi.org" target="_blank">www.uddi.org</a></p> - -<div class="section"><h4 class="sectiontitle">UDDI registries</h4><p>UDDI manages the discovery of Web -services by relying on a distributed registry of businesses and their service -descriptions implemented in a common XML format. Before you can publish your -business entity and Web service to a public registry, you must first register -your business entity with a UDDI registry.</p> -<p>UDDI registries come in two -forms: public and private. Both types comply to the same specifications. -A private registry enables you to publish and test your internal e-business -applications in a secure, private environment.</p> -<p>A public registry -is a collection of peer directories that contain information about businesses -and services. It locates services that are registered at one of its peer nodes -and facilitates the discovery of published Web services. Data is replicated -at each of the registries on a regular basis. This ensures consistency in -service description formats and makes it easy to track changes as they occur. IBM<sup>®</sup> maintains -two public registries called the IBM UDDI Business Registry and the IBM UDDI Test -Registry. The IBM UDDI -Test Registry allows you to develop your Web service and experience the UDDI -registration process without placing your Web service in an official registry. -Use the IBM UDDI -Test Registry to experiment with UDDI, and to test and validate your Web service. -For more information on the IBM's public registries, refer to <a href="http://uddi.ibm.com" target="_blank">http://uddi.ibm.com</a> For -a list of public registries, refer to <a href="http://www.uddi.org/register.html" target="_blank">http://www.uddi.org/register.html</a></p> -<p>A private -registry allows you to publish and test your internal applications in a secure, -private environment.</p> -<p>The UDDI Business Registry acts as a B2B directory -linking marketplaces, buyers, and sellers. The information provided in the -registry consists of three components: white pages, yellow pages, and green -pages. White pages include the business name, contact information, and a text -description of the business's services. Yellow pages include industrial categorizations -based on standard taxonomies such as NAICS, ISO 3166, and UNSPSC. Green pages -include references to specifications for Web services and pointers to various -file and URL-based discovery mechanisms. This makes it easy for businesses -to integrate across marketplaces. Because it is registered, information is -made available across all applications. For more information on NAICS refer -to <a href="http://www.naics.com" target="_blank">www.naics.com</a> For -more information on UNSPSC refer to <a href="http://www.unspsc.org" target="_blank">www.unspsc.org</a> For more information on ISO 3166 refer -to <a href="http://www.iso.org/iso/en/prods-services/iso3166ma/index.html" target="_blank">http://www.iso.org/iso/en/prods-services/iso3166ma/index.html</a></p> -<p>Businesses -populate the registry with descriptions of the services that they support. -UDDI assigns a unique identifier to each service description and business -registration. These become the service and business keys respectively. Search -engines, and applications query the registry to discover services. UDDI servers -are a directory of available services and service providers.</p> -</div> - -</div> - -<div> -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> -<div><a href="cwsdlud.html" title="The Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services. UDDI has two functions: (1) it is a SOAP-based protocol that defines how UDDI clients communicate with registries, and (2) it is a particular set of globally replicated registries.">Relationship between UDDI and WSDL</a></div> -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsilud.html">Relationship between UDDI and WSIL</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="../tasks/tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> -<div><a href="../../org.eclipse.jst.ws.uddi.registry.doc.user/tasks/tuddiwiz.html"> Configuring a Unit Test UDDI Registry</a></div></div> - -<div class="linklist"><strong>Related Reference</strong><br /> - -<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cwsdlud.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cwsdlud.dita deleted file mode 100644 index 729ea84cc..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cwsdlud.dita +++ /dev/null @@ -1,106 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> -<concept id="cwsdlud" xml:lang="en-us"> -<title>Relationship between UDDI and WSDL</title> -<shortdesc>The Universal Description, Discovery, and Integration (UDDI) specification -defines a way to publish and discover information about Web services. UDDI -has two functions: (1) it is a SOAP-based protocol that defines how UDDI clients -communicate with registries, and (2) it is a particular set of globally replicated -registries.</shortdesc> -<conbody> -<p>Registering a service involves four core data structure types:</p> -<ul> -<li>The <systemoutput>businessEntity</systemoutput> data type contains information -about the business that has a published service.</li> -<li>The <systemoutput>businessService</systemoutput> data type is a description -of a Web service.</li> -<li>The <systemoutput>bindingTemplate</systemoutput> data type contains technical -information for determining the entry point and construction specifications -for invoking a Web service.</li> -<li>The <systemoutput>tModel</systemoutput> data type provides a reference -system to assist in the discovery of Web services and acts as a technical -specification for a Web service.</li> -</ul> -<p>For more information on the UDDI data types, refer to the related reference -topics at the end of this topic.</p> -<p>Web Services Description Language (WSDL) is an XML-based standard specification -for describing Web services. WSDL defines an XML format for describing network -services as a set of endpoints that operate on messages that contain either -document-oriented or procedure-oriented information.</p> -<p>The WSDL service description can be structured in many ways. However, to -assist with publishing and finding WSDL service descriptions in a UDDI registry, -WSDL documents consist of two main parts: </p> -<ul> -<li>The service interface definition describes the abstract type interface -and its protocol binding, known as the WSDL binding document</li> -<li>The service implementation definition describes the service access location -information, known as the WSDL service document</li> -</ul> -<p>When creating Web services with the Apache Axis run-time environment, the -Web services tools create a single WSDL document when generating Web services -from <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> beans -or EJBs. This WSDL document contains both the service interface and implementation -documents.</p> -<p>A service interface is described by a WSDL document that contains the types, -import, message, portType, and binding elements. A service interface contains -the WSDL service definition that will be used to implement one or more services. -It is an abstract definition of a Web service, and is used to describe a specific -type of service. This document can reference another service interface document -using an import element. The Web services tools in this product generate a -service interface document that contains only the message and portType elements -that are referenced by the binding document that contains only bindings for -the portType.</p> -<p>The service implementation document contains the service elements. A service -implementation document contains a description of a service that implements -a service interface. At least one of the import elements will contain a reference -to the WSDL service interface document; however monolithic WSDL such as that -created using the Axis run-time environment does not have imports. A service -implementation document can contain references to more than one service interface -document.</p> -<p>A service provider hosts a Web service and makes it accessible using protocols -such as SOAP/HTTP and SOAP/JMS. The Web service is described by the WSDL documents -that are stored on the provider's server or in a special repository. The WSDL -documents are referenced by UDDI business services (service documents) and -tModels (binding documents). These pointers enable discovery of a Web service -by a service requestor.</p> -<p>Figure 1. Relationship between UDDI and WSDL.</p> -<p> <image alt="Illustration of the relationship between UDDI and WSDL." href="../images/wsdluddi.gif"> -</image> </p> -<p>Figure 1 illustrates the relationship between UDDI and WSDL. The WSDL service -element references the WSDL binding element. The URL of the document containing -the WSDL binding element is published to the UDDI business registry as a tModel. -The URL of the document containing the WSDL service element is published to -the UDDI business registry as a businessService and contains information about -the bindingTemplate. For more information on UDDI registry data structure -types, refer to the related reference section at the end of this document. -Note that the import portion of the diagram is optional depending on the run-time -environment; monolithic WSDL such as that created using the Axis run-time -environment does not have imports.</p> -<p>The service implementation describes an instance of a service. The instance -is defined using a WSDL service element. The service element in a service -implementation document is used to publish a UDDI businessService. When publishing -a WSDL service description, a service interface must be published as a tModel -before a service implementation is published as a businessService.</p> -<p>A service implementation is published in a UDDI registry as part of a businessService -with one or more bindingTemplate elements. The businessService is published -by the service provider. A new businessService is created for a service element -that is defined in the service implementation document. A new bindingTemplate -element is created within a businessService for each port element that is -defined within a service element.</p> -<p>For more information on the relationship between WSDL and UDDI refer to - <xref href="http://uddi.org/bestpractices.html" scope="external">uddi.org/bestpractices.html</xref>.</p> -</conbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="cuddi.dita"></link> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.dita" scope="peer"> -<linktext>Web Services Description Language (WSDL)</linktext></link> -</linklist> -<linklist><title>Related Reference</title> -<link href="../ref/ruddi.dita"></link> -<link href="../../org.eclipse.jst.ws.doc.user/ref/rwsdl.dita" scope="peer"> -<linktext>Web Services Description Language (WSDL)</linktext></link> -</linklist> -</related-links> -</concept> diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cwsdlud.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cwsdlud.html deleted file mode 100644 index 577a6edde..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cwsdlud.html +++ /dev/null @@ -1,153 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Relationship between UDDI and WSDL" /> -<meta name="abstract" content="The Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services. UDDI has two functions: (1) it is a SOAP-based protocol that defines how UDDI clients communicate with registries, and (2) it is a particular set of globally replicated registries." /> -<meta name="description" content="The Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services. UDDI has two functions: (1) it is a SOAP-based protocol that defines how UDDI clients communicate with registries, and (2) it is a particular set of globally replicated registries." /> -<meta scheme="URI" name="DC.Relation" content="cuddi.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.html" /> -<meta scheme="URI" name="DC.Relation" content="../ref/ruddi.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/ref/rwsdl.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="cwsdlud" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Relationship between UDDI and WSDL</title> -</head> -<body id="cwsdlud"><a name="cwsdlud"><!-- --></a> - - -<h1 class="topictitle1">Relationship between UDDI and WSDL</h1> - - -<div><p>The Universal Description, Discovery, and Integration (UDDI) specification -defines a way to publish and discover information about Web services. UDDI -has two functions: (1) it is a SOAP-based protocol that defines how UDDI clients -communicate with registries, and (2) it is a particular set of globally replicated -registries.</p> - -<p>Registering a service involves four core data structure types:</p> - -<ul> -<li>The <tt class="sysout">businessEntity</tt> data type contains information -about the business that has a published service.</li> - -<li>The <tt class="sysout">businessService</tt> data type is a description -of a Web service.</li> - -<li>The <tt class="sysout">bindingTemplate</tt> data type contains technical -information for determining the entry point and construction specifications -for invoking a Web service.</li> - -<li>The <tt class="sysout">tModel</tt> data type provides a reference -system to assist in the discovery of Web services and acts as a technical -specification for a Web service.</li> - -</ul> - -<p>For more information on the UDDI data types, refer to the related reference -topics at the end of this topic.</p> - -<p>Web Services Description Language (WSDL) is an XML-based standard specification -for describing Web services. WSDL defines an XML format for describing network -services as a set of endpoints that operate on messages that contain either -document-oriented or procedure-oriented information.</p> - -<p>The WSDL service description can be structured in many ways. However, to -assist with publishing and finding WSDL service descriptions in a UDDI registry, -WSDL documents consist of two main parts: </p> - -<ul> -<li>The service interface definition describes the abstract type interface -and its protocol binding, known as the WSDL binding document</li> - -<li>The service implementation definition describes the service access location -information, known as the WSDL service document</li> - -</ul> - -<p>When creating Web services with the Apache Axis run-time environment, the -Web services tools create a single WSDL document when generating Web services -from Java™ beans -or EJBs. This WSDL document contains both the service interface and implementation -documents.</p> - -<p>A service interface is described by a WSDL document that contains the types, -import, message, portType, and binding elements. A service interface contains -the WSDL service definition that will be used to implement one or more services. -It is an abstract definition of a Web service, and is used to describe a specific -type of service. This document can reference another service interface document -using an import element. The Web services tools in this product generate a -service interface document that contains only the message and portType elements -that are referenced by the binding document that contains only bindings for -the portType.</p> - -<p>The service implementation document contains the service elements. A service -implementation document contains a description of a service that implements -a service interface. At least one of the import elements will contain a reference -to the WSDL service interface document; however monolithic WSDL such as that -created using the Axis run-time environment does not have imports. A service -implementation document can contain references to more than one service interface -document.</p> - -<p>A service provider hosts a Web service and makes it accessible using protocols -such as SOAP/HTTP and SOAP/JMS. The Web service is described by the WSDL documents -that are stored on the provider's server or in a special repository. The WSDL -documents are referenced by UDDI business services (service documents) and -tModels (binding documents). These pointers enable discovery of a Web service -by a service requestor.</p> - -<p>Figure 1. Relationship between UDDI and WSDL.</p> - -<p> <img src="../images/wsdluddi.gif" alt="Illustration of the relationship between UDDI and WSDL." /> </p> - -<p>Figure 1 illustrates the relationship between UDDI and WSDL. The WSDL service -element references the WSDL binding element. The URL of the document containing -the WSDL binding element is published to the UDDI business registry as a tModel. -The URL of the document containing the WSDL service element is published to -the UDDI business registry as a businessService and contains information about -the bindingTemplate. For more information on UDDI registry data structure -types, refer to the related reference section at the end of this document. -Note that the import portion of the diagram is optional depending on the run-time -environment; monolithic WSDL such as that created using the Axis run-time -environment does not have imports.</p> - -<p>The service implementation describes an instance of a service. The instance -is defined using a WSDL service element. The service element in a service -implementation document is used to publish a UDDI businessService. When publishing -a WSDL service description, a service interface must be published as a tModel -before a service implementation is published as a businessService.</p> - -<p>A service implementation is published in a UDDI registry as part of a businessService -with one or more bindingTemplate elements. The businessService is published -by the service provider. A new businessService is created for a service element -that is defined in the service implementation document. A new bindingTemplate -element is created within a businessService for each port element that is -defined within a service element.</p> - -<p>For more information on the relationship between WSDL and UDDI refer to - <a href="http://uddi.org/bestpractices.html" target="_blank">uddi.org/bestpractices.html</a>.</p> - -</div> - -<div> -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div> -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.html">Web Services Description Language (WSDL)</a></div></div> - -<div class="linklist"><strong>Related Reference</strong><br /> - -<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div> -<div><a href="../../org.eclipse.jst.ws.doc.user/ref/rwsdl.html">Web Services Description Language (WSDL)</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/addfav.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/addfav.gif Binary files differdeleted file mode 100644 index 48895f418..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/addfav.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/adduddi.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/adduddi.gif Binary files differdeleted file mode 100644 index 8399bb0eb..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/adduddi.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/beaninfojsp.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/beaninfojsp.gif Binary files differdeleted file mode 100644 index 3cbe40c48..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/beaninfojsp.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/bindnode.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/bindnode.gif Binary files differdeleted file mode 100644 index c60abfc12..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/bindnode.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/browsebutton.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/browsebutton.gif Binary files differdeleted file mode 100644 index d84a5bb8e..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/browsebutton.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/busasst.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/busasst.gif Binary files differdeleted file mode 100644 index 3fdcbb0d0..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/busasst.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/fav.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/fav.gif Binary files differdeleted file mode 100644 index debfabd34..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/fav.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/find.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/find.gif Binary files differdeleted file mode 100644 index 6dc3ebefc..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/find.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/fswsdlicon.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/fswsdlicon.gif Binary files differdeleted file mode 100644 index b03233aa2..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/fswsdlicon.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/login.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/login.gif Binary files differdeleted file mode 100644 index 237bdd27a..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/login.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/mptwsdlicon.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/mptwsdlicon.gif Binary files differdeleted file mode 100644 index 905e65567..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/mptwsdlicon.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/newjsp.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/newjsp.gif Binary files differdeleted file mode 100644 index 2f4b50972..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/newjsp.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/opnode.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/opnode.gif Binary files differdeleted file mode 100644 index 3e8a29557..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/opnode.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/proxyonjsp.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/proxyonjsp.gif Binary files differdeleted file mode 100644 index 652e4ead9..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/proxyonjsp.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/publish2.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/publish2.gif Binary files differdeleted file mode 100644 index 14a11a578..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/publish2.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/pubserv.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/pubserv.gif Binary files differdeleted file mode 100644 index 31d36b735..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/pubserv.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/refserv.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/refserv.gif Binary files differdeleted file mode 100644 index f5c015b0d..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/refserv.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/runjsf.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/runjsf.gif Binary files differdeleted file mode 100644 index 6e884d28d..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/runjsf.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/scenario7.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/scenario7.gif Binary files differdeleted file mode 100644 index 98082685c..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/scenario7.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/servnode.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/servnode.gif Binary files differdeleted file mode 100644 index 65b9c0936..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/servnode.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/soapudws.cdr b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/soapudws.cdr Binary files differdeleted file mode 100644 index d5edaebd5..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/soapudws.cdr +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddi.cdr b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddi.cdr Binary files differdeleted file mode 100644 index 2352f01f5..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddi.cdr +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddi.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddi.gif Binary files differdeleted file mode 100644 index 7a02c09b0..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddi.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddiref.cdr b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddiref.cdr Binary files differdeleted file mode 100644 index e8da32a90..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddiref.cdr +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddiref.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddiref.gif Binary files differdeleted file mode 100644 index 7c148a776..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddiref.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddiview.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddiview.gif Binary files differdeleted file mode 100644 index 0601bc8f8..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddiview.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlbnddetl.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlbnddetl.gif Binary files differdeleted file mode 100644 index a22eda630..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlbnddetl.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdldetail.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdldetail.gif Binary files differdeleted file mode 100644 index ef54568c0..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdldetail.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdldtlicon.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdldtlicon.gif Binary files differdeleted file mode 100644 index d8ee67c1d..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdldtlicon.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlexp.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlexp.gif Binary files differdeleted file mode 100644 index 27f3f6948..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlexp.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlfavicon.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlfavicon.gif Binary files differdeleted file mode 100644 index cb9d51405..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlfavicon.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlicon.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlicon.gif Binary files differdeleted file mode 100644 index 7b6bd28e0..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlicon.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlnode.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlnode.gif Binary files differdeleted file mode 100644 index 68ef08ce7..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlnode.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlop.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlop.gif Binary files differdeleted file mode 100644 index a0f370e38..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlop.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlopret.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlopret.gif Binary files differdeleted file mode 100644 index 60d7e4136..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlopret.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlopretx.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlopretx.gif Binary files differdeleted file mode 100644 index ff93bdd15..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlopretx.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlpage.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlpage.gif Binary files differdeleted file mode 100644 index 537c1c071..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlpage.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlservdet.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlservdet.gif Binary files differdeleted file mode 100644 index 6c197c065..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlservdet.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlstatx.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlstatx.gif Binary files differdeleted file mode 100644 index 6081fa92f..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlstatx.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdluddi.cdr b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdluddi.cdr Binary files differdeleted file mode 100644 index 8949098a9..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdluddi.cdr +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdluddi.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdluddi.gif Binary files differdeleted file mode 100644 index febb7d558..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdluddi.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsilpage.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsilpage.gif Binary files differdeleted file mode 100644 index b5e6e03ee..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsilpage.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsilview.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsilview.gif Binary files differdeleted file mode 100644 index 789d68929..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsilview.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsinjsp.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsinjsp.gif Binary files differdeleted file mode 100644 index 0e5d5f004..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsinjsp.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wswizicon.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wswizicon.gif Binary files differdeleted file mode 100644 index a4fe8b3c6..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wswizicon.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/myplugin.xml b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/myplugin.xml deleted file mode 100644 index 248e72b65..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/myplugin.xml +++ /dev/null @@ -1,20 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?eclipse version="3.0"?> -<?NLS TYPE="org.eclipse.help.toc"?> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 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 - *******************************************************************************/ --> -<plugin> - - <extension point="org.eclipse.help.toc"> - <toc file="wsconsumptionbuild_toc.xml"/> - <toc file="wsconsumptiont_toc.xml" /> - </extension> -</plugin>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/org.eclipse.jst.ws.consumption.ui.doc.user.maplist b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/org.eclipse.jst.ws.consumption.ui.doc.user.maplist deleted file mode 100644 index aec04b0c6..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/org.eclipse.jst.ws.consumption.ui.doc.user.maplist +++ /dev/null @@ -1,10 +0,0 @@ -<maplist version="3.6.2"> - <nav> - <map file="wsconsumptionbuild_toc.ditamap"/> - <map file="wsconsumptiont_toc.ditamap"/> - </nav> - <link> - <map file="wsconsumptiont_toc.ditamap"/> - <map file="wsconsumptionbuild_toc.ditamap"/> - </link> -</maplist> diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/plugin.properties b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/plugin.properties deleted file mode 100644 index 2df4674b8..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/plugin.properties +++ /dev/null @@ -1,15 +0,0 @@ -############################################################################### -# Copyright (c) 2001, 2005 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 -############################################################################### -# NLS_MESSAGEFORMAT_VAR -# NLS_ENCODING=UTF-8 - -pluginName = Web service consumption documentation -pluginProvider = Eclipse.org diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/plugin.xml b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/plugin.xml deleted file mode 100644 index 248e72b65..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/plugin.xml +++ /dev/null @@ -1,20 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?eclipse version="3.0"?> -<?NLS TYPE="org.eclipse.help.toc"?> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 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 - *******************************************************************************/ --> -<plugin> - - <extension point="org.eclipse.help.toc"> - <toc file="wsconsumptionbuild_toc.xml"/> - <toc file="wsconsumptiont_toc.xml" /> - </extension> -</plugin>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/ref/ruddi.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/ref/ruddi.dita deleted file mode 100644 index 1d63add1d..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/ref/ruddi.dita +++ /dev/null @@ -1,73 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd"> -<reference id="ruddi" xml:lang="en-us"> -<title>Data structure types (UDDI registry)</title> -<shortdesc>Once you have registered and logged in to the UDDI registry that -you want to use, you can register your Web service. Registration of -a service involves four core data structure types: business information, service -information, binding information, and information describing the specifications -for services. The relationship between these data types is described in Figure -1.</shortdesc> -<refbody> -<section><lq> <p> <uicontrol>Business information.</uicontrol> Information -that is contained in a <systemoutput>businessEntity</systemoutput> structure. -The <systemoutput>businessEntity</systemoutput> contains information about -the business that has published the service, such as business name, description, -contacts and identifiers.</p> <p> <uicontrol>Service information.</uicontrol> Information -that describes a group of Web services. It is contained in a <systemoutput>businessService</systemoutput> structure. -The <systemoutput>businessService</systemoutput> contains information about -families of technical services. It groups a set of Web services related -to either a business process or group of services.</p> <p> <uicontrol>Binding -information.</uicontrol> Information represented by the <systemoutput>bindingTemplate</systemoutput> structure. -The <systemoutput>bindingTemplate</systemoutput> holds technical information -for determining the entry point and construction specifications for invoking -a Web service. The <systemoutput>bindingTemplate</systemoutput> provides -the Web service descriptions relevant for application developers that want -to find and invoke a Web service. The <systemoutput>bindingTemplate</systemoutput> points -to a service implementation descriptions, for example via a URL.</p> <p> <uicontrol>Information -describing the specifications for services.</uicontrol> Metadata about the -various specifications implemented by a given Web service represented by the - <systemoutput>tModel</systemoutput>. The <systemoutput>tModel</systemoutput> provides -a reference system to assist in the discovery of Web services.</p> </lq><p>Figure -1. Relationship between data types.</p><p> <image alt="Figure 1 illustrates the relationship between the business entity, business service, binding template, and tmodel." -href="../images/uddi.gif"></image> </p><p>Each child structure has a unique -parent structure. This means that each <systemoutput>businessService</systemoutput> structure -is owned by a specific <systemoutput>businessEntity</systemoutput>. In turn, -each <systemoutput>bindingTemplate</systemoutput> is owned by a specific - <systemoutput>businessService</systemoutput>. Each <systemoutput>bindingTemplate</systemoutput> structure -references to unique instances of <systemoutput>tModel</systemoutput> structures; -however, since references can be repeated within several parent structures, -there can be many references to <systemoutput>tModels</systemoutput> from -different Entity-Service-Template parents, as seen in Figure 2.</p><p>Figure -2. References to tModel.</p><p> <image alt="Figure 2 illustrates the multiple references to a tModel." -href="../images/uddiref.gif"></image> </p></section> -<section><title>Publisher assertions</title><p>A publisher assertion is a -way in UDDI to associate businessEntity structures. The publisher assertion -defines a group of businessEntity structures. Many businesses are not effectively -represented by a single businessEntity. A publisher assertion allows for the -association between businessEntity structures. For example, a large company -may have several subsidiaries that have different descriptions but are still -closely coupled and want to make their relationships visible in UDDI registries.</p></section> -<section><title>Service projections</title><p>A service projection enables -a business entity to reference a service that was published by another business -entity. By using the businessService structure as a projection to an already -published businessService, businesses can share or reuse services. Service -projections are managed centrally as part of the referencing businessEntity. -This means that any changes made to the businessService by any of the referencing -businessEntity structures are valid for all of the referencing businessEntity -structures.</p></section> -</refbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.dita" scope="peer"> -<linktext> Tools for Web services development</linktext></link> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cws.dita" scope="peer"> -<linktext>Web services development</linktext></link> -</linklist> -<linklist><title>Related Tasks</title><?Pub Caret?> -<link href="../tasks/tuddiexp.dita"></link> -</linklist> -</related-links> -</reference> -<?Pub *0000005079?> diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/ref/ruddi.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/ref/ruddi.html deleted file mode 100644 index f6ad7be7c..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/ref/ruddi.html +++ /dev/null @@ -1,110 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="reference" name="DC.Type" /> -<meta name="DC.Title" content="Data structure types (UDDI registry)" /> -<meta name="abstract" content="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1." /> -<meta name="description" content="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1." /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cws.html" /> -<meta scheme="URI" name="DC.Relation" content="../tasks/tuddiexp.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="ruddi" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Data structure types (UDDI registry)</title> -</head> -<body id="ruddi"><a name="ruddi"><!-- --></a> - - -<h1 class="topictitle1">Data structure types (UDDI registry)</h1> - - -<div><p>Once you have registered and logged in to the UDDI registry that -you want to use, you can register your Web service. Registration of -a service involves four core data structure types: business information, service -information, binding information, and information describing the specifications -for services. The relationship between these data types is described in Figure -1.</p> - -<div class="section"><blockquote> <p> <span class="uicontrol">Business information.</span> Information -that is contained in a <tt class="sysout">businessEntity</tt> structure. -The <tt class="sysout">businessEntity</tt> contains information about -the business that has published the service, such as business name, description, -contacts and identifiers.</p> - <p> <span class="uicontrol">Service information.</span> Information -that describes a group of Web services. It is contained in a <tt class="sysout">businessService</tt> structure. -The <tt class="sysout">businessService</tt> contains information about -families of technical services. It groups a set of Web services related -to either a business process or group of services.</p> - <p> <span class="uicontrol">Binding -information.</span> Information represented by the <tt class="sysout">bindingTemplate</tt> structure. -The <tt class="sysout">bindingTemplate</tt> holds technical information -for determining the entry point and construction specifications for invoking -a Web service. The <tt class="sysout">bindingTemplate</tt> provides -the Web service descriptions relevant for application developers that want -to find and invoke a Web service. The <tt class="sysout">bindingTemplate</tt> points -to a service implementation descriptions, for example via a URL.</p> - <p> <span class="uicontrol">Information -describing the specifications for services.</span> Metadata about the -various specifications implemented by a given Web service represented by the - <tt class="sysout">tModel</tt>. The <tt class="sysout">tModel</tt> provides -a reference system to assist in the discovery of Web services.</p> - </blockquote> -<p>Figure -1. Relationship between data types.</p> -<p> <img src="../images/uddi.gif" alt="Figure 1 illustrates the relationship between the business entity, business service, binding template, and tmodel." /> </p> -<p>Each child structure has a unique -parent structure. This means that each <tt class="sysout">businessService</tt> structure -is owned by a specific <tt class="sysout">businessEntity</tt>. In turn, -each <tt class="sysout">bindingTemplate</tt> is owned by a specific - <tt class="sysout">businessService</tt>. Each <tt class="sysout">bindingTemplate</tt> structure -references to unique instances of <tt class="sysout">tModel</tt> structures; -however, since references can be repeated within several parent structures, -there can be many references to <tt class="sysout">tModels</tt> from -different Entity-Service-Template parents, as seen in Figure 2.</p> -<p>Figure -2. References to tModel.</p> -<p> <img src="../images/uddiref.gif" alt="Figure 2 illustrates the multiple references to a tModel." /> </p> -</div> - -<div class="section"><h4 class="sectiontitle">Publisher assertions</h4><p>A publisher assertion is a -way in UDDI to associate businessEntity structures. The publisher assertion -defines a group of businessEntity structures. Many businesses are not effectively -represented by a single businessEntity. A publisher assertion allows for the -association between businessEntity structures. For example, a large company -may have several subsidiaries that have different descriptions but are still -closely coupled and want to make their relationships visible in UDDI registries.</p> -</div> - -<div class="section"><h4 class="sectiontitle">Service projections</h4><p>A service projection enables -a business entity to reference a service that was published by another business -entity. By using the businessService structure as a projection to an already -published businessService, businesses can share or reuse services. Service -projections are managed centrally as part of the referencing businessEntity. -This means that any changes made to the businessService by any of the referencing -businessEntity structures are valid for all of the referencing businessEntity -structures.</p> -</div> - -</div> - -<div> -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="../tasks/tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/taddreg.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/taddreg.dita deleted file mode 100644 index f0689c291..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/taddreg.dita +++ /dev/null @@ -1,72 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd"> -<task id="taddreg" xml:lang="en-us"><?Pub Caret?> -<title>Adding a Registry to the Web Services Explorer</title> -<titlealts> -<searchtitle>Adding a Registry to the Web Services Explorer</searchtitle> -</titlealts> -<shortdesc>Although the Web Services Explorer comes populated with several -registries, you can also add additional registries to your list of favorites.</shortdesc> -<taskbody> -<prereq><p>Prerequisites:<ol> -<li><xref href="treg.dita">Register with a registry</xref></li> -<li><xref href="tstrtexp.dita">Launch the Web Services Explorer</xref></li> -</ol></p></prereq> -<context><p>When you are ready to publish your business entity and Web service, -add a production registry to the Web Services Explorer. In order to publish -your business entity and Web service to a production registry, you must first -register with the registry. The registry will provide instructions for registering. -For more information on registries, refer to <xref href="treg.dita">Registering -with a registry</xref>.</p><p>The UDDI Business Registry is a set of global -replicated registries. For a list of public registries refer to <xref href="http://www.UDDI.org/register.html" -scope="external">www.uddi.org/register.html</xref></p><p>The <tm tmclass="ibm" -tmowner="IBM Corporation" tmtype="reg" trademark="IBM">IBM</tm> UDDI Business -Registry is a public production registry maintained by <tm tmclass="ibm" tmowner="IBM Corporation" -tmtype="reg" trademark="IBM">IBM</tm>. For more information on the <tm tmclass="ibm" -tmowner="IBM Corporation" tmtype="reg" trademark="IBM">IBM</tm> UDDI Business -Registry refer to <xref format="html" href="http://uddi.ibm.com" scope="external">http://uddi.ibm.com</xref></p></context> -<steps> -<step><cmd>To add a Registry to the Web Services Explorer from Favorites, -do the following:</cmd> -<substeps> -<substep><cmd>Click the <uicontrol>Favorites</uicontrol> icon <image alt="Picture of the Favorites icon." -href="../images/fav.gif"></image> in the main toolbar.</cmd></substep> -<substep><cmd>Expand <uicontrol>Favorite UDDI Registries</uicontrol>.</cmd> -</substep> -<substep><cmd>Select a registry then click the <uicontrol>Add to UDDI Page</uicontrol> icon - <image alt="Picture of the Add to UDDI Page icon." href="../images/adduddi.gif"> -</image> in the Actions pane.</cmd></substep> -</substeps> -</step> -<step><cmd>To add a Registry to the Web Services Explorer manually, do the -following:</cmd> -<substeps> -<substep><cmd>In the UDDI Navigator pane, click the <uicontrol>UDDI Main</uicontrol> node.</cmd> -</substep> -<substep><cmd>In the Actions pane, enter the Registry name and Inquiry URL -of the registry you want to add.</cmd></substep> -<substep><cmd>Click <uicontrol>Go</uicontrol>.</cmd></substep> -</substeps> -</step> -</steps> -</taskbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.dita" scope="peer"> -<linktext> Tools for Web services development</linktext></link> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cws.dita" scope="peer"> -<linktext>Web services development</linktext></link> -<link href="../concepts/cuddi.dita"></link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="tuddiexp.dita"></link> -<link href="tstrtexp.dita"></link> -<link href="treg.dita"></link> -</linklist> -<linklist><title>Related Reference</title> -<link href="../ref/ruddi.dita"></link> -</linklist> -</related-links> -</task> -<?Pub *0000003609?> diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/taddreg.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/taddreg.html deleted file mode 100644 index 01a8899d7..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/taddreg.html +++ /dev/null @@ -1,112 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding a Registry to the Web Services Explorer" /> -<meta name="abstract" content="Although the Web Services Explorer comes populated with several registries, you can also add additional registries to your list of favorites." /> -<meta name="description" content="Although the Web Services Explorer comes populated with several registries, you can also add additional registries to your list of favorites." /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cws.html" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cuddi.html" /> -<meta scheme="URI" name="DC.Relation" content="tuddiexp.html" /> -<meta scheme="URI" name="DC.Relation" content="tstrtexp.html" /> -<meta scheme="URI" name="DC.Relation" content="treg.html" /> -<meta scheme="URI" name="DC.Relation" content="../ref/ruddi.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddreg" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Adding a Registry to the Web Services Explorer</title> -</head> -<body id="taddreg"><a name="taddreg"><!-- --></a> - - -<h1 class="topictitle1">Adding a Registry to the Web Services Explorer</h1> - - - -<div><p>Although the Web Services Explorer comes populated with several -registries, you can also add additional registries to your list of favorites.</p> - -<div class="p"><div class="p">Prerequisites:<ol> -<li><a href="treg.html">Register with a registry</a></li> - -<li><a href="tstrtexp.html">Launch the Web Services Explorer</a></li> - -</ol> -</div> -</div> - -<div class="section"><p>When you are ready to publish your business entity and Web service, -add a production registry to the Web Services Explorer. In order to publish -your business entity and Web service to a production registry, you must first -register with the registry. The registry will provide instructions for registering. -For more information on registries, refer to <a href="treg.html">Registering with a registry</a>.</p> -<p>The UDDI Business Registry is a set of global -replicated registries. For a list of public registries refer to <a href="http://www.UDDI.org/register.html" target="_blank">www.uddi.org/register.html</a></p> -<p>The IBM<sup>®</sup> UDDI Business -Registry is a public production registry maintained by IBM. For more information on the IBM UDDI Business -Registry refer to <a href="http://uddi.ibm.com" target="_blank">http://uddi.ibm.com</a></p> -</div> - -<ol> -<li><span>To add a Registry to the Web Services Explorer from Favorites, -do the following:</span> -<ol type="a"> -<li><span>Click the <span class="uicontrol">Favorites</span> icon <img src="../images/fav.gif" alt="Picture of the Favorites icon." /> in the main toolbar.</span></li> - -<li><span>Expand <span class="uicontrol">Favorite UDDI Registries</span>.</span> -</li> - -<li><span>Select a registry then click the <span class="uicontrol">Add to UDDI Page</span> icon - <img src="../images/adduddi.gif" alt="Picture of the Add to UDDI Page icon." /> in the Actions pane.</span></li> - -</ol> - -</li> - -<li><span>To add a Registry to the Web Services Explorer manually, do the -following:</span> -<ol type="a"> -<li><span>In the UDDI Navigator pane, click the <span class="uicontrol">UDDI Main</span> node.</span> -</li> - -<li><span>In the Actions pane, enter the Registry name and Inquiry URL -of the registry you want to add.</span></li> - -<li><span>Click <span class="uicontrol">Go</span>.</span></li> - -</ol> - -</li> - -</ol> - -</div> - -<div> -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> -<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> -<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div> -<div><a href="treg.html" title="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use.">Registering with a UDDI registry</a></div></div> - -<div class="linklist"><strong>Related Reference</strong><br /> - -<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tassert.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tassert.dita deleted file mode 100644 index d64061e65..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tassert.dita +++ /dev/null @@ -1,57 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd"> -<task id="tassert" xml:lang="en-us"> -<title>Managing publisher assertions</title> -<shortdesc>A publisher assertion is a way in UDDI to associate businessEntity -structures. The publisher assertion defines a group of businessEntity -structures. Many businesses are not effectively represented by a single businessEntity. -A publisher assertion allows for associations to be formed between several -businessEntity structures. For example, a large company may have several subsidiaries -that have different descriptions but are still closely coupled and want to -make their relationships visible in UDDI registries.</shortdesc> -<taskbody> -<prereq>Prerequisites:<ol> -<li><xref href="treg.dita">Register with a registry</xref></li> -<li><xref href="tstrtexp.dita">Launch the<?Pub Caret?> Web Services Explorer</xref></li> -<li><xref href="taddreg.dita">Add the registry to the Web Services Explorer</xref></li> -</ol></prereq> -<context><p>For more information on publisher assertions, refer to the <xref -href="http://www.uddi.org/specification.html" scope="external">UDDI Version -2.0 Programmer's API Specification</xref> and the <xref href="http://www.uddi.org/specification.html" -scope="external">UDDI Version 2.0 Data Structure Specification</xref>.</p><p>To -manage publisher assertions, do the following:</p></context> -<steps> -<step><cmd>In the Navigator pane, select the business entity for which you -want to manage referenced businesses.</cmd></step> -<step><cmd>In the Actions pane toolbar, click the <uicontrol>Manage Publisher -Assertions</uicontrol> icon <image alt="Picture of the Manage Publisher Assertions icon." -href="../images/busasst.gif"></image>.</cmd></step> -<step><cmd>On the Manage Publisher Assertions page you can add, remove, and -maintain relationships with other business entities.</cmd></step> -</steps> -<result><p> <uicontrol>Important:</uicontrol> A business entity that is referenced -by another business entity must in turn reference that business entity in -order to make the publisher assertion public. A one-way reference is considered -an incomplete publisher assertion and is visible only to the owner of the -business entity.</p></result> -</taskbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.dita" scope="peer"> -<linktext> Tools for Web services development</linktext></link> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cws.dita" scope="peer"> -<linktext>Web services development</linktext></link> -<link href="../concepts/cuddi.dita"></link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="tuddiexp.dita"></link> -<link href="tstrtexp.dita"></link> -<link href="treg.dita"></link> -</linklist> -<linklist><title>Related Reference</title> -<link href="../ref/ruddi.dita"></link> -</linklist> -</related-links> -</task> -<?Pub *0000003014?> diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tassert.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tassert.html deleted file mode 100644 index 9a13bacfb..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tassert.html +++ /dev/null @@ -1,96 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Managing publisher assertions" /> -<meta name="abstract" content="A publisher assertion is a way in UDDI to associate businessEntity structures. The publisher assertion defines a group of businessEntity structures. Many businesses are not effectively represented by a single businessEntity. A publisher assertion allows for associations to be formed between several businessEntity structures. For example, a large company may have several subsidiaries that have different descriptions but are still closely coupled and want to make their relationships visible in UDDI registries." /> -<meta name="description" content="A publisher assertion is a way in UDDI to associate businessEntity structures. The publisher assertion defines a group of businessEntity structures. Many businesses are not effectively represented by a single businessEntity. A publisher assertion allows for associations to be formed between several businessEntity structures. For example, a large company may have several subsidiaries that have different descriptions but are still closely coupled and want to make their relationships visible in UDDI registries." /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cws.html" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cuddi.html" /> -<meta scheme="URI" name="DC.Relation" content="tuddiexp.html" /> -<meta scheme="URI" name="DC.Relation" content="tstrtexp.html" /> -<meta scheme="URI" name="DC.Relation" content="treg.html" /> -<meta scheme="URI" name="DC.Relation" content="../ref/ruddi.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tassert" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Managing publisher assertions</title> -</head> -<body id="tassert"><a name="tassert"><!-- --></a> - - -<h1 class="topictitle1">Managing publisher assertions</h1> - - -<div><p>A publisher assertion is a way in UDDI to associate businessEntity -structures. The publisher assertion defines a group of businessEntity -structures. Many businesses are not effectively represented by a single businessEntity. -A publisher assertion allows for associations to be formed between several -businessEntity structures. For example, a large company may have several subsidiaries -that have different descriptions but are still closely coupled and want to -make their relationships visible in UDDI registries.</p> - -<div class="p">Prerequisites:<ol> -<li><a href="treg.html">Register with a registry</a></li> - -<li><a href="tstrtexp.html">Launch the Web Services Explorer</a></li> - -<li><a href="taddreg.html">Add the registry to the Web Services Explorer</a></li> - -</ol> -</div> - -<div class="section"><p>For more information on publisher assertions, refer to the <a href="http://www.uddi.org/specification.html" target="_blank">UDDI Version 2.0 Programmer's API Specification</a> and the <a href="http://www.uddi.org/specification.html" target="_blank">UDDI Version 2.0 Data Structure Specification</a>.</p> -<p>To -manage publisher assertions, do the following:</p> -</div> - -<ol> -<li><span>In the Navigator pane, select the business entity for which you -want to manage referenced businesses.</span></li> - -<li><span>In the Actions pane toolbar, click the <span class="uicontrol">Manage Publisher -Assertions</span> icon <img src="../images/busasst.gif" alt="Picture of the Manage Publisher Assertions icon." />.</span></li> - -<li><span>On the Manage Publisher Assertions page you can add, remove, and -maintain relationships with other business entities.</span></li> - -</ol> - -<div class="section"><p> <span class="uicontrol">Important:</span> A business entity that is referenced -by another business entity must in turn reference that business entity in -order to make the publisher assertion public. A one-way reference is considered -an incomplete publisher assertion and is visible only to the owner of the -business entity.</p> -</div> - -</div> - -<div> -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> -<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> -<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div> -<div><a href="treg.html" title="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use.">Registering with a UDDI registry</a></div></div> - -<div class="linklist"><strong>Related Reference</strong><br /> - -<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbkmrk.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbkmrk.dita deleted file mode 100644 index d82ec6d5c..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbkmrk.dita +++ /dev/null @@ -1,51 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd"> -<task id="tbkmrk" xml:lang="en-us"> -<title>Adding a registry, business entity, business service, service interface, -WSIL, or WSDL service to Favorites</title> -<titlealts> -<searchtitle>Adding a registry, business entity, business service, service -interface, WSIL, or WSDL service to Favorites</searchtitle> -</titlealts> -<taskbody> -<prereq>Prerequisite: <ul> -<li><xref href="tstrtexp.dita">Launch the Web Services Explorer</xref></li> -</ul></prereq> -<context><p>To add a registry, business entity, Web service, service interface, -WSIL, or WSDL to Favorites using the<?Pub Caret?> Web Services Explorer:</p></context> -<steps> -<step><cmd>Navigate through the registry hierarchy to find the registry, business -entity, Web service, service interface or the WSIL page to find the WSIL or -WSDL service you want to add to Favorites.</cmd></step> -<step><cmd>Select the business entity, Web service, service interface, WSIL, -or WSDL service.</cmd></step> -<step><cmd>In the Actions icon bar, click the <uicontrol>Add to favorites</uicontrol> icon - <image alt="Picture of the Add to favorites icon." href="../images/addfav.gif"> -</image>.</cmd></step> -</steps> -<result><p>Any favorites that you add are saved by the Web Services Explorer -to </p><p> <varname>X</varname>:\workspace\.metadata\.plugins\com.ibm.etools.webservice.explorer\favorites.wsil</p><p>Where - <varname>X</varname> is the directory where your workspace folder is located. -If you are migrating from an earlier version of the product, your favorites -will be automatically migrated to this location.</p></result> -</taskbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.dita" scope="peer"> -<linktext> Tools for Web services development</linktext></link> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cws.dita" scope="peer"> -<linktext>Web services development</linktext></link> -<link href="../concepts/cuddi.dita"></link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="tuddiexp.dita"></link> -<link href="tstrtexp.dita"></link> -<link href="treg.dita"></link> -</linklist> -<linklist><title>Related Reference</title> -<link href="../ref/ruddi.dita"></link> -</linklist> -</related-links> -</task> -<?Pub *0000002422?> diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbkmrk.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbkmrk.html deleted file mode 100644 index 27bf2f089..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbkmrk.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="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding a registry, business entity, business service, service interface, WSIL, or WSDL service to Favorites" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cws.html" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cuddi.html" /> -<meta scheme="URI" name="DC.Relation" content="tuddiexp.html" /> -<meta scheme="URI" name="DC.Relation" content="tstrtexp.html" /> -<meta scheme="URI" name="DC.Relation" content="treg.html" /> -<meta scheme="URI" name="DC.Relation" content="../ref/ruddi.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tbkmrk" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Adding a registry, business entity, business service, service -interface, WSIL, or WSDL service to Favorites</title> -</head> -<body id="tbkmrk"><a name="tbkmrk"><!-- --></a> - - -<h1 class="topictitle1">Adding a registry, business entity, business service, service interface, -WSIL, or WSDL service to Favorites</h1> - - -<div> -<div class="p">Prerequisite: <ul> -<li><a href="tstrtexp.html">Launch the Web Services Explorer</a></li> - -</ul> -</div> - -<div class="section"><p>To add a registry, business entity, Web service, service interface, -WSIL, or WSDL to Favorites using the Web Services Explorer:</p> -</div> - -<ol> -<li><span>Navigate through the registry hierarchy to find the registry, business -entity, Web service, service interface or the WSIL page to find the WSIL or -WSDL service you want to add to Favorites.</span></li> - -<li><span>Select the business entity, Web service, service interface, WSIL, -or WSDL service.</span></li> - -<li><span>In the Actions icon bar, click the <span class="uicontrol">Add to favorites</span> icon - <img src="../images/addfav.gif" alt="Picture of the Add to favorites icon." />.</span></li> - -</ol> - -<div class="section"><p>Any favorites that you add are saved by the Web Services Explorer -to </p> -<p> <var class="varname">X</var>:\workspace\.metadata\.plugins\com.ibm.etools.webservice.explorer\favorites.wsil</p> -<p>Where - <var class="varname">X</var> is the directory where your workspace folder is located. -If you are migrating from an earlier version of the product, your favorites -will be automatically migrated to this location.</p> -</div> - -</div> - -<div> -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> -<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> -<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div> -<div><a href="treg.html" title="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use.">Registering with a UDDI registry</a></div></div> - -<div class="linklist"><strong>Related Reference</strong><br /> - -<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbusproj.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbusproj.dita deleted file mode 100644 index 719454c6f..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbusproj.dita +++ /dev/null @@ -1,50 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd"> -<task id="tbusproj" xml:lang="en-us"> -<title>Managing referenced services</title> -<shortdesc>A service projection enables a business entity to reference a service -that was published by another business entity. By using the businessService -structure as a projection to an already published businessService, businesses -can share or reuse services. Service projections are managed centrally -as part of the referencing businessEntity.</shortdesc> -<taskbody> -<prereq>Prerequisites:<ol> -<li><xref href="treg.dita">Register with a registry</xref></li> -<li><xref href="tstrtexp.dita">Launch the <?Pub Caret?>Web Services Explorer</xref></li> -<li><xref href="taddreg.dita">Add the registry to the Web Services Explorer</xref></li> -</ol></prereq> -<context><p>For more information on referenced services, refer to the <xref -href="http://www.uddi.org/specification.html" scope="external">UDDI Version -2.0 Programmer's API Specification</xref> and the <xref href="http://www.uddi.org/specification.html" -scope="external">UDDI Version 2.0 Data Structure Specification</xref>.</p><p>To -manage referenced services, do the following:</p></context> -<steps> -<step><cmd>In the Navigator pane, select the business entity for which you -want to manage referenced services.</cmd></step> -<step><cmd>In the Actions pane toolbar, click the <uicontrol>Manage Referenced -Services</uicontrol> icon <image alt="Picture of the Manage Referenced Services icon." -href="../images/refserv.gif"></image>.</cmd></step> -<step><cmd>On the Manage Referenced Services page you can add, remove, and -maintain services that are referenced by the business entity.</cmd></step> -</steps> -</taskbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.dita" scope="peer"> -<linktext> Tools for Web services development</linktext></link> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cws.dita" scope="peer"> -<linktext>Web services development</linktext></link> -<link href="../concepts/cuddi.dita"></link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="tuddiexp.dita"></link> -<link href="tstrtexp.dita"></link> -<link href="treg.dita"></link> -</linklist> -<linklist><title>Related Reference</title> -<link href="../ref/ruddi.dita"></link> -</linklist> -</related-links> -</task> -<?Pub *0000002499?> diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbusproj.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbusproj.html deleted file mode 100644 index d24195b34..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbusproj.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="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Managing referenced services" /> -<meta name="abstract" content="A service projection enables a business entity to reference a service that was published by another business entity. By using the businessService structure as a projection to an already published businessService, businesses can share or reuse services. Service projections are managed centrally as part of the referencing businessEntity." /> -<meta name="description" content="A service projection enables a business entity to reference a service that was published by another business entity. By using the businessService structure as a projection to an already published businessService, businesses can share or reuse services. Service projections are managed centrally as part of the referencing businessEntity." /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cws.html" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cuddi.html" /> -<meta scheme="URI" name="DC.Relation" content="tuddiexp.html" /> -<meta scheme="URI" name="DC.Relation" content="tstrtexp.html" /> -<meta scheme="URI" name="DC.Relation" content="treg.html" /> -<meta scheme="URI" name="DC.Relation" content="../ref/ruddi.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tbusproj" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Managing referenced services</title> -</head> -<body id="tbusproj"><a name="tbusproj"><!-- --></a> - - -<h1 class="topictitle1">Managing referenced services</h1> - - -<div><p>A service projection enables a business entity to reference a service -that was published by another business entity. By using the businessService -structure as a projection to an already published businessService, businesses -can share or reuse services. Service projections are managed centrally -as part of the referencing businessEntity.</p> - -<div class="p">Prerequisites:<ol> -<li><a href="treg.html">Register with a registry</a></li> - -<li><a href="tstrtexp.html">Launch the Web Services Explorer</a></li> - -<li><a href="taddreg.html">Add the registry to the Web Services Explorer</a></li> - -</ol> -</div> - -<div class="section"><p>For more information on referenced services, refer to the <a href="http://www.uddi.org/specification.html" target="_blank">UDDI Version 2.0 Programmer's API Specification</a> and the <a href="http://www.uddi.org/specification.html" target="_blank">UDDI Version 2.0 Data Structure Specification</a>.</p> -<p>To -manage referenced services, do the following:</p> -</div> - -<ol> -<li><span>In the Navigator pane, select the business entity for which you -want to manage referenced services.</span></li> - -<li><span>In the Actions pane toolbar, click the <span class="uicontrol">Manage Referenced -Services</span> icon <img src="../images/refserv.gif" alt="Picture of the Manage Referenced Services icon." />.</span></li> - -<li><span>On the Manage Referenced Services page you can add, remove, and -maintain services that are referenced by the business entity.</span></li> - -</ol> - -</div> - -<div> -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> -<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> -<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div> -<div><a href="treg.html" title="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use.">Registering with a UDDI registry</a></div></div> - -<div class="linklist"><strong>Related Reference</strong><br /> - -<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tdiscov.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tdiscov.dita deleted file mode 100644 index 890aaf3b5..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tdiscov.dita +++ /dev/null @@ -1,173 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd"> -<task id="tdiscov" xml:lang="en-us"> -<title>Discovering Web Services</title> -<titlealts> -<searchtitle>Discovering and importing Web services</searchtitle> -</titlealts> -<shortdesc>Web services can be located through a public business registry -such as the <tm tmclass="ibm" tmowner="IBM Corporation" tmtype="reg" trademark="IBM">IBM</tm> UDDI -Business Registry, a private business registry, or a WSIL document. UDDI manages -the discovery of Web services by relying on a distributed registry of businesses -and their service descriptions implemented in a common XML format.</shortdesc> -<taskbody> -<prereq><p>Prerequisites:<ol> -<li><xref href="treg.dita">Register with a registry</xref></li> -<li><xref href="tstrtexp.dita">Launch the Web Services Explorer</xref></li> -<li><xref href="taddreg.dita">Add the registry to the Web Services Explorer</xref></li> -</ol></p></prereq> -<context><p>Web Services Inspection Language (WSIL) is a service discovery -mechanism that is an alternative to UDDI as well as complementary to UDDI. -WSIL allows you to go directly to the service provider and ask for the services -it provides. For more information on the Web Services Inspection Language -specification, refer to <xref href="http://www-106.ibm.com/developerworks/webservices/library/ws-wsilspec.html" -scope="external"> www.ibm.com/developerworks/webservices/library/ws-wsilspec.html</xref>. - For more information on UDDI and the <tm tmclass="ibm" tmowner="IBM Corporation" -tmtype="reg" trademark="IBM">IBM</tm> UDDI Business registries, refer to <xref -href="http://www.ibm.com/services/uddi/index.html" scope="external">www.ibm.com/services/uddi/index.html</xref>.</p><p>You -can discover a Web service in two ways using the Web Services Explorer:</p></context> -<result><ul> -<li> <xref href="#tdiscov/discover_from_uddi">Discovering a Web service from -a UDDI registry</xref> </li> -<li> <xref href="#tdiscov/discover_from_wsil">Discovering a Web service from -a WSIL document</xref> </li> -</ul></result> -</taskbody> -<task id="discover_from_uddi" xml:lang="en-us"> -<title> Discovering a Web Service from a UDDI Registry</title> -<taskbody> -<context><p>The registry contains URL references to Web service WSDL documents. -In order to discover a Web service the URL to the Web service WSDL document -must be resolvable. To locate Web service descriptions:</p></context> -<steps> -<step><cmd>Launch the Web Services Explorer</cmd></step> -<step><cmd>Click <uicontrol>UDDI Main</uicontrol>.</cmd></step> -<step><cmd>In the Actions pane select a registry from the drop-down list and -click <uicontrol>Go</uicontrol>.</cmd></step> -<step><cmd>In the Actions pane toolbar click the <b>Find</b> icon <image -alt="A picture of the Find icon." href="../images/find.gif"></image>.</cmd> -</step> -<step><cmd>In the Actions pane, enter the name of the query, what you are -searching for, the type of search that you want to perform, and any query -information: </cmd> -<substeps> -<substep><cmd> <b>Search for</b> This list allows you to search for -businesses, services, or service interfaces. </cmd><info><ul> -<li> <b>Businesses</b> Once you locate a business in the registry, use the -icons in the Action pane toolbar to do the following:<ul> -<li>View and edit business details</li> -<li>Get the services associated with that business</li> -<li>Publish a service</li> -<li>Manage referenced services</li> -<li>Manage publisher assertions</li> -<li>Add the business to Favorites</li> -<li>Unpublish the business</li> -</ul></li> -<li> <b>Services</b> Once you locate a service in the registry, use the icons -in the Action pane toolbar to do the following: <ul> -<li>View and edit service details</li> -<li>Get the business associated with that service</li> -<li>Get the service interfaces associated with that service</li> -<li>Import the service WSDL file to the Eclipse workbench</li> -<li>Import the service WSDL file to the file system</li> -<li>Launch the Web Service wizards</li> -<li>Add the service to Favorites</li> -<li>Unpublish the service</li> -</ul></li> -<li> <b>Service interfaces</b> Once you locate a service interface in the -registry, use the icons in the Action pane toolbar to do the following: <ul> -<li>View and edit interface details</li> -<li>Get the services associated with that service interface</li> -<li>Get the businesses associated with that service interface</li> -<li>Import the service interface WSDL file to the Eclipse workbench</li> -<li>Import the service interface WSDL file to the file system</li> -<li>Launch the Web Service wizards</li> -<li>Add the service interface to Favorites</li> -<li>Unpublish the service interface</li> -</ul></li> -</ul></info></substep> -<substep><cmd> <b>Type of search</b> These radio buttons allow you to -specify a simple or advanced search, or a search by a Universal Unique Identifier -(UUID). </cmd><info><dl><dlentry> -<dt>Simple</dt> -<dd>Type the name of the businesses, services, or service interfaces for which -you are searching. <b>Note:</b> The search set size is set to 100 and the -maximum number of returned results is set to 10 by default. If you would -like to override the defaults, use the Advanced search.</dd> -</dlentry><dlentry> -<dt>Advanced </dt> -<dd>Allows you to enter more search options to focus the scope of your search. -Select this option if you would like to search for multiple businesses or -services.</dd> -</dlentry><dlentry> -<dt>UUID </dt> -<dd>Allow you to enter the UUID key. The UUID key is the identifier that is -associated with the published object.</dd> -</dlentry></dl></info></substep> -</substeps> -</step> -<step><cmd>Once you have searched and discovered the business service description -you desired, select the service or the service interface and click the <b>Import</b> icon -to: </cmd> -<choices> -<choice>import the WSDL document into your Web project</choice> -<choice>import the WSDL document into the WSDL Explorer for testing</choice> -<choice>launch the Web Service Skeleton Creation wizard or Web Service Client -wizard directly from the Web Services Explorer.</choice> -</choices> -</step> -</steps> -</taskbody> -</task> -<task id="discover_from_wsil" xml:lang="en-us"> -<title> Discovering a Web Service from a WSIL Document</title> -<taskbody> -<context><p>To locate Web service descriptions:</p></context> -<steps> -<step><cmd>From the Web Services Explorer toolbar, click the <b>WSIL Page</b> icon - <image alt="Picture of the WSIL Page icon." href="../images/wsilview.gif"> -</image>.</cmd></step> -<step><cmd>In the Navigator pane, click <b>WSIL Main</b>.</cmd></step> -<step><cmd>In the <b>URL to document</b> field of the Actions pane enter -the URL to the WSIL document or HTTP document that contains links to a WSIL -document. Details on how an HTTP file can contain links to WSIL can be found -here: http://www.ibm.com/developerworks/webservices/library/ws-wsilspec.html</cmd> -</step> -<step><cmd>Once you have located the WSIL document, use the icons in the Action -pane toolbar to do the following:</cmd> -<choices> -<choice>View WSIL document details</choice> -<choice>List all of the WSDL services associated with that WSIL document</choice> -<choice>List all of the UDDI services associated with that WSIL document</choice> -<choice>List all of the UDDI businesses associated with that WSIL document</choice> -<choice>List all of the WSIL links associated with that WSIL document</choice> -<choice>Import the WSIL document to the file system</choice> -<choice>Add the WSIL document to Favorites</choice> -</choices> -<info><b>Important:</b> If the Web Services Explorer does not display the -project that you would like to import your WSDL file to, ensure that you have -created the project and/or click the <b>Refresh</b> icon.</info></step> -</steps> -</taskbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.dita" scope="peer"> -<linktext> Tools for Web services development</linktext></link> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cws.dita" scope="peer"> -<linktext>Web services development</linktext></link> -<link href="../concepts/cuddi.dita"></link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="tuddiexp.dita"></link> -<link href="tstrtexp.dita"></link> -<link href="treg.dita"></link> -<link href="../../org.eclipse.jst.ws.doc.user/tasks/toverws.dita" product="" -scope="peer"><linktext> Developing Web services</linktext></link> -</linklist> -<linklist><title>Related Reference</title> -<link href="../ref/ruddi.dita"></link> -</linklist> -</related-links> -</task> -</task> diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tdiscov.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tdiscov.html deleted file mode 100644 index 6202e1956..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tdiscov.html +++ /dev/null @@ -1,273 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Discovering Web Services" /> -<meta name="abstract" content="Web services can be located through a public business registry such as the IBM UDDI Business Registry, a private business registry, or a WSIL document. UDDI manages the discovery of Web services by relying on a distributed registry of businesses and their service descriptions implemented in a common XML format." /> -<meta name="description" content="Web services can be located through a public business registry such as the IBM UDDI Business Registry, a private business registry, or a WSIL document. UDDI manages the discovery of Web services by relying on a distributed registry of businesses and their service descriptions implemented in a common XML format." /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tdiscov" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Discovering and importing Web services</title> -</head> -<body id="tdiscov"><a name="tdiscov"><!-- --></a> - - -<h1 class="topictitle1">Discovering Web Services</h1> - - - -<div><p>Web services can be located through a public business registry -such as the IBM<sup>®</sup> UDDI -Business Registry, a private business registry, or a WSIL document. UDDI manages -the discovery of Web services by relying on a distributed registry of businesses -and their service descriptions implemented in a common XML format.</p> - -<div class="p"><div class="p">Prerequisites:<ol> -<li><a href="treg.html">Register with a registry</a></li> - -<li><a href="tstrtexp.html">Launch the Web Services Explorer</a></li> - -<li><a href="taddreg.html">Add the registry to the Web Services Explorer</a></li> - -</ol> -</div> -</div> - -<div class="section"><p>Web Services Inspection Language (WSIL) is a service discovery -mechanism that is an alternative to UDDI as well as complementary to UDDI. -WSIL allows you to go directly to the service provider and ask for the services -it provides. For more information on the Web Services Inspection Language -specification, refer to <a href="http://www-106.ibm.com/developerworks/webservices/library/ws-wsilspec.html" target="_blank">www.ibm.com/developerworks/webservices/library/ws-wsilspec.html</a>. - For more information on UDDI and the IBM UDDI Business registries, refer to <a href="http://www.ibm.com/services/uddi/index.html" target="_blank">www.ibm.com/services/uddi/index.html</a>.</p> -<p>You -can discover a Web service in two ways using the Web Services Explorer:</p> -</div> - -<div class="section"><ul> -<li> <a href="#tdiscov__discover_from_uddi">Discovering a Web service from a UDDI registry</a> </li> - -<li> <a href="#tdiscov__discover_from_wsil">Discovering a Web service from a WSIL document</a> </li> - -</ul> -</div> - -</div> - -<div class="nested1" xml:lang="en-us" id="discover_from_uddi"><a name="discover_from_uddi"><!-- --></a> -<h2 class="topictitle2"> Discovering a Web Service from a UDDI Registry</h2> - -<div> -<div class="section"><p>The registry contains URL references to Web service WSDL documents. -In order to discover a Web service the URL to the Web service WSDL document -must be resolvable. To locate Web service descriptions:</p> -</div> - -<ol> -<li><span>Launch the Web Services Explorer</span></li> - -<li><span>Click <span class="uicontrol">UDDI Main</span>.</span></li> - -<li><span>In the Actions pane select a registry from the drop-down list and -click <span class="uicontrol">Go</span>.</span></li> - -<li><span>In the Actions pane toolbar click the <strong>Find</strong> icon <img src="../images/find.gif" alt="A picture of the Find icon." />.</span> -</li> - -<li><span>In the Actions pane, enter the name of the query, what you are -searching for, the type of search that you want to perform, and any query -information: </span> -<ol type="a"> -<li class="substepexpand"><span> <strong>Search for</strong> This list allows you to search for -businesses, services, or service interfaces. </span> <ul> -<li> <strong>Businesses</strong> Once you locate a business in the registry, use the -icons in the Action pane toolbar to do the following:<ul> -<li>View and edit business details</li> - -<li>Get the services associated with that business</li> - -<li>Publish a service</li> - -<li>Manage referenced services</li> - -<li>Manage publisher assertions</li> - -<li>Add the business to Favorites</li> - -<li>Unpublish the business</li> - -</ul> -</li> - -<li> <strong>Services</strong> Once you locate a service in the registry, use the icons -in the Action pane toolbar to do the following: <ul> -<li>View and edit service details</li> - -<li>Get the business associated with that service</li> - -<li>Get the service interfaces associated with that service</li> - -<li>Import the service WSDL file to the Eclipse workbench</li> - -<li>Import the service WSDL file to the file system</li> - -<li>Launch the Web Service wizards</li> - -<li>Add the service to Favorites</li> - -<li>Unpublish the service</li> - -</ul> -</li> - -<li> <strong>Service interfaces</strong> Once you locate a service interface in the -registry, use the icons in the Action pane toolbar to do the following: <ul> -<li>View and edit interface details</li> - -<li>Get the services associated with that service interface</li> - -<li>Get the businesses associated with that service interface</li> - -<li>Import the service interface WSDL file to the Eclipse workbench</li> - -<li>Import the service interface WSDL file to the file system</li> - -<li>Launch the Web Service wizards</li> - -<li>Add the service interface to Favorites</li> - -<li>Unpublish the service interface</li> - -</ul> -</li> - -</ul> -</li> - -<li class="substepexpand"><span> <strong>Type of search</strong> These radio buttons allow you to -specify a simple or advanced search, or a search by a Universal Unique Identifier -(UUID). </span> <dl> -<dt class="dlterm">Simple</dt> - -<dd>Type the name of the businesses, services, or service interfaces for which -you are searching. <strong>Note:</strong> The search set size is set to 100 and the -maximum number of returned results is set to 10 by default. If you would -like to override the defaults, use the Advanced search.</dd> - - -<dt class="dlterm">Advanced </dt> - -<dd>Allows you to enter more search options to focus the scope of your search. -Select this option if you would like to search for multiple businesses or -services.</dd> - - -<dt class="dlterm">UUID </dt> - -<dd>Allow you to enter the UUID key. The UUID key is the identifier that is -associated with the published object.</dd> - -</dl> -</li> - -</ol> - -</li> - -<li><span>Once you have searched and discovered the business service description -you desired, select the service or the service interface and click the <strong>Import</strong> icon -to: </span> -<ul> -<li>import the WSDL document into your Web project</li> - -<li>import the WSDL document into the WSDL Explorer for testing</li> - -<li>launch the Web Service Skeleton Creation wizard or Web Service Client -wizard directly from the Web Services Explorer.</li> - -</ul> - -</li> - -</ol> - -</div> - -</div> - -<div class="nested1" xml:lang="en-us" id="discover_from_wsil"><a name="discover_from_wsil"><!-- --></a> -<h2 class="topictitle2"> Discovering a Web Service from a WSIL Document</h2> - -<div> -<div class="section"><p>To locate Web service descriptions:</p> -</div> - -<ol> -<li class="stepexpand"><span>From the Web Services Explorer toolbar, click the <strong>WSIL Page</strong> icon - <img src="../images/wsilview.gif" alt="Picture of the WSIL Page icon." />.</span></li> - -<li class="stepexpand"><span>In the Navigator pane, click <strong>WSIL Main</strong>.</span></li> - -<li class="stepexpand"><span>In the <strong>URL to document</strong> field of the Actions pane enter -the URL to the WSIL document or HTTP document that contains links to a WSIL -document. Details on how an HTTP file can contain links to WSIL can be found -here: http://www.ibm.com/developerworks/webservices/library/ws-wsilspec.html</span> -</li> - -<li class="stepexpand"><span>Once you have located the WSIL document, use the icons in the Action -pane toolbar to do the following:</span> -<ul> -<li>View WSIL document details</li> - -<li>List all of the WSDL services associated with that WSIL document</li> - -<li>List all of the UDDI services associated with that WSIL document</li> - -<li>List all of the UDDI businesses associated with that WSIL document</li> - -<li>List all of the WSIL links associated with that WSIL document</li> - -<li>Import the WSIL document to the file system</li> - -<li>Add the WSIL document to Favorites</li> - -</ul> - - <strong>Important:</strong> If the Web Services Explorer does not display the -project that you would like to import your WSDL file to, ensure that you have -created the project and/or click the <strong>Refresh</strong> icon.</li> - -</ol> - -</div> - -<div> -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> -<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> -<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div> -<div><a href="treg.html" title="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use.">Registering with a UDDI registry</a></div> -<div><a href="../../org.eclipse.jst.ws.doc.user/tasks/toverws.html"> Developing Web services</a></div></div> - -<div class="linklist"><strong>Related Reference</strong><br /> - -<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div> -</div> -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tgenwsil.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tgenwsil.dita deleted file mode 100644 index c7cc9280c..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tgenwsil.dita +++ /dev/null @@ -1,68 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd"> -<task id="tgenwsil" xml:lang="en-us"><?Pub Caret1?> -<title>Generating a WSIL file</title> -<titlealts> -<searchtitle>Generating a WSIL file</searchtitle> -</titlealts> -<shortdesc>Web Services Inspection Language (WSIL) is a service discovery -mechanism that is an alternative to UDDI as well as complementary to UDDI. -WSIL can be generated at any point in the Web service development cycle once -the WSDL file for the Web service has been created.</shortdesc> -<taskbody> -<prereq><b>Prerequisites:</b> In order to generate a WSIL file, you need to -know the URL to a WSDL file.</prereq> -<context><p>WSIL helps synchronize this process by maintaining references -to WSDL URLs. Web services tools that process WSDL documents - such as the -Web Service Client and Creation wizards - will accept a WSIL document as a -substitute for WSDL. This allows you to create a standardized WSDL reference -(WSIL) document in your project during Web service client generation, then -at a later time easily regenerate the client from that reference document. -No copies of the WSDL or WSDL URLs are required.</p><p>You can generate a -WSIL file from a pre-existing WSDL file or during Web service creation or -consumption.</p></context> -</taskbody> -<task id="d0e27" xml:lang="en-us"> -<title>Generating a WSIL file though the import utility</title> -<taskbody> -<context><p>To generate a WSIL file through the import utility:</p></context> -<steps> -<step><cmd>Optional: Select the WSDL document for which you want to create -a WSIL file.</cmd></step> -<step><cmd>From the <b>File</b> menu, select <b>Import</b> > <b>WSIL > -Next</b>. The WSIL Import window opens.</cmd></step> -<step><cmd>If you have selected to perform step 1, the WSIL URI field should -be prefilled with the name of your WSDL file, where the extension has been -changed from <systemoutput>.wsdl</systemoutput> to <systemoutput>.wsil</systemoutput>. -The WSDL section should contain the URLs to the selected WSDL files. You can -also enter additional WSDL URLs. Alternately, you can browse to the location -of a WSIL file, or manually enter the location of the WSIL and WSDL files -in the appropriate locations.</cmd></step> -<step><cmd>Click Finish. A WSIL file will be generated in the specified location.</cmd> -</step> -</steps> -</taskbody> -</task> -<task id="d0e62" xml:lang="en-us"> -<title>Generating a WSIL file through the Web Services Explorer</title> -<taskbody> -<context><p>To generate a WSIL file through the Web Services Explorer:</p></context> -<steps> -<step><cmd>Open the Web Services Explorer.</cmd></step> -<step><cmd>Open the WSDL Explorer by clicking this icon: <image alt="icon used to launch the web services explorer" -href="../images/wsdlicon.gif"></image></cmd></step> -<step><cmd>Open a WSDL file.</cmd></step> -<step><cmd>Select the WSDL file that you have opened in the Navigator pane, -and from the available actions, choose to import a WSDL file to the workbench -by clicking this icon: <image alt="icon used to import a file" href="../images/mptwsdlicon.gif"> -</image></cmd></step> -<step><cmd>Select <b>Import as a service reference to a WSIL document</b>.</cmd> -</step> -<step><cmd>Enter a name for the WSIL file that you want to generate, and click - <b>Go</b>.</cmd></step> -</steps> -</taskbody> -</task> -</task> -<?Pub *0000003434?> diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tgenwsil.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tgenwsil.html deleted file mode 100644 index cbbc8e8fa..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tgenwsil.html +++ /dev/null @@ -1,112 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Generating a WSIL file" /> -<meta name="abstract" content="Web Services Inspection Language (WSIL) is a service discovery mechanism that is an alternative to UDDI as well as complementary to UDDI. WSIL can be generated at any point in the Web service development cycle once the WSDL file for the Web service has been created." /> -<meta name="description" content="Web Services Inspection Language (WSIL) is a service discovery mechanism that is an alternative to UDDI as well as complementary to UDDI. WSIL can be generated at any point in the Web service development cycle once the WSDL file for the Web service has been created." /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tgenwsil" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Generating a WSIL file</title> -</head> -<body id="tgenwsil"><a name="tgenwsil"><!-- --></a> - - -<h1 class="topictitle1">Generating a WSIL file</h1> - - - -<div><p>Web Services Inspection Language (WSIL) is a service discovery -mechanism that is an alternative to UDDI as well as complementary to UDDI. -WSIL can be generated at any point in the Web service development cycle once -the WSDL file for the Web service has been created.</p> - -<div class="p"><strong>Prerequisites:</strong> In order to generate a WSIL file, you need to -know the URL to a WSDL file.</div> - -<div class="section"><p>WSIL helps synchronize this process by maintaining references -to WSDL URLs. Web services tools that process WSDL documents - such as the -Web Service Client and Creation wizards - will accept a WSIL document as a -substitute for WSDL. This allows you to create a standardized WSDL reference -(WSIL) document in your project during Web service client generation, then -at a later time easily regenerate the client from that reference document. -No copies of the WSDL or WSDL URLs are required.</p> -<p>You can generate a -WSIL file from a pre-existing WSDL file or during Web service creation or -consumption.</p> -</div> - -</div> - -<div class="nested1" xml:lang="en-us" id="d0e27"><a name="d0e27"><!-- --></a> -<h2 class="topictitle2">Generating a WSIL file though the import utility</h2> - -<div> -<div class="section"><p>To generate a WSIL file through the import utility:</p> -</div> - -<ol> -<li><span>Optional: Select the WSDL document for which you want to create -a WSIL file.</span></li> - -<li><span>From the <strong>File</strong> menu, select <strong>Import</strong> > <strong>WSIL > -Next</strong>. The WSIL Import window opens.</span></li> - -<li><span>If you have selected to perform step 1, the WSIL URI field should -be prefilled with the name of your WSDL file, where the extension has been -changed from <tt class="sysout">.wsdl</tt> to <tt class="sysout">.wsil</tt>. -The WSDL section should contain the URLs to the selected WSDL files. You can -also enter additional WSDL URLs. Alternately, you can browse to the location -of a WSIL file, or manually enter the location of the WSIL and WSDL files -in the appropriate locations.</span></li> - -<li><span>Click Finish. A WSIL file will be generated in the specified location.</span> -</li> - -</ol> - -</div> - -</div> - -<div class="nested1" xml:lang="en-us" id="d0e62"><a name="d0e62"><!-- --></a> -<h2 class="topictitle2">Generating a WSIL file through the Web Services Explorer</h2> - -<div> -<div class="section"><p>To generate a WSIL file through the Web Services Explorer:</p> -</div> - -<ol> -<li><span>Open the Web Services Explorer.</span></li> - -<li><span>Open the WSDL Explorer by clicking this icon: <img src="../images/wsdlicon.gif" alt="icon used to launch the web services explorer" /></span></li> - -<li><span>Open a WSDL file.</span></li> - -<li><span>Select the WSDL file that you have opened in the Navigator pane, -and from the available actions, choose to import a WSDL file to the workbench -by clicking this icon: <img src="../images/mptwsdlicon.gif" alt="icon used to import a file" /></span></li> - -<li><span>Select <strong>Import as a service reference to a WSIL document</strong>.</span> -</li> - -<li><span>Enter a name for the WSIL file that you want to generate, and click - <strong>Go</strong>.</span></li> - -</ol> - -</div> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tlogexp.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tlogexp.dita deleted file mode 100644 index f500682a0..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tlogexp.dita +++ /dev/null @@ -1,50 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--ArborText, Inc., 1988-2002, v.4002--> -<!DOCTYPE task PUBLIC "-//IBM//DTD DITA Task//EN" - "..\dtd\task.dtd"> -<?Pub Inc?> -<task id="tlogexp" xml:lang="en-us"> -<title>Logging in to a UDDI registry</title> -<shortdesc> <uicontrol></uicontrol> </shortdesc> -<taskbody> -<prereq>Prerequisites:<ol> -<li><xref href="treg.dita">Register with a registry</xref></li> -<li><xref href="tstrtexp.dita">Launch the Web Services Explorer</xref></li> -</ol></prereq> -<context><p>To Log in to the registry:</p></context> -<steps> -<step><cmd> In the UDDI Navigator pane, select the registry.</cmd></step> -<step><cmd> In the Actions pane, select the <uicontrol>Login</uicontrol> icon - <image href="../images/login.gif" alt="Picture of the Login icon."/> in the -toolbar.</cmd></step> -<step><cmd>In the Actions pane, enter the publish URL and your user ID and -password in the <uicontrol>Publish URL</uicontrol>, <uicontrol>User ID</uicontrol> and - <uicontrol>Password</uicontrol> fields respectively. The Publish URL -field is the URL of the registry to which you are publishing your business -entity or business service. Click <uicontrol>Go</uicontrol>.</cmd> -</step> -</steps> -<result><p>When you have successfully logged in, the Status pane displays -a message indicating you were successful.</p></result> -</taskbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="../../com.ibm.etools.webservice.doc/concepts/cwsinwsa.dita" product="AD" -scope="peer"><linktext> Tools for Web services development</linktext></link> -<link href="../../com.ibm.etools.webservice.doc/concepts/cws.dita" product="AD" -scope="peer"><linktext>Web services development</linktext></link> -<link href="../concepts/cuddi.dita"></link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="tuddiexp.dita"></link> -<link href="tstrtexp.dita"></link> -<link href="treg.dita"></link> -<link href="../../com.ibm.etools.webservice.creation.doc/tasks/toverws.dita" -product="AD" scope="peer"><linktext> Developing Web services</linktext></link> -</linklist><?Pub Caret1?> -<linklist><title>Related Reference</title> -<link href="../ref/ruddi.dita"></link> -</linklist> -</related-links> -</task> -<?Pub *0000002235?> diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpubent.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpubent.dita deleted file mode 100644 index fceac20cd..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpubent.dita +++ /dev/null @@ -1,96 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd"> -<task id="tpubent" xml:lang="en-us"><?Pub Caret?> -<title>Publishing a business entity</title> -<shortdesc>A business entity contains information about the business that -has published a service. Before you can publish a business service, -you must publish a business entity.</shortdesc> -<taskbody> -<prereq>Prerequisites:<ol> -<li><xref href="treg.dita">Register with a registry</xref></li> -<li><xref href="tstrtexp.dita">Launch the Web Services Explorer</xref></li> -<li><xref href="taddreg.dita">Add the registry to the Web Services Explorer</xref></li> -</ol></prereq> -<context><p>You can publish a business entity using two different publication -formats: simple and advanced.</p><lq> <p> <uicontrol>Simple</uicontrol> Allows -you to enter the minimal amount of information required to publish your business -entity. A simple publish only allows you to specify only one name and -one business description.</p><p> <uicontrol>Advanced </uicontrol> Allows you -to enter more information about your business entity. An advanced publish -allows you to specify multiple names and descriptions for multi-lingual support.</p> </lq></context> -</taskbody> -<task id="d0e74" xml:lang="en-us"> -<title>Publish a business entity using the simple option</title> -<taskbody> -<context><p>To publish a business entity using the simple option:</p></context> -<steps> -<step><cmd>In the Web Services Explorer, select UDDI Main and select the registry -to which you want to publish the business entity.</cmd></step> -<step><cmd>In the Navigator pane, select the business entity for which -you want to publish the business service.</cmd></step> -<step><cmd>In the Actions pane toolbar, click the <b>Publish</b> icon <image -alt="Picture of the Publish icon." href="../images/publish2.gif"></image>.</cmd> -</step> -<step><cmd>Select the <b>Simple</b> radio button.</cmd></step> -<step><cmd>Enter the publish URL, your user ID, password, WSDL URL, business -name, and business description in the respective fields.</cmd></step> -<step><cmd>Click <b>Go</b> to publish your business entity.</cmd></step> -</steps> -<result><p>The <tm tmclass="ibm" tmowner="IBM Corporation" tmtype="reg" trademark="IBM">IBM</tm> Web -Services Explorer is automatically updated with your published Web service. -The registry contains pointers to the URL of the WSDL service document of -the Web service. Businesses can now discover and integrate with your Web service.</p></result> -</taskbody> -</task> -<task id="d0e113" xml:lang="en-us"> -<title>Publish a business entity using the advanced option</title> -<taskbody> -<context><p>To publish a business entity using the advanced option:</p></context> -<steps> -<step><cmd>In the Web Services Explorer Navigator pane, select the business -entity for which you want to publish the business service.</cmd></step> -<step><cmd>In the Actions pane toolbar, click the <b>Publish Service</b> icon - <image alt="Picture of the Publish Service icon." href="../images/pubserv.gif"> -</image>.</cmd></step> -<step><cmd>Select the <b>Advanced</b> radio button.</cmd></step> -<step><cmd>Enter the publish URL, your user ID, password, and WSDL URL in -the respective fields.</cmd></step> -<step><cmd>Click <b>Add</b> to create business names.</cmd></step> -<step><cmd>Click <b>Add</b> to create business descriptions.</cmd></step> -<step><cmd>Click <uicontrol>Add</uicontrol> to create an identifier. For example, -an identifier for your business entity may be your business phone number. -The key name would be "Phone Number" and the key value would be your business -telephone number. </cmd></step> -<step><cmd>Click <b>Add</b> to create categories. Enter your business categories. -Select a category type from the drop down list. Click <b>Browse</b> to open -the Categories pane. Navigate through the hierarchical taxonomy and select -the appropriate classification for your business service, then exit the Categories -pane.</cmd></step> -<step><cmd>Click <b>Go</b> to publish your business entity.</cmd></step> -</steps> -<result><p>The Web Services Explorer is automatically updated with your published -Web service. The registry contains pointers to the URL of the WSDL service -document of the Web service. Businesses can now discover and integrate with -your Web service.</p></result> -</taskbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.dita" scope="peer"> -<linktext> Tools for Web services development</linktext></link> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cws.dita" scope="peer"> -<linktext>Web services development</linktext></link> -<link href="../concepts/cuddi.dita"></link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="tuddiexp.dita"></link> -<link href="tstrtexp.dita"></link> -<link href="treg.dita"></link> -</linklist> -<linklist><title>Related Reference</title> -<link href="../ref/ruddi.dita"></link> -</linklist> -</related-links> -</task> -</task> -<?Pub *0000005120?> diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpubent.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpubent.html deleted file mode 100644 index 940a4b1c9..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpubent.html +++ /dev/null @@ -1,157 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Publishing a business entity" /> -<meta name="abstract" content="A business entity contains information about the business that has published a service. Before you can publish a business service, you must publish a business entity." /> -<meta name="description" content="A business entity contains information about the business that has published a service. Before you can publish a business service, you must publish a business entity." /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tpubent" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Publishing a business entity</title> -</head> -<body id="tpubent"><a name="tpubent"><!-- --></a> - - -<h1 class="topictitle1">Publishing a business entity</h1> - - -<div><p>A business entity contains information about the business that -has published a service. Before you can publish a business service, -you must publish a business entity.</p> - -<div class="p">Prerequisites:<ol> -<li><a href="treg.html">Register with a registry</a></li> - -<li><a href="tstrtexp.html">Launch the Web Services Explorer</a></li> - -<li><a href="taddreg.html">Add the registry to the Web Services Explorer</a></li> - -</ol> -</div> - -<div class="section"><p>You can publish a business entity using two different publication -formats: simple and advanced.</p> -<blockquote> <p> <span class="uicontrol">Simple</span> Allows -you to enter the minimal amount of information required to publish your business -entity. A simple publish only allows you to specify only one name and -one business description.</p> -<p> <span class="uicontrol">Advanced </span> Allows you -to enter more information about your business entity. An advanced publish -allows you to specify multiple names and descriptions for multi-lingual support.</p> - </blockquote> -</div> - -</div> - -<div class="nested1" xml:lang="en-us" id="d0e74"><a name="d0e74"><!-- --></a> -<h2 class="topictitle2">Publish a business entity using the simple option</h2> - -<div> -<div class="section"><p>To publish a business entity using the simple option:</p> -</div> - -<ol> -<li><span>In the Web Services Explorer, select UDDI Main and select the registry -to which you want to publish the business entity.</span></li> - -<li><span>In the Navigator pane, select the business entity for which -you want to publish the business service.</span></li> - -<li><span>In the Actions pane toolbar, click the <strong>Publish</strong> icon <img src="../images/publish2.gif" alt="Picture of the Publish icon." />.</span> -</li> - -<li><span>Select the <strong>Simple</strong> radio button.</span></li> - -<li><span>Enter the publish URL, your user ID, password, WSDL URL, business -name, and business description in the respective fields.</span></li> - -<li><span>Click <strong>Go</strong> to publish your business entity.</span></li> - -</ol> - -<div class="section"><p>The IBM<sup>®</sup> Web -Services Explorer is automatically updated with your published Web service. -The registry contains pointers to the URL of the WSDL service document of -the Web service. Businesses can now discover and integrate with your Web service.</p> -</div> - -</div> - -</div> - -<div class="nested1" xml:lang="en-us" id="d0e113"><a name="d0e113"><!-- --></a> -<h2 class="topictitle2">Publish a business entity using the advanced option</h2> - -<div> -<div class="section"><p>To publish a business entity using the advanced option:</p> -</div> - -<ol> -<li><span>In the Web Services Explorer Navigator pane, select the business -entity for which you want to publish the business service.</span></li> - -<li><span>In the Actions pane toolbar, click the <strong>Publish Service</strong> icon - <img src="../images/pubserv.gif" alt="Picture of the Publish Service icon." />.</span></li> - -<li><span>Select the <strong>Advanced</strong> radio button.</span></li> - -<li><span>Enter the publish URL, your user ID, password, and WSDL URL in -the respective fields.</span></li> - -<li><span>Click <strong>Add</strong> to create business names.</span></li> - -<li><span>Click <strong>Add</strong> to create business descriptions.</span></li> - -<li><span>Click <span class="uicontrol">Add</span> to create an identifier. For example, -an identifier for your business entity may be your business phone number. -The key name would be "Phone Number" and the key value would be your business -telephone number. </span></li> - -<li><span>Click <strong>Add</strong> to create categories. Enter your business categories. -Select a category type from the drop down list. Click <strong>Browse</strong> to open -the Categories pane. Navigate through the hierarchical taxonomy and select -the appropriate classification for your business service, then exit the Categories -pane.</span></li> - -<li><span>Click <strong>Go</strong> to publish your business entity.</span></li> - -</ol> - -<div class="section"><p>The Web Services Explorer is automatically updated with your published -Web service. The registry contains pointers to the URL of the WSDL service -document of the Web service. Businesses can now discover and integrate with -your Web service.</p> -</div> - -</div> - -<div> -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> -<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> -<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div> -<div><a href="treg.html" title="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use.">Registering with a UDDI registry</a></div></div> - -<div class="linklist"><strong>Related Reference</strong><br /> - -<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div> -</div> -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpublish.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpublish.dita deleted file mode 100644 index 8ad83ce67..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpublish.dita +++ /dev/null @@ -1,102 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd"> -<task id="tpublish" xml:lang="en-us"> -<title>Publishing a Web service</title> -<titlealts> -<searchtitle>Publishing a Web service</searchtitle> -</titlealts> -<shortdesc>The Web service, also known as the business service, describes -a Web service's endpoint and where its WSDL file resides. The WSDL file lists -the operations that service provides.</shortdesc> -<taskbody> -<prereq>Prerequisites:<ol> -<li> <xref href="treg.dita">Register with a registry</xref>.</li> -<li> <xref href="tstrtexp.dita">Launch the Web Services Explorer</xref>.</li> -<li> <xref href="taddreg.dita">Add the registry to the Web Services Explorer</xref>.</li> -<li>Create a Web service.</li> -<li>Deploy the Web service.</li> -<li> <xref href="tpubent.dita">Publish a Business Entity</xref>.</li> -</ol></prereq> -<result><p>You can publish a business service using two different publication -formats: simple and advanced.</p></result> -</taskbody> -<task id="d0e74" xml:lang="en-us"> -<title>Publish a business service using the simple option</title> -<taskbody> -<context><p>To publish a Web service using the simple option:</p></context> -<steps> -<step><cmd>In the Web Services Explorer Navigator pane, select the business -entity for which you want to publish the business service.</cmd></step> -<step><cmd>In the Actions pane toolbar, click the <b>Publish Service</b> icon - <image alt="Picture of the Publish Service icon." href="../images/pubserv.gif"> -</image>.</cmd></step> -<step><cmd>Select the <b>Simple</b> radio button.</cmd></step> -<step><cmd>Enter the publish URL, your user ID, password, WSDL URL, business -name, and business description in the respective fields.</cmd></step> -<step><cmd>Click <b>Go</b> to publish your business entity.</cmd></step> -</steps> -<result><p> <b>Important:</b> Ensure that you select the service document, -since the service element is the basis for the Business Service that you will -publish. You cannot publish a Business Service using a WSDL document that -does not have service elements.</p><p>The Web Services Explorer is automatically -updated with your published Web service. The registry contains pointers to -the URL of the WSDL service document of the Web service. Businesses can now -discover and integrate with your Web service.</p></result> -</taskbody> -</task> -<task id="d0e113" xml:lang="en-us"> -<title>Publish a business service using the advanced option</title> -<taskbody> -<context><p>To publish a Web service using the advanced option:</p></context> -<steps> -<step><cmd>In the Web Services Explorer Navigator pane, select the business -entity for which you want to publish the business service.</cmd></step> -<step><cmd>In the Actions pane toolbar, click the <b>Publish Service</b> icon - <image alt="Picture of the Publish Service icon." href="../images/pubserv.gif"> -</image>.</cmd></step> -<step><cmd>Select the <b>Advanced</b> radio button.</cmd></step> -<step><cmd>Enter the publish URL, your user ID, password, and WSDL URL in -the respective fields.</cmd></step> -<step><cmd>Click <b>Get</b> or <uicontrol>Find</uicontrol> to associate the -service with a business entity.</cmd></step> -<step><cmd>Click <b>Get</b> or <uicontrol>Find</uicontrol> to associate a -specific service interface with the service.</cmd></step> -<step><cmd>Click <b>Add</b> to create business service names.</cmd></step> -<step><cmd>Click <b>Add</b> to create business service descriptions.</cmd> -</step> -<step><cmd>Click <b>Add</b> to create categories. Enter your business service -categories. Select a category type from the drop down list. Click <b>Browse</b> to -open the Categories pane. Navigate through the hierarchical taxonomy -and select the appropriate classification for your business service, then -exit the Categories pane.</cmd></step> -<step><cmd>Click <b>Go</b> to publish your business entity.</cmd></step> -</steps> -<result><p> <b>Important:</b> Ensure that you select the service document, -since the service element is the basis for the Business Service that you will -publish. You cannot publish a Business Service using a WSDL document -that does not have service elements.</p><p>The<?Pub Caret?> Web Services Explorer -is automatically updated with your published Web service. The registry contains -pointers to the URL of the WSDL service document of the Web service. Businesses -can now discover and integrate with your Web service.</p></result> -</taskbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.dita" scope="peer"> -<linktext> Tools for Web services development</linktext></link> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cws.dita" scope="peer"> -<linktext>Web services development</linktext></link> -<link href="../concepts/cuddi.dita"></link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="tuddiexp.dita"></link> -<link href="tstrtexp.dita"></link> -<link href="treg.dita"></link> -</linklist> -<linklist><title>Related Reference</title> -<link href="../ref/ruddi.dita"></link> -</linklist> -</related-links> -</task> -</task> -<?Pub *0000005221?> diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpublish.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpublish.html deleted file mode 100644 index 51519149c..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpublish.html +++ /dev/null @@ -1,163 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Publishing a Web service" /> -<meta name="abstract" content="The Web service, also known as the business service, describes a Web service's endpoint and where its WSDL file resides. The WSDL file lists the operations that service provides." /> -<meta name="description" content="The Web service, also known as the business service, describes a Web service's endpoint and where its WSDL file resides. The WSDL file lists the operations that service provides." /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tpublish" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Publishing a Web service</title> -</head> -<body id="tpublish"><a name="tpublish"><!-- --></a> - - -<h1 class="topictitle1">Publishing a Web service</h1> - - - -<div><p>The Web service, also known as the business service, describes -a Web service's endpoint and where its WSDL file resides. The WSDL file lists -the operations that service provides.</p> - -<div class="p">Prerequisites:<ol> -<li> <a href="treg.html">Register with a registry</a>.</li> - -<li> <a href="tstrtexp.html">Launch the Web Services Explorer</a>.</li> - -<li> <a href="taddreg.html">Add the registry to the Web Services Explorer</a>.</li> - -<li>Create a Web service.</li> - -<li>Deploy the Web service.</li> - -<li> <a href="tpubent.html">Publish a Business Entity</a>.</li> - -</ol> -</div> - -<div class="section"><p>You can publish a business service using two different publication -formats: simple and advanced.</p> -</div> - -</div> - -<div class="nested1" xml:lang="en-us" id="d0e74"><a name="d0e74"><!-- --></a> -<h2 class="topictitle2">Publish a business service using the simple option</h2> - -<div> -<div class="section"><p>To publish a Web service using the simple option:</p> -</div> - -<ol> -<li><span>In the Web Services Explorer Navigator pane, select the business -entity for which you want to publish the business service.</span></li> - -<li><span>In the Actions pane toolbar, click the <strong>Publish Service</strong> icon - <img src="../images/pubserv.gif" alt="Picture of the Publish Service icon." />.</span></li> - -<li><span>Select the <strong>Simple</strong> radio button.</span></li> - -<li><span>Enter the publish URL, your user ID, password, WSDL URL, business -name, and business description in the respective fields.</span></li> - -<li><span>Click <strong>Go</strong> to publish your business entity.</span></li> - -</ol> - -<div class="section"><p> <strong>Important:</strong> Ensure that you select the service document, -since the service element is the basis for the Business Service that you will -publish. You cannot publish a Business Service using a WSDL document that -does not have service elements.</p> -<p>The Web Services Explorer is automatically -updated with your published Web service. The registry contains pointers to -the URL of the WSDL service document of the Web service. Businesses can now -discover and integrate with your Web service.</p> -</div> - -</div> - -</div> - -<div class="nested1" xml:lang="en-us" id="d0e113"><a name="d0e113"><!-- --></a> -<h2 class="topictitle2">Publish a business service using the advanced option</h2> - -<div> -<div class="section"><p>To publish a Web service using the advanced option:</p> -</div> - -<ol> -<li><span>In the Web Services Explorer Navigator pane, select the business -entity for which you want to publish the business service.</span></li> - -<li><span>In the Actions pane toolbar, click the <strong>Publish Service</strong> icon - <img src="../images/pubserv.gif" alt="Picture of the Publish Service icon." />.</span></li> - -<li><span>Select the <strong>Advanced</strong> radio button.</span></li> - -<li><span>Enter the publish URL, your user ID, password, and WSDL URL in -the respective fields.</span></li> - -<li><span>Click <strong>Get</strong> or <span class="uicontrol">Find</span> to associate the -service with a business entity.</span></li> - -<li><span>Click <strong>Get</strong> or <span class="uicontrol">Find</span> to associate a -specific service interface with the service.</span></li> - -<li><span>Click <strong>Add</strong> to create business service names.</span></li> - -<li><span>Click <strong>Add</strong> to create business service descriptions.</span> -</li> - -<li><span>Click <strong>Add</strong> to create categories. Enter your business service -categories. Select a category type from the drop down list. Click <strong>Browse</strong> to -open the Categories pane. Navigate through the hierarchical taxonomy -and select the appropriate classification for your business service, then -exit the Categories pane.</span></li> - -<li><span>Click <strong>Go</strong> to publish your business entity.</span></li> - -</ol> - -<div class="section"><p> <strong>Important:</strong> Ensure that you select the service document, -since the service element is the basis for the Business Service that you will -publish. You cannot publish a Business Service using a WSDL document -that does not have service elements.</p> -<p>The Web Services Explorer -is automatically updated with your published Web service. The registry contains -pointers to the URL of the WSDL service document of the Web service. Businesses -can now discover and integrate with your Web service.</p> -</div> - -</div> - -<div> -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> -<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> -<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div> -<div><a href="treg.html" title="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use.">Registering with a UDDI registry</a></div></div> - -<div class="linklist"><strong>Related Reference</strong><br /> - -<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div> -</div> -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/treg.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/treg.dita deleted file mode 100644 index 19bffea88..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/treg.dita +++ /dev/null @@ -1,67 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd"> -<task id="treg" xml:lang="en-us"><?Pub Caret?> -<title>Registering with a UDDI registry</title> -<titlealts> -<searchtitle>Registering with a UDDI Registry</searchtitle> -</titlealts> -<shortdesc>In order to publish your business entity and Web service to a UDDI -registry, you must first register with the registry that you want to use.</shortdesc> -<taskbody> -<context><p>There are many different public and private registries with which -you can register. For a list of public registries refer to <xref href="http://www.uddi.org/register.html" -scope="external">www.uddi.org/register.html</xref> Since each registry is -different, the registry provider will give you instructions for registering.</p><p>The -following registries are automatically added to Favorites:</p><ul> -<li><tm tmclass="ibm" tmowner="IBM Corporation" tmtype="reg" trademark="IBM">IBM</tm> UDDI -Registry</li> -<li><tm tmclass="ibm" tmowner="IBM Corporation" tmtype="reg" trademark="IBM">IBM</tm> UDDI -Test Registry</li> -<li><tm tmclass="special" tmowner="Microsoft Corporation" tmtype="reg" trademark="Microsoft">Microsoft</tm> UDDI -Registry</li> -<li><tm tmclass="special" tmowner="Microsoft Corporation" tmtype="reg" trademark="Microsoft">Microsoft</tm> UDDI -Test Registry</li> -<li>SAP UDDI Registry</li> -<li>SAP UDDI Test Registry</li> -<li>XMethods Registry</li> -<li>NTT Communications Registry</li> -</ul><p>You can use any of these registries by selecting the Favorites icon -in the Web Services Explorer toolbar. All of these registries are based on -the UDDI Business Registry Version 2. Go to the following URL to obtain a -user ID and password for the <tm tmclass="ibm" tmowner="IBM Corporation" tmtype="reg" -trademark="IBM">IBM</tm> UDDI registry: <xref format="html" href="http://www-3.ibm.com/services/uddi/" -scope="external">www.ibm.com/services/uddi/</xref>. The details page of each -registry will have registration instructions.</p><p>The <tm tmclass="ibm" -tmowner="IBM Corporation" tmtype="reg" trademark="IBM">IBM</tm> UDDI Test -Registry allows you to develop your Web service and experience the UDDI registration -process without placing your Web service in an official registry. Use the <tm -tmclass="ibm" tmowner="IBM Corporation" tmtype="reg" trademark="IBM">IBM</tm> UDDI -Test Registry or a private registry to experiment with UDDI, and to test and -validate your Web service. The public production registries are listed -under Favorites. The Web Services Explorer does not preload any registries -by default. You can preload registries from the favorites section of -the Web Services Explorer or by using the Unit Test UDDI wizard. You can also -preload and configure private registries using the Unit Test UDDI wizard. -On the Open Registry page of the Web Services Explorer, you can select from -public registries and registries listed in your favorites to automatically -fill in the information required to open a particular registry.</p></context> -</taskbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.dita" scope="peer"> -<linktext> Tools for Web services development</linktext></link> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cws.dita" scope="peer"> -<linktext>Web services development</linktext></link> -<link href="../concepts/cuddi.dita"></link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="tuddiexp.dita"></link> -<link href="tstrtexp.dita"></link> -</linklist> -<linklist><title>Related Reference</title> -<link href="../ref/ruddi.dita"></link> -</linklist> -</related-links> -</task> -<?Pub *0000003759?> diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/treg.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/treg.html deleted file mode 100644 index 6c1a80597..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/treg.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="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Registering with a UDDI registry" /> -<meta name="abstract" content="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use." /> -<meta name="description" content="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use." /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cws.html" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cuddi.html" /> -<meta scheme="URI" name="DC.Relation" content="tuddiexp.html" /> -<meta scheme="URI" name="DC.Relation" content="tstrtexp.html" /> -<meta scheme="URI" name="DC.Relation" content="../ref/ruddi.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="treg" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Registering with a UDDI Registry</title> -</head> -<body id="treg"><a name="treg"><!-- --></a> - - -<h1 class="topictitle1">Registering with a UDDI registry</h1> - - - -<div><p>In order to publish your business entity and Web service to a UDDI -registry, you must first register with the registry that you want to use.</p> - -<div class="section"><p>There are many different public and private registries with which -you can register. For a list of public registries refer to <a href="http://www.uddi.org/register.html" target="_blank">www.uddi.org/register.html</a> Since each registry is -different, the registry provider will give you instructions for registering.</p> -<p>The -following registries are automatically added to Favorites:</p> -<ul> -<li>IBM<sup>®</sup> UDDI -Registry</li> - -<li>IBM UDDI -Test Registry</li> - -<li>Microsoft<sup>®</sup> UDDI -Registry</li> - -<li>Microsoft UDDI -Test Registry</li> - -<li>SAP UDDI Registry</li> - -<li>SAP UDDI Test Registry</li> - -<li>XMethods Registry</li> - -<li>NTT Communications Registry</li> - -</ul> -<p>You can use any of these registries by selecting the Favorites icon -in the Web Services Explorer toolbar. All of these registries are based on -the UDDI Business Registry Version 2. Go to the following URL to obtain a -user ID and password for the IBM UDDI registry: <a href="http://www-3.ibm.com/services/uddi/" target="_blank">www.ibm.com/services/uddi/</a>. The details page of each -registry will have registration instructions.</p> -<p>The IBM UDDI Test -Registry allows you to develop your Web service and experience the UDDI registration -process without placing your Web service in an official registry. Use the IBM UDDI -Test Registry or a private registry to experiment with UDDI, and to test and -validate your Web service. The public production registries are listed -under Favorites. The Web Services Explorer does not preload any registries -by default. You can preload registries from the favorites section of -the Web Services Explorer or by using the Unit Test UDDI wizard. You can also -preload and configure private registries using the Unit Test UDDI wizard. -On the Open Registry page of the Web Services Explorer, you can select from -public registries and registries listed in your favorites to automatically -fill in the information required to open a particular registry.</p> -</div> - -</div> - -<div> -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> -<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> -<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div></div> - -<div class="linklist"><strong>Related Reference</strong><br /> - -<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tsampapp.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tsampapp.html deleted file mode 100644 index 5c65754ee..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tsampapp.html +++ /dev/null @@ -1,146 +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 http-equiv="Content-Type" content="text/html; charset=utf-8" /> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 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 - *******************************************************************************/ --> -<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" /> -<title>Generating a Java client proxy and a sample application from -a WSDL document</title> -</head> -<body id="tsampapp"><a name="tsampapp"><!-- --></a> - -<h1 class="topictitle1">Generating a Java client proxy and a sample application -from a WSDL document using the IBM SOAP run-time environment</h1> -<div><p>The Web Service Client wizard assists you in generating a Java™ bean -proxy and a sample application. The sample Web application demonstrates -how to code a proxy file.</p> -<div class="p">Prerequisites:<ol><li id="tsampapp__createtomcatlinks"><a name="tsampapp__createtomcatlinks"><!-- --></a>If you are using the Apache Jakarta Tomcat servlet -container as your server, you must install it, configure an instance of it, -and create a Web project targeted to it as described in <a href="../../org.eclipse.jst.ws.axis.creation.ui.doc.user/tasks/ttomcatserv.html">Creating a WebSphere<sup>®</sup> Server and Web project</a></li> -<li id="tsampapp__prereqcreatewsprojs"><a name="tsampapp__prereqcreatewsprojs"><!-- --></a>If you are using a WebSphere server, create a dynamic -Web project targeted to the appropriate server as described in <a href="../../org.eclipse.jst.ws.doc.user/tasks/twasserv.html">Creating a WebSphere Server and Web project</a>.</li> -<li>Discover and import a WSDL document into the Web project. You can only -use a WSDL file that contains a service element.</li> -</ol> -</div> -<div class="section"><p>To generate a Java client proxy and a sample application -from a discovered WSDL document:</p> -</div> -<ol><li><span>Switch to the J2EE perspective (<span class="uicontrol">Window > Open Perspective -> J2EE</span>).</span></li> -<li><span>In the Project Explorer view, select the Web project in which you -want to generate a sample application.</span></li> -<li><span>Click <span class="uicontrol">File > New > Other</span>. Select <span class="uicontrol">Web -Services</span> in order to display the various Web service wizards. -Select the <span class="uicontrol">Web Service Client</span> wizard. Click <span class="uicontrol">Next</span>.</span></li> -<li><span>Web Services panel: Select the type of proxy to be generated, and -whether or not it will be tested.</span></li> -<li><span>Client Environment Configuration page: Select the run-time environment -and the server for your Web service client.</span><ol type="a"><li class="substepexpand"><span>Click <span class="uicontrol">Explore Options</span> and select the IBM<sup>®</sup> SOAP -run-time environment and select the server on which you want to run your Web -service client.</span> If you want to use the Apache Axis 1.0 run-time -environment or the IBM WebSphere run-time environments, refer to the appropriate -task. </li> -<li class="substepexpand"><span>Select the type and name of project in which you want the Web -service client created.</span> <ul><li> If you enter the name of an existing project, the project type field -must match that of the existing project. Ensure that the project selected -as the Client Web Project is different from the Service Web Project, or the -service will be overwritten by the client's generated artifacts.</li> -<li>If you enter a name of a project that does not already exist, the wizard -will create the project for you.</li> -<li>Note that the only project type supported for Axis and SOAP run-time clients -is a Web project. If you want the client to be created in a Java, EJB, -or Application Client project, you must select the WebSphere run-time environment for -your client.</li> -</ul> -</li> -<li class="substepexpand"><span> Select an existing EAR or enter a unique name to associate -the Web service client with a different EAR than the Web service EAR. <strong>Note:</strong> Selecting -different EARs for the Web service and Web service client can reduce the chance -of encountering run time errors, but will use more system resources.</span></li> -</ol> -</li> -<li><span>Web Service Selection panel: Enter the URI to the WSDL, WSIL, or -HTML file that will be used to generate the Java bean. You can optionally generate a -WSIL file from this file as well.</span></li> -<li><span>Web Service Binding Proxy Generation panel: Select the binding -and proxy options.</span></li> -<li><span>Web Service Proxy Test panel: Select the test facility that you -will use to test the proxy, and the methods that you want included in the -proxy. Note that the Universal Test Client (UTC) is only compatible with Web -service clients deployed on WebSphere servers. Click <span class="uicontrol">Finish</span></span></li> -</ol> -<div class="section"><p>Notes<sup>®</sup>:</p> -<ul><li>When defining custom mappings ensure the bean, serializer, and deserializer -classes are on the build path of the Web project, otherwise the wizard will -not accept their class names.</li> -<li>Indexed properties that result from WSDL XSD complex Types involving more -than one occurrence of DOM Elements are not supported by the sample. SOAP -encoded methods using indexed properties are not available for invocation. -Literal XML encoded methods using indexed properties are available for invocation; -however, the inputs and outputs must be specified as Literal XML.</li> -<li>Only the following types are supported by the sample application: <ul><li>Members that use getters and setters.</li> -<li>All primitive types and corresponding Java types.</li> -<li>Java type -String.</li> -<li>org.w3c.dom.Element</li> -<li>Java beans.</li> -<li>BigDecimal, GregorianCalendar, and Date.</li> -</ul> -</li> -</ul> -<p><strong>Important:</strong> It is recommended that you select the service WSDL -document rather than the binding WSDL document in order to generate a client -proxy that contains the complete endpoint information. The service element -is the basis for the Business Service that you will publish. You cannot publish -a Business Service using a WSDL document that does not have service elements. -If you generate a proxy from a WSDL binding document, you must call the <tt class="sysout">setEndPoint()</tt> method -to set an endpoint URL before you call any other method in the proxy. -The proxy generated from a WSDL binding document is not automatically equipped -with an endpoint URL.</p> -<p>The generated Java bean proxy provides a remote procedure -call interface to the Web service. The sample Web application demonstrates -how to code the proxy file.</p> -<p>Once you have generated your Java client -proxy, you may test the methods of the Web service through the proxy using -Web Services sample JSPs or the Universal test client.</p> -<ul><li>If you have selected to test the generated proxy using Web service JSPs, -the proxy is launched in a Web browser at the following URL:<samp class="codeph"> http://localhost: <var class="varname">port</var>/WebProjectClient/sample/ <var class="varname">WebService</var>/TestClient.jsp </samp> You can use this sample application to test the -Web service by selecting a method, entering a value for the method, and clicking - <span class="uicontrol">Invoke</span>. The result of the method will display in the -results pane.</li> -<li>If you have selected to test the generated proxy using the Universal Test -Client, it will be launched in a browser window at the following URL:<samp class="codeph"> <tt class="sysout">http://localhost:9080/UTC/preload?object=proxy.soap. <var class="varname">ProxyName</var>Proxy</tt> </samp> In the Reference pane, -under Object References, expand the proxy to display the methods of the Web -service. Click the method you want to test, enter a value in the Parameters -pane, and click <span class="uicontrol">Invoke</span>. The result will be generated -below.</li> -</ul> -<p>For more information on creating a Web project, refer to the Web application -development documentation.</p> -</div> -</div> -<div> -<div class="linklist"><strong>Collected links</strong><br /> - -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div></div> - -</div> -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tstrtexp.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tstrtexp.dita deleted file mode 100644 index f52b6466f..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tstrtexp.dita +++ /dev/null @@ -1,115 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd"> -<task id="tstrtexp" xml:lang="en-us"> -<title>Launching the Web Services Explorer</title> -<titlealts> -<searchtitle>Launching the Web Services Explorer</searchtitle> -</titlealts> -<shortdesc>The Web services tools allows you to launch the Web Services Explorer -in several ways.</shortdesc> -<taskbody> -<context><ul> -<li>From the main toolbar in the J2EE perspective.</li> -<li>By using the Web service wizards.</li> -<li>By using the Import wizard.</li> -<li>By using the Export wizard.</li> -<li>From the Run menu in the J2EE perspective.</li> -<li>From a WSDL file.</li> -</ul></context> -</taskbody> -<task id="d0e38" xml:lang="en-us"> -<title>Launching the Web Services Explorer from the main toolbar</title> -<taskbody> -<context><p>To launch the Web Services Explorer from the main toolbar, ensure -that you are in the J2EE perspective and click the <b>Launch the Web Services -Explorer</b> icon <image alt="Picture of the Launch Web Services Explorer icon." -href="../images/uddiview.gif"></image>. The Web Services Explorer opens without -any registries displayed in the Navigator pane. You can now <xref href="taddreg.dita">add -a registry</xref> to the Web Services Explorer.</p></context> -</taskbody> -</task> -<task id="d0e50" xml:lang="en-us"> -<title>Launching the Web Services Explorer using the Web Services Wizard</title> -<taskbody> -<context><p>To launch the Web Services Explorer from the Web Services Wizard, -select the <b>Test the Web Service</b> check box in the first page of the -Web Services Wizard. Proceed with the wizard and then in the Web Service Test -Page, choose <b>Web Services Explorer</b> as the test facility and click -on the <b>Launch</b> button. If you launch the Web Services Explorer using -this method, it will automatically preload the WSDL (and its child nodes) -in the WSDL page.</p></context> -</taskbody> -</task> -<task id="d0e63" xml:lang="en-us"> -<title>Launching the Web Services Explorer using the Import wizard</title> -<taskbody> -<context><p>To launch the Web Services Explorer using the Import wizard, do -the following:</p></context> -<steps> -<step><cmd>From the main menu, click <b>File > Import</b>. The Import wizard -opens.</cmd></step> -<step><cmd>Select <b>Web Service</b> and click <b>Next</b>. The Web service -import wizard opens.</cmd></step> -<step><cmd>Click <b>Finish</b>.</cmd></step> -</steps> -<result><p>The Web Services Explorer opens. If you selected a registry on -the Web Service Publication page of the Web service Import wizard, you will -see the registry displayed in the Navigator pane.</p></result> -</taskbody> -</task> -<task id="d0e95" xml:lang="en-us"> -<title>Launching the Web Services Explorer using the Export wizard</title> -<taskbody> -<context><p>To launch the Web Services Explorer using the Export wizard, do -the following:</p></context> -<steps> -<step><cmd>From the main menu, click <b>File > Export</b>. The Export wizard -opens.</cmd></step> -<step><cmd>Select <b>Web Service</b> and click <b>Next</b>. The Web Service -Export wizard opens.</cmd></step> -<step><cmd>Click <b>Finish</b>. The Web Services Explorer opens.</cmd></step> -</steps> -<result><p>The Web Services Explorer opens. If you selected a registry -on the Web Service Publication page of the Web Service Export wizard, you -will see the registry displayed in the Navigator pane.</p></result> -</taskbody> -</task> -<task id="d0e127" xml:lang="en-us"> -<title>Launching the Web Services Explorer from the Run menu</title> -<taskbody> -<context><p>To launch the Web Services Explorer from the main menu, ensure -that you are in the J2EE perspective and click <b>Run > Launch the Web Services -Explorer</b>. The Import wizard opens. The Web Services Explorer opens. -The Web Services Explorer opens without any registries displayed in the Navigator -pane.</p></context> -</taskbody> -</task> -<task id="d0e134" xml:lang="en-us"> -<title>Launching the Web Services Explorer from a WSDL file</title> -<taskbody> -<context><p>To launch the<?Pub Caret?> Web Services Explorer from a WSDL file, -select the WSDL file and right-click and choose <b>Web Services > Test with -Web Services Explorer</b> or <b>Publish WSDL file</b>. The Web Services -Explorer opens. The <b>Test with Web Services Explorer</b> action will preload -the WSDL in the WSDL page.</p></context> -</taskbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.dita" scope="peer"> -<linktext> Tools for Web services development</linktext></link> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cws.dita" scope="peer"> -<linktext>Web services development</linktext></link> -<link href="../concepts/cuddi.dita"></link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="tuddiexp.dita"></link> -<link href="treg.dita"></link> -</linklist> -<linklist><title>Related Reference</title> -<link href="../ref/ruddi.dita"></link> -</linklist> -</related-links> -</task> -</task> -<?Pub *0000005105?> diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tstrtexp.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tstrtexp.html deleted file mode 100644 index 4682e8d17..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tstrtexp.html +++ /dev/null @@ -1,183 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Launching the Web Services Explorer" /> -<meta name="abstract" content="The Web services tools allows you to launch the Web Services Explorer in several ways." /> -<meta name="description" content="The Web services tools allows you to launch the Web Services Explorer in several ways." /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tstrtexp" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Launching the Web Services Explorer</title> -</head> -<body id="tstrtexp"><a name="tstrtexp"><!-- --></a> - - -<h1 class="topictitle1">Launching the Web Services Explorer</h1> - - - -<div><p>The Web services tools allows you to launch the Web Services Explorer -in several ways.</p> - -<div class="section"><ul> -<li>From the main toolbar in the J2EE perspective.</li> - -<li>By using the Web service wizards.</li> - -<li>By using the Import wizard.</li> - -<li>By using the Export wizard.</li> - -<li>From the Run menu in the J2EE perspective.</li> - -<li>From a WSDL file.</li> - -</ul> -</div> - -</div> - -<div class="nested1" xml:lang="en-us" id="d0e38"><a name="d0e38"><!-- --></a> -<h2 class="topictitle2">Launching the Web Services Explorer from the main toolbar</h2> - -<div> -<div class="section"><p>To launch the Web Services Explorer from the main toolbar, ensure -that you are in the J2EE perspective and click the <strong>Launch the Web Services -Explorer</strong> icon <img src="../images/uddiview.gif" alt="Picture of the Launch Web Services Explorer icon." />. The Web Services Explorer opens without -any registries displayed in the Navigator pane. You can now <a href="taddreg.html">add a registry</a> to the Web Services Explorer.</p> -</div> - -</div> - -</div> - -<div class="nested1" xml:lang="en-us" id="d0e50"><a name="d0e50"><!-- --></a> -<h2 class="topictitle2">Launching the Web Services Explorer using the Web Services Wizard</h2> - -<div> -<div class="section"><p>To launch the Web Services Explorer from the Web Services Wizard, -select the <strong>Test the Web Service</strong> check box in the first page of the -Web Services Wizard. Proceed with the wizard and then in the Web Service Test -Page, choose <strong>Web Services Explorer</strong> as the test facility and click -on the <strong>Launch</strong> button. If you launch the Web Services Explorer using -this method, it will automatically preload the WSDL (and its child nodes) -in the WSDL page.</p> -</div> - -</div> - -</div> - -<div class="nested1" xml:lang="en-us" id="d0e63"><a name="d0e63"><!-- --></a> -<h2 class="topictitle2">Launching the Web Services Explorer using the Import wizard</h2> - -<div> -<div class="section"><p>To launch the Web Services Explorer using the Import wizard, do -the following:</p> -</div> - -<ol> -<li><span>From the main menu, click <strong>File > Import</strong>. The Import wizard -opens.</span></li> - -<li><span>Select <strong>Web Service</strong> and click <strong>Next</strong>. The Web service -import wizard opens.</span></li> - -<li><span>Click <strong>Finish</strong>.</span></li> - -</ol> - -<div class="section"><p>The Web Services Explorer opens. If you selected a registry on -the Web Service Publication page of the Web service Import wizard, you will -see the registry displayed in the Navigator pane.</p> -</div> - -</div> - -</div> - -<div class="nested1" xml:lang="en-us" id="d0e95"><a name="d0e95"><!-- --></a> -<h2 class="topictitle2">Launching the Web Services Explorer using the Export wizard</h2> - -<div> -<div class="section"><p>To launch the Web Services Explorer using the Export wizard, do -the following:</p> -</div> - -<ol> -<li><span>From the main menu, click <strong>File > Export</strong>. The Export wizard -opens.</span></li> - -<li><span>Select <strong>Web Service</strong> and click <strong>Next</strong>. The Web Service -Export wizard opens.</span></li> - -<li><span>Click <strong>Finish</strong>. The Web Services Explorer opens.</span></li> - -</ol> - -<div class="section"><p>The Web Services Explorer opens. If you selected a registry -on the Web Service Publication page of the Web Service Export wizard, you -will see the registry displayed in the Navigator pane.</p> -</div> - -</div> - -</div> - -<div class="nested1" xml:lang="en-us" id="d0e127"><a name="d0e127"><!-- --></a> -<h2 class="topictitle2">Launching the Web Services Explorer from the Run menu</h2> - -<div> -<div class="section"><p>To launch the Web Services Explorer from the main menu, ensure -that you are in the J2EE perspective and click <strong>Run > Launch the Web Services -Explorer</strong>. The Import wizard opens. The Web Services Explorer opens. -The Web Services Explorer opens without any registries displayed in the Navigator -pane.</p> -</div> - -</div> - -</div> - -<div class="nested1" xml:lang="en-us" id="d0e134"><a name="d0e134"><!-- --></a> -<h2 class="topictitle2">Launching the Web Services Explorer from a WSDL file</h2> - -<div> -<div class="section"><p>To launch the Web Services Explorer from a WSDL file, -select the WSDL file and right-click and choose <strong>Web Services > Test with -Web Services Explorer</strong> or <strong>Publish WSDL file</strong>. The Web Services -Explorer opens. The <strong>Test with Web Services Explorer</strong> action will preload -the WSDL in the WSDL page.</p> -</div> - -</div> - -<div> -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> -<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> -<div><a href="treg.html" title="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use.">Registering with a UDDI registry</a></div></div> - -<div class="linklist"><strong>Related Reference</strong><br /> - -<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div> -</div> -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/ttestwsdl.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/ttestwsdl.dita deleted file mode 100644 index 485718265..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/ttestwsdl.dita +++ /dev/null @@ -1,98 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd"> -<task id="ttestwsdl" xml:lang="en-us"> -<title>Testing WSDL documents and Web services using the WSDL Explorer</title> -<titlealts> -<searchtitle>Using the WSDL Explorer</searchtitle> -</titlealts> -<shortdesc>WSDL documents allow developers to expose their applications as -network-accessible services on the Internet. Through UDDI and WSIL, other -applications can discover WSDL documents and bind with them to execute transactions -or perform other business processes. The Web Services Explorer allows you -to explore, import, and test WSDL documents.</shortdesc> -<taskbody> -<prereq>Prerequisites: To use the WSDL Explorer:<ul> -<li>You must have a valid URL for a WSDL document.</li> -<li>You must launch the Web Services Explorer: <xref href="tstrtexp.dita">Launch -the Web Services Explorer</xref></li> -</ul></prereq> -<context><p>The WSDL Explorer allows you to explore, and test WSDL documents. -For more information on exploring WSDL documents using the WSDL Explorer, -refer to <xref href="twsdlexp.dita">Using the WSDL Explorer</xref> .</p><p>To -test a Web service using the WSDL Explorer:</p></context> -<steps> -<step><cmd>To launch the WSDL Explorer, complete the following steps:</cmd> -<substeps> -<substep><cmd>In the Web Services Explorer, switch to the WSDL Explorer by -clicking the icon in the upper right-hand corner <image alt="Icon to launch the WSDL Explorer" -href="../images/wsdlicon.gif"></image>. </cmd></substep> -</substeps> -</step> -<step><cmd>Select WSDL Main in the Navigator pane, enter or browse to an existing -WSDL URL in the right-hand pane, and click <b>Go</b>. For this example the -WSDL being used is a Web Service which returns a temperature for any entered -zip code. <image alt="Screen capture of the WSDL Main pane of the Web Services Explorer" -href="../images/wsdlexp.gif" placement="break"></image> The following nodes -will be added to the WSDL tree: </cmd><info><ul> -<li>The WSDL node: <image alt="WSDL node icon" href="../images/wsdlnode.gif"> -</image></li> -<li>The service node (which represents a service element within the WSDL file): - <image alt="Service node icon" href="../images/servnode.gif"></image></li> -<li>The binding node: <image alt="Binding node icon" href="../images/bindnode.gif"> -</image></li> -<li>The operation node: <image alt="Operation node icon" href="../images/opnode.gif"> -</image></li> -</ul></info></step> -<step><cmd>In the WSDL Binding Details pane, click the operation (in this -example the <systemoutput>getTemp</systemoutput> operation) to display: </cmd> -<info><ul> -<li>A drop-down list with the endpoints available for this operation</li> -<li>Fields for each of the parameters of this operation (in this example the - <systemoutput>zipcode</systemoutput> parameter) and the type of information -the parameter is looking for (in this example <systemoutput>zipcode</systemoutput> is -requesting a string). <image alt="Invoke a WSDL Operation pane of the Web Services Explorer" -href="../images/wsdlop.gif" placement="break"></image> The Form view allows -you to enter the parameters for the Web service operation call. Parameters -names are displayed as links whose action is to display a dialog describing -embedded XML Schema Definition Language (XSD) information. More information -about XSD can be found here: <xref format="html" href="http://www.eclipse.org/xsd/">http://www.eclipse.org/xsd/</xref> - <image alt="Screen capture of the XSD Information Dialog" href="../images/scenario7.gif" -placement="break"></image> </li> -</ul></info></step> -<step><cmd>Enter your string and click <b>Go</b>. The result is returned -in the Status pane. <image alt="Screen capture of an invoked WSDL operation showing the result in the Status pane" -href="../images/wsdlopret.gif" placement="break"></image> </cmd></step> -<step><cmd>If you are using SOAP as your binding method, clicking Source or -Form in the upper right-hand corner will toggle the display between the Form -view (shown above) and the Source view, which displays the SOAP message in -the XML format. You can also enter the same information as in the form, only -in XML format (this is suggested for advanced users only). The Explorer does -validate the XML if you modify it, but not the parameter values you enter. - <image alt="Source view of the Invoke a WSDL Operation pane." href="../images/wsdlopretx.gif" -placement="break"></image></cmd></step> -<step><cmd> If you are using SOAP as your binding type, you will also -have the option of toggling the Status pane between the Source and Form views. -The Source view shows the SOAP request and response envelopes, including the -parameters you have entered to test the service and the returned value. <image -alt="Screen capture of the source view of the SOAP request and response envelopes" -href="../images/wsdlstatx.gif" placement="break"></image> </cmd></step> -</steps> -</taskbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.dita" scope="peer"> -<linktext> Tools for Web services development</linktext></link> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cws.dita" scope="peer"> -<linktext>Web services development</linktext></link> -<link href="../concepts/cuddi.dita"></link> -</linklist> -<linklist><title>Related Tasks</title><?Pub Caret?> -<link href="tuddiexp.dita"></link> -<link href="tstrtexp.dita"></link> -<link href="../../org.eclipse.jst.ws.doc.user/tasks/toverws.dita" scope="peer"> -<linktext> Developing Web services</linktext></link> -</linklist> -</related-links> -</task> -<?Pub *0000005726?> diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/ttestwsdl.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/ttestwsdl.html deleted file mode 100644 index ab25be26e..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/ttestwsdl.html +++ /dev/null @@ -1,134 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Testing WSDL documents and Web services using the WSDL Explorer" /> -<meta name="abstract" content="WSDL documents allow developers to expose their applications as network-accessible services on the Internet. Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes. The Web Services Explorer allows you to explore, import, and test WSDL documents." /> -<meta name="description" content="WSDL documents allow developers to expose their applications as network-accessible services on the Internet. Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes. The Web Services Explorer allows you to explore, import, and test WSDL documents." /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cws.html" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cuddi.html" /> -<meta scheme="URI" name="DC.Relation" content="tuddiexp.html" /> -<meta scheme="URI" name="DC.Relation" content="tstrtexp.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/tasks/toverws.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="ttestwsdl" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Using the WSDL Explorer</title> -</head> -<body id="ttestwsdl"><a name="ttestwsdl"><!-- --></a> - - -<h1 class="topictitle1">Testing WSDL documents and Web services using the WSDL Explorer</h1> - - - -<div><p>WSDL documents allow developers to expose their applications as -network-accessible services on the Internet. Through UDDI and WSIL, other -applications can discover WSDL documents and bind with them to execute transactions -or perform other business processes. The Web Services Explorer allows you -to explore, import, and test WSDL documents.</p> - -<div class="p">Prerequisites: To use the WSDL Explorer:<ul> -<li>You must have a valid URL for a WSDL document.</li> - -<li>You must launch the Web Services Explorer: <a href="tstrtexp.html">Launch the Web Services Explorer</a></li> - -</ul> -</div> - -<div class="section"><p>The WSDL Explorer allows you to explore, and test WSDL documents. -For more information on exploring WSDL documents using the WSDL Explorer, -refer to <a href="twsdlexp.html">Using the WSDL Explorer</a> .</p> -<p>To -test a Web service using the WSDL Explorer:</p> -</div> - -<ol> -<li class="stepexpand"><span>To launch the WSDL Explorer, complete the following steps:</span> -<ol type="a"> -<li><span>In the Web Services Explorer, switch to the WSDL Explorer by -clicking the icon in the upper right-hand corner <img src="../images/wsdlicon.gif" alt="Icon to launch the WSDL Explorer" />. </span></li> - -</ol> - -</li> - -<li class="stepexpand"><span>Select WSDL Main in the Navigator pane, enter or browse to an existing -WSDL URL in the right-hand pane, and click <strong>Go</strong>. For this example the -WSDL being used is a Web Service which returns a temperature for any entered -zip code. <br /><img src="../images/wsdlexp.gif" alt="Screen capture of the WSDL Main pane of the Web Services Explorer" /><br /> The following nodes -will be added to the WSDL tree: </span> <ul> -<li>The WSDL node: <img src="../images/wsdlnode.gif" alt="WSDL node icon" /></li> - -<li>The service node (which represents a service element within the WSDL file): - <img src="../images/servnode.gif" alt="Service node icon" /></li> - -<li>The binding node: <img src="../images/bindnode.gif" alt="Binding node icon" /></li> - -<li>The operation node: <img src="../images/opnode.gif" alt="Operation node icon" /></li> - -</ul> -</li> - -<li class="stepexpand"><span>In the WSDL Binding Details pane, click the operation (in this -example the <tt class="sysout">getTemp</tt> operation) to display: </span> - <ul> -<li>A drop-down list with the endpoints available for this operation</li> - -<li>Fields for each of the parameters of this operation (in this example the - <tt class="sysout">zipcode</tt> parameter) and the type of information -the parameter is looking for (in this example <tt class="sysout">zipcode</tt> is -requesting a string). <br /><img src="../images/wsdlop.gif" alt="Invoke a WSDL Operation pane of the Web Services Explorer" /><br /> The Form view allows -you to enter the parameters for the Web service operation call. Parameters -names are displayed as links whose action is to display a dialog describing -embedded XML Schema Definition Language (XSD) information. More information -about XSD can be found here: <a href="http://www.eclipse.org/xsd/">http://www.eclipse.org/xsd/</a> - <br /><img src="../images/scenario7.gif" alt="Screen capture of the XSD Information Dialog" /><br /> </li> - -</ul> -</li> - -<li class="stepexpand"><span>Enter your string and click <strong>Go</strong>. The result is returned -in the Status pane. <br /><img src="../images/wsdlopret.gif" alt="Screen capture of an invoked WSDL operation showing the result in the Status pane" /><br /> </span></li> - -<li class="stepexpand"><span>If you are using SOAP as your binding method, clicking Source or -Form in the upper right-hand corner will toggle the display between the Form -view (shown above) and the Source view, which displays the SOAP message in -the XML format. You can also enter the same information as in the form, only -in XML format (this is suggested for advanced users only). The Explorer does -validate the XML if you modify it, but not the parameter values you enter. - <br /><img src="../images/wsdlopretx.gif" alt="Source view of the Invoke a WSDL Operation pane." /><br /></span></li> - -<li class="stepexpand"><span> If you are using SOAP as your binding type, you will also -have the option of toggling the Status pane between the Source and Form views. -The Source view shows the SOAP request and response envelopes, including the -parameters you have entered to test the service and the returned value. <br /><img src="../images/wsdlstatx.gif" alt="Screen capture of the source view of the SOAP request and response envelopes" /><br /> </span></li> - -</ol> - -</div> - -<div> -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> -<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> -<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div> -<div><a href="../../org.eclipse.jst.ws.doc.user/tasks/toverws.html"> Developing Web services</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.dita deleted file mode 100644 index 1ac3b8163..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.dita +++ /dev/null @@ -1,126 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd"> -<task id="tuddiexp" xml:lang="en-us"><?Pub Caret?> -<title>Publishing Web services and business entities</title> -<titlealts> -<searchtitle>Publishing Web services and business entities with the Web Services -Explorer</searchtitle> -</titlealts> -<shortdesc>Through UDDI and WSIL, other applications can discover WSDL documents -and bind with them to execute transactions or perform other business processes. </shortdesc> -<taskbody> -<context><p>UDDI enables the discovery of Web services by providing a distributed -registry of businesses and their service descriptions, implemented in a common -XML format. In order for a service requestor to discover a service, -a service provider must first publish a business entity and at least one business -service, and service interface in a UDDI registry. The Web Services -Explorer is a Web application that supports the publication, discovery, and -maintenance of business entities, business services, and service interfaces.</p><p>WSIL -enables the discovery of Web services by defining a distributed service discovery -method that supplies references to service descriptions at the service provider's -point-of-offering, by specifying how to inspect a Web site for available Web -services. The WSIL specification defines the locations on a Web site -where you can look for Web service descriptions. Since WSIL focuses on -distributed service discovery, the WSIL specification complements UDDI by -facilitating the discovery of services that are available on Web sites that -may not be listed yet in a UDDI registry. The Web Services Explorer allows -you to generate and explore WSIL documents.</p><p>The favorites page of the -Web Services Explorer allows you to store the location of UDDI registries, -business entities, Web services, service interfaces, as well as WSIL and WSDL -documents.</p><p>Use the Web Services Explorer to do any of the following -tasks:</p><ul> -<li> <xref href="taddreg.dita">Add a registry to the Web Services Explorer</xref> </li> -<li> <xref href="tbkmrk.dita">Adding a registry, business entity, business -service, service interface, WSIL, or WSDL service to Favorites</xref> </li> -<li> <xref href="tdiscov.dita">Discover a Web service</xref> </li> -<li> <xref href="tpubent.dita">Publish a business entity to a registry</xref> </li> -<li> <xref href="tpublish.dita">Publish a business service to a registry</xref> </li> -<li> <xref href="tunpub.dita">Remove a business entity, business service, -or service interface from a registry</xref> </li> -<li> <xref href="tupdate.dita">Update a business entity, business service, -or service interface</xref> </li> -<li> <xref href="tbusproj.dita">Manage referenced services</xref> </li> -<li> <xref href="tassert.dita">Manage publisher assertions</xref> </li> -</ul><p>Prerequisites:</p></context> -<steps> -<step><cmd>Before you can use the Web Services Explorer to perform any of -these functions, you must <xref href="treg.dita">register with a public registry</xref>. -There are many different registries with which you can register.</cmd><info></info> -</step> -<step><cmd>Ensure that you are using a supported Web browser.</cmd><info>The -following Web browsers and versions are supported:<ul> -<li>Internet Explorer: 6.0 and up</li> -<li>Mozilla: 1.2.1 and up</li> -</ul></info></step> -<step><cmd> <xref href="tstrtexp.dita">Launch the Web Services Explorer</xref>.</cmd> -</step> -</steps> -<result><p><b>Known limitations of the Web Services Explorer:</b><ul> -<li>The taxonomy categories in the Web Services Explorer are not translated -since they must match those in the standards adhered to by UDDI (ISO, UNSPSC -7.3, NAICS).</li> -<li>The Web Services Explorer will launch without the browser toolbar which -shows, amongst other things, the URL to the Web application. This URL should -only be used by users with accessibility needs. The URL to the Web Services -Explorer Web application can be obtained through the following steps:<ol> -<li>From the Window menu, select Preferences.</li> -<li>In the Preferences dialog, select <uicontrol>Web Browser</uicontrol> in -the left pane.</li> -<li>On the right, select <uicontrol>Use external Web Browser</uicontrol>.</li> -<li>In the <uicontrol>Location: text</uicontrol> field, browse or type in -the full path of the Internet Explorer executable. (for example, C:\Program -Files\Internet Explorer\iexplore.exe).</li> -<li>Click <uicontrol>Apply</uicontrol> followed by <uicontrol>OK</uicontrol>.</li> -</ol> Note that this preference will now apply to any browser windows that -are launched by the user or by the tools themselves (such as the Universal -Test Client). The Web Services Explorer will now launch in an external browser -and its URL should be in the Address field. This can then be pasted or opened -using am accessibility assisting browser such as <tm tmclass="ibm" tmowner="IBM Corporation" -tmtype="reg" trademark="IBM">IBM</tm> Home Page Reader.</li> -<li>When performing an advanced find or publish in the UDDI page of the Web -Services Explorer, the items in the drop down list for picking a language -in conjunction with a name or description is sorted according to the operating -system's locale settings. On <tm tmclass="special" tmowner="Microsoft Corporation" -tmtype="reg" trademark="Windows">Windows</tm>, this order may be managed through -the Control Panel. To do this:<ol> -<li>Open the Control Panel.</li> -<li>Launch the Regional Options control panel applet.</li> -<li>In the General tab of the resulting dialog, there may be a "Sorting order" -drop-down list. If so, pick a sorting order and then click <uicontrol>Apply</uicontrol> followed -by <uicontrol>OK</uicontrol>.</li> -<li>In the Web Services Explorer, the new sorting order comes into effect -once the page reloads. This can be accomplished by pressing the back arrow -followed by the forward arrow in the main toolbar.</li> -</ol>Note: The instructions above apply to <tm tmclass="special" tmowner="Microsoft Corporation" -tmtype="reg" trademark="Windows">Windows</tm> 2000. On <tm tmclass="special" -tmowner="Microsoft Corporation" tmtype="reg" trademark="Windows">Windows</tm> XP, -the tab mentioned in step 3 is called "Regional Options". Beside the language -drop-down, there is a <uicontrol>Customize</uicontrol> button. When this is -clicked, a new dialog appears. A sorting tab will allow users to pick the -sorting method if applicable.</li> -</ul></p></result> -</taskbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.dita" scope="peer"> -<linktext> Tools for Web services development</linktext></link> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cws.dita" scope="peer"> -<linktext>Web services development</linktext></link> -<link href="../concepts/cuddi.dita"></link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="tuddiexp.dita"></link> -<link href="tstrtexp.dita"></link> -<link href="twsdlexp.dita"></link> -<link href="../../org.eclipse.jst.ws.uddi.registry.doc.user/tasks/tuddiwiz.dita" -scope="peer"><linktext>Configure a private registry</linktext></link> -<link href="../../org.eclipse.jst.ws.doc.user/tasks/toverws.dita" scope="peer"> -<linktext> Developing Web services</linktext></link> -</linklist> -<linklist><title>Related Reference</title> -<link href="../ref/ruddi.dita"></link> -</linklist> -</related-links> -</task> -<?Pub *0000007522?> diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.html deleted file mode 100644 index ddb5d685e..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.html +++ /dev/null @@ -1,186 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Publishing Web services and business entities" /> -<meta name="abstract" content="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes." /> -<meta name="description" content="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes." /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cws.html" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cuddi.html" /> -<meta scheme="URI" name="DC.Relation" content="tuddiexp.html" /> -<meta scheme="URI" name="DC.Relation" content="tstrtexp.html" /> -<meta scheme="URI" name="DC.Relation" content="twsdlexp.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.uddi.registry.doc.user/tasks/tuddiwiz.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/tasks/toverws.html" /> -<meta scheme="URI" name="DC.Relation" content="../ref/ruddi.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tuddiexp" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Publishing Web services and business entities with the Web Services -Explorer</title> -</head> -<body id="tuddiexp"><a name="tuddiexp"><!-- --></a> - - -<h1 class="topictitle1">Publishing Web services and business entities</h1> - - - -<div><p>Through UDDI and WSIL, other applications can discover WSDL documents -and bind with them to execute transactions or perform other business processes. </p> - -<div class="section"><p>UDDI enables the discovery of Web services by providing a distributed -registry of businesses and their service descriptions, implemented in a common -XML format. In order for a service requestor to discover a service, -a service provider must first publish a business entity and at least one business -service, and service interface in a UDDI registry. The Web Services -Explorer is a Web application that supports the publication, discovery, and -maintenance of business entities, business services, and service interfaces.</p> -<p>WSIL -enables the discovery of Web services by defining a distributed service discovery -method that supplies references to service descriptions at the service provider's -point-of-offering, by specifying how to inspect a Web site for available Web -services. The WSIL specification defines the locations on a Web site -where you can look for Web service descriptions. Since WSIL focuses on -distributed service discovery, the WSIL specification complements UDDI by -facilitating the discovery of services that are available on Web sites that -may not be listed yet in a UDDI registry. The Web Services Explorer allows -you to generate and explore WSIL documents.</p> -<p>The favorites page of the -Web Services Explorer allows you to store the location of UDDI registries, -business entities, Web services, service interfaces, as well as WSIL and WSDL -documents.</p> -<p>Use the Web Services Explorer to do any of the following -tasks:</p> -<ul> -<li> <a href="taddreg.html">Add a registry to the Web Services Explorer</a> </li> - -<li> <a href="tbkmrk.html">Adding a registry, business entity, business service, service interface, WSIL, or WSDL service to Favorites</a> </li> - -<li> <a href="tdiscov.html">Discover a Web service</a> </li> - -<li> <a href="tpubent.html">Publish a business entity to a registry</a> </li> - -<li> <a href="tpublish.html">Publish a business service to a registry</a> </li> - -<li> <a href="tunpub.html">Remove a business entity, business service, or service interface from a registry</a> </li> - -<li> <a href="tupdate.html">Update a business entity, business service, or service interface</a> </li> - -<li> <a href="tbusproj.html">Manage referenced services</a> </li> - -<li> <a href="tassert.html">Manage publisher assertions</a> </li> - -</ul> -<p>Prerequisites:</p> -</div> - -<ol> -<li class="stepexpand"><span>Before you can use the Web Services Explorer to perform any of -these functions, you must <a href="treg.html">register with a public registry</a>. -There are many different registries with which you can register.</span> -</li> - -<li class="stepexpand"><span>Ensure that you are using a supported Web browser.</span> The -following Web browsers and versions are supported:<ul> -<li>Internet Explorer: 6.0 and up</li> - -<li>Mozilla: 1.2.1 and up</li> - -</ul> -</li> - -<li class="stepexpand"><span> <a href="tstrtexp.html">Launch the Web Services Explorer</a>.</span> -</li> - -</ol> - -<div class="section"><div class="p"><strong>Known limitations of the Web Services Explorer:</strong><ul> -<li>The taxonomy categories in the Web Services Explorer are not translated -since they must match those in the standards adhered to by UDDI (ISO, UNSPSC -7.3, NAICS).</li> - -<li>The Web Services Explorer will launch without the browser toolbar which -shows, amongst other things, the URL to the Web application. This URL should -only be used by users with accessibility needs. The URL to the Web Services -Explorer Web application can be obtained through the following steps:<ol> -<li>From the Window menu, select Preferences.</li> - -<li>In the Preferences dialog, select <span class="uicontrol">Web Browser</span> in -the left pane.</li> - -<li>On the right, select <span class="uicontrol">Use external Web Browser</span>.</li> - -<li>In the <span class="uicontrol">Location: text</span> field, browse or type in -the full path of the Internet Explorer executable. (for example, C:\Program -Files\Internet Explorer\iexplore.exe).</li> - -<li>Click <span class="uicontrol">Apply</span> followed by <span class="uicontrol">OK</span>.</li> - -</ol> - Note that this preference will now apply to any browser windows that -are launched by the user or by the tools themselves (such as the Universal -Test Client). The Web Services Explorer will now launch in an external browser -and its URL should be in the Address field. This can then be pasted or opened -using am accessibility assisting browser such as IBM<sup>®</sup> Home Page Reader.</li> - -<li>When performing an advanced find or publish in the UDDI page of the Web -Services Explorer, the items in the drop down list for picking a language -in conjunction with a name or description is sorted according to the operating -system's locale settings. On Windows<sup>®</sup>, this order may be managed through -the Control Panel. To do this:<ol> -<li>Open the Control Panel.</li> - -<li>Launch the Regional Options control panel applet.</li> - -<li>In the General tab of the resulting dialog, there may be a "Sorting order" -drop-down list. If so, pick a sorting order and then click <span class="uicontrol">Apply</span> followed -by <span class="uicontrol">OK</span>.</li> - -<li>In the Web Services Explorer, the new sorting order comes into effect -once the page reloads. This can be accomplished by pressing the back arrow -followed by the forward arrow in the main toolbar.</li> - -</ol> -Note: The instructions above apply to Windows 2000. On Windows XP, -the tab mentioned in step 3 is called "Regional Options". Beside the language -drop-down, there is a <span class="uicontrol">Customize</span> button. When this is -clicked, a new dialog appears. A sorting tab will allow users to pick the -sorting method if applicable.</li> - -</ul> -</div> -</div> - -</div> - -<div> -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> -<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> -<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div> -<div><a href="twsdlexp.html" title="">Exploring WSDL using the WSDL Explorer</a></div> -<div><a href="../../org.eclipse.jst.ws.uddi.registry.doc.user/tasks/tuddiwiz.html">Configure a private registry</a></div> -<div><a href="../../org.eclipse.jst.ws.doc.user/tasks/toverws.html"> Developing Web services</a></div></div> - -<div class="linklist"><strong>Related Reference</strong><br /> - -<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tunpub.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tunpub.dita deleted file mode 100644 index 7f9097db7..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tunpub.dita +++ /dev/null @@ -1,56 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd"> -<task id="tunpub" xml:lang="en-us"> -<title>Removing a business entity, Web service, or service interface from -a registry</title> -<titlealts> -<searchtitle>Removing a business entity, Web service, or service interface -from a registry</searchtitle> -</titlealts> -<shortdesc>After you have published a business entity, Web service, or service -interface, you can remove or unpublish it through the Web Services Explorer.</shortdesc> -<taskbody> -<prereq>Prerequisites:<ol> -<li> <xref href="tpubent.dita">Publish a business entity</xref>.</li> -<li> <xref href="tpublish.dita">Publish a Web service</xref>.</li> -<li> <xref href="tpublish.dita">Publish a service interface</xref>.</li> -<li> <xref href="tstrtexp.dita">Launch the<?Pub Caret?> Web Services Explorer</xref>.</li> -</ol></prereq> -<context>To unpublish a business entity, Web service, or service interface -using the Web Services Explorer:</context> -<steps> -<step><cmd>Navigate through the registry hierarchy to find the business entity, -Web service, or service interface you want to unpublish. Select the business -entity, Web service, or service interface.</cmd></step> -<step><cmd>In the Actions icon bar, click the <uicontrol>Unpublish</uicontrol> icon.</cmd> -</step> -<step><cmd>Enter the publish URL, your user ID, and password, if necessary, -then click <uicontrol>Go</uicontrol>.</cmd></step> -</steps> -<result><p>The business entity, Web service, or service interface is removed -from the registry and the Web Services Explorer is automatically updated with -your change.</p></result> -</taskbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.dita" scope="peer"> -<linktext> Tools for Web services development</linktext></link> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cws.dita" scope="peer"> -<linktext>Web services development</linktext></link> -<link href="../concepts/cuddi.dita"></link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="tuddiexp.dita"></link> -<link href="tstrtexp.dita"></link> -<link href="tpubent.dita"></link> -<link href="tpublish.dita"></link> -<link href="tunpub.dita"></link> -<link href="tupdate.dita"></link> -</linklist> -<linklist><title>Related Reference</title> -<link href="../ref/ruddi.dita"></link> -</linklist> -</related-links> -</task> -<?Pub *0000002492?> diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tunpub.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tunpub.html deleted file mode 100644 index 81dfe01b2..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tunpub.html +++ /dev/null @@ -1,99 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Removing a business entity, Web service, or service interface from a registry" /> -<meta name="abstract" content="After you have published a business entity, Web service, or service interface, you can remove or unpublish it through the Web Services Explorer." /> -<meta name="description" content="After you have published a business entity, Web service, or service interface, you can remove or unpublish it through the Web Services Explorer." /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cws.html" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cuddi.html" /> -<meta scheme="URI" name="DC.Relation" content="tuddiexp.html" /> -<meta scheme="URI" name="DC.Relation" content="tstrtexp.html" /> -<meta scheme="URI" name="DC.Relation" content="tpubent.html" /> -<meta scheme="URI" name="DC.Relation" content="tpublish.html" /> -<meta scheme="URI" name="DC.Relation" content="tunpub.html" /> -<meta scheme="URI" name="DC.Relation" content="tupdate.html" /> -<meta scheme="URI" name="DC.Relation" content="../ref/ruddi.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tunpub" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Removing a business entity, Web service, or service interface -from a registry</title> -</head> -<body id="tunpub"><a name="tunpub"><!-- --></a> - - -<h1 class="topictitle1">Removing a business entity, Web service, or service interface from -a registry</h1> - - - -<div><p>After you have published a business entity, Web service, or service -interface, you can remove or unpublish it through the Web Services Explorer.</p> - -<div class="p">Prerequisites:<ol> -<li> <a href="tpubent.html">Publish a business entity</a>.</li> - -<li> <a href="tpublish.html">Publish a Web service</a>.</li> - -<li> <a href="tpublish.html">Publish a service interface</a>.</li> - -<li> <a href="tstrtexp.html">Launch the Web Services Explorer</a>.</li> - -</ol> -</div> - -<div class="section">To unpublish a business entity, Web service, or service interface -using the Web Services Explorer:</div> - -<ol> -<li><span>Navigate through the registry hierarchy to find the business entity, -Web service, or service interface you want to unpublish. Select the business -entity, Web service, or service interface.</span></li> - -<li><span>In the Actions icon bar, click the <span class="uicontrol">Unpublish</span> icon.</span> -</li> - -<li><span>Enter the publish URL, your user ID, and password, if necessary, -then click <span class="uicontrol">Go</span>.</span></li> - -</ol> - -<div class="section"><p>The business entity, Web service, or service interface is removed -from the registry and the Web Services Explorer is automatically updated with -your change.</p> -</div> - -</div> - -<div> -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> -<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> -<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div> -<div><a href="tpubent.html" title="A business entity contains information about the business that has published a service. Before you can publish a business service, you must publish a business entity.">Publishing a business entity</a></div> -<div><a href="tpublish.html" title="The Web service, also known as the business service, describes a Web service's endpoint and where its WSDL file resides. The WSDL file lists the operations that service provides.">Publishing a Web service</a></div> -<div><a href="tunpub.html" title="After you have published a business entity, Web service, or service interface, you can remove or unpublish it through the Web Services Explorer.">Removing a business entity, Web service, or service interface from a registry</a></div> -<div><a href="tupdate.html" title="After you have published a business entity, Web service, or service interface, you can update it through the Web Services Explorer.">Updating a business entity, Web service, or service interface</a></div></div> - -<div class="linklist"><strong>Related Reference</strong><br /> - -<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tupdate.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tupdate.dita deleted file mode 100644 index 23165cb1e..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tupdate.dita +++ /dev/null @@ -1,51 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd"> -<task id="tupdate" xml:lang="en-us"> -<title>Updating a business entity, Web service, or service interface</title> -<shortdesc>After you have published a business entity, Web service, or service -interface, you can update it through the Web Services Explorer.</shortdesc> -<taskbody> -<prereq>Prerequisites:<ol> -<li> <xref href="tpubent.dita">Publish a business entity</xref>.</li> -<li> <xref href="tpublish.dita">Publish a Web service</xref>.</li> -<li> <xref href="tpublish.dita">Publish a service interface</xref>.</li> -<li> <xref href="tstrtexp.dita">Launch the Web Services Explorer</xref>.</li> -</ol></prereq> -<context>To update a business entity, Web service, or service interface using -the Web Services Explorer:</context> -<steps> -<step><cmd>Navigate through the registry hierarchy to find the business entity, -Web service, or service interface you want to update. Select the business -entity, Web service, or service interface.</cmd></step> -<step><cmd>In the Actions icon bar, click the <uicontrol>Details</uicontrol> icon.</cmd> -</step> -<step><cmd>Make any necessary changes and enter your publish URL, your user -ID, and password, if necessary, then click <uicontrol>Go</uicontrol>.</cmd> -</step> -</steps> -<result><p>The business entity, Web service, or service interface is updated -in the registry and the<?Pub Caret?> Web Services Explorer is automatically -updated with your change.</p></result> -</taskbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.dita" scope="peer"> -<linktext> Tools for Web services development</linktext></link> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cws.dita" scope="peer"> -<linktext>Web services development</linktext></link> -<link href="../concepts/cuddi.dita"></link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="tuddiexp.dita"></link> -<link href="tstrtexp.dita"></link> -<link href="tpubent.dita"></link> -<link href="tpublish.dita"></link> -<link href="tunpub.dita"></link> -</linklist> -<linklist><title>Related Reference</title> -<link href="../ref/ruddi.dita"></link> -</linklist> -</related-links> -</task> -<?Pub *0000002323?> diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tupdate.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tupdate.html deleted file mode 100644 index 183653e5f..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tupdate.html +++ /dev/null @@ -1,95 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Updating a business entity, Web service, or service interface" /> -<meta name="abstract" content="After you have published a business entity, Web service, or service interface, you can update it through the Web Services Explorer." /> -<meta name="description" content="After you have published a business entity, Web service, or service interface, you can update it through the Web Services Explorer." /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cws.html" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cuddi.html" /> -<meta scheme="URI" name="DC.Relation" content="tuddiexp.html" /> -<meta scheme="URI" name="DC.Relation" content="tstrtexp.html" /> -<meta scheme="URI" name="DC.Relation" content="tpubent.html" /> -<meta scheme="URI" name="DC.Relation" content="tpublish.html" /> -<meta scheme="URI" name="DC.Relation" content="tunpub.html" /> -<meta scheme="URI" name="DC.Relation" content="../ref/ruddi.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tupdate" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Updating a business entity, Web service, or service interface</title> -</head> -<body id="tupdate"><a name="tupdate"><!-- --></a> - - -<h1 class="topictitle1">Updating a business entity, Web service, or service interface</h1> - - -<div><p>After you have published a business entity, Web service, or service -interface, you can update it through the Web Services Explorer.</p> - -<div class="p">Prerequisites:<ol> -<li> <a href="tpubent.html">Publish a business entity</a>.</li> - -<li> <a href="tpublish.html">Publish a Web service</a>.</li> - -<li> <a href="tpublish.html">Publish a service interface</a>.</li> - -<li> <a href="tstrtexp.html">Launch the Web Services Explorer</a>.</li> - -</ol> -</div> - -<div class="section">To update a business entity, Web service, or service interface using -the Web Services Explorer:</div> - -<ol> -<li><span>Navigate through the registry hierarchy to find the business entity, -Web service, or service interface you want to update. Select the business -entity, Web service, or service interface.</span></li> - -<li><span>In the Actions icon bar, click the <span class="uicontrol">Details</span> icon.</span> -</li> - -<li><span>Make any necessary changes and enter your publish URL, your user -ID, and password, if necessary, then click <span class="uicontrol">Go</span>.</span> -</li> - -</ol> - -<div class="section"><p>The business entity, Web service, or service interface is updated -in the registry and the Web Services Explorer is automatically -updated with your change.</p> -</div> - -</div> - -<div> -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> -<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> -<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div> -<div><a href="tpubent.html" title="A business entity contains information about the business that has published a service. Before you can publish a business service, you must publish a business entity.">Publishing a business entity</a></div> -<div><a href="tpublish.html" title="The Web service, also known as the business service, describes a Web service's endpoint and where its WSDL file resides. The WSDL file lists the operations that service provides.">Publishing a Web service</a></div> -<div><a href="tunpub.html" title="After you have published a business entity, Web service, or service interface, you can remove or unpublish it through the Web Services Explorer.">Removing a business entity, Web service, or service interface from a registry</a></div></div> - -<div class="linklist"><strong>Related Reference</strong><br /> - -<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdisc.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdisc.html deleted file mode 100644 index 118662223..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdisc.html +++ /dev/null @@ -1,103 +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 http-equiv="Content-Type" content="text/html; charset=utf-8" /> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 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 - *******************************************************************************/ --> -<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" /> -<title>Creating a Web service proxy using Faces</title> -</head> -<body id="creatingawebserviceproxy"><a name="creatingawebserviceproxy"><!-- --></a> - -<h1 class="topictitle1">Creating a Web service proxy using Faces</h1> -<div><p>The Web Service Discovery Dialog allows you to discover a Web service -that exists online or in your workspace, create a proxy to the Web service, -and then place the methods of the proxy on a Faces JSP file.</p> -<div class="p">Prerequisite: You must have a Faces JSP file on which you will place -the proxy methods.</div> -<div class="section">To discover a Web service and create a proxy for it:</div> -<ol><li><span>Open your Faces JSP file in an editor by double-clicking it.</span></li> -<li><span>The Page Data view should be open below the Project Navigator. -If the Page Data view is not visible, open from the Window menu by selecting <span class="menucascade"><span class="uicontrol">Show View</span> > <span class="uicontrol">Other</span> > <span class="uicontrol">Web</span> > <span class="uicontrol">Page Data</span></span>.</span></li> -<li><span>In the Page Data view, right-click and select <span class="uicontrol">New</span> > <span class="uicontrol">Web -Service</span>.</span></li> -<li><span>In the Web Service Discovery Dialog, select how you want to find -a Web service: </span> -<table border="1" frame="hsides" rules="rows" cellpadding="4" cellspacing="0" summary="" class="choicetableborder"> -<thead><tr><th valign="bottom" align="left" id="d0e42-option">Option</th> -<th valign="bottom" align="left" id="d0e42-desc">Description</th></tr></thead> -<tbody><tr><td valign="top" headers="d0e42-option" id="d0e49"><strong>Searching a public or private UDDI registry.</strong></td> -<td valign="top" headers="d0e42-desc d0e49">If -you select this option the UDDI Registry page displays.<ol type="a"><li>Enter the URL of a public or private UDDI registry, or select from the -registries supplied.</li> -<li>Enter the text with which you want to search the registry. This can include -either the partial or full name or key (UUID) of the service.</li> -<li>Select if you want to search by the name of the Web service, or by the -key that is associated with a published Web service, and click <span class="uicontrol">Go</span>.</li> -<li>The UDDI Services table is populated with a list of available Web services -that match your criteria, including their name, description, and a URL where -their WSDL file is located.<ul><li>To see additional information about the service, click Details. This will -launch the Web service in the Web Services Explorer. For more information -about using the Web Services Explorer, refer to <a href="ttestwsdl.html">Testing WSDL documents and Web services using the WSDL Explorer</a>.</li> -<li>Click a WSDL file to continue creating your Web service proxy. Go to step <a href="#creatingawebserviceproxy__disc_step_5">5</a>.</li> -</ul> -</li> -</ol> -</td> -</tr> -<tr><td valign="top" headers="d0e42-option" id="d0e77"><strong>From a known URL. This can include known WSDL, WSIL, DISCO, -and HTML URLs.</strong></td> -<td valign="top" headers="d0e42-desc d0e77">When you select this option, the URL page -displays. Enter the URL to a WSDL, WSIL, DISCO or HTML file that contains -a Web service, and click <span class="uicontrol">Go</span>.<ul><li>If you entered a URL to a WSIL, HMTL, or DISCO file, a list of Web services -available from the URL are displayed. Select one of the Web services by clicking -on the WSDL file, and go to step <a href="#creatingawebserviceproxy__disc_step_5">5</a>.</li> -<li>If you entered a URL to a WSDL file, go to step <a href="#creatingawebserviceproxy__disc_step_5">5</a>.</li> -</ul> -</td> -</tr> -<tr><td valign="top" headers="d0e42-option" id="d0e96"><strong>Selecting from Web services that are deployed and running -in your workspace.</strong></td> -<td valign="top" headers="d0e42-desc d0e96">If you selected to discover Web services -that are in your workspace, the Workspace page displays. It contains a list -of the Web services available in your workspace. Select a Web service by clicking -on the appropriate WSDL file and go to step <a href="#creatingawebserviceproxy__disc_step_5">5</a>.</td> -</tr> -</tbody></table> -</li> -<li id="creatingawebserviceproxy__disc_step_5"><a name="creatingawebserviceproxy__disc_step_5"><!-- --></a><span>Once you have selected a WSDL file, a table displays -the Web Service name and location, any documentation included in the Web service, -and lists the available ports.</span><ol type="a"><li class="substepexpand"><span>If there is more than one port, select the port for which you -want to create the proxy.</span></li> -<li class="substepexpand"><span>To test the Web service and to see additional information about -it, click Details. This will launch the Web service in the Web Services Explorer.</span> For more information about using the Web Services Explorer, refer to <a href="ttestwsdl.html">Testing WSDL documents and Web services -using the WSDL Explorer</a>.</li> -<li class="substepexpand"><span>Once you have ensured that the chosen Web service is the correct -one, click Add to Project.</span> This generates your proxy bean.</li> -</ol> -</li> -<li><span>The proxy is now listed in the list of existing proxy beans. Click <span class="uicontrol">OK</span> to -add it to your Page Data.</span></li> -<li id="creatingawebserviceproxy__ws_disc_step_7"><a name="creatingawebserviceproxy__ws_disc_step_7"><!-- --></a><span>Select the proxy method in the Page Data view, -and drag it onto your Faces JSP file Design view. You will be asked if you -want to use this bean to update fields or to display fields. Select the appropriate -choice, and if necessary add an action to the bean by clicking the Browse -button beside the Action field. Repeat for any other elements that you want -to add to the page.</span></li> -</ol> -<div class="section">The proxy for the Web service is now on a Faces JSP. Save the Faces -JSP and run it on a sever to test your Web service.</div> -</div> -<div></div> -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdlexp.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdlexp.dita deleted file mode 100644 index 646b7e5a1..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdlexp.dita +++ /dev/null @@ -1,138 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd"> -<task id="twsdlexp" xml:lang="en-us"> -<title>Exploring WSDL using the WSDL Explorer</title> -<taskbody> -<prereq>Prerequisites: To use the WSDL Explorer, you must have a valid URL -for a WSDL document.</prereq> -<context>The WSDL Explorer allows you to explore, and test WSDL documents. -The following actions are available in the WSDL Explorer:<ul> -<li>Import WSDL to the Workbench: <image alt="Import WSDL to the Workbench icon" -href="../images/mptwsdlicon.gif"></image></li> -<li>Import WSDL to your file system: <image alt="Import WSDL to your file system icon" -href="../images/fswsdlicon.gif"></image></li> -<li>Launch the Web Service Wizard: <image alt="Launch the Web Service Wizard icon" -href="../images/wswizicon.gif"></image></li> -<li>Add WSDL to Favorites: <image alt="Add WSDL to Favorites icon" href="../images/wsdlfavicon.gif"> -</image></li> -<li>Show WSDL details: <image alt="WSDL Details icon" href="../images/wsdldtlicon.gif"> -</image></li> -</ul></context> -</taskbody> -<task id="d0e47" xml:lang="en-us"> -<title>Launching the WSDL Explorer</title> -<taskbody> -<context><p>To launch the WSDL Explorer, complete the following steps:</p></context> -<steps> -<step><cmd> <xref href="tstrtexp.dita">Launch the Web Services Explorer</xref>.</cmd> -</step> -<step><cmd>Switch to the WSDL Explorer by clicking the icon in the upper right-hand -corner <image alt="Icon to launch the WSDL Explorer" href="../images/wsdlicon.gif"> -</image>.</cmd></step> -</steps> -</taskbody> -</task> -<task id="d0e64" xml:lang="en-us"> -<title>Importing a WSDL file to your workspace</title> -<taskbody> -<context><p>To import the WSDL file to the Workbench:</p></context> -<steps> -<step><cmd>Click this icon: <image alt="Import WSDL to the Workbench icon" -href="../images/mptwsdlicon.gif"></image>.</cmd></step> -<step><cmd>Select the project into which you want to import the WSDL.</cmd> -</step> -<step><cmd>If you want to generate a WSIL file from the WSDL, select <b>Import -as a service reference to a WSIL document</b>.</cmd></step> -<step><cmd>Click <b>Go</b>.</cmd></step> -</steps> -</taskbody> -</task> -<task id="d0e90" xml:lang="en-us"> -<title>Importing a WSDL file to your file system</title> -<taskbody> -<context><p>To import the WSDL file to your file system, click this icon: - <image alt="Import WSDL to your file system icon" href="../images/fswsdlicon.gif"> -</image>. Specify where you want the WSDL file saved on your system.</p></context> -</taskbody> -</task> -<task id="d0e96" xml:lang="en-us"> -<title>Launching the Web services wizard</title> -<taskbody> -<context><p>To launch the Web Service Wizard, click this icon: <image alt="Launch the Web Service Wizard icon" -href="../images/wswizicon.gif"></image>. You can select if you want to create -a Web service client or a Skeleton Web service from the WSDL file. Click <b>Go</b> to -launch the wizard.</p></context> -</taskbody> -</task> -<task id="d0e105" xml:lang="en-us"> -<title>Adding a WSDL file to your favorites</title> -<taskbody> -<context><p>To add the WSDL file to Favorites, click this icon: </p><p>. -The Status pane displays that the WSDL was successfully added to your list -of favorites. </p></context> -</taskbody> -</task> -<task id="d0e110" xml:lang="en-us"> -<title>Exploring WSDL documents using the WSDL Explorer:</title> -<taskbody> -<steps> -<step><cmd>Select WSDL Main in the Navigator pane, enter or browse to an existing -WSDL URL in the right-hand pane, and click <b>Go</b>. Note that the Explorer -will only allow you to browse for WSDL files that reside in the <codeph>WebContent/WSDL</codeph> folder -of a project. To explore WSDL files stored in other locations within your -workspace, type the name of the WSDL file or select the file in the workspace, -right-click and select <menucascade><uicontrol>Web Services </uicontrol><uicontrol> Launch -Web Services Explorer</uicontrol></menucascade>. For this example the WSDL -being used is a Web Service which returns a temperature for any entered zip -code. <image alt="" href="../images/wsdlexp.gif" placement="break"></image> -The following nodes will be added to the WSDL tree: </cmd><info><ul> -<li>The WSDL node: <image alt="WSDL node icon" href="../images/wsdlnode.gif"> -</image></li> -<li>The service node (which represents a service element within the WSDL file): - <image alt="Service node icon" href="../images/servnode.gif"></image></li> -<li>The binding node: <image alt="Binding node icon" href="../images/bindnode.gif"> -</image></li> -<li>The operation node: <image alt="Operation node icon" href="../images/opnode.gif"> -</image></li> -</ul></info></step> -<step><cmd>Clicking the Service node in the Navigator pane (in this example -this would be the <systemoutput>TemperatureService</systemoutput> node) displays -all the bindings for this service, as well as their type and a brief description -of the binding if the WSDL provider has included one in the Actions pane. -Three types of bindings are supported: SOAP, HTTP Get, and HTTP Post. <image -alt="" href="../images/wsdlservdet.gif" placement="break"></image> The WSDL -used in this example only has one binding, <systemoutput>TemperatureBinding</systemoutput>, -which is represented as the <systemoutput>TemperaturePortType</systemoutput> node -in the WSDL tree in the Navigator pane.</cmd></step> -<step><cmd>Clicking a displayed binding or its node displays the WSDL binding -details in the Actions pane. This includes the operations and endpoints available -for this service. <image alt="" href="../images/wsdlbnddetl.gif" placement="break"> -</image> In this view you can add or remove endpoints for the service. To -add an endpoint, click <b>Add</b>, enter the URL for the endpoint, and click - <b>Go</b>. The Status pane should say that the endpoints were successfully -updated. To remove an endpoint, select its checkbox, and click <b>Remove</b>.</cmd> -</step> -</steps> -<postreq><note><draft-comment>282413 (ref 279209)</draft-comment>When the -Web Services Explorer loads WSDL files that use multiple inline schemas, warning -messages will be generated for types that are referenced across these schemas. -The warning message will be similar to: <codeph>Reference of type <<i>qualified_type_name</i>> -isn't resolved.</codeph></note></postreq> -</taskbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cws.dita" scope="peer"> -<linktext>Web services development</linktext></link><?Pub Caret?> -<link href="../concepts/cuddi.dita"></link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="tuddiexp.dita"></link> -<link href="tstrtexp.dita"></link> -<link href="../../org.eclipse.jst.ws.doc.user/tasks/toverws.dita" scope="peer"> -<linktext> Developing Web services</linktext></link> -</linklist> -</related-links> -</task> -</task> -<?Pub *0000006946?> diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdlexp.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdlexp.html deleted file mode 100644 index a54aad962..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdlexp.html +++ /dev/null @@ -1,198 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Exploring WSDL using the WSDL Explorer" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="twsdlexp" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Exploring WSDL using the WSDL Explorer</title> -</head> -<body id="twsdlexp"><a name="twsdlexp"><!-- --></a> - - -<h1 class="topictitle1">Exploring WSDL using the WSDL Explorer</h1> - -<div> -<div class="p">Prerequisites: To use the WSDL Explorer, you must have a valid URL -for a WSDL document.</div> - -<div class="section">The WSDL Explorer allows you to explore, and test WSDL documents. -The following actions are available in the WSDL Explorer:<ul> -<li>Import WSDL to the Workbench: <img src="../images/mptwsdlicon.gif" alt="Import WSDL to the Workbench icon" /></li> - -<li>Import WSDL to your file system: <img src="../images/fswsdlicon.gif" alt="Import WSDL to your file system icon" /></li> - -<li>Launch the Web Service Wizard: <img src="../images/wswizicon.gif" alt="Launch the Web Service Wizard icon" /></li> - -<li>Add WSDL to Favorites: <img src="../images/wsdlfavicon.gif" alt="Add WSDL to Favorites icon" /></li> - -<li>Show WSDL details: <img src="../images/wsdldtlicon.gif" alt="WSDL Details icon" /></li> - -</ul> -</div> - -</div> - -<div class="nested1" xml:lang="en-us" id="d0e47"><a name="d0e47"><!-- --></a> -<h2 class="topictitle2">Launching the WSDL Explorer</h2> - -<div> -<div class="section"><p>To launch the WSDL Explorer, complete the following steps:</p> -</div> - -<ol> -<li><span> <a href="tstrtexp.html">Launch the Web Services Explorer</a>.</span> -</li> - -<li><span>Switch to the WSDL Explorer by clicking the icon in the upper right-hand -corner <img src="../images/wsdlicon.gif" alt="Icon to launch the WSDL Explorer" />.</span></li> - -</ol> - -</div> - -</div> - -<div class="nested1" xml:lang="en-us" id="d0e64"><a name="d0e64"><!-- --></a> -<h2 class="topictitle2">Importing a WSDL file to your workspace</h2> - -<div> -<div class="section"><p>To import the WSDL file to the Workbench:</p> -</div> - -<ol> -<li><span>Click this icon: <img src="../images/mptwsdlicon.gif" alt="Import WSDL to the Workbench icon" />.</span></li> - -<li><span>Select the project into which you want to import the WSDL.</span> -</li> - -<li><span>If you want to generate a WSIL file from the WSDL, select <strong>Import -as a service reference to a WSIL document</strong>.</span></li> - -<li><span>Click <strong>Go</strong>.</span></li> - -</ol> - -</div> - -</div> - -<div class="nested1" xml:lang="en-us" id="d0e90"><a name="d0e90"><!-- --></a> -<h2 class="topictitle2">Importing a WSDL file to your file system</h2> - -<div> -<div class="section"><p>To import the WSDL file to your file system, click this icon: - <img src="../images/fswsdlicon.gif" alt="Import WSDL to your file system icon" />. Specify where you want the WSDL file saved on your system.</p> -</div> - -</div> - -</div> - -<div class="nested1" xml:lang="en-us" id="d0e96"><a name="d0e96"><!-- --></a> -<h2 class="topictitle2">Launching the Web services wizard</h2> - -<div> -<div class="section"><p>To launch the Web Service Wizard, click this icon: <img src="../images/wswizicon.gif" alt="Launch the Web Service Wizard icon" />. You can select if you want to create -a Web service client or a Skeleton Web service from the WSDL file. Click <strong>Go</strong> to -launch the wizard.</p> -</div> - -</div> - -</div> - -<div class="nested1" xml:lang="en-us" id="d0e105"><a name="d0e105"><!-- --></a> -<h2 class="topictitle2">Adding a WSDL file to your favorites</h2> - -<div> -<div class="section"><p>To add the WSDL file to Favorites, click this icon: </p> -<p>. -The Status pane displays that the WSDL was successfully added to your list -of favorites. </p> -</div> - -</div> - -</div> - -<div class="nested1" xml:lang="en-us" id="d0e110"><a name="d0e110"><!-- --></a> -<h2 class="topictitle2">Exploring WSDL documents using the WSDL Explorer:</h2> - -<div> -<ol> -<li class="stepexpand"><span>Select WSDL Main in the Navigator pane, enter or browse to an existing -WSDL URL in the right-hand pane, and click <strong>Go</strong>. Note that the Explorer -will only allow you to browse for WSDL files that reside in the <samp class="codeph">WebContent/WSDL</samp> folder -of a project. To explore WSDL files stored in other locations within your -workspace, type the name of the WSDL file or select the file in the workspace, -right-click and select <span class="menucascade"><span class="uicontrol">Web Services </span> > <span class="uicontrol"> Launch -Web Services Explorer</span></span>. For this example the WSDL -being used is a Web Service which returns a temperature for any entered zip -code. <br /><img src="../images/wsdlexp.gif" alt="" /><br /> -The following nodes will be added to the WSDL tree: </span> <ul> -<li>The WSDL node: <img src="../images/wsdlnode.gif" alt="WSDL node icon" /></li> - -<li>The service node (which represents a service element within the WSDL file): - <img src="../images/servnode.gif" alt="Service node icon" /></li> - -<li>The binding node: <img src="../images/bindnode.gif" alt="Binding node icon" /></li> - -<li>The operation node: <img src="../images/opnode.gif" alt="Operation node icon" /></li> - -</ul> -</li> - -<li class="stepexpand"><span>Clicking the Service node in the Navigator pane (in this example -this would be the <tt class="sysout">TemperatureService</tt> node) displays -all the bindings for this service, as well as their type and a brief description -of the binding if the WSDL provider has included one in the Actions pane. -Three types of bindings are supported: SOAP, HTTP Get, and HTTP Post. <br /><img src="../images/wsdlservdet.gif" alt="" /><br /> The WSDL -used in this example only has one binding, <tt class="sysout">TemperatureBinding</tt>, -which is represented as the <tt class="sysout">TemperaturePortType</tt> node -in the WSDL tree in the Navigator pane.</span></li> - -<li class="stepexpand"><span>Clicking a displayed binding or its node displays the WSDL binding -details in the Actions pane. This includes the operations and endpoints available -for this service. <br /><img src="../images/wsdlbnddetl.gif" alt="" /><br /> In this view you can add or remove endpoints for the service. To -add an endpoint, click <strong>Add</strong>, enter the URL for the endpoint, and click - <strong>Go</strong>. The Status pane should say that the endpoints were successfully -updated. To remove an endpoint, select its checkbox, and click <strong>Remove</strong>.</span> -</li> - -</ol> - -<div class="section"><div class="note"><span class="notetitle">Note: </span>When the -Web Services Explorer loads WSDL files that use multiple inline schemas, warning -messages will be generated for types that are referenced across these schemas. -The warning message will be similar to: <samp class="codeph">Reference of type <<em>qualified_type_name</em>> -isn't resolved.</samp></div> -</div> - -</div> - -<div> -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> -<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> -<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div> -<div><a href="../../org.eclipse.jst.ws.doc.user/tasks/toverws.html"> Developing Web services</a></div></div> -</div> -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptionbuild_toc.ditamap b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptionbuild_toc.ditamap deleted file mode 100644 index 67238899b..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptionbuild_toc.ditamap +++ /dev/null @@ -1,39 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd"> -<map anchorref="../org.eclipse.jst.ws.doc.user/webservice_toc.ditamap#wsconsumptiont" -title="wsconsumptiont"> -<topicref href="concepts/cuddi.dita" navtitle="Universal Description, Discovery, and Integration (UDDI)"> -</topicref> -<topicref href="concepts/cwsdlud.dita" navtitle="Relationship between UDDI and WSDL"> -</topicref> -<topicref href="tasks/tdiscov.dita" navtitle="Discovering and importing a Web service"> -</topicref> -<topicref href="tasks/twsdlexp.dita" navtitle="Exploring and testing WSDL using the WSDL Explorer"> -</topicref> -<topicref href="tasks/ttestwsdl.dita" navtitle="Testing WSDL documents and Web services with the WSDL Explorer"> -</topicref> -<topicref href="tasks/tuddiexp.dita" navtitle="Publishing Web services and business entities"> -<topicref href="tasks/tstrtexp.dita" navtitle="Launching the Web Services Explorer"> -</topicref> -<topicref href="tasks/treg.dita" navtitle="Registering with a registry"></topicref> -<topicref href="tasks/taddreg.dita" navtitle="Adding a Registry to the Web Services Explorer"> -</topicref> -<topicref href="tasks/tpubent.dita" navtitle="Publishing a business entity"> -</topicref> -<topicref href="tasks/tpublish.dita" navtitle="Publishing a Web service"> -<topicref href="ref/ruddi.dita" navtitle="Data structure types (UDDI registry)"> -</topicref> -</topicref> -<topicref href="tasks/tupdate.dita" navtitle="Updating a business entity, Web service, or service interface"> -</topicref> -<topicref href="tasks/tunpub.dita" navtitle="Removing a business entity, Web service, or service interface from a registry"> -</topicref> -<topicref href="tasks/tbusproj.dita" navtitle="Managing referenced services"> -</topicref> -<topicref href="tasks/tassert.dita" navtitle="Managing publisher assertions"> -</topicref> -<topicref href="tasks/tbkmrk.dita" navtitle="Adding to Favorites"></topicref> -<topicref href="tasks/tgenwsil.dita" navtitle="Generating WSIL"></topicref> -</topicref> -</map> diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptionbuild_toc.xml b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptionbuild_toc.xml deleted file mode 100644 index 4bd6903db..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptionbuild_toc.xml +++ /dev/null @@ -1,26 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> - -<?NLS TYPE="org.eclipse.help.toc"?> - -<toc link_to="../org.eclipse.jst.ws.doc.user/webservice_toc.xml#wsconsumptiont" label="wsconsumptiont" topic="concepts/cuddi.html"> -<topic label="Universal Description, Discovery, and Integration (UDDI)" href="concepts/cuddi.html"/> -<topic label="Relationship between UDDI and WSDL" href="concepts/cwsdlud.html"/> -<topic label="Discovering Web Services" href="tasks/tdiscov.html"/> -<topic label="Exploring WSDL using the WSDL Explorer" href="tasks/twsdlexp.html"/> -<topic label="Testing WSDL documents and Web services using the WSDL Explorer" href="tasks/ttestwsdl.html"/> -<topic label="Publishing Web services and business entities" href="tasks/tuddiexp.html"> -<topic label="Launching the Web Services Explorer" href="tasks/tstrtexp.html"/> -<topic label="Registering with a UDDI registry" href="tasks/treg.html"/> -<topic label="Adding a Registry to the Web Services Explorer" href="tasks/taddreg.html"/> -<topic label="Publishing a business entity" href="tasks/tpubent.html"/> -<topic label="Publishing a Web service" href="tasks/tpublish.html"> -<topic label="Data structure types (UDDI registry)" href="ref/ruddi.html"/> -</topic> -<topic label="Updating a business entity, Web service, or service interface" href="tasks/tupdate.html"/> -<topic label="Removing a business entity, Web service, or service interface from a registry" href="tasks/tunpub.html"/> -<topic label="Managing referenced services" href="tasks/tbusproj.html"/> -<topic label="Managing publisher assertions" href="tasks/tassert.html"/> -<topic label="Adding a registry, business entity, business service, service interface, WSIL, or WSDL service to Favorites" href="tasks/tbkmrk.html"/> -<topic label="Generating a WSIL file" href="tasks/tgenwsil.html"/> -</topic> -</toc> diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptiont_toc.ditamap b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptiont_toc.ditamap deleted file mode 100644 index f815f48a6..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptiont_toc.ditamap +++ /dev/null @@ -1,29 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd"> -<map anchorref="../org.eclipse.jst.ws.doc.user/webservice_toc.ditamap#wsconsumptiont" -title="wsconsumptiont"><?Pub Caret1?> -<topicref href="tasks/tuddiexp.dita" navtitle="Publishing Web services and business entities"> -<topicref href="tasks/tstrtexp.dita" navtitle="Launching the Web Services Explorer"> -</topicref> -<topicref href="tasks/treg.dita" navtitle="Registering with a registry"></topicref> -<topicref href="tasks/taddreg.dita" navtitle="Adding a Registry to the Web Services Explorer"> -</topicref> -<topicref href="tasks/tpubent.dita" navtitle="Publishing a business entity"> -</topicref> -<topicref href="tasks/tpublish.dita" navtitle="Publishing a Web service"> -<topicref href="ref/ruddi.dita" navtitle="Data structure types (UDDI registry)"> -</topicref> -</topicref> -<topicref href="tasks/tupdate.dita" navtitle="Updating a business entity, Web service, or service interface"> -</topicref> -<topicref href="tasks/tunpub.dita" navtitle="Removing a business entity, Web service, or service interface from a registry"> -</topicref> -<topicref href="tasks/tbusproj.dita" navtitle="Managing referenced services"> -</topicref> -<topicref href="tasks/tassert.dita" navtitle="Managing publisher assertions"> -</topicref> -<topicref href="tasks/tbkmrk.dita" navtitle="Adding to Favorites"></topicref> -</topicref> -</map> -<?Pub *0000001480?> diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptiont_toc.xml b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptiont_toc.xml deleted file mode 100644 index c290461a3..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptiont_toc.xml +++ /dev/null @@ -1,18 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<?NLS TYPE="org.eclipse.help.toc"?> -<toc label="wsconsumptiont" link_to="../org.eclipse.jst.ws.doc.user/webservice_toc.xml#wsconsumptiont" topic="tasks/tuddiexp.html"> - <topic label="Publishing Web services and business entities" href="tasks/tuddiexp.html"> - <topic label="Launching the Web Services Explorer" href="tasks/tstrtexp.html"/> - <topic label="Registering with a UDDI registry" href="tasks/treg.html"/> - <topic label="Adding a Registry to the IBM Web Services Explorer" href="tasks/taddreg.html"/> - <topic label="Publishing a business entity" href="tasks/tpubent.html"/> - <topic label="Publishing a Web service" href="tasks/tpublish.html"> - <topic label="Data structure types (UDDI registry)" href="ref/ruddi.html"/> - </topic> - <topic label="Updating a business entity, Web service, or service interface" href="tasks/tupdate.html"/> - <topic label="Removing a business entity, Web service, or service interface from a registry" href="tasks/tunpub.html"/> - <topic label="Managing referenced services" href="tasks/tbusproj.html"/> - <topic label="Managing publisher assertions" href="tasks/tassert.html"/> - <topic label="Adding a registry, business entity, business service, service interface, WSIL, or WSDL service to Favorites" href="tasks/tbkmrk.html"/> - </topic> -</toc>
\ No newline at end of file |
