diff options
| author | ryman | 2006-04-05 21:42:24 +0000 |
|---|---|---|
| committer | ryman | 2006-04-05 21:42:24 +0000 |
| commit | c4bae084ddc22c7b8690a5a24cae99a6445ce8f4 (patch) | |
| tree | 29866df16962c2fc89dc12c0a7076e0395d4c135 | |
| parent | a73f41c57c3d5bfc039451a70a22463bec11ea12 (diff) | |
| download | webtools.webservices-c4bae084ddc22c7b8690a5a24cae99a6445ce8f4.tar.gz webtools.webservices-c4bae084ddc22c7b8690a5a24cae99a6445ce8f4.tar.xz webtools.webservices-c4bae084ddc22c7b8690a5a24cae99a6445ce8f4.zip | |
[131837] Initial commit of DITA source and build.xml.
157 files changed, 8397 insertions, 2006 deletions
diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/.cvsignore b/docs/org.eclipse.jst.ws.axis.ui.doc.user/.cvsignore index ddcf3a975..c1e365972 100644 --- a/docs/org.eclipse.jst.ws.axis.ui.doc.user/.cvsignore +++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/.cvsignore @@ -1,2 +1,3 @@ -build.xml org.eclipse.jst.ws.axis.ui.doc.user_1.0.0.jar +bak +temp diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/build.xml b/docs/org.eclipse.jst.ws.axis.ui.doc.user/build.xml new file mode 100644 index 000000000..d57765212 --- /dev/null +++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/build.xml @@ -0,0 +1,59 @@ +<?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="wsaxisbuild_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.axis.ui.doc.user/concepts/caxistover.dita b/docs/org.eclipse.jst.ws.axis.ui.doc.user/concepts/caxistover.dita new file mode 100644 index 000000000..9fa3eb72c --- /dev/null +++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/concepts/caxistover.dita @@ -0,0 +1,42 @@ +<?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="axisoverview" xml:lang="en-us"> +<title>Creating Web services with the Apache Axis run-time environment</title> +<shortdesc>This run-time environment is for users who prefer to develop for +the open Apache Axis platform. It is for non-production use only. Axis is +the third generation of the Apache SOAP implementation. It evolved from Apache +SOAP to make the SOAP engine more flexible, configurable, and able to handle +both SOAP and the upcoming XML Protocol specification from the W3C open-source +effort.</shortdesc> +<conbody> +<section><title>Overview</title><p>Axis is based on JSR 101 <tm tmclass="special" +tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> APIs +for XML based RPC (also known as JAX-RPC). JSR 101 provides a single +interface to any XML-based RPC mechanism, including SOAP.</p><p>Web services +application server uses Axis within a servlet to process the incoming message, +extract information from the message headers, and payloads, as well as conforming +to the particular RPC semantics. </p><p>The level of Axis currently supported +is 1.0. For more information on Axis, refer to <xref format="html" href="http://xml.apache.org/axis" +scope="external">http://xml.apache.org/axis</xref>. The User's Guide available +on this site provides more in-depth information about using Web services with +Apache Axis. The Reading Guide lists several documents to further your understanding +of Axis.</p><note>The support for Axis is limited to validation that the application +is invoking the Axis emitters correctly. Support for other Axis issues should +be directed to <xref format="html" href="http://ws.apache.org/axis" scope="external">http://ws.apache.org/axis</xref></note></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</linktext></link> +<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/cjaxrpc.dita" scope="peer"> +<linktext>JAX-RPC</linktext></link> +</linklist> +<linklist><title>Related Tasks</title> +<link href="../../org.eclipse.jst.ws.doc.user/tasks/toverws.dita" scope="peer"> +<linktext> Developing Web services</linktext></link> +</linklist> +</related-links> +</concept> diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/concepts/caxistover.html b/docs/org.eclipse.jst.ws.axis.ui.doc.user/concepts/caxistover.html index fa47ad504..fc209b92d 100644 --- a/docs/org.eclipse.jst.ws.axis.ui.doc.user/concepts/caxistover.html +++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/concepts/caxistover.html @@ -1,70 +1,59 @@ -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<?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> -<!-- /******************************************************************************* - * 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" /> - +<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="Creating Web services with the Apache Axis run-time environment" /> +<meta name="abstract" content="This run-time environment is for users who prefer to develop for the open Apache Axis platform. It is for non-production use only. Axis is the third generation of the Apache SOAP implementation. It evolved from Apache SOAP to make the SOAP engine more flexible, configurable, and able to handle both SOAP and the upcoming XML Protocol specification from the W3C open-source effort." /> +<meta name="description" content="This run-time environment is for users who prefer to develop for the open Apache Axis platform. It is for non-production use only. Axis is the third generation of the Apache SOAP implementation. It evolved from Apache SOAP to make the SOAP engine more flexible, configurable, and able to handle both SOAP and the upcoming XML Protocol specification from the W3C open-source effort." /> +<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cws.html" /> +<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/cjaxrpc.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="axisoverview" 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>Creating Web services with the Apache Axis run-time environment</title> </head> <body id="axisoverview"><a name="axisoverview"><!-- --></a> + <h1 class="topictitle1">Creating Web services with the Apache Axis run-time environment</h1> + + <div><p>This run-time environment is for users who prefer to develop for the open Apache Axis platform. It is for non-production use only. Axis is -the third generation of the Apache SOAP implementation. It evolved from -Apache SOAP (which began at IBM<sup>®</sup> as SOAP4J) to make the SOAP engine more flexible, -configurable, and able to handle both SOAP and the upcoming XML Protocol specification -from the W3C open-source effort.</p> -<div class="section"><h4 class="sectiontitle">Overview</h4><p>Axis is based on JSR 101 Java™ APIs -for XML based RPC (also known as JAX-RPC). JSR 101 provides a single +the third generation of the Apache SOAP implementation. It evolved from Apache +SOAP to make the SOAP engine more flexible, configurable, and able to handle +both SOAP and the upcoming XML Protocol specification from the W3C open-source +effort.</p> + +<div class="section"><h4 class="sectiontitle">Overview</h4><p>Axis is based on JSR 101 Javaâ„¢ APIs +for XML based RPC (also known as JAX-RPC). JSR 101 provides a single interface to any XML-based RPC mechanism, including SOAP.</p> <p>Web services application server uses Axis within a servlet to process the incoming message, extract information from the message headers, and payloads, as well as conforming to the particular RPC semantics. </p> <p>The level of Axis currently supported -by this product is 1.0. For more information on Axis, -refer to <a href="http://xml.apache.org/axis" target="_blank">http://xml.apache.org/axis</a>. -The User's Guide available on this site provides more in-depth information -about using Web services with Apache Axis. The Reading Guide lists several -documents to further your understanding of Axis.</p> -<div class="note"><span class="notetitle">Note:</span> The support for -Axis is limited to validation that the application +is 1.0. For more information on Axis, refer to <a href="http://xml.apache.org/axis" target="_blank">http://xml.apache.org/axis</a>. The User's Guide available +on this site provides more in-depth information about using Web services with +Apache Axis. The Reading Guide lists several documents to further your understanding +of Axis.</p> +<div class="note"><span class="notetitle">Note: </span>The support for Axis is limited to validation that the application is invoking the Axis emitters correctly. Support for other Axis issues should be directed to <a href="http://ws.apache.org/axis" target="_blank">http://ws.apache.org/axis</a></div> </div> + </div> -<div> -<ul class="ullinks"> -<li class="ulchildlink"><strong><a href="../tasks/twsbeana.html">Creating a Web service from a Java bean using the Apache Axis run-time environment</a></strong><br /> -The Web Service wizard assists you in creating a new Web service, -configuring it for deployment, and deploying the Web service to a server. -Once your Web service is deployed, the wizard assists you in generating the -client proxy and sample application to test the Web service. When you have -completed testing, you can publish your Web service to a UDDI Business Registry -using the Export wizard.</li> -<li class="ulchildlink"><strong><a href="../tasks/tsklwsdla.html">Creating a Java bean skeleton from a WSDL document using the Apache Axis run-time environment</a></strong><br /> -The Web service wizard assists you in creating a skeleton bean -from an existing WSDL document. The skeleton bean contains a set of methods -that correspond to the operations described in the WSDL document. When the -bean is created, each method has a trivial implementation that you replace -by editing the bean.</li> -<li class="ulchildlink"><strong><a href="../tasks/tsampappa.html">Generating a Java client proxy and a sample application from a WSDL document using the Axis run-time environment</a></strong><br /> -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.</li> -</ul> +<div> <div class="linklist"><strong>Related Concepts</strong><br /> <div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services</a></div> @@ -75,5 +64,6 @@ to code a proxy file.</li> <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.axis.ui.doc.user/myplugin.xml b/docs/org.eclipse.jst.ws.axis.ui.doc.user/myplugin.xml new file mode 100644 index 000000000..8c0ab31db --- /dev/null +++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/myplugin.xml @@ -0,0 +1,19 @@ +<?xml version="1.0" encoding="UTF-8"?> +<?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="wsaxisbuild_toc.xml" /> + + </extension> +</plugin>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/org.eclipse.jst.ws.axis.ui.doc.user.maplist b/docs/org.eclipse.jst.ws.axis.ui.doc.user/org.eclipse.jst.ws.axis.ui.doc.user.maplist new file mode 100644 index 000000000..4a4382296 --- /dev/null +++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/org.eclipse.jst.ws.axis.ui.doc.user.maplist @@ -0,0 +1,8 @@ +<maplist version="3.6.2"> + <nav> + <map file="wsaxisbuild_toc.ditamap"/> + </nav> + <link> + <map file="wsaxisbuild_toc.ditamap"/> + </link> +</maplist> diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsampappa.dita b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsampappa.dita new file mode 100644 index 000000000..a8b2e50d2 --- /dev/null +++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsampappa.dita @@ -0,0 +1,118 @@ +<?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="tsampappa" xml:lang="en-us"> +<title>Generating a <tm tmclass="special" tmowner="Sun Microsystems, Inc." +tmtype="tm" trademark="Java">Java</tm> client proxy and a sample application +from a WSDL document using the Axis run-time environment</title> +<titlealts> +<searchtitle>Generating a Java client proxy and a sample application from +a WSDL document using the Axis run-time environment</searchtitle> +</titlealts> +<shortdesc>The Web Service Client wizard assists you in generating a <tm tmclass="special" +tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> bean +proxy and a sample application. The sample Web application demonstrates how +to code a proxy file.</shortdesc> +<taskbody> +<prereq><p>Prerequisites:</p><ol> +<li conref="tsklwsdla.dita#tsklwsdla/createtomcatlink"></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></prereq> +<context>To generate a <tm tmclass="special" tmowner="Sun Microsystems, Inc." +tmtype="tm" trademark="Java">Java</tm> client proxy and a sample application +from a discovered WSDL document:</context> +<steps> +<step><cmd>Switch to the J2EE perspective (<uicontrol>Window > Open Perspective +> J2EE</uicontrol>).</cmd></step> +<step><cmd>In the Navigator view, select the Web project in which you want +to generate a sample application.</cmd></step> +<step><cmd>Click <uicontrol>File > New > Other</uicontrol>. Select <uicontrol>Web +Services</uicontrol> in order to display the various Web service wizards. +Select the <uicontrol>Web Service Client</uicontrol> wizard. Click <uicontrol>Next</uicontrol>.</cmd> +</step> +<step><cmd>Web Services page: Select the type of proxy to be generated, and +whether or not it will be tested.</cmd></step> +<step><cmd>Client Environment Configuration page: Select the run-time environment +and the server for your Web service client.</cmd> +<substeps> +<substep><cmd>Click <uicontrol>Explore Options</uicontrol> and select the +Apache Axis run-time environment and select the server on which you want to +run your Web service client.</cmd></substep> +<substep><cmd>Select the type and name of project in which you want the Web +service client created.</cmd><info><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 clients is a Web project. +If you want the client to be created in a <tm tmclass="special" tmowner="Sun Microsystems, Inc." +tmtype="tm" trademark="Java">Java</tm>, EJB, or Application Client project, +you must select the <tm tmclass="ibm" tmowner="IBM Corporation" tmtype="reg" +trademark="WebSphere">WebSphere</tm> run-time environment for your client.</li> +</ul></info></substep> +</substeps> +</step> +<step><cmd>Web Service Selection page: Enter the URI to the WSDL, WSIL, or +HTML file that will be used to generate the client. You can optionally generate +a WSIL file from this file as well.</cmd></step> +<step><cmd>Web Service Proxy page: This panel shows the options for the proxy. +It lists the folder where the proxy will be generated, and you can optionally +create custom mappings between namespaces and packages.</cmd></step> +<step><cmd>Web Service Namespace to Package Mappings page: if you selected + <uicontrol>Define custom mapping for namespace to package</uicontrol> on +the previous page, you can enter your custom mapping pairs on this page by +clicking <uicontrol>Add</uicontrol>.</cmd></step> +<step><cmd>Web Service Client Test page: 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 <tm tmclass="ibm" tmowner="IBM Corporation" tmtype="reg" +trademark="WebSphere">WebSphere</tm> servers.</cmd></step> +<step><cmd>Click <uicontrol>Finish</uicontrol>. If you have selected to test +the proxy, the test client will open in a browser window.</cmd></step> +</steps> +<result><p>The generated <tm tmclass="special" tmowner="Sun Microsystems, Inc." +tmtype="tm" trademark="Java">Java</tm> 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 <tm tmclass="special" +tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> 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: <codeph>http://localhost: <varname>port</varname>/ <varname>WebProject</varname>Client/sample<i +>BeanName</i>/ <varname>WebServiceName</varname>/TestClient.jsp</codeph> You +can use this sample application to test the Web service by selecting a method, +entering a value for the method, and clicking <uicontrol>Invoke</uicontrol>. +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: <systemoutput>http://localhost:9080/UTC/preload?object= <varname>BeanPackage</varname +>. <varname>BeanServiceProxy</varname></systemoutput>. In the Reference pane, +under Object References, expand the proxy stub to display the methods of the +Web service. Click the method you want to test, enter a value in the Parameters +pane, and click <uicontrol>Invoke</uicontrol>. The result will be generated +below.</li> +<li>If you have selected to test the Web service using the Web Services Explorer, +the Explorer will open. Select the operation you want to test, enter the required +information, and click <b>Go</b>. The result will display in the Status pane.</li> +</ul><p>For more information on creating a Web project, refer to the Web application +development documentation.</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> +</linklist> +<linklist><title>Related Tasks</title> +<link href="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.dita" +scope="peer"><linktext> Using the Web Services Explorer</linktext></link> +</linklist> +<linklist><title>Related Reference</title> +<link href="../../org.eclipse.jst.ws.doc.user/ref/rwsdl.dita" scope="peer"> +<linktext>WSDL documents</linktext></link> +</linklist> +</related-links> +</task> diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsampappa.html b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsampappa.html index 4b46a739a..b8abc009f 100644 --- a/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsampappa.html +++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsampappa.html @@ -1,139 +1,156 @@ -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<?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> -<!-- /******************************************************************************* - * 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" /> - +<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 Java client proxy and a sample application from a WSDL document using the Axis run-time environment" /> +<meta name="abstract" content="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." /> +<meta name="description" content="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." /> +<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="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.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="tsampappa" 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 Java client proxy and a sample application from a WSDL document using the Axis run-time environment</title> </head> <body id="tsampappa"><a name="tsampappa"><!-- --></a> + <h1 class="topictitle1">Generating a Java client proxy and a sample application from a WSDL document using the Axis run-time environment</h1> -<div><p>The Web Service Client wizard assists you in generating a Java™ bean + + + +<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"><p>Prerequisites:</p> -<ol><li>If you are using the Apache Jakarta Tomcat servlet +<ol> +<li>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="ttomcatserv.html">Creating an Apache Tomcat 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">To generate a Java client proxy and a sample application from a discovered WSDL document:</div> -<ol><li><span>Switch to the J2EE perspective (<span class="uicontrol">Window > Open Perspective + +<ol> +<li><span>Switch to the J2EE perspective (<span class="uicontrol">Window > Open Perspective > J2EE</span>).</span></li> + <li><span>In the Navigator 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> +Select the <span class="uicontrol">Web Service Client</span> wizard. Click <span class="uicontrol">Next</span>.</span> +</li> + <li><span>Web Services page: 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 +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 Apache Axis run-time environment and select the server on which you want to run your Web service client.</span></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 +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 run-time clients -is a Web project.</li> + +<li>Note that the only project type supported for Axis 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<sup>®</sup> run-time environment for your client.</li> + </ul> </li> + </ol> + </li> + <li><span>Web Service Selection page: Enter the URI to the WSDL, WSIL, or HTML file that will be used to generate the client. You can optionally generate a WSIL file from this file as well.</span></li> + <li><span>Web Service Proxy page: This panel shows the options for the proxy. It lists the folder where the proxy will be generated, and you can optionally create custom mappings between namespaces and packages.</span></li> + <li><span>Web Service Namespace to Package Mappings page: if you selected <span class="uicontrol">Define custom mapping for namespace to package</span> on the previous page, you can enter your custom mapping pairs on this page by clicking <span class="uicontrol">Add</span>.</span></li> + <li><span>Web Service Client Test page: Select the test facility that you will use to test the proxy, and the methods that you want included in the -proxy.</span></li> +proxy. Note that the Universal Test Client (UTC) is only compatible with Web +service clients deployed on WebSphere servers.</span></li> + <li><span>Click <span class="uicontrol">Finish</span>. If you have selected to test the proxy, the test client will open in a browser window.</span></li> + </ol> + <div class="section"><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, +<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>/ <var class="varname">WebProject</var>Client/sample<em>BeanName</em>/ <var class="varname">WebServiceName</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: <tt class="sysout">http://localhost:9080/UTC/preload?object= <var class="varname">BeanPackage</var>. <var class="varname">BeanServiceProxy</var></tt>. In the Reference pane, under Object References, expand the proxy stub 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> + <li>If you have selected to test the Web service using the Web Services Explorer, the Explorer will open. Select the operation you want to test, enter the required information, and click <strong>Go</strong>. The result will display in the Status pane.</li> + </ul> <p>For more information on creating a Web project, refer to the Web application development documentation.</p> -</div><p> <span class="uicontrol">Note:</span> -<ul> -<li>You may encounter the following error when running the Web Service client wizard: -<br> -<samp> -IWAB0399E Error in generating Java from WSDL java.io.IOException: WSDL2Java -emitter timed out (this often means the WSDL at the specified URL is -inaccessible)!</samp> -<br> -You might be accessing a WSDL file that requires a timeout setting of more than -the default 45 seconds (for example, trying to access a large WSDL file or a -WSDL file on a slow machine). You could change the timeout value for the Axis -WSDL to Java emitter by starting the Eclipse workbench with the -<samp>AxisWsdl2JavaTimeout</samp> virtual machine argument. The timeout value is -specified in milliseconds. Use a timeout value of <samp>-1</samp> if you want the emitter to never -time out. -<br> -For example, to set the timeout to 60 seconds, use the following command to -start the Eclipse workbench: -<br> -<samp>eclipse -vmargs "-DAxisWsdl2JavaTimeout=60000"</samp> -</li> -</ul> -</p> </div> -<div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/caxistover.html" title="This run-time environment is for users who prefer to develop for the open Apache Axis platform. It is for non-production use only. Axis is the third generation of the Apache SOAP implementation. It evolved from Apache SOAP (which began at IBM as SOAP4J) to make the SOAP engine more flexible, configurable, and able to handle both SOAP and the upcoming XML Protocol specification from the W3C open-source effort.">Creating Web services with the Apache Axis run-time environment</a></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><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 /> diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsklwsdla.dita b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsklwsdla.dita new file mode 100644 index 000000000..8f17b9057 --- /dev/null +++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsklwsdla.dita @@ -0,0 +1,151 @@ +<?xml version="1.0" encoding="utf-8"?> +<!--Arbortext, Inc., 1988-2005, v.4002--> +<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" + "../../dtd/task.dtd"> +<task id="tsklwsdla" xml:lang="en-us"> +<title>Creating a <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" +trademark="Java">Java</tm> bean skeleton from a WSDL document using the Apache +Axis run-time environment</title> +<titlealts> +<searchtitle>Creating a Java bean skeleton from a WSDL document using the +Apache Axis run-time environment</searchtitle> +</titlealts> +<shortdesc>The Web service wizard assists you in creating a skeleton bean +from an existing WSDL document. The skeleton bean contains a set of methods +that correspond to the operations described in the WSDL document. When the +bean is created, each method has a trivial implementation that you replace +by editing the bean.</shortdesc> +<taskbody> +<prereq><p>Prerequisites:</p><ol> +<li id="createtomcatlink">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 <xref href="ttomcatserv.dita" +scope="local">Creating an Apache Tomcat server and Web project</xref></li> +<li>Create or import a WSDL file into the Web Content folder of the Web project. +You can only use a WSDL file that contains a service element.</li> +</ol></prereq> +<context>To create a Web service from a WSDL file using the Apache Axis 1.0 +run-time environment:</context> +<steps> +<step><cmd>Switch to the J2EE perspective (<uicontrol>Window > Open Perspective +> J2EE</uicontrol>).</cmd></step> +<step><cmd>In the Project Explorer view, select the WSDL file that you created +or imported into the Web Content folder of your Web project.</cmd></step> +<step><cmd>Click <uicontrol>File > New > Other</uicontrol>. Select <uicontrol>Web +Services</uicontrol> in order to display the various Web service wizards. +Select the <uicontrol>Web Service</uicontrol> wizard. Click <uicontrol>Next</uicontrol>.</cmd> +</step> +<step><cmd>Web Services page: select <uicontrol>Top down Java bean Web service</uicontrol> as +your Web service type. You can optionally choose to do the following: </cmd> +<info conref="twsbeana.dita#twsbeana/createstep4ul"></info></step> +<step><cmd>Web Service Selection page: Enter the URI to the WSDL, WSIL, or +HTML file that will be used to generate the <tm tmclass="special" tmowner="Sun Microsystems, Inc." +tmtype="tm" trademark="Java">Java</tm> bean. If you have selected the WSDL +file before starting the wizard, this information should be prefilled. You +can optionally generate a WSIL file from this file as well.</cmd><info> Ensure +that there are no spaces at the beginning of the URI or you may generate a +null pointer exception.</info></step> +<step><cmd>Service Deployment Configuration page: specify the server and client +deployment settings.</cmd> +<substeps> +<substep><cmd>Click <uicontrol>Edit</uicontrol> and select the Apache Axis +run-time environment and select the server on which you want to run your Web +service and Web service client.</cmd></substep> +<substep><cmd>Select the Web project in which you want your Web service created. </cmd> +<info>The wizard will create this for you if they do not already exist.</info> +</substep> +<substep><cmd>Select the type and name of project in which you want the Web +service client created. If you enter the name of an existing project, the +project type field must match that of the existing project. If you enter a +name of a project that does not already exist, the wizard will create the +project for you. Note that the only project type supported for Axis clients +is a Web project. If you want the client to be created in a <tm tmclass="special" +tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm>, EJB, +or Application Client project, you must select the <tm tmclass="ibm" tmowner="IBM Corporation" +tmtype="reg" trademark="WebSphere">WebSphere</tm> run-time environment for +your client.</cmd></substep> +</substeps> +</step> +<step><cmd>Web Services Skeleton <tm tmclass="special" tmowner="Sun Microsystems, Inc." +tmtype="tm" trademark="Java">Java</tm> Bean Configuration page: Select the +folder where the generated <tm tmclass="special" tmowner="Sun Microsystems, Inc." +tmtype="tm" trademark="Java">Java</tm> will be stored. If you want to review +or edit the mappings between packages and namespaces, select the <uicontrol>Define +custom mapping for namespace to package</uicontrol> check box. Click <uicontrol>Next</uicontrol>.</cmd> +</step> +<step><cmd>Web Service Namespace to Package Mappings page: if you selected + <uicontrol>Define custom mapping for package to namespace</uicontrol> on +the previous panel, you can enter your custom mapping pairs on this panel +by clicking <uicontrol>Add.</uicontrol> Click <uicontrol>Next</uicontrol>.</cmd> +</step> +<step><cmd>Web Service Test page: If you selected to test the Web service, +select the test facility for the generated Web service. This will open the +Web service in the Web Services Explorer. Select the operation you want to +test, enter the required information, and click <uicontrol>Go</uicontrol>. +The result will display in the Status pane. Click <uicontrol>Next</uicontrol>.</cmd> +</step> +<step><cmd>Web Service Proxy page: If you have selected to generate a proxy, +this page shows the options for the proxy. It lists the folder where the proxy +will be generated, and you can optionally create custom mappings between namespaces +and packages. Click <uicontrol>Next</uicontrol>.</cmd></step> +<step><cmd>Web Service Client Test page: Use this page to select the following +options: </cmd> +<substeps> +<substep><cmd>Select your test facility. You can test the generated proxy +in the Universal Test Client or the Web Service Explorer, or you can generate +a sample Web service JSP.</cmd></substep> +<substep><cmd>If you selected to test the proxy through a JSP, you can select +the folder where the JSP will be located, and you can select the methods that +will be included in the JSP.</cmd></substep> +<substep><cmd>Select <uicontrol>Run test on server</uicontrol> to start the +server for you automatically.</cmd></substep> +</substeps> +</step> +<step><cmd>Web Service Publication page: If you have selected to publish your +Web service to a UDDI registry, use this page to launch the Web Services Explorer +and select the UDDI registry to which the Web service will be published. Click + <uicontrol>Finish</uicontrol>.</cmd></step> +</steps> +<result>After the Web service has been created, the following may occur depending +on the options you selected: <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: <codeph>http://localhost: <varname>port</varname>/ <varname>WebProject</varname>Client/sample<i +>BeanName</i>/<varname>WebServiceName</varname>/TestClient.jsp</codeph> You +can use this sample application to test the Web service by selecting a method, +entering a value for the method, and clicking <uicontrol>Invoke</uicontrol>. +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: <systemoutput>http://localhost:9080/UTC/preload?object= <varname>BeanPackage</varname +>. <varname>BeanServiceProxy</varname></systemoutput>. In the Reference pane, +under Object References, expand the proxy stub to display the methods of the +Web service. Click the method you want to test, enter a value in the Parameters +pane, and click <uicontrol>Invoke</uicontrol>. The result will be generated +below.</li> +<li>If you have selected to test the Web service using the Web Services Explorer, +the Explorer will open. Select the operation you want to test, enter the required +information, and click <b>Go</b>. The result will display in the Status pane.</li> +<li>If you have selected to publish the Web service, the Web Services Explorer +is launched displaying the page required to publish your Web service. Follow +the instructions in <varname>Publishing the Web service</varname> to complete +this task.</li> +</ul></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> +</linklist> +<linklist><title>Related Tasks</title> +<link href="../../org.eclipse.jst.ws.doc.user/tasks/toverws.dita" scope="peer"> +<linktext> Developing Web services</linktext></link> +<link href="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.dita" +scope="peer"><linktext> Using the Web Services Explorer</linktext></link> +</linklist> +<linklist><title>Related Reference</title> +<link href="../../org.eclipse.jst.ws.doc.user/ref/rwsdl.dita" scope="peer"> +<linktext>WSDL documents</linktext></link> +</linklist> +</related-links> +</task> diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsklwsdla.html b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsklwsdla.html index 18fa575e7..c640d9c32 100644 --- a/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsklwsdla.html +++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsklwsdla.html @@ -1,173 +1,209 @@ -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<?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> -<!-- /******************************************************************************* - * 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" /> - +<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="Creating a Java bean skeleton from a WSDL document using the Apache Axis run-time environment" /> +<meta name="abstract" content="The Web service wizard assists you in creating a skeleton bean from an existing WSDL document. The skeleton bean contains a set of methods that correspond to the operations described in the WSDL document. When the bean is created, each method has a trivial implementation that you replace by editing the bean." /> +<meta name="description" content="The Web service wizard assists you in creating a skeleton bean from an existing WSDL document. The skeleton bean contains a set of methods that correspond to the operations described in the WSDL document. When the bean is created, each method has a trivial implementation that you replace by editing the bean." /> +<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="../../org.eclipse.jst.ws.doc.user/tasks/toverws.html" /> +<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.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="tsklwsdla" 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>Creating a Java bean skeleton from a WSDL document using the Apache Axis run-time environment</title> </head> <body id="tsklwsdla"><a name="tsklwsdla"><!-- --></a> + <h1 class="topictitle1">Creating a Java bean skeleton from a WSDL document using the Apache Axis run-time environment</h1> + + + <div><p>The Web service wizard assists you in creating a skeleton bean from an existing WSDL document. The skeleton bean contains a set of methods that correspond to the operations described in the WSDL document. When the bean is created, each method has a trivial implementation that you replace by editing the bean.</p> + <div class="p"><p>Prerequisites:</p> -<ol><li id="tsklwsdla__createtomcatlink"><a name="tsklwsdla__createtomcatlink"><!-- --></a>If you are using the Apache Jakarta Tomcat servlet +<ol> +<li id="tsklwsdla__createtomcatlink"><a name="tsklwsdla__createtomcatlink"><!-- --></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="ttomcatserv.html">Creating an Apache Tomcat server and Web project</a></li> + <li>Create or import a WSDL file into the Web Content folder of the Web project. You can only use a WSDL file that contains a service element.</li> + </ol> </div> + <div class="section">To create a Web service from a WSDL file using the Apache Axis 1.0 run-time environment:</div> -<ol><li class="stepexpand"><span>Switch to the J2EE perspective (<span class="uicontrol">Window > Open Perspective + +<ol> +<li class="stepexpand"><span>Switch to the J2EE perspective (<span class="uicontrol">Window > Open Perspective > J2EE</span>).</span></li> + <li class="stepexpand"><span>In the Project Explorer view, select the WSDL file that you created or imported into the Web Content folder of your Web project.</span></li> + <li class="stepexpand"><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</span> wizard. Click <span class="uicontrol">Next</span>.</span></li> +Select the <span class="uicontrol">Web Service</span> wizard. Click <span class="uicontrol">Next</span>.</span> +</li> + <li class="stepexpand"><span>Web Services page: select <span class="uicontrol">Top down Java bean Web service</span> as -your Web service type. You can optionally choose to do the following: </span> <ul><li>Start the Web service in a Web project - if you do not select this option +your Web service type. You can optionally choose to do the following: </span> + <ul> +<li>Start the Web service in a Web project - if you do not select this option you will have to manually start the Web service. You must select this option to enable the other options on this page.</li> + <li>Launch the Web Services Explorer to publish your Web service to a UDDI registry.</li> -<li>Generate a Java™ bean client proxy to the Web service. The Java bean + +<li>Generate a Javaâ„¢ bean client proxy to the Web service. The Java bean client proxy that is generated provides a remote procedure call interface to the Web service.</li> + <li>Test the Web service - this allows you to test the Web service in the Web Service Explorer before a proxy is generated.</li> + <li>Send the Web service traffic through the TCP/IP Monitor, which allows you to watch the SOAP traffic generated by the Web service and to test this traffic for WS-I compliance. Note that this is only supported for Tomcat v4.0 and v4.1. If you are using Tomcat v5.0 and want to monitor the Web service -traffic, you need to manually set up a TCP/IP monitor as described in <a href="../../org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.html">Using -the TCP/IP Monitor to test Web services</a></li> +traffic, you need to manually set up a TCP/IP monitor as described in <a href="../../org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.html">Using the TCP/IP Monitor to test Web services</a></li> + </ul> </li> + <li class="stepexpand"><span>Web Service Selection page: Enter the URI to the WSDL, WSIL, or HTML file that will be used to generate the Java bean. If you have selected the WSDL file before starting the wizard, this information should be prefilled. You can optionally generate a WSIL file from this file as well.</span> Ensure that there are no spaces at the beginning of the URI or you may generate a null pointer exception.</li> + <li class="stepexpand"><span>Service Deployment Configuration page: specify the server and client -deployment settings.</span><ol type="a"><li class="substepexpand"><span>Click <span class="uicontrol">Edit</span> and select the Apache Axis +deployment settings.</span> +<ol type="a"> +<li class="substepexpand"><span>Click <span class="uicontrol">Edit</span> and select the Apache Axis run-time environment and select the server on which you want to run your Web service and Web service client.</span></li> -<li class="substepexpand"><span>Select the Web project in which you want your Web service created. </span> The wizard will create this for you if they do not already exist.</li> + +<li class="substepexpand"><span>Select the Web project in which you want your Web service created. </span> + The wizard will create this for you if they do not already exist. +</li> + <li class="substepexpand"><span>Select the type and name of project in which you want the Web service client created. If you enter the name of an existing project, the project type field must match that of the existing project. If you enter a name of a project that does not already exist, the wizard will create the -project for you. Note that the only project type supported for Axis run-time clients is a Web project.</span></li> +project for you. Note that the only project type supported for Axis 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<sup>®</sup> run-time environment for +your client.</span></li> + </ol> + </li> + <li class="stepexpand"><span>Web Services Skeleton Java Bean Configuration page: Select the folder where the generated Java will be stored. If you want to review or edit the mappings between packages and namespaces, select the <span class="uicontrol">Define -custom mapping for namespace to package</span> check box. Click <span class="uicontrol">Next</span>.</span></li> +custom mapping for namespace to package</span> check box. Click <span class="uicontrol">Next</span>.</span> +</li> + <li class="stepexpand"><span>Web Service Namespace to Package Mappings page: if you selected <span class="uicontrol">Define custom mapping for package to namespace</span> on the previous panel, you can enter your custom mapping pairs on this panel -by clicking <span class="uicontrol">Add.</span> Click <span class="uicontrol">Next</span>.</span></li> +by clicking <span class="uicontrol">Add.</span> Click <span class="uicontrol">Next</span>.</span> +</li> + <li class="stepexpand"><span>Web Service Test page: If you selected to test the Web service, select the test facility for the generated Web service. This will open the Web service in the Web Services Explorer. Select the operation you want to test, enter the required information, and click <span class="uicontrol">Go</span>. -The result will display in the Status pane. Click <span class="uicontrol">Next</span>.</span></li> +The result will display in the Status pane. Click <span class="uicontrol">Next</span>.</span> +</li> + <li class="stepexpand"><span>Web Service Proxy page: If you have selected to generate a proxy, this page shows the options for the proxy. It lists the folder where the proxy will be generated, and you can optionally create custom mappings between namespaces and packages. Click <span class="uicontrol">Next</span>.</span></li> + <li class="stepexpand"><span>Web Service Client Test page: Use this page to select the following -options: </span><ol type="a"><li><span>Select your test facility. You can test the generated proxy +options: </span> +<ol type="a"> +<li><span>Select your test facility. You can test the generated proxy in the Universal Test Client or the Web Service Explorer, or you can generate a sample Web service JSP.</span></li> + <li><span>If you selected to test the proxy through a JSP, you can select the folder where the JSP will be located, and you can select the methods that will be included in the JSP.</span></li> + <li><span>Select <span class="uicontrol">Run test on server</span> to start the server for you automatically.</span></li> + </ol> + </li> + <li class="stepexpand"><span>Web Service Publication page: If you have selected to publish your Web service to a UDDI registry, use this page to launch the Web Services Explorer and select the UDDI registry to which the Web service will be published. Click <span class="uicontrol">Finish</span>.</span></li> + </ol> + <div class="section">After the Web service has been created, the following may occur depending -on the options you selected: <ul><li>If you have selected to test the generated proxy using Web service JSPs, +on the options you selected: <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>/ <var class="varname">WebProject</var>Client/sample<em>BeanName</em>/<var class="varname">WebServiceName</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: <tt class="sysout">http://localhost:9080/UTC/preload?object= <var class="varname">BeanPackage</var>. <var class="varname">BeanServiceProxy</var></tt>. In the Reference pane, under Object References, expand the proxy stub 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> + <li>If you have selected to test the Web service using the Web Services Explorer, the Explorer will open. Select the operation you want to test, enter the required information, and click <strong>Go</strong>. The result will display in the Status pane.</li> + <li>If you have selected to publish the Web service, the Web Services Explorer -is launched displaying the page required to publish your Web service to the IBM<sup>®</sup> UDDI -Test Registry. Follow the instructions in <var class="varname">Publishing the Web service</var> to -complete this task.</li> -</ul> -</div><p> <span class="uicontrol">Note:</span> -<ul> -<li>You may encounter the following error when running the Web Service wizard: -<br> -<samp> -IWAB0399E Error in generating Java from WSDL java.io.IOException: WSDL2Java -emitter timed out (this often means the WSDL at the specified URL is -inaccessible)!</samp> -<br> -You might be accessing a WSDL file that requires a timeout setting of more than -the default 45 seconds (for example, trying to access a large WSDL file or a -WSDL file on a slow machine). You could change the timeout value for the Axis -WSDL to Java emitter by starting the Eclipse workbench with the -<samp>AxisWsdl2JavaTimeout</samp> virtual machine argument. The timeout value is -specified in milliseconds. Use a timeout value of <samp>-1</samp> if you want the emitter to never -time out. -<br> -For example, to set the timeout to 60 seconds, use the following command to -start the Eclipse workbench: -<br> -<samp>eclipse -vmargs "-DAxisWsdl2JavaTimeout=60000"</samp> -</li> +is launched displaying the page required to publish your Web service. Follow +the instructions in <var class="varname">Publishing the Web service</var> to complete +this task.</li> + </ul> -</p> </div> -<div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/caxistover.html" title="This run-time environment is for users who prefer to develop for the open Apache Axis platform. It is for non-production use only. Axis is the third generation of the Apache SOAP implementation. It evolved from Apache SOAP (which began at IBM as SOAP4J) to make the SOAP engine more flexible, configurable, and able to handle both SOAP and the upcoming XML Protocol specification from the W3C open-source effort.">Creating Web services with the Apache Axis run-time environment</a></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><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 /> diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/ttomcatserv.dita b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/ttomcatserv.dita new file mode 100644 index 000000000..93b3e1748 --- /dev/null +++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/ttomcatserv.dita @@ -0,0 +1,57 @@ +<?xml version="1.0" encoding="utf-8"?> +<!--Arbortext, Inc., 1988-2005, v.4002--> +<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" + "../../dtd/task.dtd"> +<task id="creatinganapachetomcatserver" xml:lang="en-us"> +<title>Creating an Apache Tomcat server and Web project</title> +<shortdesc>If you plan to create a Web service that uses Apache Jakarta Tomcat +as its server, Tomcat must be installed and a server created before you begin +creating your Web service.</shortdesc> +<taskbody> +<prereq>Install Apache Jakarta Tomcat from this URL: <xref href="http://jakarta.apache.org/tomcat" +scope="external">http://jakarta.apache.org/tomcat</xref></prereq> +<context>Once you have installed the server, create a Tomcat server in the +workbench by doing the following: </context> +<steps> +<step><cmd>From the File menu, select <uicontrol>New > Other > Server > Server +> Next</uicontrol>.</cmd></step> +<step><cmd>Select Tomcat v 3.x, 4.x or v5.x<?Pub Caret?> as the server type, +electing the correct version of Tomcat for your install, and click <uicontrol>Next</uicontrol>.</cmd> +</step> +<step><cmd>On the Tomcat server page:</cmd> +<substeps> +<substep><cmd>Enter a server name.</cmd></substep> +<substep><cmd>Specify where Tomcat is installed.</cmd></substep> +<substep><cmd>Click <uicontrol>Installed JREs</uicontrol>, click <uicontrol>Add</uicontrol>, +and enter the appropriate information for the JDK you plan to use for Tomcat. +For example, for Tomcat v5.0 the JRE name would be jdk141 and the JRE home +would be the home directory for JDK 1.4.1. Click <uicontrol>OK</uicontrol> twice +once you have entered this information. Ensure that the newly added JDK is +now selected in the JRE field of the Tomcat server page. Note that if you +point the server at a JRE rather than a JDK the JSPs will not properly compile +and will not be able to run on the Tomcat server.</cmd></substep> +</substeps> +</step> +<step><cmd>Click <uicontrol>Finish</uicontrol>.</cmd><stepresult> To see the +server you have created in the workspace, from the Window menu select <uicontrol>Show +view > Other > Server > Servers > Ok.</uicontrol> </stepresult></step> +</steps> +<example><p>To build a dynamic Web project that points to the Tomcat server +that you have created:</p><ol> +<li>Create the service Web project by selecting <uicontrol>New > Web > Dynamic +Web project</uicontrol>. Enter the following information: <ul> +<li>Web Project: enter a project name</li> +<li>Servlet version: 2.3</li> +<li>Target Server: Tomcat server v3.x, 4.x or 5.x depending on the version +you installed</li> +<li>Ensure that <uicontrol>Add Module to an EAR module</uicontrol> is <i>not</i> selected.</li> +</ul></li> +<li>Click <uicontrol>Finish</uicontrol>.</li> +<li>To associate the project with the server, right-click the Tomcat server +you created in the Server view and select <uicontrol>Add and remove projects</uicontrol>. +Select the service and client projects from the Available projects list and +click <uicontrol>Add</uicontrol>. </li> +</ol></example> +</taskbody> +</task> +<?Pub *0000003035?> diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/ttomcatserv.html b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/ttomcatserv.html index 44204496e..99299b3cd 100644 --- a/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/ttomcatserv.html +++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/ttomcatserv.html @@ -1,36 +1,51 @@ -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<?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> -<!-- /******************************************************************************* - * 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" /> - +<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="Creating an Apache Tomcat server and Web project" /> +<meta name="abstract" content="If you plan to create a Web service that uses Apache Jakarta Tomcat as its server, Tomcat must be installed and a server created before you begin creating your Web service." /> +<meta name="description" content="If you plan to create a Web service that uses Apache Jakarta Tomcat as its server, Tomcat must be installed and a server created before you begin creating your Web service." /> +<meta content="XHTML" name="DC.Format" /> +<meta content="creatinganapachetomcatserver" 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>Creating an Apache Tomcat server and Web project</title> </head> <body id="creatinganapachetomcatserver"><a name="creatinganapachetomcatserver"><!-- --></a> + <h1 class="topictitle1">Creating an Apache Tomcat server and Web project</h1> + + <div><p>If you plan to create a Web service that uses Apache Jakarta Tomcat as its server, Tomcat must be installed and a server created before you begin creating your Web service.</p> + <div class="p">Install Apache Jakarta Tomcat from this URL: <a href="http://jakarta.apache.org/tomcat" target="_blank">http://jakarta.apache.org/tomcat</a></div> + <div class="section">Once you have installed the server, create a Tomcat server in the workbench by doing the following: </div> -<ol><li class="stepexpand"><span>From the File menu, select <span class="uicontrol">New > Other > Server > Server + +<ol> +<li class="stepexpand"><span>From the File menu, select <span class="uicontrol">New > Other > Server > Server > Next</span>.</span></li> -<li class="stepexpand"><span>Select Tomcat v 3.x, 4.x or v5.0 as the server type, electing the -correct version of Tomcat for your install, and click <span class="uicontrol">Next</span>.</span></li> -<li class="stepexpand"><span>On the Tomcat server page:</span><ol type="a"><li><span>Enter a server name.</span></li> + +<li class="stepexpand"><span>Select Tomcat v 3.x, 4.x or v5.x as the server type, +electing the correct version of Tomcat for your install, and click <span class="uicontrol">Next</span>.</span> +</li> + +<li class="stepexpand"><span>On the Tomcat server page:</span> +<ol type="a"> +<li><span>Enter a server name.</span></li> + <li><span>Specify where Tomcat is installed.</span></li> + <li><span>Click <span class="uicontrol">Installed JREs</span>, click <span class="uicontrol">Add</span>, and enter the appropriate information for the JDK you plan to use for Tomcat. For example, for Tomcat v5.0 the JRE name would be jdk141 and the JRE home @@ -39,31 +54,46 @@ once you have entered this information. Ensure that the newly added JDK is now selected in the JRE field of the Tomcat server page. Note that if you point the server at a JRE rather than a JDK the JSPs will not properly compile and will not be able to run on the Tomcat server.</span></li> + </ol> + </li> + <li class="stepexpand"><span>Click <span class="uicontrol">Finish</span>.</span> To see the server you have created in the workspace, from the Window menu select <span class="uicontrol">Show view > Other > Server > Servers > Ok.</span> </li> + </ol> + <div class="example"><p>To build a dynamic Web project that points to the Tomcat server that you have created:</p> -<ol><li>Create the service Web project by selecting <span class="uicontrol">New > Web > Dynamic -Web project</span>. Enter the following information: <ul><li>Web Project: enter a project name</li> +<ol> +<li>Create the service Web project by selecting <span class="uicontrol">New > Web > Dynamic +Web project</span>. Enter the following information: <ul> +<li>Web Project: enter a project name</li> + <li>Servlet version: 2.3</li> + <li>Target Server: Tomcat server v3.x, 4.x or 5.x depending on the version you installed</li> + <li>Ensure that <span class="uicontrol">Add Module to an EAR module</span> is <em>not</em> selected.</li> + </ul> </li> + <li>Click <span class="uicontrol">Finish</span>.</li> + <li>To associate the project with the server, right-click the Tomcat server you created in the Server view and select <span class="uicontrol">Add and remove projects</span>. Select the service and client projects from the Available projects list and click <span class="uicontrol">Add</span>. </li> + </ol> </div> + </div> -<div></div> + </body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/twsbeana.dita b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/twsbeana.dita new file mode 100644 index 000000000..ef2cbebc0 --- /dev/null +++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/twsbeana.dita @@ -0,0 +1,181 @@ +<?xml version="1.0" encoding="utf-8"?> +<!--Arbortext, Inc., 1988-2005, v.4002--> +<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" + "../../dtd/task.dtd"> +<task id="twsbeana" xml:lang="en-us"> +<title>Creating a Web service from a <tm tmclass="special" tmowner="Sun Microsystems, Inc." +tmtype="tm" trademark="Java">Java</tm> bean using the Apache Axis run-time +environment</title> +<titlealts> +<searchtitle>Creating a Web service from a Java bean using the Apache Axis +run-time environment</searchtitle> +</titlealts> +<shortdesc>The Web Service wizard assists you in creating a new Web service, +configuring it for deployment, and deploying the Web service to a server. +Once your Web service is deployed, the wizard assists you in generating the +client proxy and sample application to test the Web service. When you have +completed testing, you can publish your Web service to a UDDI Business Registry +using the Export wizard.</shortdesc> +<taskbody> +<prereq><p>Prerequisites:<ol> +<li conref="tsklwsdla.dita#tsklwsdla/createtomcatlink"></li> +<li>Create or import a bean into the <tm tmclass="special" tmowner="Sun Microsystems, Inc." +tmtype="tm" trademark="Java">Java</tm> source folder of the Web project.</li> +</ol></p></prereq> +<context>To create a Web service from a bean using the Apache Axis run-time +environment:</context> +<steps> +<step><cmd>Switch to the J2EE perspective ( <uicontrol>Window > Open Perspective +> J2EE</uicontrol>).</cmd></step> +<step><cmd>In the Project Explorer view, select the bean that you created +or imported into the source folder of your Web project.</cmd></step> +<step><cmd>Click <uicontrol>File > New > Other</uicontrol>.</cmd><info>Select<uicontrol>Web +Services</uicontrol> in order to display the various Web service wizards. +Select the <uicontrol>Web Service</uicontrol> wizard. Click <uicontrol>Next</uicontrol>.</info> +</step> +<step><cmd>Web Services page: select <uicontrol>Bottom up Java bean Web service</uicontrol> as +your Web service type. You can optionally choose to do the following: </cmd> +<info id="createstep4ul"><ul> +<li>Start the Web service in a Web project - if you do not select this option +you will have to manually start the Web service. You must select this option +to enable the other options on this page.</li> +<li>Launch the Web Services Explorer to publish your Web service to a UDDI +registry.</li> +<li>Generate a <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" +trademark="Java">Java</tm> bean client proxy to the Web service. The <tm tmclass="special" +tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> bean +client proxy that is generated provides a remote procedure call interface +to the Web service.</li> +<li>Test the Web service - this allows you to test the Web service in the +Web Service Explorer before a proxy is generated.</li> +<li>Send the Web service traffic through the TCP/IP Monitor, which allows +you to watch the SOAP traffic generated by the Web service and to test this +traffic for WS-I compliance. Note that this is only supported for Tomcat v4.0 +and v4.1. If you are using Tomcat v5.0 and want to monitor the Web service +traffic, you need to manually set up a TCP/IP monitor as described in <xref +href="../../org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.dita" scope="peer">Using +the TCP/IP Monitor to test Web services</xref></li> +</ul></info></step> +<step><cmd>Object selection page: select the <tm tmclass="special" tmowner="Sun Microsystems, Inc." +tmtype="tm" trademark="Java">Java</tm> bean from which the Web service will +be created.</cmd></step> +<step><cmd>Service Deployment Configuration page: specify the server and client +deployment settings.</cmd> +<substeps> +<substep><cmd>Click <uicontrol>Edit</uicontrol> and select the Apache Axis +run-time environment and select the server on which you want to run your Web +service and Web service client.</cmd></substep> +<substep><cmd>Select the Web project in which you want your Web service created, +and the EAR with which it will be associated. </cmd><info>The wizard will +create these for you if they do not already exist.</info></substep> +<substep><cmd>Select the type and name of project in which you want the Web +service client created. If you enter the name of an existing project, the +project type field must match that of the existing project. If you enter a +name of a project that does not already exist, the wizard will create the +project for you. Note that the only project type supported for Axis clients +is a Web project. If you want the client to be created in a <tm tmclass="special" +tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm>, EJB, +or Application Client project, you must select the <tm tmclass="ibm" tmowner="IBM Corporation" +tmtype="reg" trademark="WebSphere">WebSphere</tm> run-time environment for +your client.</cmd></substep> +<substep><cmd>Select an existing EAR or enter a unique name to associate the +Web service client with a different EAR than the Web service EAR. <b>Note:</b> 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.</cmd> +</substep> +</substeps> +</step> +<step><cmd>A message will display stating that you have made a WS-I non-compliant +selection.</cmd><info>The Apache Axis run-time environment is not WS-I compliant. +Select <uicontrol>Ignore</uicontrol>.</info></step> +<step><cmd>Web Service <tm tmclass="special" tmowner="Sun Microsystems, Inc." +tmtype="tm" trademark="Java">Java</tm> Bean Identity page: the Web service +URI and WSDL name will be listed.</cmd><info>You have the following +options:<ul> +<li>Select the methods to expose.</li> +<li>Select the encoding style. RPC/Encoded is the recommended encoding style +for the Axis run-time environment. This encoding method is not WS-I compliant.</li> +<li>Select if you want to customize the package to namespace mappings.</li> +</ul>Click <uicontrol>Next</uicontrol></info></step> +<step><cmd>Web Service Package to Namespace Mappings page: if you selected + <uicontrol>Define custom mapping for package to namespace</uicontrol> on +the previous panel, you can enter your custom mapping pairs on this panel +by clicking <uicontrol>Add</uicontrol>.</cmd></step> +<step><cmd>Web Service Test page: If you selected to test the Web service, +select the test facility for the generated Web service.</cmd><info>This will +open the Web service in the Web Services Explorer. Select the operation you +want to test, enter the required information, and click<uicontrol>Go</uicontrol>. +The result will display in the Status pane. Click <uicontrol>Next</uicontrol>.</info> +</step> +<step><cmd>Web Service Proxy page: if you have selected to generate a proxy, +select if you want to customize the package to namespace mappings.</cmd></step> +<step><cmd>Web Service Client Test page: Use this page to select the following +options: </cmd> +<substeps> +<substep><cmd>Select your test facility. You can test the generated proxy +in the Universal Test Client or the Web Service Explorer, or you can generate +a sample Web service JSP.</cmd></substep> +<substep><cmd>If you selected to test the proxy through a JSP, you can select +the folder where the JSP will be located, and you can select the methods that +will be included in the JSP.</cmd></substep> +<substep><cmd>Select <uicontrol>Run test on server</uicontrol> to start the +server for you automatically.</cmd></substep> +</substeps> +</step> +<step><cmd>Web Service Publication page: Select whether or not you want to +publish this Web service to a UDDI registry. Click <uicontrol>Finish</uicontrol>. </cmd> +<info>Note: you may see a warning stating <codeph>Error in generating WSDL +from Java. ClassNotFound: <bean name></codeph>. This error can be safely +ignored.</info></step> +</steps> +<result><p>After the Web service has been created, the following may occur +depending on the options you selected: <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: http://localhost: <varname>port</varname>/ <varname>WebProject</varname>Client/sample<i +>BeanName</i>/ <varname>WebServiceName</varname>/TestClient.jsp You can use +this sample application to test the Web service by selecting a method, entering +a value for the method, and clicking <uicontrol>Invoke</uicontrol>. 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: <systemoutput>http://localhost:9080/UTC/preload?object= <varname>BeanPackage</varname +>. <varname>BeanServiceProxy</varname></systemoutput>. In the Reference pane, +under Object References, expand the proxy stub to display the methods of the +Web service. Click the method you want to test, enter a value in the Parameters +pane, and click <uicontrol>Invoke</uicontrol>. The result will be generated +below.</li> +<li>If you have selected to test the Web service using the Web Services Explorer, +the Explorer will open. Select the operation you want to test, enter the required +information, and click <b>Go</b>. The result will display in the Status pane.</li> +<li>If you have selected to publish the Web service, the Web Services Explorer +is launched displaying the page required to publish your Web service. Follow +the instructions in <varname>Publishing the Web service</varname> to complete +this task.</li> +</ul></p><p> <uicontrol>Important:</uicontrol> If your methods contain types, +not supported by the sample, such as arrays, indexed properties, and collections, +the methods will be omitted from the sample and you will receive a warning +message.</p><p>Once you have created your Web service from a bean, you may +test the methods of your Web service, using the Universal Test Client, and +then publish your Web service to a UDDI Business Registry. For more information +on publishing your Web service using the Web Services Explorer, refer to Publishing +a Web service. For more information on the Universal Test Client, refer +to the Server tools online help.</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> +</linklist> +<linklist><title>Related Tasks</title> +<link href="../../org.eclipse.jst.ws.doc.user/tasks/toverws.dita" scope="peer"> +<linktext> Developing Web services</linktext></link> +<link href="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.dita" +scope="peer"><linktext> Using the Web Services Explorer</linktext></link> +</linklist> +<linklist><title>Related Reference</title> +<link href="../../org.eclipse.jst.ws.doc.user/ref/rwsdl.dita" scope="peer"> +<linktext>WSDL documents</linktext></link> +</linklist> +</related-links> +</task> diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/twsbeana.html b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/twsbeana.html index 379a5f3eb..48634b926 100644 --- a/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/twsbeana.html +++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/twsbeana.html @@ -1,193 +1,231 @@ -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<?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> -<!-- /******************************************************************************* - * 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" /> - +<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="Creating a Web service from a Java bean using the Apache Axis run-time environment" /> +<meta name="abstract" content="The Web Service wizard assists you in creating a new Web service, configuring it for deployment, and deploying the Web service to a server. Once your Web service is deployed, the wizard assists you in generating the client proxy and sample application to test the Web service. When you have completed testing, you can publish your Web service to a UDDI Business Registry using the Export wizard." /> +<meta name="description" content="The Web Service wizard assists you in creating a new Web service, configuring it for deployment, and deploying the Web service to a server. Once your Web service is deployed, the wizard assists you in generating the client proxy and sample application to test the Web service. When you have completed testing, you can publish your Web service to a UDDI Business Registry using the Export wizard." /> +<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="../../org.eclipse.jst.ws.doc.user/tasks/toverws.html" /> +<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.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="twsbeana" 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>Creating a Web service from a Java bean using the Apache Axis run-time environment</title> </head> <body id="twsbeana"><a name="twsbeana"><!-- --></a> + <h1 class="topictitle1">Creating a Web service from a Java bean using the Apache Axis run-time environment</h1> + + + <div><p>The Web Service wizard assists you in creating a new Web service, configuring it for deployment, and deploying the Web service to a server. Once your Web service is deployed, the wizard assists you in generating the client proxy and sample application to test the Web service. When you have completed testing, you can publish your Web service to a UDDI Business Registry using the Export wizard.</p> -<div class="p"><div class="p">Prerequisites:<ol><li>If you are using the Apache Jakarta Tomcat servlet + +<div class="p"><div class="p">Prerequisites:<ol> +<li>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="ttomcatserv.html">Creating an Apache Tomcat server and Web project</a></li> -<li>Create or import a bean into the Java™ source folder of the Web project.</li> + +<li>Create or import a bean into the Javaâ„¢ source folder of the Web project.</li> + </ol> </div> </div> + <div class="section">To create a Web service from a bean using the Apache Axis run-time environment:</div> -<ol><li class="stepexpand"><span>Switch to the J2EE perspective ( <span class="uicontrol">Window > Open Perspective + +<ol> +<li class="stepexpand"><span>Switch to the J2EE perspective ( <span class="uicontrol">Window > Open Perspective > J2EE</span>).</span></li> + <li class="stepexpand"><span>In the Project Explorer view, select the bean that you created or imported into the source folder of your Web project.</span></li> + <li class="stepexpand"><span>Click <span class="uicontrol">File > New > Other</span>.</span> Select<span class="uicontrol">Web Services</span> in order to display the various Web service wizards. -Select the <span class="uicontrol">Web Service</span> wizard. Click <span class="uicontrol">Next</span>.</li> +Select the <span class="uicontrol">Web Service</span> wizard. Click <span class="uicontrol">Next</span>. +</li> + <li class="stepexpand"><span>Web Services page: select <span class="uicontrol">Bottom up Java bean Web service</span> as -your Web service type. You can optionally choose to do the following: </span> <ul><li>Start the Web service in a Web project - if you do not select this option +your Web service type. You can optionally choose to do the following: </span> + <ul> +<li>Start the Web service in a Web project - if you do not select this option you will have to manually start the Web service. You must select this option to enable the other options on this page.</li> + <li>Launch the Web Services Explorer to publish your Web service to a UDDI registry.</li> + <li>Generate a Java bean client proxy to the Web service. The Java bean client proxy that is generated provides a remote procedure call interface to the Web service.</li> + <li>Test the Web service - this allows you to test the Web service in the Web Service Explorer before a proxy is generated.</li> + <li>Send the Web service traffic through the TCP/IP Monitor, which allows you to watch the SOAP traffic generated by the Web service and to test this traffic for WS-I compliance. Note that this is only supported for Tomcat v4.0 and v4.1. If you are using Tomcat v5.0 and want to monitor the Web service -traffic, you need to manually set up a TCP/IP monitor as described in <a href="../../org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.html">Using -the TCP/IP Monitor to test Web services</a></li> +traffic, you need to manually set up a TCP/IP monitor as described in <a href="../../org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.html">Using the TCP/IP Monitor to test Web services</a></li> + </ul> </li> + <li class="stepexpand"><span>Object selection page: select the Java bean from which the Web service will be created.</span></li> + <li class="stepexpand"><span>Service Deployment Configuration page: specify the server and client -deployment settings.</span><ol type="a"><li class="substepexpand"><span>Click <span class="uicontrol">Edit</span> and select the Apache Axis +deployment settings.</span> +<ol type="a"> +<li class="substepexpand"><span>Click <span class="uicontrol">Edit</span> and select the Apache Axis run-time environment and select the server on which you want to run your Web service and Web service client.</span></li> + <li class="substepexpand"><span>Select the Web project in which you want your Web service created, and the EAR with which it will be associated. </span> The wizard will create these for you if they do not already exist.</li> + <li class="substepexpand"><span>Select the type and name of project in which you want the Web service client created. If you enter the name of an existing project, the project type field must match that of the existing project. If you enter a name of a project that does not already exist, the wizard will create the -project for you. Note that the only project type supported for Axis -run-time clients is a Web project.</span></li> +project for you. Note that the only project type supported for Axis 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<sup>®</sup> run-time environment for +your client.</span></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> +of encountering run time errors, but will use more system resources.</span> +</li> + </ol> + </li> + <li class="stepexpand"><span>A message will display stating that you have made a WS-I non-compliant selection.</span> The Apache Axis run-time environment is not WS-I compliant. Select <span class="uicontrol">Ignore</span>.</li> + <li class="stepexpand"><span>Web Service Java Bean Identity page: the Web service -URI and WSDL name will be listed.</span> You have the following -options:<ul><li>Select the methods to expose.</li> +URI and WSDL name will be listed.</span> You have the following +options:<ul> +<li>Select the methods to expose.</li> + <li>Select the encoding style. RPC/Encoded is the recommended encoding style for the Axis run-time environment. This encoding method is not WS-I compliant.</li> + <li>Select if you want to customize the package to namespace mappings.</li> + </ul> Click <span class="uicontrol">Next</span></li> + <li class="stepexpand"><span>Web Service Package to Namespace Mappings page: if you selected <span class="uicontrol">Define custom mapping for package to namespace</span> on the previous panel, you can enter your custom mapping pairs on this panel by clicking <span class="uicontrol">Add</span>.</span></li> + <li class="stepexpand"><span>Web Service Test page: If you selected to test the Web service, select the test facility for the generated Web service.</span> This will open the Web service in the Web Services Explorer. Select the operation you want to test, enter the required information, and click<span class="uicontrol">Go</span>. -The result will display in the Status pane. Click <span class="uicontrol">Next</span>.</li> +The result will display in the Status pane. Click <span class="uicontrol">Next</span>. +</li> + <li class="stepexpand"><span>Web Service Proxy page: if you have selected to generate a proxy, select if you want to customize the package to namespace mappings.</span></li> + <li class="stepexpand"><span>Web Service Client Test page: Use this page to select the following -options: </span><ol type="a"><li><span>Select your test facility. You can test the generated proxy +options: </span> +<ol type="a"> +<li><span>Select your test facility. You can test the generated proxy in the Universal Test Client or the Web Service Explorer, or you can generate a sample Web service JSP.</span></li> + <li><span>If you selected to test the proxy through a JSP, you can select the folder where the JSP will be located, and you can select the methods that will be included in the JSP.</span></li> + <li><span>Select <span class="uicontrol">Run test on server</span> to start the server for you automatically.</span></li> + </ol> + </li> + <li class="stepexpand"><span>Web Service Publication page: Select whether or not you want to -publish this Web service to a UDDI registry. Click <span class="uicontrol">Finish</span>. </span> Note: you may see a warning stating <samp class="codeph">Error in generating WSDL +publish this Web service to a UDDI registry. Click <span class="uicontrol">Finish</span>. </span> + Note: you may see a warning stating <samp class="codeph">Error in generating WSDL from Java. ClassNotFound: <bean name></samp>. This error can be safely ignored.</li> + </ol> + <div class="section"><div class="p">After the Web service has been created, the following may occur -depending on the options you selected: <ul><li>If you have selected to test the generated proxy using Web service JSPs, +depending on the options you selected: <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: http://localhost: <var class="varname">port</var>/ <var class="varname">WebProject</var>Client/sample<em>BeanName</em>/ <var class="varname">WebServiceName</var>/TestClient.jsp 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: <tt class="sysout">http://localhost:9080/UTC/preload?object= <var class="varname">BeanPackage</var>. <var class="varname">BeanServiceProxy</var></tt>. In the Reference pane, under Object References, expand the proxy stub 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> + <li>If you have selected to test the Web service using the Web Services Explorer, the Explorer will open. Select the operation you want to test, enter the required information, and click <strong>Go</strong>. The result will display in the Status pane.</li> + <li>If you have selected to publish the Web service, the Web Services Explorer -is launched displaying the page required to publish your Web service to the IBM<sup>®</sup> UDDI -Test Registry. Follow the instructions in <var class="varname">Publishing the Web service</var> to -complete this task.</li> +is launched displaying the page required to publish your Web service. Follow +the instructions in <var class="varname">Publishing the Web service</var> to complete +this task.</li> + </ul> </div> -<p> <span class="uicontrol">Note:</span> -<ul> -<li>If your methods contain types, +<p> <span class="uicontrol">Important:</span> If your methods contain types, not supported by the sample, such as arrays, indexed properties, and collections, the methods will be omitted from the sample and you will receive a warning -message.</li> -<li>You may encounter the following error when running the Web Service wizard: -<br> -<samp> -IWAB0399E Error in generating Java from WSDL java.io.IOException: WSDL2Java -emitter timed out (this often means the WSDL at the specified URL is -inaccessible)!</samp> -<br> -You might be accessing a WSDL file that requires a timeout setting of more than -the default 45 seconds (for example, trying to access a large WSDL file or a -WSDL file on a slow machine). You could change the timeout value for the Axis -WSDL to Java emitter by starting the Eclipse workbench with the -<samp>AxisWsdl2JavaTimeout</samp> virtual machine argument. The timeout value is -specified in milliseconds. Use a timeout value of <samp>-1</samp> if you want the emitter to never -time out. -<br> -For example, to set the timeout to 60 seconds, use the following command to -start the Eclipse workbench: -<br> -<samp>eclipse -vmargs "-DAxisWsdl2JavaTimeout=60000"</samp> -</li> -</ul> -</p> +message.</p> <p>Once you have created your Web service from a bean, you may test the methods of your Web service, using the Universal Test Client, and then publish your Web service to a UDDI Business Registry. For more information on publishing your Web service using the Web Services Explorer, refer to Publishing -a Web service. For more information on the Universal Test Client, refer +a Web service. For more information on the Universal Test Client, refer to the Server tools online help.</p> </div> -</div> -<div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/caxistover.html" title="This run-time environment is for users who prefer to develop for the open Apache Axis platform. It is for non-production use only. Axis is the third generation of the Apache SOAP implementation. It evolved from Apache SOAP (which began at IBM as SOAP4J) to make the SOAP engine more flexible, configurable, and able to handle both SOAP and the upcoming XML Protocol specification from the W3C open-source effort.">Creating Web services with the Apache Axis run-time environment</a></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><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 /> @@ -198,5 +236,6 @@ to the Server tools online help.</p> <div><a href="../../org.eclipse.jst.ws.doc.user/ref/rwsdl.html">WSDL documents</a></div></div> </div> + </body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/wsaxisbuild_toc.ditamap b/docs/org.eclipse.jst.ws.axis.ui.doc.user/wsaxisbuild_toc.ditamap new file mode 100644 index 000000000..3c8683006 --- /dev/null +++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/wsaxisbuild_toc.ditamap @@ -0,0 +1,16 @@ +<?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/wscreationt1_toc.ditamap#wsaxis" +id="wsaxis" title="wsaxis"> +<topicref href="concepts/caxistover.dita" navtitle="Axis runtime" toc="no"> +<topicref href="tasks/twsbeana.dita" navtitle="Creating a Web service from a Java bean"> +</topicref> +<topicref href="tasks/tsklwsdla.dita" navtitle="Creating a Java Skeleton from WSDL"> +</topicref> +<topicref href="tasks/tsampappa.dita" navtitle="Generating a Java client proxy from a WSDL document"> +</topicref> +</topicref> +<topicref href="tasks/ttomcatserv.dita" navtitle="Installing and configuring Apache Tomcat"> +</topicref> +</map> diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/wsaxisbuild_toc.xml b/docs/org.eclipse.jst.ws.axis.ui.doc.user/wsaxisbuild_toc.xml index c3ec062ab..13dfd7891 100644 --- a/docs/org.eclipse.jst.ws.axis.ui.doc.user/wsaxisbuild_toc.xml +++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/wsaxisbuild_toc.xml @@ -1,15 +1,7 @@ -<?xml version="1.0" encoding="utf-8"?> -<?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 - *******************************************************************************/ --> -<toc label="wsaxis" > - <topic label="Creating an Apache Tomcat server and Web project" href="tasks/ttomcatserv.html"/> -</toc>
\ No newline at end of file +<?xml version="1.0" encoding="UTF-8"?> + +<?NLS TYPE="org.eclipse.help.toc"?> + +<toc link_to="../org.eclipse.jst.ws.doc.user/wscreationt1_toc.xml#wsaxis" label="wsaxis" topic="concepts/caxistover.html"> +<topic label="Creating an Apache Tomcat server and Web project" href="tasks/ttomcatserv.html"/> +</toc> diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/.cvsignore b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/.cvsignore index 9dcb2662b..c9d32abd5 100644 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/.cvsignore +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/.cvsignore @@ -1,2 +1,3 @@ -build.xml 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/build.xml b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/build.xml new file mode 100644 index 000000000..ae96a16ad --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/build.xml @@ -0,0 +1,59 @@ +<?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 new file mode 100644 index 000000000..49df34fa1 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cuddi.dita @@ -0,0 +1,88 @@ +<?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 index c54c1cbe7..33969e148 100644 --- 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 @@ -1,37 +1,54 @@ -<?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"> +<?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" /> +<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 + +<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 @@ -41,8 +58,8 @@ your business entity with a UDDI registry.</p> 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 +<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 @@ -55,20 +72,22 @@ 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>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>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 @@ -76,23 +95,25 @@ 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><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> +<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 new file mode 100644 index 000000000..729ea84cc --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cwsdlud.dita @@ -0,0 +1,106 @@ +<?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 index d42cda3f4..577a6edde 100644 --- 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 @@ -1,59 +1,84 @@ -<?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"> +<?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" /> +<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 + +<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 + +<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 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>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. @@ -63,21 +88,26 @@ 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 and WebSphere run-time environments do not have imports. -A service implementation document can contain references to more than one -service interface document.</p> +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. @@ -86,22 +116,27 @@ 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 and WebSphere run-time -environments do not have imports.</p> +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 /> @@ -113,5 +148,6 @@ defined within a service element.</p> <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/beaninfojsp.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/beaninfojsp.gif Binary files differnew file mode 100644 index 000000000..3cbe40c48 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/beaninfojsp.gif 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 differnew file mode 100644 index 000000000..d84a5bb8e --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/browsebutton.gif 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 differnew file mode 100644 index 000000000..237bdd27a --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/login.gif 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 differnew file mode 100644 index 000000000..2f4b50972 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/newjsp.gif 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 differnew file mode 100644 index 000000000..652e4ead9 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/proxyonjsp.gif 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 differnew file mode 100644 index 000000000..6e884d28d --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/runjsf.gif 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 differnew file mode 100644 index 000000000..d5edaebd5 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/soapudws.cdr 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 differnew file mode 100644 index 000000000..2352f01f5 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddi.cdr 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 differnew file mode 100644 index 000000000..e8da32a90 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddiref.cdr 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 differnew file mode 100644 index 000000000..ef54568c0 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdldetail.gif 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 differnew file mode 100644 index 000000000..537c1c071 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlpage.gif 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 differnew file mode 100644 index 000000000..8949098a9 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdluddi.cdr 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 differnew file mode 100644 index 000000000..b5e6e03ee --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsilpage.gif 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 differnew file mode 100644 index 000000000..0e5d5f004 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsinjsp.gif 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 new file mode 100644 index 000000000..248e72b65 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/myplugin.xml @@ -0,0 +1,20 @@ +<?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 new file mode 100644 index 000000000..aec04b0c6 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/org.eclipse.jst.ws.consumption.ui.doc.user.maplist @@ -0,0 +1,10 @@ +<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/ref/ruddi.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/ref/ruddi.dita new file mode 100644 index 000000000..1d63add1d --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/ref/ruddi.dita @@ -0,0 +1,73 @@ +<?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 index 0e8a157d7..f6ad7be7c 100644 --- 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 @@ -1,31 +1,38 @@ -<?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"> +<?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" /> +<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 @@ -66,6 +73,7 @@ different Entity-Service-Template parents, as seen in Figure 2.</p> 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 @@ -74,6 +82,7 @@ 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 @@ -83,12 +92,10 @@ This means that any changes made to the businessService by any of the referencin businessEntity structures are valid for all of the referencing businessEntity structures.</p> </div> -</div> -<div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/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> +<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> @@ -98,5 +105,6 @@ structures.</p> <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 new file mode 100644 index 000000000..f0689c291 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/taddreg.dita @@ -0,0 +1,72 @@ +<?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 index 87c7d2008..01a8899d7 100644 --- 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 @@ -1,66 +1,96 @@ -<?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"> +<?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" /> +<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 IBM Web Services Explorer</h1> + +<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> + +<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 IBM<sup>®</sup> Web Services Explorer. In order to publish +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 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> +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> + +<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> +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="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <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> <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> @@ -77,5 +107,6 @@ of the registry you want to add.</span></li> <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 new file mode 100644 index 000000000..d64061e65 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tassert.dita @@ -0,0 +1,57 @@ +<?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 index d970c06f9..9a13bacfb 100644 --- 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 @@ -1,25 +1,35 @@ -<?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"> +<?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" /> +<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. @@ -27,35 +37,44 @@ 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> + +<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> + +<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 + +<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="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <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> <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> @@ -72,5 +91,6 @@ business entity.</p> <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 new file mode 100644 index 000000000..d82ec6d5c --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbkmrk.dita @@ -0,0 +1,51 @@ +<?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 index 77d5f2472..27bf2f089 100644 --- 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 @@ -1,55 +1,71 @@ -<?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"> +<?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" /> +<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> + + +<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 + +<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\org.eclipse.webservice.explorer\favorites.wsil</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="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <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> <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> @@ -66,5 +82,6 @@ will be automatically migrated to this location.</p> <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 new file mode 100644 index 000000000..719454c6f --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbusproj.dita @@ -0,0 +1,50 @@ +<?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 index bbd85d072..d24195b34 100644 --- 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 @@ -1,53 +1,71 @@ -<?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"> +<?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" /> +<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> + +<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> + +<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 + +<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="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <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> <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> @@ -64,5 +82,6 @@ maintain services that are referenced by the business entity.</span></li> <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 new file mode 100644 index 000000000..890aaf3b5 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tdiscov.dita @@ -0,0 +1,173 @@ +<?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 index 7b4a71a66..6202e1956 100644 --- 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 @@ -1,152 +1,253 @@ -<?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"> +<?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" /> +<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 IBM Web Services Explorer</a></li> -<li><a href="taddreg.html">Add the registry to the IBM Web Services Explorer</a></li> + +<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>. +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> + +<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></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. + +<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> + +<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 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> +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> +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> +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> +(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> + +<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> +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 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 + +<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> +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> +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 IBM 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> + + <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 /> @@ -164,6 +265,9 @@ have created the project and/or click the <strong>Refresh</strong> icon.</li> <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> +</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 new file mode 100644 index 000000000..c7cc9280c --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tgenwsil.dita @@ -0,0 +1,68 @@ +<?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 index ae282f890..cbbc8e8fa 100644 --- 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 @@ -1,31 +1,37 @@ -<?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"> +<?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" /> +<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 @@ -37,18 +43,23 @@ No copies of the WSDL or WSDL URLs are required.</p> 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="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <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><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 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 + +<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>. @@ -56,24 +67,46 @@ 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> + +<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 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> + +<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>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> + +</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 new file mode 100644 index 000000000..f500682a0 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tlogexp.dita @@ -0,0 +1,50 @@ +<?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 new file mode 100644 index 000000000..fceac20cd --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpubent.dita @@ -0,0 +1,96 @@ +<?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 index dbfe06619..940a4b1c9 100644 --- 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 @@ -1,33 +1,42 @@ -<?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"> +<?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" /> +<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 IBM<sup>®</sup> Web Services Explorer</a></li> -<li><a href="taddreg.html">Add the registry to the IBM Web Services Explorer</a></li> + +<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 @@ -39,60 +48,91 @@ 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="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <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 class="section"><p>To publish a business entity using the simple option:</p> </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 + +<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>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 Web + +<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 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 + +<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 /> @@ -109,6 +149,9 @@ your Web service.</p> <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> +</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 new file mode 100644 index 000000000..8ad83ce67 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpublish.dita @@ -0,0 +1,102 @@ +<?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 index 68fe52807..51519149c 100644 --- 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 @@ -1,66 +1,78 @@ -<?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"> +<?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" /> +<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> + +<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> -<ul class="ullinks"> -<li class="ulchildlink"><strong><a href="../ref/ruddi.html">Data structure types (UDDI registry)</a></strong><br /> -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.</li> -</ul> - -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <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 class="section"><p>To publish a Web service using the simple option:</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 + +<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 @@ -70,31 +82,51 @@ 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 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 + +<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 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 @@ -104,7 +136,9 @@ 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 /> @@ -121,6 +155,9 @@ can now discover and integrate with your Web service.</p> <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> +</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 new file mode 100644 index 000000000..19bffea88 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/treg.dita @@ -0,0 +1,67 @@ +<?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 index 115e4a7e2..6c1a80597 100644 --- 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 @@ -1,54 +1,73 @@ -<?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"> +<?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" /> +<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 +<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 +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 @@ -59,12 +78,10 @@ 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="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <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> <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> @@ -80,5 +97,6 @@ fill in the information required to open a particular registry.</p> <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/tstrtexp.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tstrtexp.dita new file mode 100644 index 000000000..f52b6466f --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tstrtexp.dita @@ -0,0 +1,115 @@ +<?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 index 6fb1de568..4682e8d17 100644 --- 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 @@ -1,51 +1,69 @@ -<?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"> +<?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" /> +<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> + +<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="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <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><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 +<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> +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, + +<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 @@ -53,57 +71,95 @@ on the <strong>Launch</strong> button. If you launch the Web Services Explorer 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 + +<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 + +<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 + +<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 + +<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 + +<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, + +<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 /> @@ -119,6 +175,9 @@ the WSDL in the WSDL page.</p> <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> +</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 new file mode 100644 index 000000000..485718265 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/ttestwsdl.dita @@ -0,0 +1,98 @@ +<?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 index 61132abfe..ab25be26e 100644 --- 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 @@ -1,58 +1,88 @@ -<?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"> +<?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" /> +<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> + +<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 + +<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> +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> +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 @@ -62,10 +92,13 @@ 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 @@ -73,12 +106,16 @@ 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 /> @@ -92,5 +129,6 @@ parameters you have entered to test the service and the returned value. <br /> <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 new file mode 100644 index 000000000..1ac3b8163 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.dita @@ -0,0 +1,126 @@ +<?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 index 8d1148e6d..ddb5d685e 100644 --- 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 @@ -1,28 +1,42 @@ -<?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"> +<?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" /> +<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, @@ -37,8 +51,8 @@ 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 +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, @@ -46,121 +60,109 @@ 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> +<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="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> + +<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> +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> + +<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 + +<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> +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> +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> -<ul class="ullinks"> -<li class="ulchildlink"><strong><a href="../tasks/tstrtexp.html">Launching the Web Services Explorer</a></strong><br /> -The Web services tools allows you to launch the Web Services Explorer -in several ways.</li> -<li class="ulchildlink"><strong><a href="../tasks/treg.html">Registering with a UDDI registry</a></strong><br /> -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.</li> -<li class="ulchildlink"><strong><a href="../tasks/taddreg.html">Adding a Registry to the IBM Web Services Explorer</a></strong><br /> -Although the Web Services Explorer comes populated with several -registries, you can also add additional registries to your list of favorites.</li> -<li class="ulchildlink"><strong><a href="../tasks/tpubent.html">Publishing a business entity</a></strong><br /> -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.</li> -<li class="ulchildlink"><strong><a href="../tasks/tpublish.html">Publishing a Web service</a></strong><br /> -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.</li> -<li class="ulchildlink"><strong><a href="../tasks/tupdate.html">Updating a business entity, Web service, or service interface</a></strong><br /> -After you have published a business entity, Web service, or service -interface, you can update it through the Web Services Explorer.</li> -<li class="ulchildlink"><strong><a href="../tasks/tunpub.html">Removing a business entity, Web service, or service interface from a registry</a></strong><br /> -After you have published a business entity, Web service, or service -interface, you can remove or unpublish it through the Web Services Explorer.</li> -<li class="ulchildlink"><strong><a href="../tasks/tbusproj.html">Managing referenced services</a></strong><br /> -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.</li> -<li class="ulchildlink"><strong><a href="../tasks/tassert.html">Managing publisher assertions</a></strong><br /> -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.</li> -<li class="ulchildlink"><strong><a href="../tasks/tbkmrk.html">Adding a registry, business entity, business service, service interface, WSIL, or WSDL service to Favorites</a></strong><br /> -</li> -<li class="ulchildlink"><strong><a href="../tasks/tgenwsil.html">Generating a WSIL file</a></strong><br /> -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.</li> -</ul> +<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> @@ -171,13 +173,14 @@ the WSDL file for the Web service has been created.</li> <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">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="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 new file mode 100644 index 000000000..7f9097db7 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tunpub.dita @@ -0,0 +1,56 @@ +<?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 index f5587c4c9..81dfe01b2 100644 --- 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 @@ -1,54 +1,80 @@ -<?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"> +<?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" /> +<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> + +<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 IBM<sup>®</sup> Web Services Explorer</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, + +<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>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="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <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> <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> @@ -68,5 +94,6 @@ your change.</p> <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 new file mode 100644 index 000000000..23165cb1e --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tupdate.dita @@ -0,0 +1,51 @@ +<?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 index edb2c8111..183653e5f 100644 --- 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 @@ -1,52 +1,77 @@ -<?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"> +<?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" /> +<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> + +<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, + +<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>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> +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="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <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> <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> @@ -65,5 +90,6 @@ updated with your change.</p> <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/twsdlexp.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdlexp.dita new file mode 100644 index 000000000..646b7e5a1 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdlexp.dita @@ -0,0 +1,138 @@ +<?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 index a07c991db..a54aad962 100644 --- 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 @@ -1,78 +1,135 @@ -<?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"> +<?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" /> +<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 + +<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> +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></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 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> + +<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 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> + +<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: + +<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 + +<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> + +<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 + +<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 @@ -81,13 +138,19 @@ right-click and select <span class="menucascade"><span class="uicontrol">Web Ser 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> +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 @@ -96,20 +159,26 @@ Three types of bindings are supported: SOAP, HTTP Get, and HTTP Post. <br /><i 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> +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 + +<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 /> @@ -120,8 +189,10 @@ isn't resolved.</samp></div> <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><a href="../../org.eclipse.jst.ws.doc.user/tasks/toverws.html"> Developing Web services</a></div></div> </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 new file mode 100644 index 000000000..67238899b --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptionbuild_toc.ditamap @@ -0,0 +1,39 @@ +<?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 index e52d25646..4bd6903db 100644 --- 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 @@ -1,25 +1,26 @@ -<?xml version="1.0" encoding="utf-8"?> -<?NLS TYPE="org.eclipse.help.toc"?> +<?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="Generating a Java client proxy and a sample application from a WSDL document using the IBM SOAP run-time environment" href="tasks/tsampapp.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 label="Generating a WSIL file" href="tasks/tgenwsil.html"/> - </topic> -</toc>
\ No newline at end of file +<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 new file mode 100644 index 000000000..f815f48a6 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptiont_toc.ditamap @@ -0,0 +1,29 @@ +<?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.doc.user/.cvsignore b/docs/org.eclipse.jst.ws.doc.user/.cvsignore index 15518307e..c84496d36 100644 --- a/docs/org.eclipse.jst.ws.doc.user/.cvsignore +++ b/docs/org.eclipse.jst.ws.doc.user/.cvsignore @@ -1,2 +1,3 @@ -build.xml org.eclipse.jst.ws.doc.user_1.0.0.jar +bak +temp diff --git a/docs/org.eclipse.jst.ws.doc.user/build.xml b/docs/org.eclipse.jst.ws.doc.user/build.xml new file mode 100644 index 000000000..ce22ff914 --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/build.xml @@ -0,0 +1,59 @@ +<?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="webservice_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.doc.user/concepts/cjaxrpc.dita b/docs/org.eclipse.jst.ws.doc.user/concepts/cjaxrpc.dita new file mode 100644 index 000000000..537a28c20 --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cjaxrpc.dita @@ -0,0 +1,61 @@ +<?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="cjaxrpc" xml:lang="en-us"><?Pub Caret?> +<title>JAX-RPC</title> +<shortdesc>JAX-RPC stands for <tm tmclass="special" tmowner="Sun Microsystems, Inc." +tmtype="tm" trademark="Java">Java</tm> API for XML-based RPC, also known as +JSR 101. It is a specification that describes <tm tmclass="special" tmowner="Sun Microsystems, Inc." +tmtype="tm" trademark="Java">Java</tm> Application Programming Interfaces +(APIs) and conventions for building Web services and Web service clients that +use remote procedure calls (RPC) and XML. It standardizes the <tm tmclass="special" +tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> to +WSDL and WSDL to <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" +trademark="Java">Java</tm> mappings, and provides the core APIs for developing +Web services and Web service clients on the <tm tmclass="special" tmowner="Sun Microsystems, Inc." +tmtype="tm" trademark="Java">Java</tm> platform. Often used in a distributed +client/server model, an RPC mechanism enables clients to execute procedures +on other systems.</shortdesc> +<conbody> +<p>The current release of JAX-RPC requires the support of SOAP over HTTP for +interoperability purposes. The SOAP specification defines message structure, +encoding rules, and conventions for exchanging information in the RPC programming +model. These calls and responses are transmitted as SOAP messages over HTTP. +In this release, JAX-RPC supports SOAP 1.1 and HTTP 1.1. For more information +on SOAP, refer to <xref href="csoap.dita" scope="local"></xref>.</p> +<p>Although the underlying run-time mechanisms (for example, <tm tmclass="special" +tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> to +WSDL serialization, WSDL to <tm tmclass="special" tmowner="Sun Microsystems, Inc." +tmtype="tm" trademark="Java">Java</tm> deserialization, protocol and transport) +are very complex, the API hides this complexity from the application developer. +On the server side, the developer can provide a Service Endpoint Interface +(SEI); alternately an SEI can be created using the Web services wizrds. An +SEI is an interface written in the <tm tmclass="special" tmowner="Sun Microsystems, Inc." +tmtype="tm" trademark="Java">Java</tm> programming language that specifies +the remote procedures of a Web service. The developer also provides the implementation +of a Web service, in the form of one or more <tm tmclass="special" tmowner="Sun Microsystems, Inc." +tmtype="tm" trademark="Java">Java</tm> classes that implement methods of the +same signature as those on the SEI. Client programs are also easy to code. +A client creates a proxy, a local object representing the service implementation +and the SEI, and then simply invokes methods on the proxy.</p> +<p>JAX-RPC is highly interoperable: a JAX-RPC client can access a Web service +that is not running on the <tm tmclass="special" tmowner="Sun Microsystems, Inc." +tmtype="tm" trademark="Java">Java</tm> platform and vice versa. This flexibility +is possible because JAX-RPC uses SOAP over HTTP, and the Web Service Description +Language (WSDL). JAX-RPC was designed to support WS-I.</p> +<p>For more information on JAX-RPC, refer to the <xref format="html" href="http://www.jcp.org/en/jsr/detail?id=101" +scope="external">official JSR 101 specifications</xref>.</p> +</conbody> +<related-links> +<linklist><title>Related Concepts</title> +<link href="cws.dita"></link> +<link href="cwsinwsa.dita"></link> +<link href="cjsr109.dita"></link> +</linklist> +<linklist><title>Related Tasks</title> +<link href="../tasks/toverws.dita" scope="peer"><linktext> Developing Web +services</linktext></link> +</linklist> +</related-links> +</concept> +<?Pub *0000003863?> diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cjaxrpc.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cjaxrpc.html index 30a692a82..e18d4f28c 100644 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cjaxrpc.html +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cjaxrpc.html @@ -1,25 +1,33 @@ -<?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"> +<?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" /> +<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="JAX-RPC" /> +<meta name="abstract" content="JAX-RPC stands for Java API for XML-based RPC, also known as JSR 101. It is a specification that describes Java Application Programming Interfaces (APIs) and conventions for building Web services and Web service clients that use remote procedure calls (RPC) and XML. It standardizes the Java to WSDL and WSDL to Java mappings, and provides the core APIs for developing Web services and Web service clients on the Java platform. Often used in a distributed client/server model, an RPC mechanism enables clients to execute procedures on other systems." /> +<meta name="description" content="JAX-RPC stands for Java API for XML-based RPC, also known as JSR 101. It is a specification that describes Java Application Programming Interfaces (APIs) and conventions for building Web services and Web service clients that use remote procedure calls (RPC) and XML. It standardizes the Java to WSDL and WSDL to Java mappings, and provides the core APIs for developing Web services and Web service clients on the Java platform. Often used in a distributed client/server model, an RPC mechanism enables clients to execute procedures on other systems." /> +<meta scheme="URI" name="DC.Relation" content="../concepts/cwsstandards.html" /> +<meta scheme="URI" name="DC.Relation" content="cws.html" /> +<meta scheme="URI" name="DC.Relation" content="cwsinwsa.html" /> +<meta scheme="URI" name="DC.Relation" content="cjsr109.html" /> +<meta scheme="URI" name="DC.Relation" content="../tasks/toverws.html" /> +<meta content="XHTML" name="DC.Format" /> +<meta content="cjaxrpc" 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>JAX-RPC</title> </head> <body id="cjaxrpc"><a name="cjaxrpc"><!-- --></a> + <h1 class="topictitle1">JAX-RPC</h1> + + <div><p>JAX-RPC stands for Javaâ„¢ API for XML-based RPC, also known as JSR 101. It is a specification that describes Java Application Programming Interfaces (APIs) and conventions for building Web services and Web service clients that @@ -28,12 +36,14 @@ WSDL and WSDL to Java mappings, and provides the core APIs for developing Web services and Web service clients on the Java platform. Often used in a distributed client/server model, an RPC mechanism enables clients to execute procedures on other systems.</p> + <p>The current release of JAX-RPC requires the support of SOAP over HTTP for interoperability purposes. The SOAP specification defines message structure, encoding rules, and conventions for exchanging information in the RPC programming model. These calls and responses are transmitted as SOAP messages over HTTP. In this release, JAX-RPC supports SOAP 1.1 and HTTP 1.1. For more information -on SOAP, refer to <a href="csoap.html">Simple Object Access Protocol (SOAP)</a>.</p> +on SOAP, refer to <a href="csoap.html" title="SOAP (formerly known as Simple Object Access Protocol) is a lightweight protocol for the exchange of information in a decentralized, distributed environment. A SOAP message is a transmission of information from a sender to a receiver. SOAP messages can be combined to perform request/response patterns. ">SOAP</a>.</p> + <p>Although the underlying run-time mechanisms (for example, Java to WSDL serialization, WSDL to Java deserialization, protocol and transport) are very complex, the API hides this complexity from the application developer. @@ -45,27 +55,32 @@ of a Web service, in the form of one or more Java classes that implement methods same signature as those on the SEI. Client programs are also easy to code. A client creates a proxy, a local object representing the service implementation and the SEI, and then simply invokes methods on the proxy.</p> + <p>JAX-RPC is highly interoperable: a JAX-RPC client can access a Web service that is not running on the Java platform and vice versa. This flexibility is possible because JAX-RPC uses SOAP over HTTP, and the Web Service Description Language (WSDL). JAX-RPC was designed to support WS-I.</p> + <p>For more information on JAX-RPC, refer to the <a href="http://www.jcp.org/en/jsr/detail?id=101" target="_blank">official JSR 101 specifications</a>.</p> + </div> + <div> <div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cwsstandards.html" title="One of the key attributes of Internet standards is that they focus on protocols and not on implementations. The Internet is composed of heterogeneous technologies that successfully interoperate through shared protocols. This prevents individual vendors from imposing a standard on the Internet. Open Source software development plays a crucial role in preserving the interoperability of vendor implementations of standards.">Web services standards</a></div> </div> <div class="linklist"><strong>Related Concepts</strong><br /> <div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> -<div><a href="cwsinwsa.html">Tools for Web services development</a></div> +<div><a href="cwsinwsa.html" title="">Tools for Web services development</a></div> <div><a href="cjsr109.html" title="JSR 109 and JSR 921 (Implementing Enterprise Web Services) define the programming model and run-time architecture to deploy and look up Web services in the J2EE environment; more specifically, in the Web, EJB, and Client Application containers. One of its main goals is to ensure vendors' implementations interoperate.">JSR 109 and JSR 921- Implementing Enterprise Web services</a></div></div> <div class="linklist"><strong>Related Tasks</strong><br /> -<div><a href="../tasks/toverws.html"> Developing -Web services</a></div></div> +<div><a href="../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.doc.user/concepts/cjsr109.dita b/docs/org.eclipse.jst.ws.doc.user/concepts/cjsr109.dita new file mode 100644 index 000000000..0736ad1d9 --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cjsr109.dita @@ -0,0 +1,34 @@ +<?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="cjsr109" xml:lang="en-us"> +<title>JSR 109 and JSR 921- Implementing Enterprise Web services</title> +<shortdesc>JSR 109 and JSR 921 (Implementing Enterprise Web Services) define +the programming model and run-time architecture to deploy and look up Web +services in the J2EE environment; more specifically, in the Web, EJB, and +Client Application containers. One of its main goals is to ensure vendors' +implementations interoperate.</shortdesc> +<conbody> +<p>JSR 109 and JSR 921 build on top of JAX-RPC to cover the use of JAX-RPC +in a J2EE environment, as well as the implementation and deployment of Web +services to a J2EE application server. JSR 109 and JSR 921 define a set of +XML-based deployment descriptors to standardize Web services and Web service +client deployments in the J2EE environment. These tools support JSR 109 for +J2EE 1.3 and JSR 921 for J2EE 1.4.</p> +<p>For more information, refer to: <xref format="html" href="http://www.jcp.org/en/jsr/detail?id=109" +scope="external">JSR 109, "Implementing Enterprise Web Services</xref> and <xref +href="http://www.jcp.org/en/jsr/detail?id=921" scope="external">JSR 921: Implementing +Enterprise Web Services 1.1</xref>.</p> +</conbody> +<related-links> +<linklist><title>Related Concepts</title> +<link href="cws.dita"></link> +<link href="cwsinwsa.dita"></link> +<link href="cjaxrpc.dita"></link> +</linklist> +<linklist><title>Related Tasks</title> +<link href="../tasks/toverws.dita" scope="peer"><linktext> Developing Web +services</linktext></link> +</linklist> +</related-links> +</concept> diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cjsr109.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cjsr109.html index 905f9b65a..9a13e2c02 100644 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cjsr109.html +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cjsr109.html @@ -1,54 +1,66 @@ -<?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"> +<?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" /> +<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="JSR 109 and JSR 921- Implementing Enterprise Web services" /> +<meta name="abstract" content="JSR 109 and JSR 921 (Implementing Enterprise Web Services) define the programming model and run-time architecture to deploy and look up Web services in the J2EE environment; more specifically, in the Web, EJB, and Client Application containers. One of its main goals is to ensure vendors' implementations interoperate." /> +<meta name="description" content="JSR 109 and JSR 921 (Implementing Enterprise Web Services) define the programming model and run-time architecture to deploy and look up Web services in the J2EE environment; more specifically, in the Web, EJB, and Client Application containers. One of its main goals is to ensure vendors' implementations interoperate." /> +<meta scheme="URI" name="DC.Relation" content="../concepts/cwsstandards.html" /> +<meta scheme="URI" name="DC.Relation" content="cws.html" /> +<meta scheme="URI" name="DC.Relation" content="cwsinwsa.html" /> +<meta scheme="URI" name="DC.Relation" content="cjaxrpc.html" /> +<meta scheme="URI" name="DC.Relation" content="../tasks/toverws.html" /> +<meta content="XHTML" name="DC.Format" /> +<meta content="cjsr109" 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>JSR 109 and JSR 921- Implementing Enterprise Web services</title> </head> <body id="cjsr109"><a name="cjsr109"><!-- --></a> + <h1 class="topictitle1">JSR 109 and JSR 921- Implementing Enterprise Web services</h1> + + <div><p>JSR 109 and JSR 921 (Implementing Enterprise Web Services) define the programming model and run-time architecture to deploy and look up Web services in the J2EE environment; more specifically, in the Web, EJB, and Client Application containers. One of its main goals is to ensure vendors' implementations interoperate.</p> + <p>JSR 109 and JSR 921 build on top of JAX-RPC to cover the use of JAX-RPC in a J2EE environment, as well as the implementation and deployment of Web services to a J2EE application server. JSR 109 and JSR 921 define a set of XML-based deployment descriptors to standardize Web services and Web service -client deployments in the J2EE environment. These tools support -JSR 109 for J2EE 1.3 and JSR 921 for J2EE 1.4.</p> -<p>For more information, refer to: <a href="http://www.jcp.org/en/jsr/detail?id=109" target="_blank">JSR 109, "Implementing Enterprise Web Services</a> and <a href="http://www.jcp.org/en/jsr/detail?id=921" target="_blank">JSR 921: Implementing -Enterprise Web Services 1.1</a>.</p> +client deployments in the J2EE environment. These tools support JSR 109 for +J2EE 1.3 and JSR 921 for J2EE 1.4.</p> + +<p>For more information, refer to: <a href="http://www.jcp.org/en/jsr/detail?id=109" target="_blank">JSR 109, "Implementing Enterprise Web Services</a> and <a href="http://www.jcp.org/en/jsr/detail?id=921" target="_blank">JSR 921: Implementing Enterprise Web Services 1.1</a>.</p> + </div> + <div> <div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cwsstandards.html" title="One of the key attributes of Internet standards is that they focus on protocols and not on implementations. The Internet is composed of heterogeneous technologies that successfully interoperate through shared protocols. This prevents individual vendors from imposing a standard on the Internet. Open Source software development plays a crucial role in preserving the interoperability of vendor implementations of standards.">Web services standards</a></div> </div> <div class="linklist"><strong>Related Concepts</strong><br /> <div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> -<div><a href="cwsinwsa.html">Tools for Web services development</a></div> +<div><a href="cwsinwsa.html" title="">Tools for Web services development</a></div> <div><a href="cjaxrpc.html" title="JAX-RPC stands for Java API for XML-based RPC, also known as JSR 101. It is a specification that describes Java Application Programming Interfaces (APIs) and conventions for building Web services and Web service clients that use remote procedure calls (RPC) and XML. It standardizes the Java to WSDL and WSDL to Java mappings, and provides the core APIs for developing Web services and Web service clients on the Java platform. Often used in a distributed client/server model, an RPC mechanism enables clients to execute procedures on other systems.">JAX-RPC</a></div></div> <div class="linklist"><strong>Related Tasks</strong><br /> -<div><a href="../tasks/toverws.html"> Developing -Web services</a></div></div> +<div><a href="../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.doc.user/concepts/csoap.dita b/docs/org.eclipse.jst.ws.doc.user/concepts/csoap.dita new file mode 100644 index 000000000..66b53ce09 --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/csoap.dita @@ -0,0 +1,102 @@ +<?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="csoap" xml:lang="en-us"> +<title>SOAP</title> +<shortdesc>SOAP (formerly known as Simple Object Access Protocol) is a lightweight +protocol for the exchange of information in a decentralized, distributed environment. +A SOAP message is a transmission of information from a sender to a receiver. +SOAP messages can be combined to perform request/response patterns. </shortdesc> +<conbody> +<p>SOAP is transport independent but is most commonly carried over HTTP in +order to run with the existing Internet infrastructure. SOAP enables +the binding and usage of discovered Web services by defining a message path +for routing messages. SOAP is used to query UDDI for Web services. The workbench +supports SOAP 1.1.</p> +<p>SOAP is an XML-based protocol that defines three parts to every message:</p> +<ul> +<li> <uicontrol>Envelope.</uicontrol> The envelope defines a framework +for describing what is in a message and how to process it. A SOAP message +is an envelope containing zero or more headers and exactly one body. +The envelope is the top element of the XML document, providing a container +for control information, the address of a message, and the message itself. +Headers transport any control information such as quality-of-service attributes. +The body contains the message identification and its parameters. Both +the headers and the body are child elements of the envelope.</li> +<li> <uicontrol>Encoding rules.</uicontrol> The set of encoding rules +expresses instances of application-defined data types. Encoding rules define +a serialization mechanism that can be used to exchange instances of application-defined +data types. SOAP defines a programming language-independent data type scheme +based on XSD plus encoding rules for all data types defined according to this +model. SOAP encoding is not WS-I compliant and thus the Literal use (which +is no encoding) is suggested for interoperable Web services and required for +WS-I compliance.</li> +<li> <uicontrol>Communication styles.</uicontrol> Communications can follow +a remote procedure call (RPC) or message-oriented (Document) format. +These are discussed below.</li> +</ul> +<section><title>Binding styles</title><p>SOAP supports two different communication +styles:</p><lq> <p> <uicontrol>Remote procedure call (RPC):</uicontrol> +Invocation of an operation returning a result. Typically used with SOAP encoding, +which is not WS-I compliant.</p><p> <uicontrol>Document Style:</uicontrol> +Also known as document-oriented or message-oriented style. This style +provides a lower layer of abstraction, and requires more programming work.</p> </lq></section> +<section><title>Encoding styles</title><p>In distributed computing environments, +encoding styles define how data values defined in the application can be translated +to and from a particular protocol format. The translation process is +know as serialization and deserialization.</p><p>The SOAP specification defines +the SOAP encoding style:</p><lq> <p> <uicontrol>SOAP encoding:</uicontrol> +The SOAP encoding style allows you to serialize/deserialize values of data +types from the SOAP data model. This encoding style is defined in the +SOAP 1.1 standard, and is not WS-I compliant.</p> </lq><p>WSDL defines the +Literal XML encoding style:</p><lq> <p> <uicontrol>Literal XML:</uicontrol> +Literal refers to the fact that the document should be read as-is, or unencoded. +The document is serialized as XMI, meaning that the message XML complies with +the Schema in the WSDL. When using Literal encoding, each message part references +a concrete schema definition. Literal encoding is WS-I compliant.</p> </lq></section> +<section><title>Data model</title><p>The purpose of the SOAP data model is +to provide a language-independent abstraction for data types used by common +programming language types. It consists of:</p><ul> +<li> <uicontrol>Simple XSD types.</uicontrol> For example int, string, +and date.</li> +<li> <uicontrol>Compound types.</uicontrol> There are two kinds of compound +types, <varname>structs</varname> and <varname>arrays</varname>. Structs +are named aggregate types in which each element has a unique name or XML tag. +Arrays have elements that are identified by position, not by name.</li> +</ul><p>All elements and identifiers comprising the SOAP data model are defined +in the namespace URI. The SOAP standard defines the rules for how data +types can be constructed. A project specific XML schema must define the actual +data types. The elements of the SOAP specification are defined in <xref format="html" +href="http://schemas.xmlsoap.org/soap/envelope/" scope="external">http://schemas.xmlsoap.org/soap/envelope/</xref> and + <xref format="html" href="http://schemas.xmlsoap.org/soap/encoding/" scope="external">http://schemas.xmlsoap.org/soap/encoding/</xref></p></section> +<section><title>SOAP implementations</title><p>Different implementations of +the SOAP protocol are available today. For example, the Apache Foundation +provides Apache SOAP, which grew out of an <tm tmclass="ibm" tmowner="IBM Corporation" +tmtype="reg" trademark="IBM">IBM</tm> project called SOAP4J, as well as Apache +Axis and the <tm tmclass="ibm" tmowner="IBM Corporation" tmtype="reg" trademark="IBM">IBM</tm> <tm +tmclass="ibm" tmowner="IBM Corporation" tmtype="reg" trademark="WebSphere">WebSphere</tm> run-time +environment. The provided Web services tools support Apache SOAP 2.3, Axis +1.0, and <tm tmclass="ibm" tmowner="IBM Corporation" tmtype="reg" trademark="IBM">IBM</tm> <tm +tmclass="ibm" tmowner="IBM Corporation" tmtype="reg" trademark="WebSphere">WebSphere</tm> implementations.</p></section> +<section><title>Mappings</title><p>A mapping defines an association between +a qualified XML element name, a <tm tmclass="special" tmowner="Sun Microsystems, Inc." +tmtype="tm" trademark="Java">Java</tm> class name, and an encoding style. +The mapping specifies how, under the given encoding, an incoming XML element +with a fully qualified name is converted to a <tm tmclass="special" tmowner="Sun Microsystems, Inc." +tmtype="tm" trademark="Java">Java</tm> class and vice versa.</p><p>For more +information on Apache SOAP, refer to <xref format="html" href="http://xml.apache.org/soap" +scope="external">xml.apache.org/soap</xref> For more information on +SOAP refer to <xref format="html" href="http://www.w3.org/TR/SOAP" scope="external">www.w3.org/TR/SOAP</xref> </p></section> +</conbody> +<related-links> +<linklist><title>Related Concepts</title> +<link href="cws.dita"><linktext>Web services overview</linktext></link> +<link href="cwsinwsa.dita"><linktext>Tools for Web services development</linktext> +</link> +</linklist> +<linklist><title>Related Tasks</title> +<link href="../tasks/toverws.dita" scope="peer"><linktext> Developing Web +services</linktext></link> +</linklist> +</related-links> +</concept> diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/csoap.html b/docs/org.eclipse.jst.ws.doc.user/concepts/csoap.html index 1ebc29446..08824f4a6 100644 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/csoap.html +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/csoap.html @@ -1,36 +1,46 @@ -<?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"> +<?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>Simple Object Access Protocol (SOAP)</title> +<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="SOAP" /> +<meta name="abstract" content="SOAP (formerly known as Simple Object Access Protocol) is a lightweight protocol for the exchange of information in a decentralized, distributed environment. A SOAP message is a transmission of information from a sender to a receiver. SOAP messages can be combined to perform request/response patterns." /> +<meta name="description" content="SOAP (formerly known as Simple Object Access Protocol) is a lightweight protocol for the exchange of information in a decentralized, distributed environment. A SOAP message is a transmission of information from a sender to a receiver. SOAP messages can be combined to perform request/response patterns." /> +<meta scheme="URI" name="DC.Relation" content="cws.html" /> +<meta scheme="URI" name="DC.Relation" content="cwsinwsa.html" /> +<meta scheme="URI" name="DC.Relation" content="../tasks/toverws.html" /> +<meta content="XHTML" name="DC.Format" /> +<meta content="csoap" 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>SOAP</title> </head> <body id="csoap"><a name="csoap"><!-- --></a> -<h1 class="topictitle1">Simple Object Access Protocol (SOAP)</h1> -<div><p>SOAP (also known as Simple Object Access Protocol) is a lightweight protocol -for the exchange of information in a decentralized, distributed environment. + +<h1 class="topictitle1">SOAP</h1> + + +<div><p>SOAP (formerly known as Simple Object Access Protocol) is a lightweight +protocol for the exchange of information in a decentralized, distributed environment. A SOAP message is a transmission of information from a sender to a receiver. SOAP messages can be combined to perform request/response patterns. </p> + <p>SOAP is transport independent but is most commonly carried over HTTP in order to run with the existing Internet infrastructure. SOAP enables the binding and usage of discovered Web services by defining a message path -for routing messages. SOAP is used to query UDDI for Web services. This -product supports SOAP 1.1.</p> +for routing messages. SOAP is used to query UDDI for Web services. The workbench +supports SOAP 1.1.</p> + <p>SOAP is an XML-based protocol that defines three parts to every message:</p> -<ul><li> <span class="uicontrol">Envelope.</span> The envelope defines a framework + +<ul> +<li> <span class="uicontrol">Envelope.</span> The envelope defines a framework for describing what is in a message and how to process it. A SOAP message is an envelope containing zero or more headers and exactly one body. The envelope is the top element of the XML document, providing a container @@ -38,6 +48,7 @@ for control information, the address of a message, and the message itself. Headers transport any control information such as quality-of-service attributes. The body contains the message identification and its parameters. Both the headers and the body are child elements of the envelope.</li> + <li> <span class="uicontrol">Encoding rules.</span> The set of encoding rules expresses instances of application-defined data types. Encoding rules define a serialization mechanism that can be used to exchange instances of application-defined @@ -46,10 +57,13 @@ based on XSD plus encoding rules for all data types defined according to this model. SOAP encoding is not WS-I compliant and thus the Literal use (which is no encoding) is suggested for interoperable Web services and required for WS-I compliance.</li> + <li> <span class="uicontrol">Communication styles.</span> Communications can follow a remote procedure call (RPC) or message-oriented (Document) format. These are discussed below.</li> + </ul> + <div class="section"><h4 class="sectiontitle">Binding styles</h4><p>SOAP supports two different communication styles:</p> <blockquote> <p> <span class="uicontrol">Remote procedure call (RPC):</span> @@ -57,10 +71,10 @@ Invocation of an operation returning a result. Typically used with SOAP encoding which is not WS-I compliant.</p> <p> <span class="uicontrol">Document Style:</span> Also known as document-oriented or message-oriented style. This style -provides a lower layer of abstraction, and requires more programming work -if you are using the IBM<sup>®</sup> SOAP or Apache Axis run-time environments.</p> +provides a lower layer of abstraction, and requires more programming work.</p> </blockquote> </div> + <div class="section"><h4 class="sectiontitle">Encoding styles</h4><p>In distributed computing environments, encoding styles define how data values defined in the application can be translated to and from a particular protocol format. The translation process is @@ -81,52 +95,57 @@ the Schema in the WSDL. When using Literal encoding, each message part reference a concrete schema definition. Literal encoding is WS-I compliant.</p> </blockquote> </div> + <div class="section"><h4 class="sectiontitle">Data model</h4><p>The purpose of the SOAP data model is to provide a language-independent abstraction for data types used by common programming language types. It consists of:</p> -<ul><li> <span class="uicontrol">Simple XSD types.</span> For example int, string, +<ul> +<li> <span class="uicontrol">Simple XSD types.</span> For example int, string, and date.</li> + <li> <span class="uicontrol">Compound types.</span> There are two kinds of compound types, <var class="varname">structs</var> and <var class="varname">arrays</var>. Structs are named aggregate types in which each element has a unique name or XML tag. Arrays have elements that are identified by position, not by name.</li> + </ul> <p>All elements and identifiers comprising the SOAP data model are defined in the namespace URI. The SOAP standard defines the rules for how data -types can be constructed. A project specific XML schema must define -the actual data types. The elements of the SOAP specification are defined -in <a href="http://schemas.xmlsoap.org/soap/envelope/" target="_blank">http://schemas.xmlsoap.org/soap/envelope/</a> and +types can be constructed. A project specific XML schema must define the actual +data types. The elements of the SOAP specification are defined in <a href="http://schemas.xmlsoap.org/soap/envelope/" target="_blank">http://schemas.xmlsoap.org/soap/envelope/</a> and <a href="http://schemas.xmlsoap.org/soap/encoding/" target="_blank">http://schemas.xmlsoap.org/soap/encoding/</a></p> </div> + <div class="section"><h4 class="sectiontitle">SOAP implementations</h4><p>Different implementations of the SOAP protocol are available today. For example, the Apache Foundation -provides Apache SOAP, which grew out of an IBM project called SOAP4J, as well as Apache +provides Apache SOAP, which grew out of an IBM<sup>®</sup> project called SOAP4J, as well as Apache Axis and the IBM WebSphere<sup>®</sup> run-time -environment. This release of the Web services tools supports the Axis 1.0 implementation.</p> +environment. The provided Web services tools support Apache SOAP 2.3, Axis +1.0, and IBM WebSphere implementations.</p> </div> + <div class="section"><h4 class="sectiontitle">Mappings</h4><p>A mapping defines an association between a qualified XML element name, a Java™ class name, and an encoding style. The mapping specifies how, under the given encoding, an incoming XML element with a fully qualified name is converted to a Java class and vice versa.</p> <p>For more information on Apache SOAP, refer to <a href="http://xml.apache.org/soap" target="_blank">xml.apache.org/soap</a> For more information on -SOAP refer to <a href="http://www.w3.org/TR/SOAP" target="_blank">www.w3.org/TR/SOAP</a></p> +SOAP refer to <a href="http://www.w3.org/TR/SOAP" target="_blank">www.w3.org/TR/SOAP</a> </p> </div> -</div> -<div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> + </div> +<div> <div class="linklist"><strong>Related Concepts</strong><br /> <div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> -<div><a href="cwsinwsa.html">Tools for Web services development</a></div></div> +<div><a href="cwsinwsa.html" title="">Tools for Web services development</a></div></div> <div class="linklist"><strong>Related Tasks</strong><br /> -<div><a href="../tasks/toverws.html"> Developing -Web services</a></div></div> +<div><a href="../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.doc.user/concepts/cws.dita b/docs/org.eclipse.jst.ws.doc.user/concepts/cws.dita new file mode 100644 index 000000000..b7e681fbd --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cws.dita @@ -0,0 +1,88 @@ +<?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="cws" xml:lang="en-us"> +<title>Web services overview</title> +<shortdesc>A Web service is a set of related application functions that can +be programmatically invoked over the Internet. Businesses can dynamically +mix and match Web services to perform complex transactions with minimal programming. +Web services allow buyers and sellers all over the world to discover each +other, connect dynamically, and execute transactions in real time with minimal +human interaction.</shortdesc> +<conbody> +<p>Web services are self-contained, self-describing modular applications that +can be published, located, and invoked across the Web.</p> +<lq> <p> <uicontrol>Web services are self-contained.</uicontrol> On the client +side, no additional software is required. A programming language with +XML and HTTP client support is enough to get you started. On the server +side, a Web server and servlet engine are required. The client and server +can be implemented in different environments. It is possible to Web +service enable an existing application without writing a single line of code.</p> <p> <uicontrol>Web +services are self-describing.</uicontrol> The client and server need to recognize +only the format and content of request and response messages. The definition +of the message format travels with the message; no external metadata repositories +or code generation tools are required.</p> <p> <uicontrol>Web services are +modular.</uicontrol> Simple Web services can be aggregated to form more complex +Web services either by using workflow techniques or by calling lower layer +Web services from a Web service implementation.</p><p><uicontrol>Web Services +are platform independent.</uicontrol> Web services are based on a concise +set of open, XML-based standards designed to promote interoperability between +a Web service and clients across a variety of computing platforms and programming +languages.</p> </lq> +<p>Web services might be anything, for example, theatre review articles, weather +reports, credit checks, stock quotations, travel advisories, or airline travel +reservation processes. Each of these self-contained business services is an +application that can easily integrate with other services, from the same or +different companies, to create a complete business process. This interoperability +allows businesses to dynamically publish, discover, and bind a range of Web +services through the Internet.</p> +<section><title>Categories of Web services</title><p>Web services can be grouped +into three categories:</p><lq> <p> <uicontrol>Business information.</uicontrol> A +business shares information with consumers or other businesses. In this case, +the business is using Web services to expand its scope. Examples of business +informational Web services are news streams, weather reports, or stock quotations.</p> <p> <uicontrol>Business +integration.</uicontrol> A business provides transactional, "for fee" services +to its customers. In this case, the business becomes part of a global network +of value-added suppliers that can be used to conduct commerce. Examples of +business integration Web services include bid and auction e-marketplaces, +reservation systems, and credit checking.</p> <p> <uicontrol>Business process +externalization.</uicontrol> A business differentiates itself from its competition +through the creation of a global value chain. In this case, the business uses +Web services to dynamically integrate its processes. An example of business +process externalization Web services is the associations between different +companies to combine manufacturing, assembly, wholesale distribution, and +retail sales of a particular product.</p> </lq></section> +<section><title>Service roles and interactions</title><p>A network component +in a Web Services architecture can play one or more fundamental roles: service +provider, service broker, and service client.</p><ul> +<li>Service providers create and deploy their Web services and can publish +the availability of their WSDL-described services through a service registry, +such as a UDDI Business Registry.</li> +<li>Service brokers register and categorize published services and provide +search services. For example, UDDI acts as a service broker for WSDL-described +Web services.</li> +<li>Service clients use broker services such as the UDDI Business Registry +to discover a needed WSDL-described service and then bind to and call the +service provider.</li> +</ul><p>Binding involves establishing all environmental prerequisites that +are necessary to successfully complete the services. Examples of environmental +prerequisites include security, transaction monitoring, and HTTP availability. +The relationships between these roles are described in Figure 1.</p><p>Figure +1. Service roles and interactions.</p><p> <image alt="Figure 1 illustrates the interactions between the service broker, service provider, and service requestor." +href="../images/roles.gif"></image> </p><p>For more information on Web services, +refer to <xref format="html" href="http://www.ibm.com/developerworks/webservices" +scope="external">www..com/developerworks/webservices</xref></p></section> +</conbody> +<related-links> +<linklist><title>Related Concepts</title> +<link href="cwsinwsa.dita"><linktext>Tools for Web services development</linktext> +</link> +<link href="cwsstandards.dita" scope="local"><linktext>Web services standards</linktext> +</link> +</linklist> +<linklist><title>Related Tasks</title> +<link href="../tasks/toverws.dita" scope="local"><linktext> Developing Web +services</linktext></link> +</linklist> +</related-links> +</concept> diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cws.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cws.html index a1d920470..b1bb85c0e 100644 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cws.html +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cws.html @@ -1,54 +1,63 @@ -<?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"> +<?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" /> +<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="Web services overview" /> +<meta name="abstract" content="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction." /> +<meta name="description" content="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction." /> +<meta scheme="URI" name="DC.Relation" content="cwsinwsa.html" /> +<meta scheme="URI" name="DC.Relation" content="cwsstandards.html" /> +<meta scheme="URI" name="DC.Relation" content="../tasks/toverws.html" /> +<meta content="XHTML" name="DC.Format" /> +<meta content="cws" 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>Web services overview</title> </head> <body id="cws"><a name="cws"><!-- --></a> + <h1 class="topictitle1">Web services overview</h1> + + <div><p>A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.</p> + <p>Web services are self-contained, self-describing modular applications that can be published, located, and invoked across the Web.</p> -<blockquote> <p> <span class="uicontrol">Web services are self-contained.</span> On -the client side, no additional software is required. A programming language -with XML and HTTP client support is enough to get you started. On the -server side, a Web server and servlet engine are required. The client -and server can be implemented in different environments. It is possible -to Web service enable an existing application without writing a single line -of code.</p> - <p> <span class="uicontrol">Web services are self-describing.</span> -The client and server need to recognize only the format and content of request -and response messages. The definition of the message format travels -with the message; no external metadata repositories or code generation tools -are required.</p> - <p> <span class="uicontrol">Web services are modular.</span> -Simple Web services can be aggregated to form more complex Web services either -by using workflow techniques or by calling lower layer Web services from a -Web service implementation.</p> -<p><span class="uicontrol">Web Services are platform independent.</span> Web -services are based on a concise set of open, XML-based standards designed -to promote interoperability between a Web service and clients across a variety -of computing platforms and programming languages.</p> + +<blockquote> <p> <span class="uicontrol">Web services are self-contained.</span> On the client +side, no additional software is required. A programming language with +XML and HTTP client support is enough to get you started. On the server +side, a Web server and servlet engine are required. The client and server +can be implemented in different environments. It is possible to Web +service enable an existing application without writing a single line of code.</p> + <p> <span class="uicontrol">Web +services are self-describing.</span> The client and server need to recognize +only the format and content of request and response messages. The definition +of the message format travels with the message; no external metadata repositories +or code generation tools are required.</p> + <p> <span class="uicontrol">Web services are +modular.</span> Simple Web services can be aggregated to form more complex +Web services either by using workflow techniques or by calling lower layer +Web services from a Web service implementation.</p> +<p><span class="uicontrol">Web Services +are platform independent.</span> Web services are based on a concise +set of open, XML-based standards designed to promote interoperability between +a Web service and clients across a variety of computing platforms and programming +languages.</p> </blockquote> + <p>Web services might be anything, for example, theatre review articles, weather reports, credit checks, stock quotations, travel advisories, or airline travel reservation processes. Each of these self-contained business services is an @@ -56,6 +65,7 @@ application that can easily integrate with other services, from the same or different companies, to create a complete business process. This interoperability allows businesses to dynamically publish, discover, and bind a range of Web services through the Internet.</p> + <div class="section"><h4 class="sectiontitle">Categories of Web services</h4><p>Web services can be grouped into three categories:</p> <blockquote> <p> <span class="uicontrol">Business information.</span> A @@ -77,18 +87,23 @@ companies to combine manufacturing, assembly, wholesale distribution, and retail sales of a particular product.</p> </blockquote> </div> + <div class="section"><h4 class="sectiontitle">Service roles and interactions</h4><p>A network component in a Web Services architecture can play one or more fundamental roles: service provider, service broker, and service client.</p> -<ul><li>Service providers create and deploy their Web services and can publish +<ul> +<li>Service providers create and deploy their Web services and can publish the availability of their WSDL-described services through a service registry, such as a UDDI Business Registry.</li> + <li>Service brokers register and categorize published services and provide search services. For example, UDDI acts as a service broker for WSDL-described Web services.</li> + <li>Service clients use broker services such as the UDDI Business Registry to discover a needed WSDL-described service and then bind to and call the service provider.</li> + </ul> <p>Binding involves establishing all environmental prerequisites that are necessary to successfully complete the services. Examples of environmental @@ -97,22 +112,23 @@ The relationships between these roles are described in Figure 1.</p> <p>Figure 1. Service roles and interactions.</p> <p> <img src="../images/roles.gif" alt="Figure 1 illustrates the interactions between the service broker, service provider, and service requestor." /> </p> +<p>For more information on Web services, +refer to <a href="http://www.ibm.com/developerworks/webservices" target="_blank">www..com/developerworks/webservices</a></p> </div> -<p>For more information on Web services, refer to <a href="http://www.ibm.com/developerworks/webservices" target="_blank">www.ibm.com/developerworks/webservices</a></p> - </div> + <div> <div class="linklist"><strong>Related Concepts</strong><br /> -<div><a href="cwsinwsa.html">Tools for Web services development</a></div> -<div><a href="cwsiover.html" title="WS-I is an organization designed to promote Web service interoperability across platforms, operating systems, and programming languages.">Web services -interoperability (WS-I)</a></div></div> +<div><a href="cwsinwsa.html" title="">Tools for Web services development</a></div> +<div><a href="cwsstandards.html" title="One of the key attributes of Internet standards is that they focus on protocols and not on implementations. The Internet is composed of heterogeneous technologies that successfully interoperate through shared protocols. This prevents individual vendors from imposing a standard on the Internet. Open Source software development plays a crucial role in preserving the interoperability of vendor implementations of standards.">Web services standards</a></div></div> <div class="linklist"><strong>Related Tasks</strong><br /> -<div><a href="../tasks/toverws.html" title="Use Web services tools to discover, create, and publish Web services that are created from Java beans, DADX files, enterprise beans, WSDL files, and URLs. The Rational Developer products support the creation of Web services using a top-down approach (which starts with a WSDL file) or a bottom-up approach (which starts with a Java bean or EJB)."> Developing Web +<div><a href="../tasks/toverws.html" title="Use Web services tools to discover, create, and publish Web services that are created from Java beans, enterprise beans, and WSDL files. You can create of Web services using a top-down approach (which starts with a WSDL file) or a bottom-up approach (which starts with a Java bean or EJB)."> Developing Web services</a></div></div> </div> + </body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsbtmup.dita b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsbtmup.dita new file mode 100644 index 000000000..a7a19ea43 --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsbtmup.dita @@ -0,0 +1,33 @@ +<?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="creatingbottom-upwebservices" xml:lang="en-us"><?Pub Caret?> +<title>Creating bottom-up Web services</title> +<shortdesc>Web services can be created using two methods: top-down development +and bottom-up development. Bottom-up Web services development involves creating +a Web service from a <tm tmclass="special" tmowner="Sun Microsystems, Inc." +tmtype="tm" trademark="Java">Java</tm> bean or enterprise bean.</shortdesc> +<conbody> +<p>Although bottom-up Web service development may be faster and easier, especially +if you are new to Web services, the top-down approach is the recommended way +of creating a Web service.</p> +<p>When creating a Web service using a bottom-up approach, first you create +a <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> bean +or EJB bean and then use the Web services wizard to create the WSDL file and +Web service.</p> +</conbody> +<related-links> +<linklist><title>Related Concepts</title> +<link href="cws.dita"><linktext>Web services overview</linktext></link> +<link href="cwsinwsa.dita"><linktext>Tools for Web services development</linktext> +</link> +<link href="cwstopdown.dita" scope="local"><linktext>Creating top-down Web +services</linktext></link> +</linklist> +<linklist><title>Related Tasks</title> +<link href="../tasks/toverws.dita" scope="local"><linktext> Developing Web +services</linktext></link> +</linklist> +</related-links> +</concept> +<?Pub *0000001612?> diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsbtmup.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsbtmup.html index ecef71fec..16b3596be 100644 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsbtmup.html +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsbtmup.html @@ -1,46 +1,60 @@ -<?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"> +<?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" /> +<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="Creating bottom-up Web services" /> +<meta name="abstract" content="Web services can be created using two methods: top-down development and bottom-up development. Bottom-up Web services development involves creating a Web service from a Java bean or enterprise bean." /> +<meta name="description" content="Web services can be created using two methods: top-down development and bottom-up development. Bottom-up Web services development involves creating a Web service from a Java bean or enterprise bean." /> +<meta scheme="URI" name="DC.Relation" content="cws.html" /> +<meta scheme="URI" name="DC.Relation" content="cwsinwsa.html" /> +<meta scheme="URI" name="DC.Relation" content="cwstopdown.html" /> +<meta scheme="URI" name="DC.Relation" content="../tasks/toverws.html" /> +<meta content="XHTML" name="DC.Format" /> +<meta content="creatingbottom-upwebservices" 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>Creating bottom-up Web services</title> </head> <body id="creatingbottom-upwebservices"><a name="creatingbottom-upwebservices"><!-- --></a> + <h1 class="topictitle1">Creating bottom-up Web services</h1> + + <div><p>Web services can be created using two methods: top-down development and bottom-up development. Bottom-up Web services development involves creating a Web service from a Javaâ„¢ bean or enterprise bean.</p> + <p>Although bottom-up Web service development may be faster and easier, especially if you are new to Web services, the top-down approach is the recommended way of creating a Web service.</p> + <p>When creating a Web service using a bottom-up approach, first you create a Java bean or EJB bean and then use the Web services wizard to create the WSDL file and Web service.</p> -</div> -<div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="/tasks/toverws.html">Creating Web services</a></div> + </div> +<div> <div class="linklist"><strong>Related Concepts</strong><br /> <div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> -<div><a href="cwsinwsa.html">Tools for Web services development</a></div> +<div><a href="cwsinwsa.html" title="">Tools for Web services development</a></div> <div><a href="cwstopdown.html" title="Web services can be created using two methods: top-down development and bottom-up development. Top-down Web services development involves creating a Web service from a WSDL file.">Creating top-down Web services</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="../tasks/toverws.html" title="Use Web services tools to discover, create, and publish Web services that are created from Java beans, enterprise beans, and WSDL files. You can create of Web services using a top-down approach (which starts with a WSDL file) or a bottom-up approach (which starts with a Java bean or EJB)."> Developing Web +services</a></div></div> +</div> + </body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsdl.dita b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsdl.dita new file mode 100644 index 000000000..750fc1022 --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsdl.dita @@ -0,0 +1,70 @@ +<?xml version="1.0" encoding="utf-8"?> +<!--Arbortext, Inc., 1988-2005, v.4002--> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<?Pub Inc?> +<concept id="cwsdl" xml:lang="en-us"><?Pub Caret?> +<title>Web Services Description Language (WSDL)</title> +<shortdesc>Web Services Description Language (WSDL) is a standard specification +for describing networked, XML-based services. It provides a simple way for +service providers to describe the basic format of requests to their systems +regardless of the underlying run-time implementation.</shortdesc> +<conbody> +<p>WSDL defines an XML format for describing network services as a set of + <varname>endpoints</varname> that operate on messages that contain either +document-oriented or procedure-oriented information. The operations and messages +are first described abstractly and then bound to a concrete network protocol +and message format in order to define an endpoint. Related concrete endpoints +are combined into abstract endpoints (services). WSDL is extensible to allow +description of endpoints and their messages, regardless of which message formats +or network protocols are used to communicate. This means that interfaces are +defined abstractly using XML schema and then bound to concrete representations +that are appropriate for the protocol.</p> +<p>WSDL allows a service provider to specify the following characteristics +of a Web service:</p> +<ul> +<li>The name of the Web service and addressing information</li> +<li>The protocol and encoding style to be used when accessing the public operations +of the Web service</li> +<li>The type information such as operations, parameters, and data types comprising +the interface of the Web service</li> +</ul> +<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.</p> +<p>This development platform supports and encourages the development and use +of WS-I compliant WSDL. Business service providers can deploy <tm tmclass="special" +tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> beans +and enterprise beans as a Web service and generate a WSDL document that describes +the service. They can also generate <tm tmclass="special" tmowner="Sun Microsystems, Inc." +tmtype="tm" trademark="Java">Java</tm> and enterprise bean skeletons from +an existing WSDL file. A business service client can generate a <tm tmclass="special" +tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> proxy +from a WSDL document, thereby providing an easy-to-use <tm tmclass="special" +tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> interface +to the Web service. The <tm tmclass="special" tmowner="Sun Microsystems, Inc." +tmtype="tm" trademark="Java">Java</tm> interface hides the network communications +details from the client enabling the business service provider to focus on +business and process portions of the application.</p> +<p>In addition to providing tools to create Web services, the workbench provides +a WSDL editor that allows you to create WSDL files using a graphical interface, +a WSDL validator that ensures that your WSDL file is semantically correct +and optionally checks for WS-I compliance, and the Web Services Explorer which +allows you to dynamically test Web services without requiring you to generate +a proxy.</p> +<p>The workbench supports WSDL 1.1. For more information on the WSDL specification, +refer to <xref format="html" href="http://www.w3.org/TR/wsdl" scope="external">www.w3.org/TR/wsdl</xref></p> +</conbody> +<related-links> +<linklist><title>Related Concepts</title> +<link href="cws.dita"><linktext>Web services overview</linktext></link> +<link href="cwsinwsa.dita"><linktext>Tools for Web services development</linktext> +</link> +</linklist> +<linklist><title>Related Tasks</title> +<link href="../tasks/toverws.dita" scope="peer"><linktext> Developing Web +services</linktext></link> +</linklist> +</related-links> +</concept> +<?Pub *0000004138?> diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsdl.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsdl.html index 52ede93c5..463c6abed 100644 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsdl.html +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsdl.html @@ -1,29 +1,36 @@ -<?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"> +<?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" /> +<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="Web Services Description Language (WSDL)" /> +<meta name="abstract" content="Web Services Description Language (WSDL) is a standard specification for describing networked, XML-based services. It provides a simple way for service providers to describe the basic format of requests to their systems regardless of the underlying run-time implementation." /> +<meta name="description" content="Web Services Description Language (WSDL) is a standard specification for describing networked, XML-based services. It provides a simple way for service providers to describe the basic format of requests to their systems regardless of the underlying run-time implementation." /> +<meta scheme="URI" name="DC.Relation" content="cws.html" /> +<meta scheme="URI" name="DC.Relation" content="cwsinwsa.html" /> +<meta scheme="URI" name="DC.Relation" content="../tasks/toverws.html" /> +<meta content="XHTML" name="DC.Format" /> +<meta content="cwsdl" 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>Web Services Description Language (WSDL)</title> </head> <body id="cwsdl"><a name="cwsdl"><!-- --></a> + <h1 class="topictitle1">Web Services Description Language (WSDL)</h1> + + <div><p>Web Services Description Language (WSDL) is a standard specification for describing networked, XML-based services. It provides a simple way for service providers to describe the basic format of requests to their systems regardless of the underlying run-time implementation.</p> + <p>WSDL defines an XML format for describing network services as a set of <var class="varname">endpoints</var> that operate on messages that contain either document-oriented or procedure-oriented information. The operations and messages @@ -34,61 +41,59 @@ description of endpoints and their messages, regardless of which message formats or network protocols are used to communicate. This means that interfaces are defined abstractly using XML schema and then bound to concrete representations that are appropriate for the protocol.</p> + <p>WSDL allows a service provider to specify the following characteristics of a Web service:</p> -<ul><li>The name of the Web service and addressing information</li> + +<ul> +<li>The name of the Web service and addressing information</li> + <li>The protocol and encoding style to be used when accessing the public operations of the Web service</li> + <li>The type information such as operations, parameters, and data types comprising the interface of the Web service</li> + </ul> + <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.</p> -<p>This product supports and encourages the development and use of WS-I compliant -WSDL. Using Rational Developer -products a business service provider can deploy Javaâ„¢ beans and enterprise beans, DADX-described -queries and remote procedures, or existing URLs as a Web service and generate -a WSDL document that describes the service. They can also generate Java and -enterprise bean skeletons from an existing WSDL file. A business service client -can generate a Java proxy from a WSDL document, thereby providing an -easy-to-use Java interface to the Web service. The Java interface -hides the network communications details from the client enabling the business -service provider to focus on business and process portions of the application.</p> -<p>In addition to providing tools to create Web services, -you are also provided with a WSDL editor that allows you to create WSDL files using -a graphical interface, a WSDL validator that ensures that your WSDL file is -semantically correct and optionally checks for WS-I compliance, and the Web -Services Explorer which allows you to dynamically test Web services without -requiring you to generate a proxy.</p> -<p>This product supports WSDL 1.1. For more information on the WSDL specification, + +<p>This development platform supports and encourages the development and use +of WS-I compliant WSDL. Business service providers can deploy Javaâ„¢ beans +and enterprise beans as a Web service and generate a WSDL document that describes +the service. They can also generate Java and enterprise bean skeletons from +an existing WSDL file. A business service client can generate a Java proxy +from a WSDL document, thereby providing an easy-to-use Java interface +to the Web service. The Java interface hides the network communications +details from the client enabling the business service provider to focus on +business and process portions of the application.</p> + +<p>In addition to providing tools to create Web services, the workbench provides +a WSDL editor that allows you to create WSDL files using a graphical interface, +a WSDL validator that ensures that your WSDL file is semantically correct +and optionally checks for WS-I compliance, and the Web Services Explorer which +allows you to dynamically test Web services without requiring you to generate +a proxy.</p> + +<p>The workbench supports WSDL 1.1. For more information on the WSDL specification, refer to <a href="http://www.w3.org/TR/wsdl" target="_blank">www.w3.org/TR/wsdl</a></p> -</div> -<div> -<ul class="ullinks"> -<li class="ulchildlink"><strong><a href="../ref/rwsdl.html">Web Services Description Language (WSDL) reference</a></strong><br /> -A WSDL document defines services as collections of network endpoints, -or ports. In WSDL, the abstract definition of endpoints and messages is separated -from their concrete network deployment or data format bindings. This allows -the reuse of abstract definitions: messages, which are abstract descriptions -of the data being exchanged, and port types which are abstract collections -of operations. </li> -</ul> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> </div> +<div> <div class="linklist"><strong>Related Concepts</strong><br /> <div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> -<div><a href="cwsinwsa.html">Tools for Web services development</a></div></div> +<div><a href="cwsinwsa.html" title="">Tools for Web services development</a></div></div> <div class="linklist"><strong>Related Tasks</strong><br /> <div><a href="../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.doc.user/concepts/cwsil.dita b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsil.dita new file mode 100644 index 000000000..f9bf93009 --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsil.dita @@ -0,0 +1,79 @@ +<?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="cwsil" xml:lang="en-us"> +<title>Web Services Inspection Language (WSIL)</title> +<shortdesc>Web Services Inspection Language (WSIL) is a service discovery +mechanism that is an alternative to UDDI as well as complementary to UDDI. +When you discover Web services with UDDI, you go to a centralized registry. +WSIL is an alternative approach to Web service discovery. WSIL allows +you to go directly to the service provider and ask for the services it provides.</shortdesc> +<conbody> +<p><tm tmclass="ibm" tmowner="IBM Corporation" tmtype="reg" trademark="IBM">IBM</tm> and +Microsoft's proposal for the WSIL specification is designed around an XML-based +model for building an aggregation of references to existing Web service descriptions, +that are exposed using standard Web server technology.</p> +<p>WSIL provides 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.</p> +<p>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. A separate topic +in this documentation discusses the <xref href="cwsilud.dita">Relationship +between UDDI and WSIL</xref>.</p> +<p>The WSIL specification does not define a service description language. +WSIL documents provide a method for aggregating different types of service +descriptions. Within a WSIL document, a single service can have more +than one reference to a service description. For example, a single Web +service might be referenced twice in a WSIL document: once directly via its +WSDL, and again via its businessService entry in a UDDI registry. References +to these two service descriptions should be put into a WSIL document. +If multiple references are available, it is beneficial to put all of them +in the WSIL document so that the application that uses the document can select +the type of service description that is compatible with and preferred by that +application.</p> +<p>The WSIL specification serves two primary functions:</p> +<ul> +<li>WSIL defines an XML format for listing references to existing service +descriptions. These service descriptions can be defined in any format, such +as WSDL, UDDI, or plain HTML. A WSIL document is generally made available +at the point-of-offering for the services that are referenced within the document. +A WSIL document can contain a list of references to service descriptions, +as well as references to other WSIL documents. <p>The ability to link a WSIL +document to one or more different WSIL documents allows you to manage service +description references by grouping them into different documents and to build +a hierarchy of WSIL documents. For example, separate WSIL documents +can be created for different categories of services, and one primary WSIL +document can link all of them together.</p></li> +<li>WSIL defines a set of conventions so that it is easy to locate other WSIL +documents. The WSIL specification does not limit the type of service descriptions +that can be referenced. The WSIL specification defines a set of standard +extensibility elements for both WSDL and UDDI. The WSIL specification +is the definition of locations where you can access WSIL documents.</li> +<li> Two conventions make the location and retrieval of WSIL documents easy: <ul> +<li> <uicontrol>Fixed-name WSIL documents.</uicontrol> The fixed name for +WSIL documents is inspection.wsil. The inspection.wsil file is placed +at common entry points for a Web site. For example, if the common entry +point is http://entrypoint.com then the location of the WSIL document would +be http://entrypoint.com/inspection.wsil</li> +<li> <uicontrol>Linked WSIL documents.</uicontrol> References to WSIL documents +can also appear within different content documents, such as HTML pages.</li> +</ul> </li> +</ul> +<p>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></p> +</conbody> +<related-links> +<linklist><title>Related Concepts</title> +<link href="cws.dita"><linktext>Web services overview</linktext></link> +<link href="cwsinwsa.dita"><linktext>Tools for Web services development</linktext> +</link> +</linklist> +<linklist><title>Related Tasks</title> +<link href="../tasks/toverws.dita" scope="peer"><linktext> Developing Web +services</linktext></link> +</linklist> +</related-links> +</concept> diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsil.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsil.html index 7c6abfae1..673de5e42 100644 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsil.html +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsil.html @@ -1,43 +1,52 @@ -<?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"> +<?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" /> +<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="Web Services Inspection Language (WSIL)" /> +<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. When you discover Web services with UDDI, you go to a centralized registry. WSIL is an alternative approach to Web service discovery. WSIL allows you to go directly to the service provider and ask for the services it provides." /> +<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. When you discover Web services with UDDI, you go to a centralized registry. WSIL is an alternative approach to Web service discovery. WSIL allows you to go directly to the service provider and ask for the services it provides." /> +<meta scheme="URI" name="DC.Relation" content="cws.html" /> +<meta scheme="URI" name="DC.Relation" content="cwsinwsa.html" /> +<meta scheme="URI" name="DC.Relation" content="../tasks/toverws.html" /> +<meta content="XHTML" name="DC.Format" /> +<meta content="cwsil" 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>Web Services Inspection Language (WSIL)</title> </head> <body id="cwsil"><a name="cwsil"><!-- --></a> + <h1 class="topictitle1">Web Services Inspection Language (WSIL)</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. When you discover Web services with UDDI, you go to a centralized registry. WSIL is an alternative approach to Web service discovery. WSIL allows you to go directly to the service provider and ask for the services it provides.</p> + <p>IBM<sup>®</sup> and Microsoft's proposal for the WSIL specification is designed around an XML-based model for building an aggregation of references to existing Web service descriptions, that are exposed using standard Web server technology.</p> + <p>WSIL provides 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. </p> +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.</p> + <p>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. A separate -topic in this documentation discusses the <a href="cwsilud.html">Relationship -between UDDI and WSIL</a>.</p> +on Web sites that may not be listed yet in a UDDI registry. A separate topic +in this documentation discusses the <a href="cwsilud.html">Relationship between UDDI and WSIL</a>.</p> + <p>The WSIL specification does not define a service description language. WSIL documents provide a method for aggregating different types of service descriptions. Within a WSIL document, a single service can have more @@ -49,8 +58,11 @@ If multiple references are available, it is beneficial to put all of them in the WSIL document so that the application that uses the document can select the type of service description that is compatible with and preferred by that application.</p> + <p>The WSIL specification serves two primary functions:</p> -<ul><li>WSIL defines an XML format for listing references to existing service + +<ul> +<li>WSIL defines an XML format for listing references to existing service descriptions. These service descriptions can be defined in any format, such as WSDL, UDDI, or plain HTML. A WSIL document is generally made available at the point-of-offering for the services that are referenced within the document. @@ -62,48 +74,44 @@ a hierarchy of WSIL documents. For example, separate WSIL documents can be created for different categories of services, and one primary WSIL document can link all of them together.</p> </li> + <li>WSIL defines a set of conventions so that it is easy to locate other WSIL documents. The WSIL specification does not limit the type of service descriptions that can be referenced. The WSIL specification defines a set of standard extensibility elements for both WSDL and UDDI. The WSIL specification -is the definition of locations where you can access WSIL documents.  </li> -<li> Two conventions make the location and retrieval of WSIL documents easy: <ul><li> <span class="uicontrol">Fixed-name WSIL documents.</span> The fixed name for +is the definition of locations where you can access WSIL documents.</li> + +<li> Two conventions make the location and retrieval of WSIL documents easy: <ul> +<li> <span class="uicontrol">Fixed-name WSIL documents.</span> The fixed name for WSIL documents is inspection.wsil. The inspection.wsil file is placed at common entry points for a Web site. For example, if the common entry point is http://entrypoint.com then the location of the WSIL document would be http://entrypoint.com/inspection.wsil</li> + <li> <span class="uicontrol">Linked WSIL documents.</span> References to WSIL documents can also appear within different content documents, such as HTML pages.</li> + </ul> </li> + </ul> + <p>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></p> -</div> -<div> -<ul class="ullinks"> -<li class="ulchildlink"><strong><a href="../concepts/cwsilud.html">Relationship between UDDI and WSIL</a></strong><br /> -The Web Services Inspection Language (WSIL) and the Universal Description, -Discovery, and Integration (UDDI) specification both address issues related -to Web service discovery. However, each specification takes a different -approach to the discovery of Web services. The two specifications can -be used separately or jointly; searching with WSIL can result in finding items -in UDDI.</li> -</ul> +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></p> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> </div> +<div> <div class="linklist"><strong>Related Concepts</strong><br /> <div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> -<div><a href="cwsinwsa.html">Tools for Web services development</a></div></div> +<div><a href="cwsinwsa.html" title="">Tools for Web services development</a></div></div> <div class="linklist"><strong>Related Tasks</strong><br /> -<div><a href="../tasks/toverws.html"> Developing -Web services</a></div></div> +<div><a href="../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.doc.user/concepts/cwsilud.dita b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsilud.dita new file mode 100644 index 000000000..477eb1f54 --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsilud.dita @@ -0,0 +1,68 @@ +<?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="cwsilud" xml:lang="en-us"> +<title>Relationship between UDDI and WSIL</title> +<shortdesc>The Web Services Inspection Language (WSIL) and the Universal Description, +Discovery, and Integration (UDDI) specification both address issues related +to Web service discovery. However, each specification takes a different +approach to the discovery of Web services. The two specifications can +be used separately or jointly; searching with WSIL can result in finding items +in UDDI.</shortdesc> +<conbody> +<p>The UDDI specification addresses Web service discovery through the use +of a centralized model. One or more repositories are created to house +information about businesses and the services they offer. Requests and +updates pertaining to the service and business related information are issued +directly against the repositories. In addition, UDDI prescribes a specific +format for a portion of the stored description information and, to facilitate +advanced (focused) searching, assumes that other description information will +be stored and registered within the system as well.</p> +<p>UDDI systems facilitate focused discovery patterns since these systems +are based on organized repositories that provide advanced searching capabilities. +This helps requestors locate potential communication partners. In order +to provide advanced functionality, however, UDDI requires the deployment and +maintenance of a certain amount of infrastructure, thus increasing the cost +of operation. In addition, unless the service descriptions are stored +only within UDDI, there is a cost associated with keeping the different versions +synchronized.</p> +<p>The WSIL specification relies on a completely distributed model for providing +service-related information. The service descriptions can be stored +at any location, and requests to retrieve the information are generally made +directly to the entities that are offering the services. The WSIL specification +does not stipulate any particular format for the service information. +It relies on other standards, including UDDI, to define the description formats. +The WSIL specification also relies on existing Web technologies and infrastructure +to provide mechanisms for publishing and retrieving its documents.</p> +<p>WSIL provides the ability to disseminate service-related information through +existing protocols directly from the point at which the service is being offered. +This enables focused discovery to be performed on a single target; however, +because of its decentralized and distributed model, WSIL is not a good mechanism +for executing focused discovery if the communication partner is unknown.</p> +<p>The UDDI and WSIL specifications should be viewed as complementary technologies +to be used either together or separately depending on the situation. +For example, a UDDI repository could be populated based on the results found +when performing a search for WSIL documents. Likewise, a UDDI repository +may itself be discovered when a requester retrieves a WSIL document that references +an entry in the repository. In environments where the advanced functionality +afforded by UDDI is not required and where constraints do not allow for its +deployment, the WSIL mechanism may provide all of the capabilities that are +needed. In situations where data needs to be centrally managed, a UDDI +solution alone may provide the best fit. The UDDI and WSIL specifications +should not be viewed as mutually exclusive.</p> +<note>Both UDDI and WSIL contain only references to WSDL - they do not contain +the WSDL documents themselves.</note> +</conbody> +<related-links> +<linklist><title>Related Concepts</title> +<link href="cws.dita"></link> +<link href="cwsinwsa.dita"></link> +<link href="cwsil.dita"></link> +</linklist> +<linklist><title>Related Tasks</title> +<link href="../tasks/toverws.dita" scope="peer"><?Pub Caret?><linktext> Developing +Web services</linktext></link> +</linklist> +</related-links> +</concept> +<?Pub *0000004226?> diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsilud.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsilud.html index e54aec916..ff9df85ae 100644 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsilud.html +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsilud.html @@ -1,31 +1,39 @@ -<?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"> +<?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" /> +<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 WSIL" /> +<meta name="abstract" content="The Web Services Inspection Language (WSIL) and the Universal Description, Discovery, and Integration (UDDI) specification both address issues related to Web service discovery. However, each specification takes a different approach to the discovery of Web services. The two specifications can be used separately or jointly; searching with WSIL can result in finding items in UDDI." /> +<meta name="description" content="The Web Services Inspection Language (WSIL) and the Universal Description, Discovery, and Integration (UDDI) specification both address issues related to Web service discovery. However, each specification takes a different approach to the discovery of Web services. The two specifications can be used separately or jointly; searching with WSIL can result in finding items in UDDI." /> +<meta scheme="URI" name="DC.Relation" content="cws.html" /> +<meta scheme="URI" name="DC.Relation" content="cwsinwsa.html" /> +<meta scheme="URI" name="DC.Relation" content="cwsil.html" /> +<meta scheme="URI" name="DC.Relation" content="../tasks/toverws.html" /> +<meta content="XHTML" name="DC.Format" /> +<meta content="cwsilud" 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 WSIL</title> </head> <body id="cwsilud"><a name="cwsilud"><!-- --></a> + <h1 class="topictitle1">Relationship between UDDI and WSIL</h1> + + <div><p>The Web Services Inspection Language (WSIL) and the Universal Description, Discovery, and Integration (UDDI) specification both address issues related to Web service discovery. However, each specification takes a different approach to the discovery of Web services. The two specifications can be used separately or jointly; searching with WSIL can result in finding items in UDDI.</p> + <p>The UDDI specification addresses Web service discovery through the use of a centralized model. One or more repositories are created to house information about businesses and the services they offer. Requests and @@ -34,6 +42,7 @@ directly against the repositories. In addition, UDDI prescribes a specific format for a portion of the stored description information and, to facilitate advanced (focused) searching, assumes that other description information will be stored and registered within the system as well.</p> + <p>UDDI systems facilitate focused discovery patterns since these systems are based on organized repositories that provide advanced searching capabilities. This helps requestors locate potential communication partners. In order @@ -42,6 +51,7 @@ maintenance of a certain amount of infrastructure, thus increasing the cost of operation. In addition, unless the service descriptions are stored only within UDDI, there is a cost associated with keeping the different versions synchronized.</p> + <p>The WSIL specification relies on a completely distributed model for providing service-related information. The service descriptions can be stored at any location, and requests to retrieve the information are generally made @@ -50,11 +60,13 @@ does not stipulate any particular format for the service information. It relies on other standards, including UDDI, to define the description formats. The WSIL specification also relies on existing Web technologies and infrastructure to provide mechanisms for publishing and retrieving its documents.</p> + <p>WSIL provides the ability to disseminate service-related information through existing protocols directly from the point at which the service is being offered. This enables focused discovery to be performed on a single target; however, because of its decentralized and distributed model, WSIL is not a good mechanism for executing focused discovery if the communication partner is unknown.</p> + <p>The UDDI and WSIL specifications should be viewed as complementary technologies to be used either together or separately depending on the situation. For example, a UDDI repository could be populated based on the results found @@ -66,18 +78,17 @@ deployment, the WSIL mechanism may provide all of the capabilities that are needed. In situations where data needs to be centrally managed, a UDDI solution alone may provide the best fit. The UDDI and WSIL specifications should not be viewed as mutually exclusive.</p> -<div class="note"><span class="notetitle">Note:</span> Both UDDI and WSIL contain only references to WSDL - they do not contain + +<div class="note"><span class="notetitle">Note: </span>Both UDDI and WSIL contain only references to WSDL - they do not contain the WSDL documents themselves.</div> -</div> -<div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cwsil.html" title="Web Services Inspection Language (WSIL) is a service discovery mechanism that is an alternative to UDDI as well as complementary to UDDI. When you discover Web services with UDDI, you go to a centralized registry. WSIL is an alternative approach to Web service discovery. WSIL allows you to go directly to the service provider and ask for the services it provides.">Web Services Inspection Language (WSIL)</a></div> + </div> +<div> <div class="linklist"><strong>Related Concepts</strong><br /> <div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> -<div><a href="cwsinwsa.html">Tools for Web services development</a></div> +<div><a href="cwsinwsa.html" title="">Tools for Web services development</a></div> <div><a href="cwsil.html" title="Web Services Inspection Language (WSIL) is a service discovery mechanism that is an alternative to UDDI as well as complementary to UDDI. When you discover Web services with UDDI, you go to a centralized registry. WSIL is an alternative approach to Web service discovery. WSIL allows you to go directly to the service provider and ask for the services it provides.">Web Services Inspection Language (WSIL)</a></div></div> <div class="linklist"><strong>Related Tasks</strong><br /> @@ -85,5 +96,6 @@ the WSDL documents themselves.</div> <div><a href="../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.doc.user/concepts/cwsinwsa.dita b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.dita new file mode 100644 index 000000000..dfcefe176 --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.dita @@ -0,0 +1,44 @@ +<?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="cwsinwsa" xml:lang="en-us"> +<title>Tools for Web services development</title> +<conbody> +<p>Tools are provided to assist with the following aspects of Web services +development:</p> +<ul> +<li> <uicontrol>Discover</uicontrol>. Browse the UDDI Business Registries +or WSIL documents to locate existing Web services for integration.</li> +<li> <uicontrol>Create or Transform</uicontrol>. Create bottom-up Web services +from existing artifacts, such as <tm tmclass="special" tmowner="Sun Microsystems, Inc." +tmtype="tm" trademark="Java">Java</tm> beans and enterprise beans. Create +top-down Web services from WSDL discovered from others or created using the +WSDL Editor.</li> +<li> <uicontrol>Build</uicontrol>. Wrap existing artifacts as SOAP accessible +services and describe them in WSDL. The Web services wizards assist you in +generating a <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" +trademark="Java">Java</tm> client proxy to Web services described in WSDL +and in generating <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" +trademark="Java">Java</tm> bean skeletons from WSDL.</li> +<li> <uicontrol>Deploy</uicontrol>. Deploy Web services into a variety of +test environments.</li> +<li> <uicontrol>Test</uicontrol>. Test Web services running locally or remotely +in order to get instant feedback.</li> +<li> <uicontrol>Develop</uicontrol>. Generate sample applications to assist +you in creating your own Web service client application.</li> +<li> <uicontrol>Publish</uicontrol>. Publish Web services to a UDDI v2 or +v3 Business Registry, advertising your Web services so that other businesses +and clie<?Pub Caret?>nts can access them.</li> +</ul> +</conbody> +<related-links> +<linklist><title>Related Concepts</title> +<link href="cws.dita"></link> +</linklist> +<linklist><title>Related Tasks</title> +<link href="../tasks/toverws.dita" scope="local"><linktext> Developing Web +services</linktext></link> +</linklist> +</related-links> +</concept> +<?Pub *0000002161?> diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html index a884a9329..e088074b7 100644 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html @@ -1,92 +1,72 @@ -<?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"> +<?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" /> +<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="Tools for Web services development" /> +<meta scheme="URI" name="DC.Relation" content="cws.html" /> +<meta scheme="URI" name="DC.Relation" content="../tasks/toverws.html" /> +<meta content="XHTML" name="DC.Format" /> +<meta content="cwsinwsa" 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>Tools for Web services development</title> </head> <body id="cwsinwsa"><a name="cwsinwsa"><!-- --></a> + <h1 class="topictitle1">Tools for Web services development</h1> -<div><p>Tools are provided to assist with the following aspects of Web services + +<div> +<p>Tools are provided to assist with the following aspects of Web services development:</p> -<ul><li> <span class="uicontrol">Discover</span>. Browse the UDDI Business Registries + +<ul> +<li> <span class="uicontrol">Discover</span>. Browse the UDDI Business Registries or WSIL documents to locate existing Web services for integration.</li> + <li> <span class="uicontrol">Create or Transform</span>. Create bottom-up Web services -from existing artifacts, such as Java™ beans, enterprise beans, URLs that -take and return data, DB2<sup>®</sup> XML Extender calls, DB2 Stored Procedures, and SQL queries. -Create top-down Web services from WSDL discovered from others or created using -the WSDL Editor.</li> +from existing artifacts, such as Java™ beans and enterprise beans. Create +top-down Web services from WSDL discovered from others or created using the +WSDL Editor.</li> + <li> <span class="uicontrol">Build</span>. Wrap existing artifacts as SOAP accessible services and describe them in WSDL. The Web services wizards assist you in generating a Java client proxy to Web services described in WSDL and in generating Java bean skeletons from WSDL.</li> -<li> <span class="uicontrol">Deploy</span>. Deploy Web services into the WebSphere<sup>®</sup> Application -Server or Tomcat test environments.</li> + +<li> <span class="uicontrol">Deploy</span>. Deploy Web services into a variety of +test environments.</li> + <li> <span class="uicontrol">Test</span>. Test Web services running locally or remotely in order to get instant feedback.</li> + <li> <span class="uicontrol">Develop</span>. Generate sample applications to assist you in creating your own Web service client application.</li> + <li> <span class="uicontrol">Publish</span>. Publish Web services to a UDDI v2 or v3 Business Registry, advertising your Web services so that other businesses and clients can access them.</li> -</ul> -<div class="p">Some of the Web service tools available and their uses include the following:<ul><li>Use the Web Services Client wizard to create the Java client -to a deployed Web service and to test the Web service.</li> -<li>Use the Web Services wizard to create, deploy, test, and publish Web services -bottom-up from existing Java beans and enterprise beans, or top-down -from WSDL. The Web Services wizard supports the generation of the Java bean -proxy and a sample application.</li> -<li>Publish your Web service to a UDDI Business Registry using the Web Services -Explorer.</li> -<li>The Unit Test UDDI wizard installs, configures, and removes a Private -UDDI Registry.</li> -<li>The Java Beans for XML Schema wizard enables you to generate Java beans -from schema.</li> -<li>The IBM<sup>�</sup> Web -Services Explorer assists you in discovering and publishing your Web service -descriptions.</li> -<li>Use the WSDL validator to check for structural and semantic problems in -WSDL files.</li> -<li>WS-I compliance can be validated using several tools, such as the WSDL -validator, the Web service and client wizards, and a TCP/IP monitor.</li> -<li>The deployment settings for a Web service can be modified using the J2EE -deployment descriptor editors. Double-click any deployment descriptor to launch -the appropriate editor.</li> -</ul> - </div> -</div> -<div> -<ul class="ullinks"> -<li class="ulchildlink"><strong><a href="../../org.eclipse.jst.ws.axis.ui.doc.user/concepts/caxistover.html">Creating Web services with the Apache Axis run-time environment</a></strong><br /> -</li> </ul> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> </div> +<div> <div class="linklist"><strong>Related Concepts</strong><br /> <div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div></div> <div class="linklist"><strong>Related Tasks</strong><br /> -<div><a href="../tasks/toverws.html" title="Use Web services tools to discover, create, and publish Web services that are created from Java beans, DADX files, enterprise beans, WSDL files, and URLs. These tools support the creation of Web services using a top-down approach (which starts with a WSDL file) or a bottom-up approach (which starts with a Java bean or EJB)."> Developing Web +<div><a href="../tasks/toverws.html" title="Use Web services tools to discover, create, and publish Web services that are created from Java beans, enterprise beans, and WSDL files. You can create of Web services using a top-down approach (which starts with a WSDL file) or a bottom-up approach (which starts with a Java bean or EJB)."> Developing Web services</a></div></div> -</div> +</div> + </body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsiover.dita b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsiover.dita new file mode 100644 index 000000000..578dadf07 --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsiover.dita @@ -0,0 +1,36 @@ +<?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="cwsiover" xml:lang="en-us"><?Pub Caret?> +<title>Web services interoperability (WS-I)</title> +<shortdesc>WS-I is an organization designed to promote Web service interoperability +across platforms, operating systems, and programming languages.</shortdesc> +<conbody> +<p>For more information on WS-I, refer to their Web site: <xref format="html" +href="http://www.ws-i.org/" scope="external">http://www.ws-i.org/</xref>. +This site contains resources such as an overview of Web services interoperability, +usage scenarios, and specifications.</p> +<p>WS-I Basic Profile is a outline of requirements to which WSDL and Web service +protocol (SOAP/HTTP) traffic must comply in order to claim WS-I conformance. +The Web services WS-I validation tools currently support WS-I Simple SOAP +Binding Profile 1.0 (WS-I SSBP) which builds on the WS-I Basic Profile, and +the WS-I Attachments Profile 1.0 (WS-I AP). To view the specifications, refer +to the WS-I Web site, and under <uicontrol>Deliverables</uicontrol> select + <uicontrol>Basic Profile</uicontrol>.</p> +<p>Depending on the type of Web service being created, you may or may not +want your Web service to comply with the WS-I profiles. The default level +of compliance is to generate a warning if a non WS-I SSBP complaint Web service +option is selected and to ignore any non WS-I AP compliant selections. You +can set the level of WS-I compliance at the workspace or project level. The +Web services wizards, the <tm tmclass="ibm" tmowner="IBM Corporation" tmtype="reg" +trademark="WebSphere">WebSphere</tm> run-time environments, the WSDL editor, +and other Web services tools provided support and encourage the development +of WS-I compliance services.</p> +</conbody> +<related-links> +<linklist><title>Related Tasks</title> +<link href="../tasks/twsicomply.dita"></link> +</linklist> +</related-links> +</concept> +<?Pub *0000002039?> diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsiover.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsiover.html index 3d4aa5996..a8d4488b1 100644 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsiover.html +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsiover.html @@ -1,30 +1,36 @@ -<?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"> +<?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" /> +<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="Web services interoperability (WS-I)" /> +<meta name="abstract" content="WS-I is an organization designed to promote Web service interoperability across platforms, operating systems, and programming languages." /> +<meta name="description" content="WS-I is an organization designed to promote Web service interoperability across platforms, operating systems, and programming languages." /> +<meta scheme="URI" name="DC.Relation" content="../tasks/twsicomply.html" /> +<meta content="XHTML" name="DC.Format" /> +<meta content="cwsiover" 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>Web services interoperability (WS-I)</title> </head> <body id="cwsiover"><a name="cwsiover"><!-- --></a> + <h1 class="topictitle1">Web services interoperability (WS-I)</h1> + + <div><p>WS-I is an organization designed to promote Web service interoperability across platforms, operating systems, and programming languages.</p> + <p>For more information on WS-I, refer to their Web site: <a href="http://www.ws-i.org/" target="_blank">http://www.ws-i.org/</a>. This site contains resources such as an overview of Web services interoperability, usage scenarios, and specifications.</p> + <p>WS-I Basic Profile is a outline of requirements to which WSDL and Web service protocol (SOAP/HTTP) traffic must comply in order to claim WS-I conformance. The Web services WS-I validation tools currently support WS-I Simple SOAP @@ -32,33 +38,23 @@ Binding Profile 1.0 (WS-I SSBP) which builds on the WS-I Basic Profile, and the WS-I Attachments Profile 1.0 (WS-I AP). To view the specifications, refer to the WS-I Web site, and under <span class="uicontrol">Deliverables</span> select <span class="uicontrol">Basic Profile</span>.</p> + <p>Depending on the type of Web service being created, you may or may not want your Web service to comply with the WS-I profiles. The default level of compliance is to generate a warning if a non WS-I SSBP complaint Web service option is selected and to ignore any non WS-I AP compliant selections. You can set the level of WS-I compliance at the workspace or project level. The -Web services wizards, the WSDL editor, +Web services wizards, the WebSphere<sup>®</sup> run-time environments, the WSDL editor, and other Web services tools provided support and encourage the development of WS-I compliance services.</p> -</div> -<div> -<ul class="ullinks"> -<li class="ulchildlink"><strong><a href="../tasks/twsicomply.html">Setting the level of WS-I compliance</a></strong><br /> -The Web services WS-I validation tools support the level of WS-I -compliance outlined in the WS-I Basic Profile 1.1, the WS-I Simple SOAP Binding -Profile 1.0 (WS-I SSBP), and the WS-I Attachments Profile 1.0 (WS-I AP). You -can choose to make your Web service compliant or non-compliant, depending -on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols, -and secured Web services, are not WS-I compliant.</li> -</ul> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> </div> +<div> <div class="linklist"><strong>Related Tasks</strong><br /> <div><a href="../tasks/twsicomply.html" title="The Web services WS-I validation tools support the level of WS-I compliance outlined in the WS-I Basic Profile 1.1, the WS-I Simple SOAP Binding Profile 1.0 (WS-I SSBP), and the WS-I Attachments Profile 1.0 (WS-I AP). You can choose to make your Web service compliant or non-compliant, depending on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols, and secured Web services, are not WS-I compliant.">Setting the level of WS-I compliance</a></div></div> -</div> +</div> + </body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsstandards.dita b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsstandards.dita new file mode 100644 index 000000000..0aadf7c96 --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsstandards.dita @@ -0,0 +1,217 @@ +<?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="webservicesstandards" xml:lang="en-us"> +<title>Web services standards</title> +<shortdesc>One of the key attributes of Internet standards is that they focus +on protocols and not on implementations. The Internet is composed of heterogeneous +technologies that successfully interoperate through shared protocols. This +prevents individual vendors from imposing a standard on the Internet. Open +Source software development plays a crucial role in preserving the interoperability +of vendor implementations of standards.</shortdesc> +<conbody> +<p>The following standards play key roles in Web services: Universal Description, +Discovery and Integration (UDDI), Web Services Description Language (WSDL), +Web Services Inspection Language (WSIL), SOAP, and Web Services Interoperability +(WS-I). The relationship between these standards is described in Figure 2.</p> +<p>The UDDI specification defines open, platform-independent standards that +enable businesses to share information in a global business registry, discover +services on the registry, and define how they interact over the Internet. +For more information on UDDI, refer to <xref format="html" href="http://www.uddi.org" +scope="external">www.uddi.org</xref></p> +<p>WSIL is an XML-based open specification that defines 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. A WSIL document 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. A separate topic in this +documentation discusses the <xref href="cwsilud.dita">Relationship between +UDDI and WSIL</xref>. For more information on WSIL, 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></p> +<p>WSDL is an XML-based open specification that describes the interfaces to +and instances of Web services on the network. It is extensible, so endpoints +can be described regardless of the message formats or network protocols that +are used to communicate. Businesses can make the WSDL documents for their +Web services available though UDDI, WSIL, or by broadcasting the URLs to their +WSDL via email or Web sites. WSDL is described as a separate topic in this +documentation. For more information on WSDL, refer to <xref format="html" +href="http://www.w3.org/TR/wsdl" scope="external">www.w3.org/TR/wsdl</xref></p> +<p>SOAP is an XML-based standard for messaging over HTTP and other Internet +protocols. It is a lightweight protocol for the exchange of information in +a decentralized, distributed environment. It is based on XML and consists +of three parts:<ul> +<li>An envelope that defines a framework for describing what is in a message +and how to process it.</li> +<li>A set of encoding rules for expressing instances of application-defined +data types.</li> +<li>A convention for representing remote procedure calls and responses.</li> +</ul>SOAP enables the binding and usage of discovered Web services by defining +a message path for routing messages. SOAP may be used to query UDDI for Web +services. For more information on SOAP, refer to <xref format="html" href="http://www.w3.org/TR/SOAP" +scope="external">www.w3.org/TR/SOAP</xref></p> +<p>Figure 2. Relationships between SOAP, UDDI, WSIL and WSDL.</p> +<p> <image alt="Figure 2 illustrates the relationships between SOAP, UDDI, WSIL, and WSDL." +href="../images/soapudws.gif"></image> </p> +<p>A service provider hosts a Web service and makes it accessible using protocols +such as SOAP/HTTP or SOAP/JMS. The Web service is described by a WSDL document +that is stored on the provider's server or in a special repository. The WSDL +document may be referenced by the UDDI business registry and WSIL documents. +These contain pointers to the Web service's WSDL files.</p> +<p>The WS-I Simple SOAP Binding Profile and WS-I Attachments Profile are outlines +of requirements to which WSDL and Web service protocol (SOAP/HTTP) traffic +must comply in order to claim WS-I conformance. The Web services WS-I validation +tools currently support WS-I Simple SOAP Binding Profile 1.0 and the Attachment +Profile 1.0. To view the specifications, refer to the WS-I Web site, and under + <uicontrol>Resources</uicontrol> select <uicontrol>Documentation</uicontrol>: <xref +href="http://www.ws-i.org" scope="external">http://www.ws-i.org</xref></p> +<p>Several new Web services standards are also supported by <tm tmclass="ibm" +tmowner="IBM Corporation" tmtype="reg" trademark="Rational">Rational</tm> Developer +products. These include:<dl><dlentry> +<dt>JAX-RPC</dt> +<dd>JAX-RPC stands for <tm tmclass="special" tmowner="Sun Microsystems, Inc." +tmtype="tm" trademark="Java">Java</tm> API for XML-based RPC, also known as +JSR 101. It is a specification that describes <tm tmclass="special" tmowner="Sun Microsystems, Inc." +tmtype="tm" trademark="Java">Java</tm> Application Programming Interfaces +(APIs) and conventions for building Web services and Web service clients that +use remote procedure calls (RPC) and XML. It standardizes the <tm tmclass="special" +tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> to +WSDL and WSDL to <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" +trademark="Java">Java</tm> mappings, and provides the core APIs for developing +and deploying Web services and Web service clients on the <tm tmclass="special" +tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> platform. +For more information refer to the <xref href="http://www.jcp.org/en/jsr/detail?id=101" +scope="external">official specifications</xref>.</dd> +</dlentry><dlentry> +<dt>JSR-109 and JSR-921</dt> +<dd>JSR-109 and JSR-921 (Implementing Enterprise Web Services) define the +programming model and run-time architecture to deploy and look up Web services +in the J2EE environment; more specifically, in the Web, EJB, and Client Application +containers. One of its main goals is to ensure vendors' implementations interoperate. +For more information, refer to the official specifications: <ul> +<li><xref href="http://www.jcp.org/en/jsr/detail?id=109" scope="external" +type="html">JSR-109</xref></li> +<li><xref href="http://www.jcp.org/en/jsr/detail?id=921" scope="external" +type="html">JSR-921</xref></li> +</ul></dd> +</dlentry><dlentry> +<dt>WS-S</dt> +<dd>These tools support the OASIS Web Services Security 1.0 standard. For +more information on the various components of this standard, refer to:<ul> +<li><xref href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf" +scope="external" type="html">Web Services Security: SOAP Message Security +V1.0</xref> </li> +<li> <xref href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0.pdf" +scope="external" type="html">Web Services Security: Username Token Profile +V1.0</xref></li> +<li> <xref href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0.pdf" +scope="external" type="html">Web Services Security: X.509 Token Profile V1.0</xref></li> +</ul></dd> +</dlentry></dl></p> +<p>Web services tooling supports the following specifications:</p> +<table> +<tgroup cols="2"><colspec colname="col1" colwidth="95*"/><colspec colname="col2" +colwidth="104*"/> +<thead> +<row> +<entry colname="col1" valign="top">Technology or specification</entry> +<entry colname="col2" valign="top">Version or level supported</entry> +</row> +</thead> +<tbody> +<row> +<entry nameend="col2" namest="col1"><b>Transports</b></entry> +</row> +<row> +<entry colname="col1">HTTP/HTTPS</entry> +<entry colname="col2">v1.0 and v1.1</entry> +</row> +<row> +<entry colname="col1">JMS</entry> +<entry colname="col2"></entry> +</row> +<row> +<entry nameend="col2" namest="col1"><b>Messaging</b></entry> +</row> +<row> +<entry colname="col1">SOAP specification</entry> +<entry colname="col2">v1.1</entry> +</row> +<row> +<entry colname="col1">SOAP Attachements</entry> +<entry colname="col2"></entry> +</row> +<row> +<entry nameend="col2" namest="col1"><b>Description</b></entry> +</row> +<row> +<entry colname="col1">UDDI</entry> +<entry colname="col2">v2.0</entry> +</row> +<row> +<entry colname="col1">WSDL</entry> +<entry colname="col2">v1.1</entry> +</row> +<row> +<entry colname="col1">WSIL</entry> +<entry colname="col2">v1.0</entry> +</row> +<row> +<entry nameend="col2" namest="col1"><b>Security</b></entry> +</row> +<row> +<entry colname="col1">WS-Security</entry> +<entry colname="col2">OASIS Standard 1.0</entry> +</row> +<row> +<entry nameend="col2" namest="col1"><b>Ineroperability</b></entry> +</row> +<row> +<entry colname="col1">WS-I Basic Profile</entry> +<entry colname="col2">1.1.2</entry> +</row> +<row> +<entry colname="col1">WS-I Simple SOAP Binding Profile</entry> +<entry colname="col2">1.0.3</entry> +</row> +<row> +<entry colname="col1">WS-I Attachments Profile</entry> +<entry colname="col2">1.0</entry> +</row> +<row> +<entry colname="col1"><b>Other Standards</b></entry> +<entry colname="col2"></entry> +</row> +<row> +<entry colname="col1">JAX-RPC</entry> +<entry colname="col2">v1.0 for J2EE 1.3, v1.1 for J2EE 1.4</entry> +</row> +<row> +<entry colname="col1">JSR 109</entry> +<entry colname="col2">J2EE 1.3</entry> +</row> +<row> +<entry colname="col1">JSR 921</entry> +<entry colname="col2">J2EE 1.4</entry> +</row> +</tbody> +</tgroup> +</table> +</conbody> +<related-links> +<linklist><title>Related Concepts</title> +<link href="cws.dita" scope="local"><linktext>Web services overview</linktext> +</link> +<link href="cwsinwsa.dita" scope="local"><linktext>Tools for Web services +development</linktext></link> +<link href="cwsiover.dita" scope="local"><linktext>Web services interoperability +(WS-I)</linktext></link> +</linklist> +<linklist><title>Related Tasks</title> +<link href="../tasks/toverws.dita" scope="local"><linktext> Developing Web +services</linktext></link> +</linklist> +</related-links> +</concept> diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsstandards.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsstandards.html index 227d10a61..d6e712916 100644 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsstandards.html +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsstandards.html @@ -1,49 +1,59 @@ -<?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"> +<?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> -<!-- /******************************************************************************* - * 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" /> - +<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="Web services standards" /> +<meta name="abstract" content="One of the key attributes of Internet standards is that they focus on protocols and not on implementations. The Internet is composed of heterogeneous technologies that successfully interoperate through shared protocols. This prevents individual vendors from imposing a standard on the Internet. Open Source software development plays a crucial role in preserving the interoperability of vendor implementations of standards." /> +<meta name="description" content="One of the key attributes of Internet standards is that they focus on protocols and not on implementations. The Internet is composed of heterogeneous technologies that successfully interoperate through shared protocols. This prevents individual vendors from imposing a standard on the Internet. Open Source software development plays a crucial role in preserving the interoperability of vendor implementations of standards." /> +<meta scheme="URI" name="DC.Relation" content="cws.html" /> +<meta scheme="URI" name="DC.Relation" content="cwsinwsa.html" /> +<meta scheme="URI" name="DC.Relation" content="cwsiover.html" /> +<meta scheme="URI" name="DC.Relation" content="../tasks/toverws.html" /> +<meta content="XHTML" name="DC.Format" /> +<meta content="webservicesstandards" 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>Web services standards</title> </head> <body id="webservicesstandards"><a name="webservicesstandards"><!-- --></a> + + <h1 class="topictitle1">Web services standards</h1> + + <div><p>One of the key attributes of Internet standards is that they focus on protocols and not on implementations. The Internet is composed of heterogeneous technologies that successfully interoperate through shared protocols. This prevents individual vendors from imposing a standard on the Internet. Open Source software development plays a crucial role in preserving the interoperability of vendor implementations of standards.</p> + <p>The following standards play key roles in Web services: Universal Description, Discovery and Integration (UDDI), Web Services Description Language (WSDL), -Web Services Inspection Language (WSIL), Simple Object Access Protocol (SOAP) -and Web Services Interoperability (WS-I). The relationship between these standards -is described in Figure 2.</p> +Web Services Inspection Language (WSIL), SOAP, and Web Services Interoperability +(WS-I). The relationship between these standards is described in Figure 2.</p> + <p>The UDDI specification defines open, platform-independent standards that enable businesses to share information in a global business registry, discover services on the registry, and define how they interact over the Internet. For more information on UDDI, refer to <a href="http://www.uddi.org" target="_blank">www.uddi.org</a></p> + <p>WSIL is an XML-based open specification that defines 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. A WSIL document defines the locations on a Web -site where you can look for Web service descriptions. Since WSIL focuses +available Web services. A WSIL document 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. A separate topic in this -documentation discusses the <a href="cwsilud.html">Relationship between -UDDI and WSIL</a>. For more information on WSIL, 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></p> +that may not be listed yet in a UDDI registry. A separate topic in this +documentation discusses the <a href="cwsilud.html">Relationship between UDDI and WSIL</a>. For more information on WSIL, 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></p> + <p>WSDL is an XML-based open specification that describes the interfaces to and instances of Web services on the network. It is extensible, so endpoints can be described regardless of the message formats or network protocols that @@ -51,175 +61,251 @@ are used to communicate. Businesses can make the WSDL documents for their Web services available though UDDI, WSIL, or by broadcasting the URLs to their WSDL via email or Web sites. WSDL is described as a separate topic in this documentation. For more information on WSDL, refer to <a href="http://www.w3.org/TR/wsdl" target="_blank">www.w3.org/TR/wsdl</a></p> + <div class="p">SOAP is an XML-based standard for messaging over HTTP and other Internet protocols. It is a lightweight protocol for the exchange of information in a decentralized, distributed environment. It is based on XML and consists -of three parts:<ul><li>An envelope that defines a framework for describing what is in a message +of three parts:<ul> +<li>An envelope that defines a framework for describing what is in a message and how to process it.</li> + <li>A set of encoding rules for expressing instances of application-defined data types.</li> + <li>A convention for representing remote procedure calls and responses.</li> + </ul> SOAP enables the binding and usage of discovered Web services by defining a message path for routing messages. SOAP may be used to query UDDI for Web services. For more information on SOAP, refer to <a href="http://www.w3.org/TR/SOAP" target="_blank">www.w3.org/TR/SOAP</a></div> + <p>Figure 2. Relationships between SOAP, UDDI, WSIL and WSDL.</p> + <p> <img src="../images/soapudws.gif" alt="Figure 2 illustrates the relationships between SOAP, UDDI, WSIL, and WSDL." /> </p> + <p>A service provider hosts a Web service and makes it accessible using protocols such as SOAP/HTTP or SOAP/JMS. The Web service is described by a WSDL document that is stored on the provider's server or in a special repository. The WSDL document may be referenced by the UDDI business registry and WSIL documents. These contain pointers to the Web service's WSDL files.</p> + <p>The WS-I Simple SOAP Binding Profile and WS-I Attachments Profile are outlines of requirements to which WSDL and Web service protocol (SOAP/HTTP) traffic must comply in order to claim WS-I conformance. The Web services WS-I validation tools currently support WS-I Simple SOAP Binding Profile 1.0 and the Attachment Profile 1.0. To view the specifications, refer to the WS-I Web site, and under <span class="uicontrol">Resources</span> select <span class="uicontrol">Documentation</span>: <a href="http://www.ws-i.org" target="_blank">http://www.ws-i.org</a></p> -<div class="p">Several new Web services standards are also supported by these tools. These include:<dl><dt class="dlterm">JAX-RPC</dt> -<dd>JAX-RPC stands for Java„¢ API for XML-based RPC, also known as + +<div class="p">Several new Web services standards are also supported by Rational<sup>®</sup> Developer +products. These include:<dl> +<dt class="dlterm">JAX-RPC</dt> + +<dd>JAX-RPC stands for Javaâ„¢ API for XML-based RPC, also known as JSR 101. It is a specification that describes Java Application Programming Interfaces (APIs) and conventions for building Web services and Web service clients that use remote procedure calls (RPC) and XML. It standardizes the Java to WSDL and WSDL to Java mappings, and provides the core APIs for developing and deploying Web services and Web service clients on the Java platform. For more information refer to the <a href="http://www.jcp.org/en/jsr/detail?id=101" target="_blank">official specifications</a>.</dd> + + <dt class="dlterm">JSR-109 and JSR-921</dt> + <dd>JSR-109 and JSR-921 (Implementing Enterprise Web Services) define the programming model and run-time architecture to deploy and look up Web services in the J2EE environment; more specifically, in the Web, EJB, and Client Application containers. One of its main goals is to ensure vendors' implementations interoperate. -For more information, refer to the official specifications: <ul><li><a href="http://www.jcp.org/en/jsr/detail?id=109" target="_blank">JSR-109</a></li> +For more information, refer to the official specifications: <ul> +<li><a href="http://www.jcp.org/en/jsr/detail?id=109" target="_blank">JSR-109</a></li> + <li><a href="http://www.jcp.org/en/jsr/detail?id=921" target="_blank">JSR-921</a></li> + </ul> </dd> + + <dt class="dlterm">WS-S</dt> -<dd>These tools support the OASIS Web Services Security 1.0 standard. For more information -on the various components of this standard, refer to:<ul><li><a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf" target="_blank">Web Services Security: SOAP Message Security -V1.0</a> </li> -<li> <a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0.pdf" target="_blank">Web Services Security: Username Token Profile -V1.0</a></li> + +<dd>These tools support the OASIS Web Services Security 1.0 standard. For +more information on the various components of this standard, refer to:<ul> +<li><a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf" target="_blank">Web Services Security: SOAP Message Security V1.0</a> </li> + +<li> <a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0.pdf" target="_blank">Web Services Security: Username Token Profile V1.0</a></li> + <li> <a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0.pdf" target="_blank">Web Services Security: X.509 Token Profile V1.0</a></li> + </ul> </dd> + </dl> </div> + <p>Web services tooling supports the following specifications:</p> -<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="47.73869346733669%" id="d0e125">Technology or specification</th> -<th valign="top" width="52.26130653266332%" id="d0e127">Version or level supported</th> + +<div class="tablenoborder"><table summary="" cellspacing="0" cellpadding="4" frame="border" border="1" rules="all"> +<thead align="left"> +<tr> +<th valign="top" width="47.73869346733669%" id="N101A4">Technology or specification</th> + +<th valign="top" width="52.26130653266332%" id="N101AC">Version or level supported</th> + </tr> + </thead> -<tbody><tr><td colspan="2" valign="top" headers="d0e125 d0e127 "><strong>Transports</strong></td> + +<tbody> +<tr> +<td colspan="2" valign="top" headers="N101A4 N101AC "><strong>Transports</strong></td> + </tr> -<tr><td valign="top" width="47.73869346733669%" headers="d0e125 ">HTTP/HTTPS</td> -<td valign="top" width="52.26130653266332%" headers="d0e127 ">v1.0 and v1.1</td> + +<tr> +<td valign="top" width="47.73869346733669%" headers="N101A4 ">HTTP/HTTPS</td> + +<td valign="top" width="52.26130653266332%" headers="N101AC ">v1.0 and v1.1</td> + </tr> -<tr><td valign="top" width="47.73869346733669%" headers="d0e125 ">JMS</td> -<td valign="top" width="52.26130653266332%" headers="d0e127 "> </td> + +<tr> +<td valign="top" width="47.73869346733669%" headers="N101A4 ">JMS</td> + +<td valign="top" width="52.26130653266332%" headers="N101AC "> </td> + </tr> -<tr><td colspan="2" valign="top" headers="d0e125 d0e127 "><strong>Messaging</strong></td> + +<tr> +<td colspan="2" valign="top" headers="N101A4 N101AC "><strong>Messaging</strong></td> + </tr> -<tr><td valign="top" width="47.73869346733669%" headers="d0e125 ">SOAP specification</td> -<td valign="top" width="52.26130653266332%" headers="d0e127 ">v1.1</td> + +<tr> +<td valign="top" width="47.73869346733669%" headers="N101A4 ">SOAP specification</td> + +<td valign="top" width="52.26130653266332%" headers="N101AC ">v1.1</td> + </tr> -<tr><td valign="top" width="47.73869346733669%" headers="d0e125 ">SOAP Attachements</td> -<td valign="top" width="52.26130653266332%" headers="d0e127 "> </td> + +<tr> +<td valign="top" width="47.73869346733669%" headers="N101A4 ">SOAP Attachements</td> + +<td valign="top" width="52.26130653266332%" headers="N101AC "> </td> + </tr> -<tr><td colspan="2" valign="top" headers="d0e125 d0e127 "><strong>Description</strong></td> + +<tr> +<td colspan="2" valign="top" headers="N101A4 N101AC "><strong>Description</strong></td> + </tr> -<tr><td valign="top" width="47.73869346733669%" headers="d0e125 ">UDDI</td> -<td valign="top" width="52.26130653266332%" headers="d0e127 ">v2.0</td> + +<tr> +<td valign="top" width="47.73869346733669%" headers="N101A4 ">UDDI</td> + +<td valign="top" width="52.26130653266332%" headers="N101AC ">v2.0</td> + </tr> -<tr><td valign="top" width="47.73869346733669%" headers="d0e125 ">WSDL</td> -<td valign="top" width="52.26130653266332%" headers="d0e127 ">v1.1</td> + +<tr> +<td valign="top" width="47.73869346733669%" headers="N101A4 ">WSDL</td> + +<td valign="top" width="52.26130653266332%" headers="N101AC ">v1.1</td> + </tr> -<tr><td valign="top" width="47.73869346733669%" headers="d0e125 ">WSIL</td> -<td valign="top" width="52.26130653266332%" headers="d0e127 ">v1.0</td> + +<tr> +<td valign="top" width="47.73869346733669%" headers="N101A4 ">WSIL</td> + +<td valign="top" width="52.26130653266332%" headers="N101AC ">v1.0</td> + </tr> -<tr><td colspan="2" valign="top" headers="d0e125 d0e127 "><strong>Security</strong></td> + +<tr> +<td colspan="2" valign="top" headers="N101A4 N101AC "><strong>Security</strong></td> + </tr> -<tr><td valign="top" width="47.73869346733669%" headers="d0e125 ">WS-Security</td> -<td valign="top" width="52.26130653266332%" headers="d0e127 ">OASIS Standard 1.0</td> + +<tr> +<td valign="top" width="47.73869346733669%" headers="N101A4 ">WS-Security</td> + +<td valign="top" width="52.26130653266332%" headers="N101AC ">OASIS Standard 1.0</td> + </tr> -<tr><td colspan="2" valign="top" headers="d0e125 d0e127 "><strong>Ineroperability</strong></td> + +<tr> +<td colspan="2" valign="top" headers="N101A4 N101AC "><strong>Ineroperability</strong></td> + </tr> -<tr><td valign="top" width="47.73869346733669%" headers="d0e125 ">WS-I Basic Profile</td> -<td valign="top" width="52.26130653266332%" headers="d0e127 ">1.1.2</td> + +<tr> +<td valign="top" width="47.73869346733669%" headers="N101A4 ">WS-I Basic Profile</td> + +<td valign="top" width="52.26130653266332%" headers="N101AC ">1.1.2</td> + </tr> -<tr><td valign="top" width="47.73869346733669%" headers="d0e125 ">WS-I Simple SOAP Binding Profile</td> -<td valign="top" width="52.26130653266332%" headers="d0e127 ">1.0.3</td> + +<tr> +<td valign="top" width="47.73869346733669%" headers="N101A4 ">WS-I Simple SOAP Binding Profile</td> + +<td valign="top" width="52.26130653266332%" headers="N101AC ">1.0.3</td> + </tr> -<tr><td valign="top" width="47.73869346733669%" headers="d0e125 ">WS-I Attachments Profile</td> -<td valign="top" width="52.26130653266332%" headers="d0e127 ">1.0</td> + +<tr> +<td valign="top" width="47.73869346733669%" headers="N101A4 ">WS-I Attachments Profile</td> + +<td valign="top" width="52.26130653266332%" headers="N101AC ">1.0</td> + </tr> -<tr><td valign="top" width="47.73869346733669%" headers="d0e125 "><strong>Other Standards</strong></td> -<td valign="top" width="52.26130653266332%" headers="d0e127 "> </td> + +<tr> +<td valign="top" width="47.73869346733669%" headers="N101A4 "><strong>Other Standards</strong></td> + +<td valign="top" width="52.26130653266332%" headers="N101AC "> </td> + </tr> -<tr><td valign="top" width="47.73869346733669%" headers="d0e125 ">JAX-RPC</td> -<td valign="top" width="52.26130653266332%" headers="d0e127 ">v1.0 for J2EE 1.3, v1.1 for J2EE 1.4</td> + +<tr> +<td valign="top" width="47.73869346733669%" headers="N101A4 ">JAX-RPC</td> + +<td valign="top" width="52.26130653266332%" headers="N101AC ">v1.0 for J2EE 1.3, v1.1 for J2EE 1.4</td> + </tr> -<tr><td valign="top" width="47.73869346733669%" headers="d0e125 ">JSR 109</td> -<td valign="top" width="52.26130653266332%" headers="d0e127 ">J2EE 1.3</td> + +<tr> +<td valign="top" width="47.73869346733669%" headers="N101A4 ">JSR 109</td> + +<td valign="top" width="52.26130653266332%" headers="N101AC ">J2EE 1.3</td> + </tr> -<tr><td valign="top" width="47.73869346733669%" headers="d0e125 ">JSR 921</td> -<td valign="top" width="52.26130653266332%" headers="d0e127 ">J2EE 1.4</td> + +<tr> +<td valign="top" width="47.73869346733669%" headers="N101A4 ">JSR 921</td> + +<td valign="top" width="52.26130653266332%" headers="N101AC ">J2EE 1.4</td> + </tr> + </tbody> + </table> </div> -</div> -<div> -<ul class="ullinks"> -<li class="ulchildlink"><strong><a href="../concepts/cwsdl.html">Web Services Description Language (WSDL)</a></strong><br /> -Web Services Description Language (WSDL) is a standard specification -for describing networked, XML-based services. It provides a simple way for -service providers to describe the basic format of requests to their systems -regardless of the underlying run-time implementation.</li> -<li class="ulchildlink"><strong><a href="../concepts/csoap.html">Simple Object Access Protocol (SOAP)</a></strong><br /> -Simple Object Access Protocol (SOAP) is a lightweight protocol -for the exchange of information in a decentralized, distributed environment. -A SOAP message is a transmission of information from a sender to a receiver. -SOAP messages can be combined to perform request/response patterns. </li> -<li class="ulchildlink"><strong><a href="../../org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cuddi.html">Universal Description, Discovery, and Integration (UDDI)</a></strong><br /> -</li> -<li class="ulchildlink"><strong><a href="../concepts/cwsil.html">Web Services Inspection Language (WSIL)</a></strong><br /> -Web Services Inspection Language (WSIL) is a service discovery -mechanism that is an alternative to UDDI as well as complementary to UDDI. -When you discover Web services with UDDI, you go to a centralized registry. -WSIL is an alternative approach to Web service discovery. WSIL allows -you to go directly to the service provider and ask for the services it provides.</li> -<li class="ulchildlink"><strong><a href="../concepts/cjaxrpc.html">JAX-RPC</a></strong><br /> -JAX-RPC stands for Java API for XML-based RPC, also known as -JSR 101. It is a specification that describes Java Application Programming Interfaces -(APIs) and conventions for building Web services and Web service clients that -use remote procedure calls (RPC) and XML. It standardizes the Java to -WSDL and WSDL to Java mappings, and provides the core APIs for developing -Web services and Web service clients on the Java platform. Often used in a distributed -client/server model, an RPC mechanism enables clients to execute procedures -on other systems.</li> -<li class="ulchildlink"><strong><a href="../concepts/cjsr109.html">JSR 109 and JSR 921- Implementing Enterprise Web services</a></strong><br /> -JSR 109 and JSR 921 (Implementing Enterprise Web Services) define -the programming model and run-time architecture to deploy and look up Web -services in the J2EE environment; more specifically, in the Web, EJB, and -Client Application containers. One of its main goals is to ensure vendors' -implementations interoperate.</li> -</ul> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> </div> +<div> <div class="linklist"><strong>Related Concepts</strong><br /> <div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> -<div><a href="cwsinwsa.html">Tools for Web services +<div><a href="cwsinwsa.html" title="">Tools for Web services development</a></div> <div><a href="cwsiover.html" title="WS-I is an organization designed to promote Web service interoperability across platforms, operating systems, and programming languages.">Web services interoperability (WS-I)</a></div></div> <div class="linklist"><strong>Related Tasks</strong><br /> +<div><a href="../tasks/toverws.html" title="Use Web services tools to discover, create, and publish Web services that are created from Java beans, enterprise beans, and WSDL files. You can create of Web services using a top-down approach (which starts with a WSDL file) or a bottom-up approach (which starts with a Java bean or EJB)."> Developing Web +services</a></div></div> </div> -</div></body> + +</body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwstopdown.dita b/docs/org.eclipse.jst.ws.doc.user/concepts/cwstopdown.dita new file mode 100644 index 000000000..b15b6ceeb --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwstopdown.dita @@ -0,0 +1,32 @@ +<?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="creatingtop-downwebservices" xml:lang="en-us"><?Pub Caret?> +<title>Creating top-down Web services</title> +<shortdesc>Web services can be created using two methods: top-down development +and bottom-up development. Top-down Web services development involves creating +a Web service from a WSDL file.</shortdesc> +<conbody> +<p>Although bottom-up Web service development may be faster and easier, especially +if you are new to Web services, the top-down approach is the recommended way +of creating a Web service.</p> +<p>When creating a Web service using a top-down approach, first you design +the implementation of the Web service by creating a WSDL file. You can do +this using the WSDL Editor. You can then use the Web services wizard to create +the Web service and skeleton <tm tmclass="special" tmowner="Sun Microsystems, Inc." +tmtype="tm" trademark="Java">Java</tm> classes to which you can add the required +code.</p> +</conbody> +<related-links> +<linklist><title>Related Concepts</title> +<link href="cws.dita"></link> +<link href="cwsinwsa.dita"></link> +<link href="cwsbtmup.dita" scope="local"></link> +</linklist> +<linklist><title>Related Tasks</title> +<link href="../tasks/toverws.dita" scope="local"><linktext> Developing Web +services</linktext></link> +</linklist> +</related-links> +</concept> +<?Pub *0000001482?> diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwstopdown.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwstopdown.html index 248b77578..3f296567f 100644 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwstopdown.html +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwstopdown.html @@ -1,47 +1,60 @@ -<?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"> +<?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" /> +<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="Creating top-down Web services" /> +<meta name="abstract" content="Web services can be created using two methods: top-down development and bottom-up development. Top-down Web services development involves creating a Web service from a WSDL file." /> +<meta name="description" content="Web services can be created using two methods: top-down development and bottom-up development. Top-down Web services development involves creating a Web service from a WSDL file." /> +<meta scheme="URI" name="DC.Relation" content="cws.html" /> +<meta scheme="URI" name="DC.Relation" content="cwsinwsa.html" /> +<meta scheme="URI" name="DC.Relation" content="cwsbtmup.html" /> +<meta scheme="URI" name="DC.Relation" content="../tasks/toverws.html" /> +<meta content="XHTML" name="DC.Format" /> +<meta content="creatingtop-downwebservices" 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>Creating top-down Web services</title> </head> <body id="creatingtop-downwebservices"><a name="creatingtop-downwebservices"><!-- --></a> + <h1 class="topictitle1">Creating top-down Web services</h1> + + <div><p>Web services can be created using two methods: top-down development and bottom-up development. Top-down Web services development involves creating a Web service from a WSDL file.</p> + <p>Although bottom-up Web service development may be faster and easier, especially if you are new to Web services, the top-down approach is the recommended way of creating a Web service.</p> + <p>When creating a Web service using a top-down approach, first you design the implementation of the Web service by creating a WSDL file. You can do this using the WSDL Editor. You can then use the Web services wizard to create the Web service and skeleton Javaâ„¢ classes to which you can add the required code.</p> -</div> -<div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="/tasks/toverws.html">Creating Web services</a></div> + </div> +<div> <div class="linklist"><strong>Related Concepts</strong><br /> <div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> -<div><a href="cwsinwsa.html">Tools for Web services development</a></div> -<div><a href="cwsbtmup.html" title="Web services can be created using two methods: top-down development and bottom-up development. Bottom-up Web services development involves creating a Web service from a Java bean, enterprise bean, URL, DADX file, or ISD.">Creating bottom-up Web services</a></div></div> +<div><a href="cwsinwsa.html" title="">Tools for Web services development</a></div> +<div><a href="cwsbtmup.html" title="Web services can be created using two methods: top-down development and bottom-up development. Bottom-up Web services development involves creating a Web service from a Java bean or enterprise bean.">Creating bottom-up Web services</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="../tasks/toverws.html" title="Use Web services tools to discover, create, and publish Web services that are created from Java beans, enterprise beans, and WSDL files. You can create of Web services using a top-down approach (which starts with a WSDL file) or a bottom-up approach (which starts with a Java bean or EJB)."> Developing Web +services</a></div></div> </div> + </body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/myplugin.xml b/docs/org.eclipse.jst.ws.doc.user/myplugin.xml new file mode 100644 index 000000000..6eda01aba --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/myplugin.xml @@ -0,0 +1,20 @@ +<?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="webservice_toc.xml" /> + </extension> + +</plugin>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/org.eclipse.jst.ws.doc.user.maplist b/docs/org.eclipse.jst.ws.doc.user/org.eclipse.jst.ws.doc.user.maplist new file mode 100644 index 000000000..b266991a9 --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/org.eclipse.jst.ws.doc.user.maplist @@ -0,0 +1,8 @@ +<maplist version="3.6.2"> + <nav> + <map file="webservice_toc.ditamap"/> + </nav> + <link> + <map file="webservice_toc.ditamap"/> + </link> +</maplist> diff --git a/docs/org.eclipse.jst.ws.doc.user/ref/rwsdl.dita b/docs/org.eclipse.jst.ws.doc.user/ref/rwsdl.dita new file mode 100644 index 000000000..4b0b3bf78 --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/ref/rwsdl.dita @@ -0,0 +1,51 @@ +<?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="rwsdl" xml:lang="en-us"> +<title>Web Services Description Language (WSDL) reference</title> +<shortdesc>A WSDL document defines services as collections of network endpoints, +or ports. In WSDL, the abstract definition of endpoints and messages is separated +from their concrete network deployment or data format bindings. This allows +the reuse of abstract definitions: messages, which are abstract descriptions +of the data being exchanged, and port types which are abstract collections +of operations. </shortdesc> +<refbody> +<section><p>The concrete protocol and data format specifications for a particular +port type constitutes a reusable binding. A port is defined by associating +a network address with a reusable binding, and a collection of ports define +a service. Hence, a WSDL document uses the following elements in the definition +of network services:</p><ul> +<li> <uicontrol>Types</uicontrol>: a container for data type definitions using +some type system (such as XSD).</li> +<li> <uicontrol>Message</uicontrol>: an abstract, typed definition of the +data being communicated.</li> +<li> <uicontrol>Operation</uicontrol>: an abstract description of an action +supported by the service.</li> +<li> <uicontrol>Port Type</uicontrol>: an abstract set of operations supported +by one or more endpoints.</li> +<li> <uicontrol>Binding</uicontrol>: a concrete protocol and data format specification +for a particular port type. The binding is usually SOAP and the encoding and +data formatting regulations used (also known as the style) is usually literal +(this includes document/literal, and sometimes rpc/literal).</li> +<li> <uicontrol>Port</uicontrol>: a single endpoint defined as a combination +of a binding and a network address.</li> +<li> <uicontrol>Service</uicontrol>: a collection of related endpoints.</li> +</ul><p>For more information on WSDL, refer to </p><p><xref format="html" +href="http://www.w3.org/TR/wsdl" scope="external">www.w3.org/TR/wsdl</xref></p><p>The +various WSDL elements can be structured in many ways. It can be in one single +WSDL file or in mulitple WSDL files.</p></section> +</refbody> +<related-links> +<linklist><title>Related Concepts</title> +<link href="../concepts/cws.dita"></link> +<link href="../concepts/cwsdl.dita"></link> +</linklist> +<linklist><title>Related Tasks</title> +<link href="../tasks/toverws.dita" scope="peer"><linktext> Developing Web +services</linktext></link> +<link href="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.dita" +scope="peer"><linktext> Using the Web Services Explorer</linktext></link> +</linklist> +</related-links><?Pub Caret1?> +</reference> +<?Pub *0000002813?> diff --git a/docs/org.eclipse.jst.ws.doc.user/ref/rwsdl.html b/docs/org.eclipse.jst.ws.doc.user/ref/rwsdl.html index 14817f20e..05c7f867e 100644 --- a/docs/org.eclipse.jst.ws.doc.user/ref/rwsdl.html +++ b/docs/org.eclipse.jst.ws.doc.user/ref/rwsdl.html @@ -1,61 +1,78 @@ -<?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"> +<?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" /> +<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="Web Services Description Language (WSDL) reference" /> +<meta name="abstract" content="A WSDL document defines services as collections of network endpoints, or ports. In WSDL, the abstract definition of endpoints and messages is separated from their concrete network deployment or data format bindings. This allows the reuse of abstract definitions: messages, which are abstract descriptions of the data being exchanged, and port types which are abstract collections of operations." /> +<meta name="description" content="A WSDL document defines services as collections of network endpoints, or ports. In WSDL, the abstract definition of endpoints and messages is separated from their concrete network deployment or data format bindings. This allows the reuse of abstract definitions: messages, which are abstract descriptions of the data being exchanged, and port types which are abstract collections of operations." /> +<meta scheme="URI" name="DC.Relation" content="../concepts/cws.html" /> +<meta scheme="URI" name="DC.Relation" content="../concepts/cwsdl.html" /> +<meta scheme="URI" name="DC.Relation" content="../tasks/toverws.html" /> +<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.html" /> +<meta content="XHTML" name="DC.Format" /> +<meta content="rwsdl" 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>Web Services Description Language (WSDL) reference</title> </head> <body id="rwsdl"><a name="rwsdl"><!-- --></a> + <h1 class="topictitle1">Web Services Description Language (WSDL) reference</h1> + + <div><p>A WSDL document defines services as collections of network endpoints, or ports. In WSDL, the abstract definition of endpoints and messages is separated from their concrete network deployment or data format bindings. This allows the reuse of abstract definitions: messages, which are abstract descriptions of the data being exchanged, and port types which are abstract collections of operations. </p> + <div class="section"><p>The concrete protocol and data format specifications for a particular port type constitutes a reusable binding. A port is defined by associating a network address with a reusable binding, and a collection of ports define a service. Hence, a WSDL document uses the following elements in the definition of network services:</p> -<ul><li> <span class="uicontrol">Types</span>: a container for data type definitions using +<ul> +<li> <span class="uicontrol">Types</span>: a container for data type definitions using some type system (such as XSD).</li> + <li> <span class="uicontrol">Message</span>: an abstract, typed definition of the data being communicated.</li> + <li> <span class="uicontrol">Operation</span>: an abstract description of an action supported by the service.</li> + <li> <span class="uicontrol">Port Type</span>: an abstract set of operations supported by one or more endpoints.</li> + <li> <span class="uicontrol">Binding</span>: a concrete protocol and data format specification for a particular port type. The binding is usually SOAP and the encoding and data formatting regulations used (also known as the style) is usually literal (this includes document/literal, and sometimes rpc/literal).</li> + <li> <span class="uicontrol">Port</span>: a single endpoint defined as a combination of a binding and a network address.</li> + <li> <span class="uicontrol">Service</span>: a collection of related endpoints.</li> + </ul> <p>For more information on WSDL, refer to </p> <p><a href="http://www.w3.org/TR/wsdl" target="_blank">www.w3.org/TR/wsdl</a></p> +<p>The +various WSDL elements can be structured in many ways. It can be in one single +WSDL file or in mulitple WSDL files.</p> </div> -</div> -<div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cwsdl.html" title="Web Services Description Language (WSDL) is a standard specification for describing networked, XML-based services. It provides a simple way for service providers to describe the basic format of requests to their systems regardless of the underlying run-time implementation.">Web Services Description Language (WSDL)</a></div> + </div> +<div> <div class="linklist"><strong>Related Concepts</strong><br /> <div><a href="../concepts/cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> @@ -66,10 +83,7 @@ of a binding and a network address.</li> <div><a href="../tasks/toverws.html"> Developing Web services</a></div> <div><a href="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.html"> Using the Web Services Explorer</a></div></div> - -<div class="linklist"><strong>Related Reference</strong><br /> - -<div><a href="rsoapwsdl.html" title="When using the IBM SOAP run-time environment, by default the Web services tools in this product store the elements in three separate XML documents when generating Web services from Java beans, EJBs, and URLs: the WSDL binding document, the WSDL service document, and the WSDL interface document. By default XSD files are also generated if non-inline complex types are used by the interface. When generating Web services from DADX files, one WSDL document is generated.">WSDL files generated by the IBM SOAP run-time environment</a></div></div> </div> + </body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/ref/rwspref.dita b/docs/org.eclipse.jst.ws.doc.user/ref/rwspref.dita new file mode 100644 index 000000000..551af5a2e --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/ref/rwspref.dita @@ -0,0 +1,93 @@ +<?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="rwspref" xml:lang="en-us"> +<title>Web services preferences</title> +<refbody> +<section><p id="setprefmain">To set any of the Web services preferences, follow +these steps:<ol> +<li>Click <uicontrol>Window > Preferences</uicontrol> to open the Preferences +notebook.</li> +<li>Expand <uicontrol>Web services</uicontrol>, and click the preference +category that you want to set</li> +<li>Select the check boxes that you want to set as the default when creating +your Web service.</li> +<li>Click <uicontrol>OK</uicontrol> to apply the changes and close the Preferences +notebook.</li> +</ol>If you require more information on any of the options, select the option +and press <uicontrol>F1</uicontrol>.</p><p>Web services tools enable you +to define the following preferences:</p><dl><dlentry id="popupdialogselect"> +<dt>Popup Dialog Selection</dt> +<dd>The Dialogs preferences enable you to determine which dialog boxes that +you want to see when running popup actions. If you have disabled any of the +dialogs by selecting "Do not show this dialog again" on the first page of +a Web services wizard, you can undo your change by clearing the check box +beside the dialog that you have chosen to hide.</dd> +</dlentry><dlentry id="projtopology"> +<dt>Project Topology</dt> +<dd>The Project Topology preferences allow you to:<ul> +<li>Select the default client project type that the Web services wizards will +create when generating a Web service client. You can also set the order in +which the client project types will be listed in the wizard. Note that this +selection is simply a default and an alternate project type can be selected +in the wizard.</li> +<li>Select whether you want to generate the Web service and the Web service +client in the same EAR project or different EAR projects. Generating the service +and client into different EAR projects can reduce the chance of conflicts +that occur when both exist in a single EAR project, but uses more system resources.</li> +</ul></dd> +</dlentry><dlentry id="resourcemanagement"> +<dt>Resource Management</dt> +<dd>The Resource Management preferences enable you to determine the file and +folder creation and overwriting defaults that you want to use when creating +your Web service.</dd> +</dlentry><dlentry id="scenariodefaults"> +<dt>Scenario Defaults</dt> +<dd>The Scenario Defaults preferences enable you to set the following scenario +defaults that you want to use when creating your Web service:<ul> +<li>which type of Web service you want to be selected by default.</li> +<li>whether or not you want the Web service started by the wizard.</li> +<li>if you want the Web Services Explorer to launch by default so that you +can publish your Web service to a UDDI registry.</li> +<li>if you want to generate a proxy and the default type of proxy generated.</li> +<li>if you want the Web Services Explorer to launch by default so that you +can test the Web service.</li> +<li>if you want the Web service SOAP traffic routed through a TCP/IP monitor +so that you can monitor the SOAP packets and optionally test them for WS-I +compliance.</li> +</ul>Note that all these defaults can be overridden in the wizard.</dd> +</dlentry><dlentry id="serverandruntime"> +<dt>Server and Runtime</dt><?Pub Caret?> +<dd>Select the server, Web service run-time environment, and J2EE version +that you want selected by default in the Web services wizard. Note that all +these defaults can be overridden in the wizard.</dd> +</dlentry><dlentry id="testfacilitydefaults"> +<dt>Test Facility Defaults</dt> +<dd>can select whether to have the wizard automatically launch a test facility, +and you can select your preferred type of test facility</dd> +</dlentry><dlentry id="wsdlfiles"> +<dt>WSDL files</dt> +<dd>When creating a WSDL file in the WSDL editor, you can set the default +target namespace. If you do not select to change the default, your WSDL file +will have http://tempuri.org as its target namespace.</dd> +</dlentry><dlentry id="wsicompliance"> +<dt>WS-I Compliance</dt> +<dd>The WS-I Compliance preferences allow you to select your level of compliance +with the WS-I Simple SOAP Binding Profile (SSBP) and WS-I Attachement Profile +(AP). Note: if you change the level of WS-I compliance while WS-I incompliances +are listed in the Task view, the Task view will not be automatically updated. +The workspace must be revalidated before the warnings will be removed from +the Task view. For more information on WS-I, refer to: </dd> +</dlentry></dl></section> +</refbody> +<related-links> +<linklist><title>Related Concepts</title> +<link href="../concepts/cwsinwsa.dita"></link> +</linklist> +<linklist><title>Related Tasks</title> +<link href="../tasks/toverws.dita" scope="peer"><linktext> Developing Web +services</linktext></link> +</linklist> +</related-links> +</reference> +<?Pub *0000004954?> diff --git a/docs/org.eclipse.jst.ws.doc.user/ref/rwspref.html b/docs/org.eclipse.jst.ws.doc.user/ref/rwspref.html index 94e72b548..4ede98751 100644 --- a/docs/org.eclipse.jst.ws.doc.user/ref/rwspref.html +++ b/docs/org.eclipse.jst.ws.doc.user/ref/rwspref.html @@ -1,99 +1,141 @@ -<?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"> +<?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" /> +<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="Web services preferences" /> +<meta scheme="URI" name="DC.Relation" content="../concepts/cws.html" /> +<meta scheme="URI" name="DC.Relation" content="../concepts/cwsinwsa.html" /> +<meta scheme="URI" name="DC.Relation" content="../tasks/toverws.html" /> +<meta content="XHTML" name="DC.Format" /> +<meta content="rwspref" 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>Web services preferences</title> </head> <body id="rwspref"><a name="rwspref"><!-- --></a> + <h1 class="topictitle1">Web services preferences</h1> -<div><div class="section"><div class="p">To set any of the Web services preferences, follow these steps:<ol><li>Click <span class="uicontrol">Window > Preferences</span> to open the Preferences + +<div> +<div class="section"><div class="p" id="rwspref__setprefmain"><a name="rwspref__setprefmain"><!-- --></a>To set any of the Web services preferences, follow +these steps:<ol> +<li>Click <span class="uicontrol">Window > Preferences</span> to open the Preferences notebook.</li> -<li>Expand <span class="uicontrol">Web services</span> or <span class="uicontrol">Web and XML</span>, and click the preference + +<li>Expand <span class="uicontrol">Web services</span>, and click the preference category that you want to set</li> + <li>Select the check boxes that you want to set as the default when creating your Web service.</li> + <li>Click <span class="uicontrol">OK</span> to apply the changes and close the Preferences notebook.</li> + </ol> If you require more information on any of the options, select the option and press <span class="uicontrol">F1</span>.</div> <p>Web services tools enable you to define the following preferences:</p> -<dl><dt class="dlterm">Popup Dialog Selection</dt> +<dl> +<dt class="dlterm"><a name="rwspref__popupdialogselect"><!-- --></a>Popup Dialog Selection</dt> + <dd>The Dialogs preferences enable you to determine which dialog boxes that you want to see when running popup actions. If you have disabled any of the dialogs by selecting "Do not show this dialog again" on the first page of a Web services wizard, you can undo your change by clearing the check box beside the dialog that you have chosen to hide.</dd> -<dt class="dlterm">Profile Compliance and Validation</dt> -<dd>The Profile Compliance preferences allow you to select your level of compliance -with the WS-I Simple SOAP Binding Profile (SSBP) and WS-I Attachement Profile -(AP). Note: if you change the level of WS-I compliance while WS-I incompliances -are listed in the Task view, the Task view will not be automatically updated. -The workspace must be revalidated before the warnings will be removed from -the Task view. For more information on WS-I, refer to: <a href="http://www.ws-i.org/" target="_blank">http://www.ws-i.org/</a> -<p>For validation preferences, you can choose whether -or not WSDL files consumed by the Web services wizards are validated, and -whether or not the WSDL validation must complete before the wizard will move -to the next step.</p></dd> -<dt class="dlterm">Project Topology</dt> -<dd>The Project Topology preferences allow you to:<ul><li>Select the default client project type that the Web services wizards will + + +<dt class="dlterm"><a name="rwspref__projtopology"><!-- --></a>Project Topology</dt> + +<dd>The Project Topology preferences allow you to:<ul> +<li>Select the default client project type that the Web services wizards will create when generating a Web service client. You can also set the order in which the client project types will be listed in the wizard. Note that this selection is simply a default and an alternate project type can be selected in the wizard.</li> + <li>Select whether you want to generate the Web service and the Web service client in the same EAR project or different EAR projects. Generating the service and client into different EAR projects can reduce the chance of conflicts that occur when both exist in a single EAR project, but uses more system resources.</li> + </ul> </dd> -<dt class="dlterm">Resource Management</dt> + + +<dt class="dlterm"><a name="rwspref__resourcemanagement"><!-- --></a>Resource Management</dt> + <dd>The Resource Management preferences enable you to determine the file and folder creation and overwriting defaults that you want to use when creating your Web service.</dd> -<dt class="dlterm">Scenario Defaults</dt> + + +<dt class="dlterm"><a name="rwspref__scenariodefaults"><!-- --></a>Scenario Defaults</dt> + <dd>The Scenario Defaults preferences enable you to set the following scenario -defaults that you want to use when creating your Web service:<ul><li>which type of Web service you want to be selected by default.</li> +defaults that you want to use when creating your Web service:<ul> +<li>which type of Web service you want to be selected by default.</li> + <li>whether or not you want the Web service started by the wizard.</li> + <li>if you want the Web Services Explorer to launch by default so that you can publish your Web service to a UDDI registry.</li> + <li>if you want to generate a proxy and the default type of proxy generated.</li> + <li>if you want the Web Services Explorer to launch by default so that you can test the Web service.</li> + <li>if you want the Web service SOAP traffic routed through a TCP/IP monitor so that you can monitor the SOAP packets and optionally test them for WS-I compliance.</li> + </ul> Note that all these defaults can be overridden in the wizard.</dd> -<dt class="dlterm">Server and Runtime</dt> + + +<dt class="dlterm"><a name="rwspref__serverandruntime"><!-- --></a>Server and Runtime</dt> + <dd>Select the server, Web service run-time environment, and J2EE version that you want selected by default in the Web services wizard. Note that all these defaults can be overridden in the wizard.</dd> -<dt class="dlterm">Test Facility Defaults</dt> + + +<dt class="dlterm"><a name="rwspref__testfacilitydefaults"><!-- --></a>Test Facility Defaults</dt> + <dd>can select whether to have the wizard automatically launch a test facility, and you can select your preferred type of test facility</dd> -<dt class="dlterm">WSDL files</dt> + + +<dt class="dlterm"><a name="rwspref__wsdlfiles"><!-- --></a>WSDL files</dt> + <dd>When creating a WSDL file in the WSDL editor, you can set the default target namespace. If you do not select to change the default, your WSDL file will have http://tempuri.org as its target namespace.</dd> + + +<dt class="dlterm"><a name="rwspref__wsicompliance"><!-- --></a>WS-I Compliance</dt> + +<dd>The WS-I Compliance preferences allow you to select your level of compliance +with the WS-I Simple SOAP Binding Profile (SSBP) and WS-I Attachement Profile +(AP). Note: if you change the level of WS-I compliance while WS-I incompliances +are listed in the Task view, the Task view will not be automatically updated. +The workspace must be revalidated before the warnings will be removed from +the Task view. For more information on WS-I, refer to: </dd> + </dl> </div> + </div> + <div> <div class="familylinks"> <div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> @@ -101,12 +143,13 @@ will have http://tempuri.org as its target namespace.</dd> <div class="linklist"><strong>Related Concepts</strong><br /> -<div><a href="../concepts/cwsinwsa.html">Tools for Web services development</a></div></div> +<div><a href="../concepts/cwsinwsa.html" title="">Tools for Web services development</a></div></div> <div class="linklist"><strong>Related Tasks</strong><br /> <div><a href="../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.doc.user/tasks/toverws.dita b/docs/org.eclipse.jst.ws.doc.user/tasks/toverws.dita new file mode 100644 index 000000000..21a711115 --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/tasks/toverws.dita @@ -0,0 +1,49 @@ +<?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="toverws" xml:lang="en-us"><?Pub Caret?> +<title>Developing Web services</title> +<shortdesc>Use Web services tools to discover, create, and publish Web services +that are created from <tm tmclass="special" tmowner="Sun Microsystems, Inc." +tmtype="tm" trademark="Java">Java</tm> beans, enterprise beans, and WSDL files. +You can create of Web services using a top-down approach (which starts with +a WSDL file) or a bottom-up approach (which starts with a <tm tmclass="special" +tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> bean +or EJB).</shortdesc> +<taskbody> +<context><p>In this release, the development path that you would typically +follow to create and publish a Web service is as follows:</p></context> +<steps> +<step><cmd>Create a Web project.</cmd></step> +<step><cmd>Create or import an artifact to be turned into a Web service.</cmd> +</step> +<step><cmd>Create a Web service.</cmd></step> +<step><cmd>Publish a business entity.</cmd></step> +<step><cmd>Publish a Web service.</cmd></step> +</steps> +<result><p>For instructions on performing these tasks, refer to the list of +related topics at the end of this topic.</p><p>Web tools assist you in developing +Web applications that you can configure as a Web service. Web applications +are developed in a Web project, and Server tools allow you to use the server +test environment to test and deploy your Web services.</p></result> +</taskbody> +<related-links> +<linklist><title>Related Concepts</title> +<link href="../concepts/cws.dita" scope="local"><linktext>Web services overview</linktext> +</link> +<link href="../concepts/cwsinwsa.dita" scope="local"><linktext>Tools for Web +services development</linktext></link> +<link href="../concepts/cwsbtmup.dita" scope="local"><linktext>Creating bottom-up +Web services</linktext></link> +<link href="../concepts/cwstopdown.dita" scope="local"><linktext>Creating +top-down Web services</linktext></link> +</linklist> +<linklist><title>Related Tasks</title> +<link href="../../org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtwsdl.dita" scope="peer"> +</link> +<link href="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.dita" +scope="peer"></link> +</linklist> +</related-links> +</task> +<?Pub *0000002379?> diff --git a/docs/org.eclipse.jst.ws.doc.user/tasks/toverws.html b/docs/org.eclipse.jst.ws.doc.user/tasks/toverws.html index 35711074e..47a78dced 100644 --- a/docs/org.eclipse.jst.ws.doc.user/tasks/toverws.html +++ b/docs/org.eclipse.jst.ws.doc.user/tasks/toverws.html @@ -1,37 +1,58 @@ -<?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"> +<?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> -<!-- /******************************************************************************* - * 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" /> +<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="Developing Web services" /> +<meta name="abstract" content="Use Web services tools to discover, create, and publish Web services that are created from Java beans, enterprise beans, and WSDL files. You can create of Web services using a top-down approach (which starts with a WSDL file) or a bottom-up approach (which starts with a Java bean or EJB)." /> +<meta name="description" content="Use Web services tools to discover, create, and publish Web services that are created from Java beans, enterprise beans, and WSDL files. You can create of Web services using a top-down approach (which starts with a WSDL file) or a bottom-up approach (which starts with a Java bean or EJB)." /> +<meta scheme="URI" name="DC.Relation" content="../concepts/cws.html" /> +<meta scheme="URI" name="DC.Relation" content="../concepts/cwsinwsa.html" /> +<meta scheme="URI" name="DC.Relation" content="../concepts/cwsbtmup.html" /> +<meta scheme="URI" name="DC.Relation" content="../concepts/cwstopdown.html" /> +<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtwsdl.html" /> +<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.html" /> +<meta content="XHTML" name="DC.Format" /> +<meta content="toverws" 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>Developing Web services</title> </head> <body id="toverws"><a name="toverws"><!-- --></a> + + <h1 class="topictitle1">Developing Web services</h1> + + <div><p>Use Web services tools to discover, create, and publish Web services that are created from Javaâ„¢ beans, enterprise beans, and WSDL files. You can create of Web services using a top-down approach (which starts with a WSDL file) or a bottom-up approach (which starts with a Java bean or EJB).</p> + <div class="section"><p>In this release, the development path that you would typically follow to create and publish a Web service is as follows:</p> </div> -<ol><li><span>Create a Web project.</span></li> -<li><span>Create or import an artifact to be turned into a Web service.</span></li> + +<ol> +<li><span>Create a Web project.</span></li> + +<li><span>Create or import an artifact to be turned into a Web service.</span> +</li> + <li><span>Create a Web service.</span></li> + <li><span>Publish a business entity.</span></li> + <li><span>Publish a Web service.</span></li> + </ol> + <div class="section"><p>For instructions on performing these tasks, refer to the list of related topics at the end of this topic.</p> <p>Web tools assist you in developing @@ -39,12 +60,14 @@ Web applications that you can configure as a Web service. Web applications are developed in a Web project, and Server tools allow you to use the server test environment to test and deploy your Web services.</p> </div> + </div> + <div> <div class="linklist"><strong>Related Concepts</strong><br /> <div><a href="../concepts/cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> -<div><a href="../concepts/cwsinwsa.html">Tools for Web +<div><a href="../concepts/cwsinwsa.html" title="">Tools for Web services development</a></div> <div><a href="../concepts/cwsbtmup.html" title="Web services can be created using two methods: top-down development and bottom-up development. Bottom-up Web services development involves creating a Web service from a Java bean or enterprise bean.">Creating bottom-up Web services</a></div> @@ -53,7 +76,9 @@ top-down Web services</a></div></div> <div class="linklist"><strong>Related Tasks</strong><br /> -<div><a href="../../org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtwsdl.html">Creating a WSDL file</a></div> -<div><a href="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.html">Publishing Web services and business entities</a></div></div> -</div></body> +<div><a href="../../org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtwsdl.html">../../org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtwsdl.html</a></div> +<div><a href="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.html">../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.html</a></div></div> +</div> + +</body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/tasks/twsicomply.dita b/docs/org.eclipse.jst.ws.doc.user/tasks/twsicomply.dita new file mode 100644 index 000000000..66db9727c --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/tasks/twsicomply.dita @@ -0,0 +1,61 @@ +<?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="twsicomply" xml:lang="en-us"> +<title>Setting the level of WS-I compliance</title> +<shortdesc>The Web services WS-I validation tools support the level of WS-I +compliance outlined in the WS-I Basic Profile 1.1, the WS-I Simple SOAP Binding +Profile 1.0 (WS-I SSBP), and the WS-I Attachments Profile 1.0 (WS-I AP). You +can choose to make your Web service compliant or non-compliant, depending +on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols, +and secured Web services, are not WS-I compliant.</shortdesc> +<taskbody> +<context><p>You can set the level of compliance for either the Basic Profile +and the Simple SOAP Binding Profile, or for the Attachments Profile. You can +select from three levels of compliance with WS-I specifications:</p><ul> +<li>Require WS-I compliance - this level prevents you from creating a non-compliant +Web service.</li> +<li>Suggest WS-I compliance - this level allows you to create a non-compliant +Web service, but provides a visible warning stating how the service is non-compliant.</li> +<li>Ignore WS-I compliance - this level allows you to create a non-compliant +Web service and does not notify you of non-compliance.</li> +</ul><p>You can set the level of WS-I compliance at the workspace level, or +at the project level.</p></context> +</taskbody> +<task id="sdgfsdgs" xml:lang="en-us"> +<title>Set the level of WS-I compliance for the workspace</title> +<taskbody> +<context><p>To set the level of WS-I compliance for the workspace:</p></context> +<steps> +<step><cmd>From the <b>Window</b> menu, select <b>Preferences</b>.</cmd> +</step> +<step><cmd>Select <b>Web Services</b> from the component tree on the left-hand +side of the panel.</cmd></step> +<step><cmd>Under Profile Compliance and Validation, select the level of compliance +you want from the drop-down lists.</cmd></step> +<step><cmd>Click <b>Apply</b>, then click <b>OK</b>.</cmd></step> +</steps> +</taskbody> +</task> +<task id="xvgdsgfsg" xml:lang="en-us"> +<title>Set the level of WS-I compliance for a project</title> +<taskbody> +<context><p>To set the level of WS-I compliance for a project:</p></context> +<steps> +<step><cmd>In the Project Navigator, right click and select <b>Properties</b>.</cmd> +</step> +<step><cmd>Select <b>WS-I Compliance</b> from the component tree on the left-hand +side of the panel.</cmd></step> +<step><cmd>Under WS-I compliance, select the level of compliance you want +from the drop-down lists, or select to have the project share the same level +of WS-I compliance as the workspace</cmd></step> +<step><cmd>Click <b>Apply</b>, then click <b>OK</b>.</cmd></step> +</steps> +</taskbody> +<related-links> +<linklist><title>Related Concepts</title> +<link href="../concepts/cwsiover.dita" scope="local"></link> +</linklist> +</related-links> +</task> +</task> diff --git a/docs/org.eclipse.jst.ws.doc.user/tasks/twsicomply.html b/docs/org.eclipse.jst.ws.doc.user/tasks/twsicomply.html index fe21e4d44..d46a62fbd 100644 --- a/docs/org.eclipse.jst.ws.doc.user/tasks/twsicomply.html +++ b/docs/org.eclipse.jst.ws.doc.user/tasks/twsicomply.html @@ -1,77 +1,111 @@ -<?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"> +<?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" /> +<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="Setting the level of WS-I compliance" /> +<meta name="abstract" content="The Web services WS-I validation tools support the level of WS-I compliance outlined in the WS-I Basic Profile 1.1, the WS-I Simple SOAP Binding Profile 1.0 (WS-I SSBP), and the WS-I Attachments Profile 1.0 (WS-I AP). You can choose to make your Web service compliant or non-compliant, depending on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols, and secured Web services, are not WS-I compliant." /> +<meta name="description" content="The Web services WS-I validation tools support the level of WS-I compliance outlined in the WS-I Basic Profile 1.1, the WS-I Simple SOAP Binding Profile 1.0 (WS-I SSBP), and the WS-I Attachments Profile 1.0 (WS-I AP). You can choose to make your Web service compliant or non-compliant, depending on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols, and secured Web services, are not WS-I compliant." /> +<meta content="XHTML" name="DC.Format" /> +<meta content="twsicomply" name="DC.Identifier" /> +<meta content="en-us" name="DC.Language" /> +<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> <title>Setting the level of WS-I compliance</title> </head> <body id="twsicomply"><a name="twsicomply"><!-- --></a> + <h1 class="topictitle1">Setting the level of WS-I compliance</h1> + + <div><p>The Web services WS-I validation tools support the level of WS-I compliance outlined in the WS-I Basic Profile 1.1, the WS-I Simple SOAP Binding Profile 1.0 (WS-I SSBP), and the WS-I Attachments Profile 1.0 (WS-I AP). You can choose to make your Web service compliant or non-compliant, depending on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols, and secured Web services, are not WS-I compliant.</p> + <div class="section"><p>You can set the level of compliance for either the Basic Profile and the Simple SOAP Binding Profile, or for the Attachments Profile. You can select from three levels of compliance with WS-I specifications:</p> -<ul><li>Require WS-I compliance - this level prevents you from creating a non-compliant +<ul> +<li>Require WS-I compliance - this level prevents you from creating a non-compliant Web service.</li> + <li>Suggest WS-I compliance - this level allows you to create a non-compliant Web service, but provides a visible warning stating how the service is non-compliant.</li> + <li>Ignore WS-I compliance - this level allows you to create a non-compliant Web service and does not notify you of non-compliance.</li> + </ul> -<p>You can set the level of WS-I compliance at the workspace -level, or at the project level.</p> +<p>You can set the level of WS-I compliance at the workspace level, or +at the project level.</p> </div> + </div> + +<div class="nested1" xml:lang="en-us" id="sdgfsdgs"><a name="sdgfsdgs"><!-- --></a> +<h2 class="topictitle2">Set the level of WS-I compliance for the workspace</h2> + <div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cwsiover.html" title="WS-I is an organization designed to promote Web service interoperability across platforms, operating systems, and programming languages.">Web services interoperability (WS-I)</a></div> +<div class="section"><p>To set the level of WS-I compliance for the workspace:</p> </div> -</div><div class="nested1" xml:lang="en-us" id="sdgfsdgs"><a name="sdgfsdgs"><!-- --></a><h2 class="topictitle2">Set the level of WS-I compliance for the workspace</h2> -<div><div class="section"><p>To set the level of WS-I compliance for the workspace:</p> -</div> -<ol><li><span>From the <strong>Window</strong> menu, select <strong>Preferences</strong>.</span></li> + +<ol> +<li><span>From the <strong>Window</strong> menu, select <strong>Preferences</strong>.</span> +</li> + <li><span>Select <strong>Web Services</strong> from the component tree on the left-hand side of the panel.</span></li> -<li><span>Under Profile Compliance and Validation, select the level of compliance you want -from the drop-down lists.</span></li> + +<li><span>Under Profile Compliance and Validation, select the level of compliance +you want from the drop-down lists.</span></li> + <li><span>Click <strong>Apply</strong>, then click <strong>OK</strong>.</span></li> + </ol> + </div> + </div> -<div class="nested1" xml:lang="en-us" id="xvgdsgfsg"><a name="xvgdsgfsg"><!-- --></a><h2 class="topictitle2">Set the level of WS-I compliance for a project</h2> -<div><div class="section"><p>To set the level of WS-I compliance for a project:</p> + +<div class="nested1" xml:lang="en-us" id="xvgdsgfsg"><a name="xvgdsgfsg"><!-- --></a> +<h2 class="topictitle2">Set the level of WS-I compliance for a project</h2> + +<div> +<div class="section"><p>To set the level of WS-I compliance for a project:</p> </div> -<ol><li><span>In the Project Navigator, right click and select <strong>Properties</strong>.</span></li> -<li><span>Select <strong>Profile Compliance and Validation</strong> from the component tree on the left-hand + +<ol> +<li><span>In the Project Navigator, right click and select <strong>Properties</strong>.</span> +</li> + +<li><span>Select <strong>WS-I Compliance</strong> from the component tree on the left-hand side of the panel.</span></li> -<li><span>Select the level of compliance you want + +<li><span>Under WS-I compliance, select the level of compliance you want from the drop-down lists, or select to have the project share the same level of WS-I compliance as the workspace</span></li> + <li><span>Click <strong>Apply</strong>, then click <strong>OK</strong>.</span></li> + </ol> + </div> + <div> <div class="linklist"><strong>Related Concepts</strong><br /> <div><a href="../concepts/cwsiover.html" title="WS-I is an organization designed to promote Web service interoperability across platforms, operating systems, and programming languages.">Web services interoperability (WS-I)</a></div></div> -</div></div> +</div> +</div> + + </body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/webservice_toc.ditamap b/docs/org.eclipse.jst.ws.doc.user/webservice_toc.ditamap new file mode 100644 index 000000000..b5db6a928 --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/webservice_toc.ditamap @@ -0,0 +1,89 @@ +<?xml version="1.0" encoding="utf-8"?> +<!--Arbortext, Inc., 1988-2005, v.4002--> +<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd"> +<map id="wsmaintoc" title="wsmaintoc"> +<topicref href="concepts/cws.dita" navtitle="Web services development"> +<topicref href="concepts/cwsstandards.dita" navtitle="Web services standards" +scope="local"> +<topicref href="concepts/cwsdl.dita" navtitle="Web Services Description Language (WSDL)"> +<topicref href="ref/rwsdl.dita" navtitle="Web Services Description Language (WSDL) reference"> +</topicref> +</topicref> +<topicref href="concepts/csoap.dita" navtitle="SOAP"></topicref> +<topicref href="../org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cuddi.dita" +navtitle="Universal Description, Discovery, and Integration (UDDI)" scope="peer"> +<topicref href="../org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cwsdlud.dita" +navtitle="Relationship between UDDI and WSDL" scope="peer"></topicref> +</topicref> +<topicref href="concepts/cwsil.dita" navtitle="Web Services Inspection Language (WSIL)"> +<topicref href="concepts/cwsilud.dita" navtitle="Relationship between UDDI and WSIL"> +</topicref> +</topicref> +<topicref href="concepts/cjaxrpc.dita" navtitle="JAX-RPC"></topicref> +<topicref href="concepts/cjsr109.dita" navtitle="JSR 109 and JSR 921"></topicref> +</topicref> +<topicref navtitle="Workspace and tools"> +<topicref href="concepts/cwsinwsa.dita" navtitle="Tools for Web services development" +scope="local"> +<topicref href="../org.eclipse.jst.ws.axis.ui.doc.user/concepts/caxistover.dita" +navtitle="Creating Web services with the Apache Axis run-time environment" +scope="peer"></topicref> +</topicref> +<topicref navtitle="Configuring your workspace"> +<topicref href="ref/rwspref.dita" navtitle="Setting Web services preferences" +scope="local"></topicref> +<topicref href="concepts/cwsiover.dita" navtitle="WS-I compliance" scope="local"> +<topicref href="tasks/twsicomply.dita" navtitle="Setting the level of WS-I compliance" +scope="local"></topicref> +</topicref> +<topicref href="../org.eclipse.jst.ws.axis.ui.doc.user/tasks/ttomcatserv.dita" +navtitle="Creating an Apache Tomcat server and Web project" scope="peer"> +</topicref> +</topicref> +</topicref> +</topicref> +<topicref navtitle="Importing and creating resources used by Web services"> +<navref mapref="../org.eclipse.wst.wsdl.ui.doc.user/wswsdleditort_toc.ditamap"/> +</topicref> +<topicref href="/tasks/toverws.dita" navtitle="Creating Web services" scope="peer"> +<topicref href="concepts/cwstopdown.dita" navtitle="Top-down Web services development" +scope="local"> +<topicgroup> +<topicref href="../org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsklwsdla.dita" +navtitle="Creating a Web service and Java bean skeleton from WSDL" scope="peer"> +</topicref> +</topicgroup> +</topicref> +<topicref href="concepts/cwsbtmup.dita" navtitle="Bottom-up Web services development" +scope="local"> +<topicgroup> +<topicref href="../org.eclipse.jst.ws.axis.ui.doc.user/tasks/twsbeana.dita" +navtitle="Creating a Web service from a Java bean" scope="peer"></topicref> +</topicgroup> +</topicref> +<topicref navtitle="Creating Web service clients"> +<topicref href="../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tdiscov.dita" +navtitle="Discovering and importing a Web service" scope="peer"></topicref> +<topicref href="../org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsampappa.dita" +navtitle="Generating a Java client proxy from a WSDL document using the Axis run-time environment" +scope="peer"></topicref> +</topicref> +</topicref> +<topicref navtitle="Testing and validating Web services"> +<topicref href="../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/ttestwsdl.dita" +navtitle="Testing WSDL documents and Web services with the WSDL Explorer" +scope="peer"></topicref> +<topicref href="../org.eclipse.wst.wsi.ui.doc.user/tasks/twsdlval.dita" navtitle="Validating WSDL" +scope="peer"></topicref> +<topicref href="../org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.dita" navtitle="Testing Web services with the TCP/IP Monitor" +scope="peer"> +<topicref href="../org.eclipse.wst.wsi.ui.doc.user/tasks/twsival.dita" navtitle="Validating WS-I compliance of Web service SOAP traffic" +scope="peer"></topicref> +</topicref> +</topicref> +<topicref navtitle="Publishing Web services"> +<navref mapref="../org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptiont_toc.ditamap"/> +<topicref href="../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tgenwsil.dita" +navtitle="Generating WSIL" scope="peer"></topicref> +</topicref> +</map> diff --git a/docs/org.eclipse.jst.ws.doc.user/webservice_toc.xml b/docs/org.eclipse.jst.ws.doc.user/webservice_toc.xml index 0a179213e..8766626c9 100644 --- a/docs/org.eclipse.jst.ws.doc.user/webservice_toc.xml +++ b/docs/org.eclipse.jst.ws.doc.user/webservice_toc.xml @@ -1,68 +1,60 @@ -<?xml version="1.0" encoding="utf-8"?> +<?xml version="1.0" encoding="UTF-8"?> + <?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 - *******************************************************************************/ --> + <toc label="wsmaintoc" topic="concepts/cws.html"> - <topic label="Web services overview" href="concepts/cws.html"> - <topic label="Web services standards" href="concepts/cwsstandards.html"> - <topic label="Web Services Description Language (WSDL)" href="concepts/cwsdl.html"> - <topic label="Web Services Description Language (WSDL) reference" href="ref/rwsdl.html"/> - </topic> - <topic label="Simple Object Access Protocol (SOAP)" href="concepts/csoap.html"/> - <topic label="Universal Description, Discovery, and Integration (UDDI)" href="../org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cuddi.html"> - <topic label="Relationship between UDDI and WSDL" href="../org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cwsdlud.html"/> - </topic> - <topic label="Web Services Inspection Language (WSIL)" href="concepts/cwsil.html"> - <topic label="Relationship between UDDI and WSIL" href="concepts/cwsilud.html"/> - </topic> - <topic label="JAX-RPC" href="concepts/cjaxrpc.html"/> - <topic label="JSR 109 and JSR 921- Implementing Enterprise Web services" href="concepts/cjsr109.html"/> - </topic> - <topic label="Workspace and tools"> - <topic label="Tools for Web services development" href="concepts/cwsinwsa.html"> - <topic label="Creating Web services with the Apache Axis run-time environment" href="../org.eclipse.jst.ws.axis.ui.doc.user/concepts/caxistover.html"/> - </topic> - <topic label="Configuring your workspace"> - <topic label="Web services preferences" href="ref/rwspref.html"/> - <topic label="Web services interoperability (WS-I)" href="concepts/cwsiover.html"> - <topic label="Setting the level of WS-I compliance" href="tasks/twsicomply.html"/> - </topic> - <topic label="Creating an Apache Tomcat server and Web project" href="../org.eclipse.jst.ws.axis.ui.doc.user/tasks/ttomcatserv.html"/> - </topic> - </topic> - </topic> - <topic label="Importing and creating resources used by Web services"> - <link toc="../org.eclipse.wst.wsdl.ui.doc.user/wswsdleditort_toc.xml"/> - </topic> - <topic label="Creating Web services" href="tasks/toverws.html"> - <topic label="Creating top-down Web services" href="concepts/cwstopdown.html"> - <topic label="Creating a Web service and Java bean skeleton from WSDL" href="../org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsklwsdla.html"/> - </topic> - <topic label="Creating bottom-up Web services" href="concepts/cwsbtmup.html"> - <topic label="Creating a Web service from a Java bean" href="../org.eclipse.jst.ws.axis.ui.doc.user/tasks/twsbeana.html"/> - </topic> - <topic label="Creating Web service clients"> - <topic label="Discovering and importing a Web service" href="../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tdiscov.html"/> - <topic label="Generating a Java client proxy from a WSDL document using the Axis run-time environment" href="../org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsampappa.html"/> - </topic> - </topic> - <topic label="Testing and validating Web services"> - <topic label="Testing WSDL documents and Web services with the WSDL Explorer" href="../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/ttestwsdl.html"/> - <topic label="Validating WSDL" href="../org.eclipse.wst.wsi.ui.doc.user/tasks/twsdlval.html"/> - <topic label="Testing Web services with the TCP/IP Monitor" href="../org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.html"> - <topic label="Validating WS-I compliance of Web service SOAP traffic" href="../org.eclipse.wst.wsi.ui.doc.user/tasks/twsival.html"/> - </topic> - </topic> - <topic label="Publishing Web services"> - <link toc="../org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptiont_toc.xml"/> - <topic label="Generating WSIL" href="../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tgenwsil.html"/> - </topic> -</toc>
\ No newline at end of file +<topic label="Web services overview" href="concepts/cws.html"> +<topic label="Web services standards" href="concepts/cwsstandards.html"> +<topic label="Web Services Description Language (WSDL)" href="concepts/cwsdl.html"> +<topic label="Web Services Description Language (WSDL) reference" href="ref/rwsdl.html"/> +</topic> +<topic label="SOAP" href="concepts/csoap.html"/> +<topic label="Universal Description, Discovery, and Integration (UDDI)" href="../org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cuddi.html"> +<topic label="Relationship between UDDI and WSDL" href="../org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cwsdlud.html"/> +</topic> +<topic label="Web Services Inspection Language (WSIL)" href="concepts/cwsil.html"> +<topic label="Relationship between UDDI and WSIL" href="concepts/cwsilud.html"/> +</topic> +<topic label="JAX-RPC" href="concepts/cjaxrpc.html"/> +<topic label="JSR 109 and JSR 921- Implementing Enterprise Web services" href="concepts/cjsr109.html"/> +</topic> +<topic label="Workspace and tools"> +<topic label="Tools for Web services development" href="concepts/cwsinwsa.html"> +<topic label="Creating Web services with the Apache Axis run-time environment" href="../org.eclipse.jst.ws.axis.ui.doc.user/concepts/caxistover.html"/> +</topic> +<topic label="Configuring your workspace"> +<topic label="Web services preferences" href="ref/rwspref.html"/> +<topic label="Web services interoperability (WS-I)" href="concepts/cwsiover.html"> +<topic label="Setting the level of WS-I compliance" href="tasks/twsicomply.html"/> +</topic> +<topic label="Creating an Apache Tomcat server and Web project" href="../org.eclipse.jst.ws.axis.ui.doc.user/tasks/ttomcatserv.html"/> +</topic> +</topic> +</topic> +<topic label="Importing and creating resources used by Web services"> +<link toc="../org.eclipse.wst.wsdl.ui.doc.user/wswsdleditort_toc.xml"/> +</topic> +<topic label="Creating Web services" href="/tasks/toverws.html"> +<topic label="Creating top-down Web services" href="concepts/cwstopdown.html"> +<topic label="Creating a Web service and Java bean skeleton from WSDL" href="../org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsklwsdla.html"/> +</topic> +<topic label="Creating bottom-up Web services" href="concepts/cwsbtmup.html"> +<topic label="Creating a Web service from a Java bean" href="../org.eclipse.jst.ws.axis.ui.doc.user/tasks/twsbeana.html"/> +</topic> +<topic label="Creating Web service clients"> +<topic label="Discovering and importing a Web service" href="../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tdiscov.html"/> +<topic label="Generating a Java client proxy from a WSDL document using the Axis run-time environment" href="../org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsampappa.html"/> +</topic> +</topic> +<topic label="Testing and validating Web services"> +<topic label="Testing WSDL documents and Web services with the WSDL Explorer" href="../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/ttestwsdl.html"/> +<topic label="Validating WSDL" href="../org.eclipse.wst.wsi.ui.doc.user/tasks/twsdlval.html"/> +<topic label="Testing Web services with the TCP/IP Monitor" href="../org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.html"> +<topic label="Validating WS-I compliance of Web service SOAP traffic" href="../org.eclipse.wst.wsi.ui.doc.user/tasks/twsival.html"/> +</topic> +</topic> +<topic label="Publishing Web services"> +<link toc="../org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptiont_toc.xml"/> +<topic label="Generating WSIL" href="../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tgenwsil.html"/> +</topic> +</toc> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/.cvsignore b/docs/org.eclipse.wst.wsdl.ui.doc.user/.cvsignore index dfce8dd02..9bf87299c 100644 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/.cvsignore +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/.cvsignore @@ -1,2 +1,3 @@ -build.xml org.eclipse.wst.wsdl.ui.doc.user_1.0.0.jar +bak +temp diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/build.xml b/docs/org.eclipse.wst.wsdl.ui.doc.user/build.xml new file mode 100644 index 000000000..ef2ead0a7 --- /dev/null +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/build.xml @@ -0,0 +1,59 @@ +<?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="wswsdleditort_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.wst.wsdl.ui.doc.user/concepts/cwsdled.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/concepts/cwsdled.dita new file mode 100644 index 000000000..d17fcafca --- /dev/null +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/concepts/cwsdled.dita @@ -0,0 +1,56 @@ +<?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="cwsdled" xml:lang="en-us"><?Pub Caret1?> +<title>Editing WSDL files with the WSDL Editor</title> +<titlealts> +<searchtitle>Editing WSDL files with the WSDL editor</searchtitle> +</titlealts> +<shortdesc>The WSDL editor allows you to easily and graphically create, modify, +view, and validate WSDL files.</shortdesc> +<conbody> +<p>Using the WSDL editor, you can do the following:</p> +<ul> +<li>Create new WSDL files</li> +<li>Validate and edit WSDL files</li> +<li>Create and delete: <ul> +<li>services, which are used to aggregate a set of related ports. These are +the root elements of all WSDL files.</li> +<li>ports, which specify an address for a binding, thus defining a single +communication endpoint.</li> +<li>bindings, which specify concrete protocol and data format specifications +for the operations and messages defined by a particular port type.</li> +<li>port types, which are a set of abstract operations. Each operation refers +to an input message and output messages.</li> +<li>operations, which refer to input and output messages</li> +<li>messages, which represent an abstract definition of the data being transmitted. +A message consists of logical parts, each of which is associated with a definition +within some type system.</li> +<li>parts, which are a flexible mechanism for describing the logical abstract +content of a message</li> +<li>types, which describe all the data types used between the client and server. +WSDL is not tied exclusively to a specific typing system, but it uses the +W3C XML Schema specification as its default choice.</li> +<li>import statements, which are used to associate a namespace with a document +location </li> +</ul></li> +<li>Import existing WSDL files for structured viewing</li> +<li>Generate documentation from a WSDL document.</li> +</ul> +<p>The WSDL support in the WSDL editor is based on the W3C <xref format="html" +href="http://www.w3.org/TR/wsdl" scope="external">Web Services Description +Language (WSDL) 1.1</xref>. The WSDL specification from the W3C Web site is +also used for validation. </p> +</conbody> +<related-links> +<linklist><title>Related concepts</title> +<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.dita" scope="peer"> +<linktext>WSDL</linktext></link> +</linklist> +<linklist><title>Related tasks</title> +<link href="../tasks/tcrtwsdl.dita" scope="local"></link> +<link href="../tasks/tedtwsdl.dita" scope="local"></link> +</linklist> +</related-links> +</concept> +<?Pub *0000002624?> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/concepts/cwsdled.html b/docs/org.eclipse.wst.wsdl.ui.doc.user/concepts/cwsdled.html index b853ce3fb..92dda0b40 100644 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/concepts/cwsdled.html +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/concepts/cwsdled.html @@ -1,65 +1,86 @@ -<?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> +<?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> -<!-- /******************************************************************************* - * 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" /> +<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="Editing WSDL files with the WSDL Editor" /> +<meta name="abstract" content="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files." /> +<meta name="description" content="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files." /> +<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.html" /> +<meta scheme="URI" name="DC.Relation" content="../tasks/tcrtwsdl.html" /> +<meta scheme="URI" name="DC.Relation" content="../tasks/tedtwsdl.html" /> +<meta content="XHTML" name="DC.Format" /> +<meta content="cwsdled" 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>Editing WSDL files with the WSDL editor</title> </head> <body id="cwsdled"><a name="cwsdled"><!-- --></a> + <h1 class="topictitle1">Editing WSDL files with the WSDL Editor</h1> + + + <div><p>The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.</p> + <p>Using the WSDL editor, you can do the following:</p> -<ul><li>Create new WSDL files</li> + +<ul> +<li>Create new WSDL files</li> + <li>Validate and edit WSDL files</li> -<li>Create and delete: <ul><li>services, which are used to aggregate a set of related ports. These are + +<li>Create and delete: <ul> +<li>services, which are used to aggregate a set of related ports. These are the root elements of all WSDL files.</li> + <li>ports, which specify an address for a binding, thus defining a single communication endpoint.</li> + <li>bindings, which specify concrete protocol and data format specifications for the operations and messages defined by a particular port type.</li> + <li>port types, which are a set of abstract operations. Each operation refers to an input message and output messages.</li> + <li>operations, which refer to input and output messages</li> + <li>messages, which represent an abstract definition of the data being transmitted. A message consists of logical parts, each of which is associated with a definition within some type system.</li> + <li>parts, which are a flexible mechanism for describing the logical abstract content of a message</li> + <li>types, which describe all the data types used between the client and server. WSDL is not tied exclusively to a specific typing system, but it uses the W3C XML Schema specification as its default choice.</li> + <li>import statements, which are used to associate a namespace with a document location </li> + </ul> </li> + <li>Import existing WSDL files for structured viewing</li> + <li>Generate documentation from a WSDL document.</li> + </ul> -<p>The WSDL support in the WSDL editor is based on the W3C <a href="http://www.w3.org/TR/wsdl" target="_blank">Web Services Description -Language (WSDL) 1.1</a>. The WSDL specification from the W3C Web site is -also used for validation. </p> + +<p>The WSDL support in the WSDL editor is based on the W3C <a href="http://www.w3.org/TR/wsdl" target="_blank">Web Services Description Language (WSDL) 1.1</a>. The WSDL specification from the W3C Web site is +also used for validation. </p> + </div> -<div> -<ul class="ullinks"> -<li class="ulchildlink"><strong><a href="../tasks/tedtwsdl.html">Editing WSDL files</a></strong><br /> -Once you have created a WSDL file, you can edit it in the WSDL -editor. You can also import WSDL files you have created outside Rational Developer -products into the workbench and edit them in the WSDL editor.</li> -</ul> +<div> <div class="linklist"><strong>Related concepts</strong><br /> <div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.html">WSDL</a></div></div> @@ -67,7 +88,8 @@ products into the workbench and edit them in the WSDL editor.</li> <div class="linklist"><strong>Related tasks</strong><br /> <div><a href="../tasks/tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div> -<div><a href="../tasks/tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created outside Rational Developer products into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> +<div><a href="../tasks/tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> </div> + </body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/myplugin.xml b/docs/org.eclipse.wst.wsdl.ui.doc.user/myplugin.xml new file mode 100644 index 000000000..ada66bcaa --- /dev/null +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/myplugin.xml @@ -0,0 +1,28 @@ +<?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 + *******************************************************************************/ --> +<!-- ================================================= --> +<!-- This is the plugin for declaring the help --> +<!-- contributions for using the tool. --> +<!-- ================================================= --> + +<plugin> + +<extension point="org.eclipse.help.toc"> + <toc file="wswsdleditort_toc.xml"/> + <toc file="wswsdleditorc_toc.xml"/> + +</extension> + + +</plugin>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/org.eclipse.wst.wsdl.ui.doc.user.maplist b/docs/org.eclipse.wst.wsdl.ui.doc.user/org.eclipse.wst.wsdl.ui.doc.user.maplist new file mode 100644 index 000000000..ddeb99f96 --- /dev/null +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/org.eclipse.wst.wsdl.ui.doc.user.maplist @@ -0,0 +1,10 @@ +<maplist version="3.6.2"> + <nav> + <map file="wswsdleditort_toc.ditamap"/> + <map file="wswsdleditorc_toc.ditamap"/> + </nav> + <link> + <map file="wswsdleditort_toc.ditamap"/> + <map file="wswsdleditorc_toc.ditamap"/> + </link> +</maplist> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddmess.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddmess.dita new file mode 100644 index 000000000..1c3133133 --- /dev/null +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddmess.dita @@ -0,0 +1,59 @@ +<?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="taddmess" xml:lang="en-us"> +<title>Adding a message</title> +<shortdesc>Messages represent an abstract definition of the data being transmitted. +A message consists of logical parts, each of which is associated with a definition +within some type system. WSDL messages are top level objects that can be referenced +by an operation's input, output and fault elements (within a port type).</shortdesc> +<taskbody> +<context><p>If you want to create a new message for your input, output, or +fault element, follow these steps: </p></context> +<steps> +<step><cmd>In the Graph view, right-click your input, output, or fault element +and click <b>Set Message.</b></cmd></step> +<step><cmd>Select the <b>Create a new message</b> radio button.</cmd></step> +<step><cmd>Type the name of the message in dialog.</cmd><info>This name should +be a unique amongst all messages defined within the enclosing WSDL document. +Click <b>OK</b>.</info></step> +<step><cmd>The new message will appear in the graph view within the messages +section.</cmd><info>An line should be visible connecting the input, output +or fault with the message.</info></step> +</steps> +<result><p> <b>Note</b>: Messages are referenced within a port type (specifically +by an operation's input, output and fault objects). The input, output and +fault objects within a binding do not reference messages. Hence you cannot +create a new message by right clicking on a input, output, or fault within +a binding (these are also known as binding input, binding output and binding +faults).</p><p> <b>Tip</b>: You can also create a new message for your input, +output, or fault element using the Outline view. Under the <b>Port Types</b> +folder, right-click your element and click <b>Set Message > Create a new +message</b>. Your message will appear in the Outline view under the <b>Messages</b> folder. </p><p>If +you want to reuse a message for your input, output, or fault element, follow +these steps: </p><ol> +<li>In the Graph view, right-click your input, output, or fault element and +click <b>Set Message.</b></li> +<li>Press the <uicontrol>Select an existing message</uicontrol> radio button.</li> +<li>The existing messages will be listed. Select one and click <b>Finish</b>.</li> +</ol><p>If you want to import an existing message for your input, output, +or fault element, follow these steps:</p><ol> +<li>In the Graph view, right-click your input, output, or fault element and +click <b>Set Message.</b></li> +<li>Select the <b>Import message from a file</b> check box. Click <b>Browse</b>.</li> +<li>Select the file that contains the message you want to use. Click <b>OK</b>.</li> +<li>The messages in the file will be listed. Select one and click <b>Finish</b>.</li> +</ol><p>You can now add parts to your message. Parts are a flexible mechanism +for describing the logical abstract content of a message.</p></result> +</taskbody> +<related-links> +<linklist><title>Related concepts</title><?Pub Caret?> +<link href="../concepts/cwsdled.dita" scope="local"></link> +</linklist> +<linklist><title>Related tasks</title> +<link href="tcrtwsdl.dita" scope="local"></link> +<link href="tedtwsdl.dita" scope="local"></link> +</linklist> +</related-links> +</task> +<?Pub *0000003378?> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddmess.html b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddmess.html index 742d36e69..769aa0d52 100644 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddmess.html +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddmess.html @@ -1,41 +1,57 @@ -<?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> +<?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> -<!-- /******************************************************************************* - * 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" /> +<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 message" /> +<meta name="abstract" content="Messages represent an abstract definition of the data being transmitted. A message consists of logical parts, each of which is associated with a definition within some type system. WSDL messages are top level objects that can be referenced by an operation's input, output and fault elements (within a port type)." /> +<meta name="description" content="Messages represent an abstract definition of the data being transmitted. A message consists of logical parts, each of which is associated with a definition within some type system. WSDL messages are top level objects that can be referenced by an operation's input, output and fault elements (within a port type)." /> +<meta scheme="URI" name="DC.Relation" content="../tasks/tedtwsdl.html" /> +<meta scheme="URI" name="DC.Relation" content="../concepts/cwsdled.html" /> +<meta scheme="URI" name="DC.Relation" content="tcrtwsdl.html" /> +<meta scheme="URI" name="DC.Relation" content="tedtwsdl.html" /> +<meta content="XHTML" name="DC.Format" /> +<meta content="taddmess" 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 message</title> </head> <body id="taddmess"><a name="taddmess"><!-- --></a> + <h1 class="topictitle1">Adding a message</h1> + + <div><p>Messages represent an abstract definition of the data being transmitted. A message consists of logical parts, each of which is associated with a definition within some type system. WSDL messages are top level objects that can be referenced by an operation's input, output and fault elements (within a port type).</p> + <div class="section"><p>If you want to create a new message for your input, output, or fault element, follow these steps: </p> </div> -<ol><li class="stepexpand"><span>In the Graph view, right-click your input, output, or fault element + +<ol> +<li class="stepexpand"><span>In the Graph view, right-click your input, output, or fault element and click <strong>Set Message.</strong></span></li> + <li class="stepexpand"><span>Select the <strong>Create a new message</strong> radio button.</span></li> + <li class="stepexpand"><span>Type the name of the message in dialog.</span> This name should be a unique amongst all messages defined within the enclosing WSDL document. Click <strong>OK</strong>.</li> + <li class="stepexpand"><span>The new message will appear in the graph view within the messages section.</span> An line should be visible connecting the input, output or fault with the message.</li> + </ol> + <div class="section"><p> <strong>Note</strong>: Messages are referenced within a port type (specifically by an operation's input, output and fault objects). The input, output and fault objects within a binding do not reference messages. Hence you cannot @@ -45,30 +61,41 @@ faults).</p> <p> <strong>Tip</strong>: You can also create a new message for your input, output, or fault element using the Outline view. Under the <strong>Port Types</strong> folder, right-click your element and click <strong>Set Message > Create a new -message</strong>. Your message will appear in the Outline view under the <strong>Messages</strong> folder. </p> +message</strong>. Your message will appear in the Outline view under the <strong>Messages</strong> folder. </p> <p>If you want to reuse a message for your input, output, or fault element, follow these steps: </p> -<ol><li>In the Graph view, right-click your input, output, or fault element and +<ol> +<li>In the Graph view, right-click your input, output, or fault element and click <strong>Set Message.</strong></li> + <li>Press the <span class="uicontrol">Select an existing message</span> radio button.</li> + <li>The existing messages will be listed. Select one and click <strong>Finish</strong>.</li> + </ol> <p>If you want to import an existing message for your input, output, or fault element, follow these steps:</p> -<ol><li>In the Graph view, right-click your input, output, or fault element and +<ol> +<li>In the Graph view, right-click your input, output, or fault element and click <strong>Set Message.</strong></li> + <li>Select the <strong>Import message from a file</strong> check box. Click <strong>Browse</strong>.</li> + <li>Select the file that contains the message you want to use. Click <strong>OK</strong>.</li> + <li>The messages in the file will be listed. Select one and click <strong>Finish</strong>.</li> + </ol> <p>You can now add parts to your message. Parts are a flexible mechanism for describing the logical abstract content of a message.</p> </div> + </div> + <div> <div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created outside Rational Developer products into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div> </div> <div class="linklist"><strong>Related concepts</strong><br /> @@ -78,7 +105,8 @@ for describing the logical abstract content of a message.</p> <div class="linklist"><strong>Related tasks</strong><br /> <div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div> -<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created outside Rational Developer products into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> +<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> </div> + </body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddoper.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddoper.dita new file mode 100644 index 000000000..2cb1081f3 --- /dev/null +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddoper.dita @@ -0,0 +1,48 @@ +<?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="taddoper" xml:lang="en-us"> +<title>Adding an operation</title> +<shortdesc>An operation names the operation and lists the expected inputs +and outputs. The operation element may also contain a fault sub-element that +describes any error data the operation may return.</shortdesc> +<taskbody> +<context>Using these, you can declare four transmission primitives that an +endpoint can support:<ul> +<li> <b>One-way</b>. The endpoint receives a message.</li> +<li> <b>Request-response</b>. The endpoint receives a message, and sends a +correlated message.</li> +<li> <b>Solicit-response</b>. The endpoint sends a message, and receives a +correlated message.</li> +<li> <b>Notification</b>. The endpoint sends a message.</li> +</ul><p>You can add an operation to a port type or a port binding.</p><p>To +add an operation to a port type, follow these steps:</p></context> +<steps> +<step><cmd>In the Graph view, right-click your port type.</cmd><info>Click <b>Add Child +> Operation</b>.</info></step> +<step><cmd>In the dialog, enter a name for the operation.</cmd></step> +<step><cmd>Right click on the operation to add an input, output or fault objects.</cmd> +<info>Depending on an operation's inputs and outputs it can be classified +as follows:<ul> +<li><b>One way operation</b>: input </li> +<li><b>Request response operation</b>: input, output </li> +<li><b> Solicit response operation</b>: output, input </li> +<li><b>Notification operation</b> : output</li> +</ul></info></step> +<step><cmd>Type any information about the operation you wish the user to read +in the <b>Documentation</b> pane. </cmd></step> +</steps> +<result><p> <b>Tip</b>: You can also create a new operation for your port +type using the Outline view.</p></result> +</taskbody> +<related-links> +<linklist><title>Related concepts</title><?Pub Caret?> +<link href="../concepts/cwsdled.dita" scope="local"></link> +</linklist> +<linklist><title>Related tasks</title> +<link href="tcrtwsdl.dita" scope="local"></link> +<link href="tedtwsdl.dita" scope="local"></link> +</linklist> +</related-links> +</task> +<?Pub *0000002230?> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddoper.html b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddoper.html index bb553f6dd..3f566a414 100644 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddoper.html +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddoper.html @@ -1,59 +1,88 @@ -<?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> +<?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> -<!-- /******************************************************************************* - * 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" /> +<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 an operation" /> +<meta name="abstract" content="An operation names the operation and lists the expected inputs and outputs. The operation element may also contain a fault sub-element that describes any error data the operation may return." /> +<meta name="description" content="An operation names the operation and lists the expected inputs and outputs. The operation element may also contain a fault sub-element that describes any error data the operation may return." /> +<meta scheme="URI" name="DC.Relation" content="../tasks/tedtwsdl.html" /> +<meta scheme="URI" name="DC.Relation" content="../concepts/cwsdled.html" /> +<meta scheme="URI" name="DC.Relation" content="tcrtwsdl.html" /> +<meta scheme="URI" name="DC.Relation" content="tedtwsdl.html" /> +<meta content="XHTML" name="DC.Format" /> +<meta content="taddoper" 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 an operation</title> </head> <body id="taddoper"><a name="taddoper"><!-- --></a> + <h1 class="topictitle1">Adding an operation</h1> + + <div><p>An operation names the operation and lists the expected inputs and outputs. The operation element may also contain a fault sub-element that describes any error data the operation may return.</p> + <div class="section">Using these, you can declare four transmission primitives that an -endpoint can support:<ul><li> <strong>One-way</strong>. The endpoint receives a message.</li> +endpoint can support:<ul> +<li> <strong>One-way</strong>. The endpoint receives a message.</li> + <li> <strong>Request-response</strong>. The endpoint receives a message, and sends a correlated message.</li> + <li> <strong>Solicit-response</strong>. The endpoint sends a message, and receives a correlated message.</li> + <li> <strong>Notification</strong>. The endpoint sends a message.</li> + </ul> <p>You can add an operation to a port type or a port binding.</p> <p>To add an operation to a port type, follow these steps:</p> </div> -<ol><li class="stepexpand"><span>In the Graph view, right-click your port type.</span> Click <strong>Add Child + +<ol> +<li class="stepexpand"><span>In the Graph view, right-click your port type.</span> Click <strong>Add Child > Operation</strong>.</li> + <li class="stepexpand"><span>In the dialog, enter a name for the operation.</span></li> -<li class="stepexpand"><span>Right click on the operation to add an input, output or fault objects.</span> Depending on an operation's inputs and outputs it can be classified -as follows:<ul><li><strong>One way operation</strong>: input </li> + +<li class="stepexpand"><span>Right click on the operation to add an input, output or fault objects.</span> + Depending on an operation's inputs and outputs it can be classified +as follows:<ul> +<li><strong>One way operation</strong>: input </li> + <li><strong>Request response operation</strong>: input, output </li> + <li><strong> Solicit response operation</strong>: output, input </li> + <li><strong>Notification operation</strong> : output</li> + </ul> </li> + <li class="stepexpand"><span>Type any information about the operation you wish the user to read -in the <strong>Documentation</strong> pane. </span></li> +in the <strong>Documentation</strong> pane. </span></li> + </ol> + <div class="section"><p> <strong>Tip</strong>: You can also create a new operation for your port type using the Outline view.</p> </div> + </div> + <div> <div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created outside Rational Developer products into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div> </div> <div class="linklist"><strong>Related concepts</strong><br /> @@ -63,7 +92,8 @@ type using the Outline view.</p> <div class="linklist"><strong>Related tasks</strong><br /> <div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div> -<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created outside Rational Developer products into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> +<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> </div> + </body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddpart.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddpart.dita new file mode 100644 index 000000000..1859932fd --- /dev/null +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddpart.dita @@ -0,0 +1,46 @@ +<?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="taddpart" xml:lang="en-us"> +<title>Adding a part to a message</title> +<shortdesc>All messages contain one or more parts. Parts are a flexible mechanism +for describing the logical abstract content of a message. The message definition +associates each part with a type using a message-typing attribute.</shortdesc> +<taskbody> +<context><p>To add a part to a message, follow these steps:</p></context> +<steps> +<step><cmd>In Graph view, select the message you want to add a part to.</cmd> +</step> +<step><cmd>Right-click the message and click <b>Add Child > Part</b>.</cmd> +</step> +<step><cmd>Type the name of the part in the dialog.</cmd><info>Click <b>OK</b>.</info> +</step> +<step><cmd>Your part can refer to either a <b>type</b> or an <b>element</b>.</cmd> +<info>Select the appropriate option from the <b>Reference Kind</b> list.</info> +</step> +<step><cmd>If you selected <b>type</b> in the <b>Reference Kind</b> list, +you now have the option of selecting an XML schema data type from the <b>Type</b> drop +down list. The list of types comes from any available referenced XML schemas.</cmd> +<info></info></step> +<step><cmd>If you selected <b>element</b> in the <b>Reference Kind</b> list, +you now have the option of selecting an <?Pub Caret?>XML schema element from +the <b>Element</b> drop down list. The list of elements comes from any +available referenced XML schemas.</cmd><info></info></step> +</steps> +<result><p> <b>Tip</b>: You can also create a new part for your message using +the Outline view. Under the <b>Messages</b> folder, right-click your element +and click <b>Add Child > Part</b>. Your part will automatically appear in +the Outline view (under the <b>Messages</b> folder), but it will only appear +in the Graph view if the message you added it to currently does.</p></result> +</taskbody> +<related-links> +<linklist><title>Related concepts</title> +<link href="../concepts/cwsdled.dita" scope="local"></link> +</linklist> +<linklist><title>Related tasks</title> +<link href="tcrtwsdl.dita" scope="local"></link> +<link href="tedtwsdl.dita" scope="local"></link> +</linklist> +</related-links> +</task> +<?Pub *0000002294?> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddpart.html b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddpart.html index 579b6eefe..12c469dcd 100644 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddpart.html +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddpart.html @@ -1,51 +1,77 @@ -<?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> +<?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> -<!-- /******************************************************************************* - * 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" /> +<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 part to a message" /> +<meta name="abstract" content="All messages contain one or more parts. Parts are a flexible mechanism for describing the logical abstract content of a message. The message definition associates each part with a type using a message-typing attribute." /> +<meta name="description" content="All messages contain one or more parts. Parts are a flexible mechanism for describing the logical abstract content of a message. The message definition associates each part with a type using a message-typing attribute." /> +<meta scheme="URI" name="DC.Relation" content="../tasks/tedtwsdl.html" /> +<meta scheme="URI" name="DC.Relation" content="../concepts/cwsdled.html" /> +<meta scheme="URI" name="DC.Relation" content="tcrtwsdl.html" /> +<meta scheme="URI" name="DC.Relation" content="tedtwsdl.html" /> +<meta content="XHTML" name="DC.Format" /> +<meta content="taddpart" 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 part to a message</title> </head> <body id="taddpart"><a name="taddpart"><!-- --></a> + <h1 class="topictitle1">Adding a part to a message</h1> + + <div><p>All messages contain one or more parts. Parts are a flexible mechanism for describing the logical abstract content of a message. The message definition associates each part with a type using a message-typing attribute.</p> + <div class="section"><p>To add a part to a message, follow these steps:</p> </div> -<ol><li class="stepexpand"><span>In Graph view, select the message you want to add a part to.</span></li> -<li class="stepexpand"><span>Right-click the message and click <strong>Add Child > Part</strong>.</span></li> -<li class="stepexpand"><span>Type the name of the part in the dialog.</span> Click <strong>OK</strong>.</li> -<li class="stepexpand"><span>Your part can refer to either a <strong>type</strong> or an <strong>element</strong>.</span> Select the appropriate option from the <strong>Reference Kind</strong> list.</li> + +<ol> +<li class="stepexpand"><span>In Graph view, select the message you want to add a part to.</span> +</li> + +<li class="stepexpand"><span>Right-click the message and click <strong>Add Child > Part</strong>.</span> +</li> + +<li class="stepexpand"><span>Type the name of the part in the dialog.</span> Click <strong>OK</strong>. +</li> + +<li class="stepexpand"><span>Your part can refer to either a <strong>type</strong> or an <strong>element</strong>.</span> + Select the appropriate option from the <strong>Reference Kind</strong> list. +</li> + <li class="stepexpand"><span>If you selected <strong>type</strong> in the <strong>Reference Kind</strong> list, you now have the option of selecting an XML schema data type from the <strong>Type</strong> drop -down list. The list of types comes from any available referenced XML schemas.</span> </li> +down list. The list of types comes from any available referenced XML schemas.</span> + </li> + <li class="stepexpand"><span>If you selected <strong>element</strong> in the <strong>Reference Kind</strong> list, you now have the option of selecting an XML schema element from -the <strong>Element</strong> drop down list. The list of elements comes from any +the <strong>Element</strong> drop down list. The list of elements comes from any available referenced XML schemas.</span> </li> + </ol> + <div class="section"><p> <strong>Tip</strong>: You can also create a new part for your message using the Outline view. Under the <strong>Messages</strong> folder, right-click your element and click <strong>Add Child > Part</strong>. Your part will automatically appear in the Outline view (under the <strong>Messages</strong> folder), but it will only appear in the Graph view if the message you added it to currently does.</p> </div> + </div> + <div> <div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created outside Rational Developer products into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div> </div> <div class="linklist"><strong>Related concepts</strong><br /> @@ -55,7 +81,8 @@ in the Graph view if the message you added it to currently does.</p> <div class="linklist"><strong>Related tasks</strong><br /> <div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div> -<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created outside Rational Developer products into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> +<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> </div> + </body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddport.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddport.dita new file mode 100644 index 000000000..77e75c937 --- /dev/null +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddport.dita @@ -0,0 +1,49 @@ +<?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="taddport" xml:lang="en-us"> +<title>Adding a port to a service</title> +<shortdesc>A port defines an individual endpoint by specifying a single address +for a binding. The port contains a 'binding' attribute that references a binding +and an address element that provides a specification for the endpoint.</shortdesc> +<taskbody> +<context><p>Services are used to group sets of related ports together. Ports +within a service have the following relationship:</p><ul> +<li>None of the ports communicate with each other (for example, the output +of one port is not the input of another).</li> +<li>If a service has several ports that share a port type, but employ different +bindings or addresses, the ports are alternatives. Each port provides semantically +equivalent behavior (within the transport and message format limitations imposed +by each binding).</li> +<li>You can determine a service's port types by examining its ports. Using +this information a user can determine if a given machine supports all the +operations needed to complete a given task.</li> +</ul><p>To add a port to a service, follow these steps:</p></context> +<steps> +<step><cmd>In the Graph view, right-click the service you want to add a port +to, then click <b>Add Child > Port.</b></cmd></step> +<step><cmd>Type the name of the port in the dialog.</cmd><info>Click <b>Finish</b>. +The name of the port should provide it with a unique name amongst all the +ports defined within the service.</info></step> +<step><cmd>A <b>Binding</b> defines the message format and protocol details +for operations and messages defined by a particular port type.</cmd><info>You +can either create a new binding for your port, re-use an existing one, or +import one. Refer to the related tasks for more details.</info></step> +<step><cmd>Type any information about the port you want the user to read in +the <b>Documentation</b> field.</cmd></step> +</steps> +<result><p> <b>Tip</b>: You can also create a port using the Outline view +by right-clicking your service under the <b>Services</b> folder and clicking + <b>Add Child > Port</b>. Your port (regardless of which view you create it +in) will appear in both the Graph view and the Outline view.</p></result> +</taskbody> +<related-links> +<linklist><title>Related concepts</title> +<link href="../concepts/cwsdled.dita" scope="local"></link> +</linklist> +<linklist><title>Related tasks</title> +<link href="tcrtwsdl.dita" scope="local"></link> +<link href="tedtwsdl.dita" scope="local"></link> +</linklist> +</related-links> +</task> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddport.html b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddport.html index 535dbc5d8..0f32b68a1 100644 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddport.html +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddport.html @@ -1,62 +1,84 @@ -<?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> +<?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> -<!-- /******************************************************************************* - * 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" /> +<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 port to a service" /> +<meta name="abstract" content="A port defines an individual endpoint by specifying a single address for a binding. The port contains a 'binding' attribute that references a binding and an address element that provides a specification for the endpoint." /> +<meta name="description" content="A port defines an individual endpoint by specifying a single address for a binding. The port contains a 'binding' attribute that references a binding and an address element that provides a specification for the endpoint." /> +<meta scheme="URI" name="DC.Relation" content="../tasks/tedtwsdl.html" /> +<meta scheme="URI" name="DC.Relation" content="../concepts/cwsdled.html" /> +<meta scheme="URI" name="DC.Relation" content="tcrtwsdl.html" /> +<meta scheme="URI" name="DC.Relation" content="tedtwsdl.html" /> +<meta content="XHTML" name="DC.Format" /> +<meta content="taddport" 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 port to a service</title> </head> <body id="taddport"><a name="taddport"><!-- --></a> + <h1 class="topictitle1">Adding a port to a service</h1> + + <div><p>A port defines an individual endpoint by specifying a single address for a binding. The port contains a 'binding' attribute that references a binding and an address element that provides a specification for the endpoint.</p> + <div class="section"><p>Services are used to group sets of related ports together. Ports within a service have the following relationship:</p> -<ul><li>None of the ports communicate with each other (for example, the output +<ul> +<li>None of the ports communicate with each other (for example, the output of one port is not the input of another).</li> + <li>If a service has several ports that share a port type, but employ different bindings or addresses, the ports are alternatives. Each port provides semantically equivalent behavior (within the transport and message format limitations imposed -by each binding). </li> +by each binding).</li> + <li>You can determine a service's port types by examining its ports. Using this information a user can determine if a given machine supports all the operations needed to complete a given task.</li> + </ul> <p>To add a port to a service, follow these steps:</p> </div> -<ol><li class="stepexpand"><span>In the Graph view, right-click the service you want to add a port + +<ol> +<li class="stepexpand"><span>In the Graph view, right-click the service you want to add a port to, then click <strong>Add Child > Port.</strong></span></li> + <li class="stepexpand"><span>Type the name of the port in the dialog.</span> Click <strong>Finish</strong>. The name of the port should provide it with a unique name amongst all the ports defined within the service.</li> + <li class="stepexpand"><span>A <strong>Binding</strong> defines the message format and protocol details for operations and messages defined by a particular port type.</span> You can either create a new binding for your port, re-use an existing one, or import one. Refer to the related tasks for more details.</li> + <li class="stepexpand"><span>Type any information about the port you want the user to read in the <strong>Documentation</strong> field.</span></li> + </ol> + <div class="section"><p> <strong>Tip</strong>: You can also create a port using the Outline view by right-clicking your service under the <strong>Services</strong> folder and clicking <strong>Add Child > Port</strong>. Your port (regardless of which view you create it in) will appear in both the Graph view and the Outline view.</p> </div> + </div> + <div> <div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created outside Rational Developer products into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div> </div> <div class="linklist"><strong>Related concepts</strong><br /> @@ -66,7 +88,8 @@ in) will appear in both the Graph view and the Outline view.</p> <div class="linklist"><strong>Related tasks</strong><br /> <div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div> -<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created outside Rational Developer products into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> +<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> </div> + </body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddsrvc.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddsrvc.dita new file mode 100644 index 000000000..709f85362 --- /dev/null +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddsrvc.dita @@ -0,0 +1,35 @@ +<?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="taddsrvc" xml:lang="en-us"> +<title>Adding a service</title> +<shortdesc>The <systemoutput>service</systemoutput> element is a collection +of related ports and specifies the location of the service.</shortdesc> +<taskbody> +<context><p>To create a new service, follow these steps:</p></context> +<steps> +<step><cmd>In the Graph view, right-click in any blank space and click <b>Add +Child > Service</b>.</cmd></step> +<step><cmd>Type the name of the service in the dialog.</cmd><info>The name +of the service provides it with a unique name amongst all the services defined +within in the enclosing WSDL document.</info></step> +<step><cmd>Click <b>OK</b>.</cmd></step> +<step><cmd>Type any information about the service you want the user to read +in the <b>Documentation</b> pane.</cmd></step> +</steps> +<result><p> <b>Tip</b>: You can also create a service using the Outline view +by right-clicking the <b>Services</b> folder and clicking <b>Add Child > +Service</b>.</p><p>You can now add a port to your service. A port defines +an individual endpoint by specifying a single address for a binding.</p></result> +</taskbody> +<related-links> +<linklist><title>Related concepts</title><?Pub Caret?> +<link href="../concepts/cwsdled.dita" scope="local"></link> +</linklist> +<linklist><title>Related tasks</title> +<link href="tcrtwsdl.dita" scope="local"></link> +<link href="tedtwsdl.dita" scope="local"></link> +</linklist> +</related-links> +</task> +<?Pub *0000001613?> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddsrvc.html b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddsrvc.html index 07b3c9182..ee23f10cf 100644 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddsrvc.html +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddsrvc.html @@ -1,47 +1,65 @@ -<?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> +<?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> -<!-- /******************************************************************************* - * 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" /> +<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 service" /> +<meta name="abstract" content="The service element is a collection of related ports and specifies the location of the service." /> +<meta name="description" content="The service element is a collection of related ports and specifies the location of the service." /> +<meta scheme="URI" name="DC.Relation" content="../tasks/tedtwsdl.html" /> +<meta scheme="URI" name="DC.Relation" content="../concepts/cwsdled.html" /> +<meta scheme="URI" name="DC.Relation" content="tcrtwsdl.html" /> +<meta scheme="URI" name="DC.Relation" content="tedtwsdl.html" /> +<meta content="XHTML" name="DC.Format" /> +<meta content="taddsrvc" 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 service</title> </head> <body id="taddsrvc"><a name="taddsrvc"><!-- --></a> + <h1 class="topictitle1">Adding a service</h1> + + <div><p>The <tt class="sysout">service</tt> element is a collection of related ports and specifies the location of the service.</p> + <div class="section"><p>To create a new service, follow these steps:</p> </div> -<ol><li class="stepexpand"><span>In the Graph view, right-click in any blank space and click <strong>Add + +<ol> +<li class="stepexpand"><span>In the Graph view, right-click in any blank space and click <strong>Add Child > Service</strong>.</span></li> + <li class="stepexpand"><span>Type the name of the service in the dialog.</span> The name of the service provides it with a unique name amongst all the services defined within in the enclosing WSDL document.</li> + <li class="stepexpand"><span>Click <strong>OK</strong>.</span></li> + <li class="stepexpand"><span>Type any information about the service you want the user to read in the <strong>Documentation</strong> pane.</span></li> + </ol> + <div class="section"><p> <strong>Tip</strong>: You can also create a service using the Outline view by right-clicking the <strong>Services</strong> folder and clicking <strong>Add Child > Service</strong>.</p> <p>You can now add a port to your service. A port defines an individual endpoint by specifying a single address for a binding.</p> </div> + </div> + <div> <div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created outside Rational Developer products into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div> </div> <div class="linklist"><strong>Related concepts</strong><br /> @@ -51,7 +69,8 @@ an individual endpoint by specifying a single address for a binding.</p> <div class="linklist"><strong>Related tasks</strong><br /> <div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div> -<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created outside Rational Developer products into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> +<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> </div> + </body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtimpt.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtimpt.dita new file mode 100644 index 000000000..ccec7314c --- /dev/null +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtimpt.dita @@ -0,0 +1,37 @@ +<?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="tcrtimpt" xml:lang="en-us"> +<title>Creating an import statement</title> +<shortdesc>The import statement is used to import other WSDL documents or +XML schemas into your WSDL document. This enables you to have more modular +WSDL documents. The use of the <b>import</b> statement allows the separation +of the different elements of a service definition into independent documents, +which can then be imported as needed. This technique helps in writing clearer +service definitions, by separating the definitions according to their level +of abstraction.</shortdesc> +<taskbody> +<context><p>To create an import statement, follow these steps:</p></context> +<steps> +<step><cmd>In the Graph view, right-click the <b>Imports</b> group and click + <b>Add Child > Import.</b></cmd></step> +<step><cmd>Select your new import statement.</cmd></step> +<step><cmd>Specify the <b>namespace</b> of the document you wish to import, +then specify the <b>location</b> of the document you wish to import.</cmd> +</step> +</steps> +<result>Once you specify the location of the document you wish to import, +the import object's label changes to reflect the specified location. Imported +WSDL components may now be visible within the editor.</result> +</taskbody> +<related-links> +<linklist><title>Related concepts</title><?Pub Caret?> +<link href="../concepts/cwsdled.dita" scope="local"></link> +</linklist> +<linklist><title>Related tasks</title> +<link href="tcrtwsdl.dita" scope="local"></link> +<link href="tedtwsdl.dita" scope="local"></link> +</linklist> +</related-links> +</task> +<?Pub *0000001728?> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtimpt.html b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtimpt.html index 398b62df1..bbda93d29 100644 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtimpt.html +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtimpt.html @@ -1,24 +1,32 @@ -<?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> +<?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> -<!-- /******************************************************************************* - * 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" /> +<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="Creating an import statement" /> +<meta name="abstract" content="The import statement is used to import other WSDL documents or XML schemas into your WSDL document. This enables you to have more modular WSDL documents. The use of the import statement allows the separation of the different elements of a service definition into independent documents, which can then be imported as needed. This technique helps in writing clearer service definitions, by separating the definitions according to their level of abstraction." /> +<meta name="description" content="The import statement is used to import other WSDL documents or XML schemas into your WSDL document. This enables you to have more modular WSDL documents. The use of the import statement allows the separation of the different elements of a service definition into independent documents, which can then be imported as needed. This technique helps in writing clearer service definitions, by separating the definitions according to their level of abstraction." /> +<meta scheme="URI" name="DC.Relation" content="../tasks/tedtwsdl.html" /> +<meta scheme="URI" name="DC.Relation" content="../concepts/cwsdled.html" /> +<meta scheme="URI" name="DC.Relation" content="tcrtwsdl.html" /> +<meta scheme="URI" name="DC.Relation" content="tedtwsdl.html" /> +<meta content="XHTML" name="DC.Format" /> +<meta content="tcrtimpt" 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>Creating an import statement</title> </head> <body id="tcrtimpt"><a name="tcrtimpt"><!-- --></a> + <h1 class="topictitle1">Creating an import statement</h1> + + <div><p>The import statement is used to import other WSDL documents or XML schemas into your WSDL document. This enables you to have more modular WSDL documents. The use of the <strong>import</strong> statement allows the separation @@ -26,21 +34,31 @@ of the different elements of a service definition into independent documents, which can then be imported as needed. This technique helps in writing clearer service definitions, by separating the definitions according to their level of abstraction.</p> + <div class="section"><p>To create an import statement, follow these steps:</p> </div> -<ol><li><span>In the Graph view, right-click the <strong>Imports</strong> group and click + +<ol> +<li><span>In the Graph view, right-click the <strong>Imports</strong> group and click <strong>Add Child > Import.</strong></span></li> + <li><span>Select your new import statement.</span></li> + <li><span>Specify the <strong>namespace</strong> of the document you wish to import, -then specify the <strong>location</strong> of the document you wish to import.</span></li> +then specify the <strong>location</strong> of the document you wish to import.</span> +</li> + </ol> + <div class="section">Once you specify the location of the document you wish to import, the import object's label changes to reflect the specified location. Imported WSDL components may now be visible within the editor.</div> + </div> + <div> <div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created outside Rational Developer products into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div> </div> <div class="linklist"><strong>Related concepts</strong><br /> @@ -50,7 +68,8 @@ WSDL components may now be visible within the editor.</div> <div class="linklist"><strong>Related tasks</strong><br /> <div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div> -<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created outside Rational Developer products into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> +<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> </div> + </body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrttype.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrttype.dita new file mode 100644 index 000000000..00f17d3a3 --- /dev/null +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrttype.dita @@ -0,0 +1,50 @@ +<?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="tcrttype" xml:lang="en-us"> +<title>Creating a new type for your WSDL file</title> +<shortdesc>Types describe all the data types used between the client and server. +WSDL is not tied exclusively to a specific typing system, but it uses the +W3C XML Schema specification as its default choice.</shortdesc> +<taskbody> +<context><p>WSDL allows type systems to be added via extensibility elements. +An extensibility element may appear under the <b>types</b> element to identify +the type definition system being used and to provide an XML container element +for the type definitions.</p><p>To add an extensibility element to your WSDL +file, follow these steps:</p></context> +<steps> +<step><cmd>In the Graph view right-click the <b>Types</b> group.</cmd></step> +<step><cmd>Click <b>Add Child</b> > <b>Add Schema</b>. You will be +creating an inline schema - a schema that is defined directly within the WSDL +file.</cmd><info></info></step> +<step><cmd>A schema object will appear in the group.</cmd><info>Select it.</info> +</step> +<step><cmd>The following information about your schema is listed: </cmd> +<info><ul> +<li> <b>Prefix</b> - The prefix associated with the current namespace</li> +<li> <b>URI</b> - the target namespace for the schema</li> +<li>Other attributes, such as <b>version</b>, <b>language</b>, and <b>attribute +form</b>.</li> +</ul> You can manually modify the value of any of these attributes.</info> +</step> +<step><cmd>You can also add new components to your XML schema. In the Graph +view, press the arrow icon to the left of the schema object to drill down +into the schema.</cmd><info> Now you can edit the schema within the graph +view. When finished, press the <uicontrol>Back</uicontrol> button at the top +left of the WSDL editor to return to the definition view of the WSDL document.</info> +</step> +</steps> +<result><p>For more information about XML schemas, refer to the XML schema +editor online documentation.</p></result> +</taskbody> +<related-links> +<linklist><title>Related concepts</title><?Pub Caret?> +<link href="../concepts/cwsdled.dita" scope="local"></link> +</linklist> +<linklist><title>Related tasks</title> +<link href="tcrtwsdl.dita" scope="local"></link> +<link href="tedtwsdl.dita" scope="local"></link> +</linklist> +</related-links> +</task> +<?Pub *0000002458?> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrttype.html b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrttype.html index 34d86fffb..a9c4db2be 100644 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrttype.html +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrttype.html @@ -1,27 +1,36 @@ -<?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> +<?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> -<!-- /******************************************************************************* - * 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" /> +<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="Creating a new type for your WSDL file" /> +<meta name="abstract" content="Types describe all the data types used between the client and server. WSDL is not tied exclusively to a specific typing system, but it uses the W3C XML Schema specification as its default choice." /> +<meta name="description" content="Types describe all the data types used between the client and server. WSDL is not tied exclusively to a specific typing system, but it uses the W3C XML Schema specification as its default choice." /> +<meta scheme="URI" name="DC.Relation" content="../tasks/tedtwsdl.html" /> +<meta scheme="URI" name="DC.Relation" content="../concepts/cwsdled.html" /> +<meta scheme="URI" name="DC.Relation" content="tcrtwsdl.html" /> +<meta scheme="URI" name="DC.Relation" content="tedtwsdl.html" /> +<meta content="XHTML" name="DC.Format" /> +<meta content="tcrttype" 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>Creating a new type for your WSDL file</title> </head> <body id="tcrttype"><a name="tcrttype"><!-- --></a> + <h1 class="topictitle1">Creating a new type for your WSDL file</h1> + + <div><p>Types describe all the data types used between the client and server. WSDL is not tied exclusively to a specific typing system, but it uses the W3C XML Schema specification as its default choice.</p> + <div class="section"><p>WSDL allows type systems to be added via extensibility elements. An extensibility element may appear under the <strong>types</strong> element to identify the type definition system being used and to provide an XML container element @@ -29,30 +38,48 @@ for the type definitions.</p> <p>To add an extensibility element to your WSDL file, follow these steps:</p> </div> -<ol><li class="stepexpand"><span>In the Graph view right-click the <strong>Types</strong> group.</span></li> -<li class="stepexpand"><span>Click <strong>Add Child</strong> > <strong>Add Schema</strong>. You will be + +<ol> +<li class="stepexpand"><span>In the Graph view right-click the <strong>Types</strong> group.</span></li> + +<li class="stepexpand"><span>Click <strong>Add Child</strong> > <strong>Add Schema</strong>. You will be creating an inline schema - a schema that is defined directly within the WSDL file.</span> </li> -<li class="stepexpand"><span>A schema object will appear in the group.</span> Select it.</li> -<li class="stepexpand"><span>The following information about your schema is listed: </span> <ul><li> <strong>Prefix</strong> - The prefix associated with the current namespace</li> + +<li class="stepexpand"><span>A schema object will appear in the group.</span> Select it. +</li> + +<li class="stepexpand"><span>The following information about your schema is listed: </span> + <ul> +<li> <strong>Prefix</strong> - The prefix associated with the current namespace</li> + <li> <strong>URI</strong> - the target namespace for the schema</li> + <li>Other attributes, such as <strong>version</strong>, <strong>language</strong>, and <strong>attribute form</strong>.</li> + </ul> - You can manually modify the value of any of these attributes.</li> + You can manually modify the value of any of these attributes. +</li> + <li class="stepexpand"><span>You can also add new components to your XML schema. In the Graph view, press the arrow icon to the left of the schema object to drill down into the schema.</span> Now you can edit the schema within the graph view. When finished, press the <span class="uicontrol">Back</span> button at the top -left of the WSDL editor to return to the definition view of the WSDL document.</li> +left of the WSDL editor to return to the definition view of the WSDL document. +</li> + </ol> + <div class="section"><p>For more information about XML schemas, refer to the XML schema editor online documentation.</p> </div> + </div> + <div> <div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created outside Rational Developer products into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div> </div> <div class="linklist"><strong>Related concepts</strong><br /> @@ -62,7 +89,8 @@ editor online documentation.</p> <div class="linklist"><strong>Related tasks</strong><br /> <div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div> -<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created outside Rational Developer products into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> +<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> </div> + </body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtwsdl.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtwsdl.dita new file mode 100644 index 000000000..3c703c361 --- /dev/null +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtwsdl.dita @@ -0,0 +1,64 @@ +<?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="tcrtwsdl" xml:lang="en-us"><?Pub Caret?> +<title>Creating a new WSDL file</title> +<shortdesc>You can create a new, empty WSDL file, then edit it using the WSDL +editor.</shortdesc> +<taskbody> +<context><p>To create a WSDL file, follow these steps:</p></context> +<steps> +<step><cmd>Create a project to contain the WSDL document.</cmd><info>It does +not matter what kind of project you create.</info></step> +<step><cmd>In the workbench, click <b>File > New > Other > Web Services > +WSDL</b>.</cmd><info>Click <b>Next</b>.</info></step> +<step><cmd>Select the project or folder that will contain the WSDL file.</cmd> +<info>In the <b>File name</b> field, type the name of the WSDL file, for +example <systemoutput>MyWSDLFile.wsdl</systemoutput>. The name of your XML +file must end in <systemoutput>.wsdl</systemoutput></info></step> +<step><cmd>Click <b>Next.</b></cmd></step> +<step><cmd>Enter the following information: </cmd> +<substeps> +<substep><cmd><b>Target namespace</b> is the namespace for the WSDL file or +accept the default (<codeph>http://www.example.org/<i>MyWSDLFile</i>/</codeph>).</cmd> +<info>The target namespace is used for the names of messages and the port +type, binding and service defined in the WSDL file. The value must take the +form of a valid URI (for example, <codeph>http://www.mycompany.com/myservice/</codeph>)</info> +</substep> +<substep><cmd>The <b>Prefix</b> is the prefix associated with the target +namespace.</cmd></substep> +<substep><cmd>Select <uicontrol>Create WSDL Skeleton</uicontrol> if you want +the wizard to create the skeleton of the WSDL file.</cmd><info> This will +generate the WSDL elements required for your service, including bindings, +ports and messages. You can then modify these to meet the requirements of +your Web service.</info></substep> +<substep><cmd>If you have chosen to create a WSDL skeleton, select the binding +options you want to use in the WSDL document. The options are SOAP and HTTP.</cmd> +<info> If you select SOAP you can then select the encoding style you want +to use. If you select HTTP you can select whether to create an HTTP getter +or setter.</info></substep> +</substeps> +</step> +<step><cmd>Click <b>Finish</b>.</cmd><info>The WSDL file opens in the WSDL +editor.</info></step> +</steps> +<result><p>If you created a WSDL file with a skeleton using SOAP bindings, +it should look similar to the following:<image alt="Image of a WSDL skeleton using SOAP bindings" +href="../images/soapskel.gif" placement="break"></image></p><p>If you created +a WSDL file with a skeleton using HTTP bindings, it should look similar to +the following:<image alt="Image of a WSDL skeleton using HTTP bindings" href="../images/httpskel.gif" +placement="break"></image></p></result> +</taskbody> +<related-links> +<linklist><title>Related concepts</title> +<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.dita" scope="peer"> +<linktext>WSDL</linktext></link> +<link href="../concepts/cwsdled.dita" scope="local"></link> +</linklist> +<linklist><title>Related tasks</title> +<link href="timpwsdl.dita" scope="local"></link> +<link href="tedtwsdl.dita" scope="local"></link> +</linklist> +</related-links> +</task> +<?Pub *0000003334?> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtwsdl.html b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtwsdl.html index f16e13e98..cf4021eb7 100644 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtwsdl.html +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtwsdl.html @@ -1,63 +1,94 @@ -<?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> +<?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> -<!-- /******************************************************************************* - * 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" /> +<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="Creating a new WSDL file" /> +<meta name="abstract" content="You can create a new, empty WSDL file, then edit it using the WSDL editor." /> +<meta name="description" content="You can create a new, empty WSDL file, then edit it using the WSDL editor." /> +<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.html" /> +<meta scheme="URI" name="DC.Relation" content="../concepts/cwsdled.html" /> +<meta scheme="URI" name="DC.Relation" content="timpwsdl.html" /> +<meta scheme="URI" name="DC.Relation" content="tedtwsdl.html" /> +<meta content="XHTML" name="DC.Format" /> +<meta content="tcrtwsdl" name="DC.Identifier" /> +<meta content="en-us" name="DC.Language" /> +<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> <title>Creating a new WSDL file</title> </head> <body id="tcrtwsdl"><a name="tcrtwsdl"><!-- --></a> + <h1 class="topictitle1">Creating a new WSDL file</h1> + + <div><p>You can create a new, empty WSDL file, then edit it using the WSDL editor.</p> + <div class="section"><p>To create a WSDL file, follow these steps:</p> </div> -<ol><li class="stepexpand"><span>Create a project to contain the WSDL document.</span> It does + +<ol> +<li class="stepexpand"><span>Create a project to contain the WSDL document.</span> It does not matter what kind of project you create.</li> + <li class="stepexpand"><span>In the workbench, click <strong>File > New > Other > Web Services > WSDL</strong>.</span> Click <strong>Next</strong>.</li> -<li class="stepexpand"><span>Select the project or folder that will contain the WSDL file.</span> In the <strong>File name</strong> field, type the name of the WSDL file, for + +<li class="stepexpand"><span>Select the project or folder that will contain the WSDL file.</span> + In the <strong>File name</strong> field, type the name of the WSDL file, for example <tt class="sysout">MyWSDLFile.wsdl</tt>. The name of your XML file must end in <tt class="sysout">.wsdl</tt></li> + <li class="stepexpand"><span>Click <strong>Next.</strong></span></li> -<li class="stepexpand"><span>Enter the following information: </span><ol type="a"><li class="substepexpand"><span><strong>Target namespace</strong> is the namespace for the WSDL file or -accept the default (<samp class="codeph">http://www.example.org/<em>MyWSDLFile</em>/</samp>).</span> The target namespace is used for the names of messages and the port + +<li class="stepexpand"><span>Enter the following information: </span> +<ol type="a"> +<li class="substepexpand"><span><strong>Target namespace</strong> is the namespace for the WSDL file or +accept the default (<samp class="codeph">http://www.example.org/<em>MyWSDLFile</em>/</samp>).</span> + The target namespace is used for the names of messages and the port type, binding and service defined in the WSDL file. The value must take the -form of a valid URI (for example, <samp class="codeph">http://www.mycompany.com/myservice/</samp>)</li> +form of a valid URI (for example, <samp class="codeph">http://www.mycompany.com/myservice/</samp>) +</li> + <li class="substepexpand"><span>The <strong>Prefix</strong> is the prefix associated with the target namespace.</span></li> + <li class="substepexpand"><span>Select <span class="uicontrol">Create WSDL Skeleton</span> if you want the wizard to create the skeleton of the WSDL file.</span> This will generate the WSDL elements required for your service, including bindings, ports and messages. You can then modify these to meet the requirements of your Web service.</li> + <li class="substepexpand"><span>If you have chosen to create a WSDL skeleton, select the binding -options you want to use in the WSDL document. The options are SOAP and HTTP.</span> If you select SOAP you can then select the encoding style you want +options you want to use in the WSDL document. The options are SOAP and HTTP.</span> + If you select SOAP you can then select the encoding style you want to use. If you select HTTP you can select whether to create an HTTP getter or setter.</li> + </ol> + </li> + <li class="stepexpand"><span>Click <strong>Finish</strong>.</span> The WSDL file opens in the WSDL editor.</li> + </ol> + <div class="section"><p>If you created a WSDL file with a skeleton using SOAP bindings, it should look similar to the following:<br /><img src="../images/soapskel.gif" alt="Image of a WSDL skeleton using SOAP bindings" /><br /></p> <p>If you created a WSDL file with a skeleton using HTTP bindings, it should look similar to the following:<br /><img src="../images/httpskel.gif" alt="Image of a WSDL skeleton using HTTP bindings" /><br /></p> </div> + </div> + <div> <div class="linklist"><strong>Related concepts</strong><br /> @@ -66,8 +97,9 @@ the following:<br /><img src="../images/httpskel.gif" alt="Image of a WSDL skele <div class="linklist"><strong>Related tasks</strong><br /> -<div><a href="timpwsdl.html">Importing a WSDL file</a></div> -<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created outside Rational Developer products into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> +<div><a href="timpwsdl.html" title="">Importing a WSDL file</a></div> +<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> </div> + </body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tedtwsdl.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tedtwsdl.dita new file mode 100644 index 000000000..0257fb925 --- /dev/null +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tedtwsdl.dita @@ -0,0 +1,86 @@ +<?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="tedtwsdl" xml:lang="en-us"> +<title>Editing WSDL files</title> +<shortdesc>Once you have created a WSDL file, you can edit it in the WSDL +editor. You can also import WSDL files you have created into the workbench +and edit them in the WSDL editor.</shortdesc> +<taskbody> +<context><p>To open a WSDL file in the WSDL editor, double-click it in the +Navigator view or right-click it and click <b>Open With > WSDL Editor.</b></p></context> +</taskbody> +<task id="editisourceview"> +<title>Editing in the Source view</title> +<taskbody> +<context>To edit a WSDL file in the Source view, follow these steps:</context> +<steps> +<step><cmd>Open your WSDL file in the WSDL editor.</cmd></step> +<step><cmd>Click the <b>Source</b> tab.</cmd></step> +<step><cmd>Select the source code you want to edit.</cmd></step> +</steps> +<result><p>At any time, you can switch to the Source view to review the source +for the WSDL file. You can also edit your WSDL file directly in the Source +view.</p></result> +</taskbody> +</task> +<task id="editeditview"> +<title>Editing in the Graph view</title> +<taskbody> +<context><p>The Graph view provides a graphical way to browse and edit your +WSDL file. Each type of top level wsdl object is shown within a group (for +example service, port type, message). Within each group is a tree view that +can be used to browse the structure of the object. The service, binding, port +type and message groups are 'linked'. If for example we select an input in +the port types, we'll notice that the message that is referenced by this message +is scrolled into view in the messages group. A line displays to denote a reference +(or association) between these objects.</p><p> <image alt="Image of a WSDL file open in the WSDL editor" +href="../images/wsdleditor.gif" placement="break"></image> </p></context> +</taskbody> +</task> +<task id="showbndgraph"> +<title>Showing Bindings in the Graph view</title> +<taskbody> +<context>By default bindings are shown in the Graph View. Select the show/hide +binding button at the top left of the Graph View to hide the bindings. With +the bindings hidden a service can be browsed from a purely abstract level +without showing binding information. When the need arises to understand the +concrete details represented by the binding, select the show/hide binding +button again to make them visible.</context> +</taskbody> +</task> +<task id="editoutlineview"> +<title>Editing in the Outline view</title> +<taskbody> +<context><p>The Outline view will show you all the items in your WSDL file +as you add them. In this view, you can both create and delete WSDL components.</p><p>The +Outline view contains the following folders you can use (by right-clicking +and selecting the appropriate option) to edit your WSDL file:</p><ul> +<li> <b>Imports</b> statements, which are used to associate a namespace +with a document location.</li> +<li> <b>Types</b>, which provide data type definitions used to describe the +messages exchanged. You cannot edit any types directly using this folder.</li> +<li> <b>Messages</b>, which represent an abstract definition of the data being +transmitted. A message consists of logical parts, each of which is associated +with a definition within some type system.</li> +<li> <b>Port Types</b>, which are a set of abstract operations. Each operation +refers to an input message and output messages.</li> +<li> <b>Bindings</b>, which specify concrete protocol and data format specifications +for the operations and messages defined by a particular port type.</li> +<li> <b>Services</b>, which are used to aggregate a set of related ports <image +alt="" href="../images/show-hide-binding.gif"></image> </li> +</ul></context> +</taskbody> +<related-links> +<linklist><title>Related concepts</title> +<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.dita" scope="peer"> +<linktext>WSDL</linktext></link> +<link href="../concepts/cwsdled.dita" scope="local"></link> +</linklist> +<linklist><title>Related tasks</title> +<link href="tcrtwsdl.dita" scope="local"></link> +<link href="timpwsdl.dita" scope="local"></link> +</linklist> +</related-links> +</task> +</task> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tedtwsdl.html b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tedtwsdl.html index f1a8ecbe2..6270567aa 100644 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tedtwsdl.html +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tedtwsdl.html @@ -1,138 +1,129 @@ -<?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> +<?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> -<!-- /******************************************************************************* - * 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" /> +<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="Editing WSDL files" /> +<meta name="abstract" content="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor." /> +<meta name="description" content="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor." /> +<meta content="XHTML" name="DC.Format" /> +<meta content="tedtwsdl" 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>Editing WSDL files</title> </head> <body id="tedtwsdl"><a name="tedtwsdl"><!-- --></a> + <h1 class="topictitle1">Editing WSDL files</h1> + + <div><p>Once you have created a WSDL file, you can edit it in the WSDL -editor. You can also import WSDL files you have created in other -products into the workbench and edit them in the WSDL editor.</p> +editor. You can also import WSDL files you have created into the workbench +and edit them in the WSDL editor.</p> + <div class="section"><p>To open a WSDL file in the WSDL editor, double-click it in the Navigator view or right-click it and click <strong>Open With > WSDL Editor.</strong></p> </div> + </div> + +<div class="nested1" id="editisourceview"><a name="editisourceview"><!-- --></a> +<h2 class="topictitle2">Editing in the Source view</h2> + <div> -<ul class="ullinks"> -<li class="ulchildlink"><strong><a href="../tasks/taddsrvc.html">Adding a service</a></strong><br /> -The <tt class="sysout">service</tt> element is a collection -of related ports and specifies the location of the service.</li> -<li class="ulchildlink"><strong><a href="../tasks/taddport.html">Adding a port to a service</a></strong><br /> -A port defines an individual endpoint by specifying a single address -for a binding. The port contains a 'binding' attribute that references a binding -and an address element that provides a specification for the endpoint.</li> -<li class="ulchildlink"><strong><a href="../tasks/tsetprtt.html">Setting a port type</a></strong><br /> -A port type is a named set of abstract operations and the abstract -messages involved. Each operation refers to an input message and output messages. -A port type is reference by a binding object. Each binding references exactly -one port type. Since each port refers to exactly one binding, each port has -exactly one port type.</li> -<li class="ulchildlink"><strong><a href="../tasks/tsetbind.html">Setting a binding</a></strong><br /> -A binding is a top level WSDL object that provides a concrete specification -regarding the transmission of messages to and from a web service. A binding -references exactly one port type. The structure of a binding corresponds very -closely to that of the port type. The binding contains extensibility elements -(for example, soap, http, and mime) that specify protocol specific details. -Each port within a service references exactly one binding.</li> -<li class="ulchildlink"><strong><a href="../tasks/taddoper.html">Adding an operation</a></strong><br /> -An operation names the operation and lists the expected inputs -and outputs. The operation element may also contain a fault sub-element that -describes any error data the operation may return.</li> -<li class="ulchildlink"><strong><a href="../tasks/taddmess.html">Adding a message</a></strong><br /> -Messages represent an abstract definition of the data being transmitted. -A message consists of logical parts, each of which is associated with a definition -within some type system. WSDL messages are top level objects that can be referenced -by an operation's input, output and fault elements (within a port type).</li> -<li class="ulchildlink"><strong><a href="../tasks/taddpart.html">Adding a part to a message</a></strong><br /> -All messages contain one or more parts. Parts are a flexible mechanism -for describing the logical abstract content of a message. The message definition -associates each part with a type using a message-typing attribute.</li> -<li class="ulchildlink"><strong><a href="../tasks/tcrtimpt.html">Creating an import statement</a></strong><br /> -The import statement is used to import other WSDL documents or -XML schemas into your WSDL document. This enables you to have more modular -WSDL documents. The use of the <strong>import</strong> statement allows the separation -of the different elements of a service definition into independent documents, -which can then be imported as needed. This technique helps in writing clearer -service definitions, by separating the definitions according to their level -of abstraction.</li> -<li class="ulchildlink"><strong><a href="../tasks/tcrttype.html">Creating a new type for your WSDL file</a></strong><br /> -Types describe all the data types used between the client and server. -WSDL is not tied exclusively to a specific typing system, but it uses the -W3C XML Schema specification as its default choice.</li> -</ul> +<div class="section">To edit a WSDL file in the Source view, follow these steps:</div> + +<ol> +<li><span>Open your WSDL file in the WSDL editor.</span></li> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></div> -</div> -</div><div class="nested1" id="editisourceview"><a name="editisourceview"><!-- --></a><h2 class="topictitle2">Editing in the Source view</h2> -<div><div class="section">To edit a WSDL file in the Source view, follow these steps:</div> -<ol><li><span>Open your WSDL file in the WSDL editor.</span></li> <li><span>Click the <strong>Source</strong> tab.</span></li> + <li><span>Select the source code you want to edit.</span></li> + </ol> + <div class="section"><p>At any time, you can switch to the Source view to review the source for the WSDL file. You can also edit your WSDL file directly in the Source view.</p> </div> + </div> + </div> -<div class="nested1" id="editeditview"><a name="editeditview"><!-- --></a><h2 class="topictitle2">Editing in the Graph view</h2> -<div><div class="section"><p>The Graph view provides a graphical way to browse and edit your -WSDL file. Each type of top level wsdl object is shown within a group (e.g. -service, port type, message). Within each group is a tree view that can be -used to browse the structure of the object. The service, binding, port type -and message groups are 'linked'. If for example we select an input in the -port types, we'll notice that the message that is referenced by this message + +<div class="nested1" id="editeditview"><a name="editeditview"><!-- --></a> +<h2 class="topictitle2">Editing in the Graph view</h2> + +<div> +<div class="section"><p>The Graph view provides a graphical way to browse and edit your +WSDL file. Each type of top level wsdl object is shown within a group (for +example service, port type, message). Within each group is a tree view that +can be used to browse the structure of the object. The service, binding, port +type and message groups are 'linked'. If for example we select an input in +the port types, we'll notice that the message that is referenced by this message is scrolled into view in the messages group. A line displays to denote a reference (or association) between these objects.</p> <p> <br /><img src="../images/wsdleditor.gif" alt="Image of a WSDL file open in the WSDL editor" /><br /> </p> </div> + </div> + </div> -<div class="nested1" id="showbndgraph"><a name="showbndgraph"><!-- --></a><h2 class="topictitle2">Showing Bindings in the Graph view</h2> -<div><div class="section">By default bindings are shown in the Graph View. Select the show/hide + +<div class="nested1" id="showbndgraph"><a name="showbndgraph"><!-- --></a> +<h2 class="topictitle2">Showing Bindings in the Graph view</h2> + +<div> +<div class="section">By default bindings are shown in the Graph View. Select the show/hide binding button at the top left of the Graph View to hide the bindings. With the bindings hidden a service can be browsed from a purely abstract level without showing binding information. When the need arises to understand the concrete details represented by the binding, select the show/hide binding button again to make them visible.</div> + </div> + </div> -<div class="nested1" id="editoutlineview"><a name="editoutlineview"><!-- --></a><h2 class="topictitle2">Editing in the Outline view</h2> -<div><div class="section"><p>The Outline view will show you all the items in your WSDL file + +<div class="nested1" id="editoutlineview"><a name="editoutlineview"><!-- --></a> +<h2 class="topictitle2">Editing in the Outline view</h2> + +<div> +<div class="section"><p>The Outline view will show you all the items in your WSDL file as you add them. In this view, you can both create and delete WSDL components.</p> <p>The Outline view contains the following folders you can use (by right-clicking and selecting the appropriate option) to edit your WSDL file:</p> -<ul><li> <strong>Imports</strong> statements, which are used to associate a namespace +<ul> +<li> <strong>Imports</strong> statements, which are used to associate a namespace with a document location.</li> + <li> <strong>Types</strong>, which provide data type definitions used to describe the -messages exchanged. You cannot edit any types directly using this folder.</li> +messages exchanged. You cannot edit any types directly using this folder.</li> + <li> <strong>Messages</strong>, which represent an abstract definition of the data being transmitted. A message consists of logical parts, each of which is associated with a definition within some type system.</li> + <li> <strong>Port Types</strong>, which are a set of abstract operations. Each operation refers to an input message and output messages.</li> + <li> <strong>Bindings</strong>, which specify concrete protocol and data format specifications for the operations and messages defined by a particular port type.</li> + <li> <strong>Services</strong>, which are used to aggregate a set of related ports <img src="../images/show-hide-binding.gif" alt="" /> </li> + </ul> </div> + </div> + <div> <div class="linklist"><strong>Related concepts</strong><br /> @@ -142,8 +133,10 @@ for the operations and messages defined by a particular port type.</li> <div class="linklist"><strong>Related tasks</strong><br /> <div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div> -<div><a href="timpwsdl.html">Importing a WSDL file</a></div></div> -</div></div> +<div><a href="timpwsdl.html" title="">Importing a WSDL file</a></div></div> +</div> +</div> + </body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/timpwsdl.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/timpwsdl.dita new file mode 100644 index 000000000..40ec6904c --- /dev/null +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/timpwsdl.dita @@ -0,0 +1,73 @@ +<?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="timpwsdl" xml:lang="en-us"> +<title>Importing a WSDL file</title> +<titlealts> +<searchtitle>Importing WSDL files</searchtitle> +</titlealts> +<taskbody> +<context><p>The Web Service wizard assists you in creating a new Web service +from a WSDL file. You must first create or import a WSDL file. A WSDL file +can be created using the WSDL editor. This is described in: <xref href="../tasks/tcrtwsdl.dita" +scope="peer">Creating a new WSDL file</xref>. To import a WSDL file follow +the instructions below.</p><p>You can import WSDL files into the workbench +and open them in the WSDL editor. Opening them in the WSDL editor provides +you with an opportunity to have a structured viewing of the WSDL file.</p><p> <uicontrol>Prerequisite:</uicontrol> Create +a project. It is recommend that you create a Web project so that the WSDL +can be easily used to generate additional artifacts and deployed.</p><p>For +more information on creating a Web project, refer to the Web application development +documentation.</p><p>To import a WSDL file to your Web project:</p></context> +<steps> +<step><cmd>Select your project in the J2EE Navigator pane, and from the <uicontrol>File</uicontrol> menu, +select <uicontrol>Import</uicontrol>.</cmd></step> +<step><cmd>Select <uicontrol>File System</uicontrol> and click <uicontrol>Next</uicontrol>.</cmd> +</step> +<step><cmd>Click the <uicontrol>Browse</uicontrol> button on the next page +of the wizard to select the directories from which you would like to add the +WSDL.</cmd></step> +<step><cmd>In the import selection panes, use the following methods to select +exactly the resources you want to add: </cmd><info><ul> +<li>Expand the hierarchies in the left pane and select or clear the checkboxes +that represent the folders in the selected directory. Then in the right pane, +select or clear checkboxes for individual files.</li> +<li>Click <uicontrol>Filter Types</uicontrol> to filter the current selection +for files of a specific type.</li> +<li>Click <uicontrol>Select All</uicontrol> to select all resources in the +directory, then go through and deselect the ones that you do not want to add.</li> +<li>Click <uicontrol>Deselect All</uicontrol> to deselect all resources in +the directory, then go through and choose individual resources to add.</li> +</ul></info></step> +<step><cmd>Specify the Workbench project or folder that will be the import +destination.</cmd></step> +<step><cmd>When you have finished specifying your import options, click <uicontrol>Finish.</uicontrol></cmd> +</step> +</steps> +<result><p>After you have imported a WSDL file into the workbench and opened +it in the WSDL editor, you can edit it.</p><p>Alternately, you can import +a WSDL file using the WSDL Explorer. For more information, refer to: <xref +href="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdlexp.dita" +scope="peer"> Using the WSDL Explorer</xref>. </p></result> +<postreq><b>Known limitation when importing WSDL:</b> On some <tm tmclass="special" +tmowner="Microsoft Corporation" tmtype="reg" trademark="Windows">Windows</tm> systems, +the "Import to File System" operation may result in saving the HTML file rather +than the desired WSDL files. The workaround and fix for this problem is documented +in <tm tmclass="special" tmowner="Microsoft Corporation" tmtype="reg" trademark="Microsoft">Microsoft</tm> Knowledge +Base article Q281119. A dialog box may ask if you want to save "WSDLFileDownloader", +the message is incorrect and does not affect the actual name of the file saved. +If the file extension displays XML when selecting the save location for the +WSDL document, ignore the incorrect extension and continue the save. The file +will be saved with the WSDL extension.</postreq> +</taskbody> +<related-links> +<linklist><title>Related concepts</title> +<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.dita" scope="peer"> +<linktext>WSDL</linktext></link> +<link href="../concepts/cwsdled.dita" scope="local"></link> +</linklist> +<linklist><title>Related tasks</title> +<link href="tcrtwsdl.dita" scope="local"></link> +<link href="tedtwsdl.dita" scope="local"></link> +</linklist> +</related-links> +</task> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/timpwsdl.html b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/timpwsdl.html index 90a8205df..15fe0d954 100644 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/timpwsdl.html +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/timpwsdl.html @@ -1,25 +1,32 @@ -<?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> +<?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> -<!-- /******************************************************************************* - * 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" /> +<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="Importing a WSDL file" /> +<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.html" /> +<meta scheme="URI" name="DC.Relation" content="../concepts/cwsdled.html" /> +<meta scheme="URI" name="DC.Relation" content="tcrtwsdl.html" /> +<meta scheme="URI" name="DC.Relation" content="tedtwsdl.html" /> +<meta content="XHTML" name="DC.Format" /> +<meta content="timpwsdl" name="DC.Identifier" /> +<meta content="en-us" name="DC.Language" /> +<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> <title>Importing WSDL files</title> </head> <body id="timpwsdl"><a name="timpwsdl"><!-- --></a> + <h1 class="topictitle1">Importing a WSDL file</h1> -<div><div class="section"><p>The Web Service wizard assists you in creating a new Web service + + +<div> +<div class="section"><p>The Web Service wizard assists you in creating a new Web service from a WSDL file. You must first create or import a WSDL file. A WSDL file can be created using the WSDL editor. This is described in: <a href="../tasks/tcrtwsdl.html">Creating a new WSDL file</a>. To import a WSDL file follow the instructions below.</p> @@ -34,43 +41,62 @@ more information on creating a Web project, refer to the Web application develop documentation.</p> <p>To import a WSDL file to your Web project:</p> </div> -<ol><li class="stepexpand"><span>Select your project in the J2EE Navigator pane, and from the <span class="uicontrol">File</span> menu, + +<ol> +<li class="stepexpand"><span>Select your project in the J2EE Navigator pane, and from the <span class="uicontrol">File</span> menu, select <span class="uicontrol">Import</span>.</span></li> -<li class="stepexpand"><span>Select <span class="uicontrol">File System</span> and click <span class="uicontrol">Next</span>.</span></li> + +<li class="stepexpand"><span>Select <span class="uicontrol">File System</span> and click <span class="uicontrol">Next</span>.</span> +</li> + <li class="stepexpand"><span>Click the <span class="uicontrol">Browse</span> button on the next page of the wizard to select the directories from which you would like to add the WSDL.</span></li> + <li class="stepexpand"><span>In the import selection panes, use the following methods to select -exactly the resources you want to add: </span> <ul><li>Expand the hierarchies in the left pane and select or clear the checkboxes +exactly the resources you want to add: </span> <ul> +<li>Expand the hierarchies in the left pane and select or clear the checkboxes that represent the folders in the selected directory. Then in the right pane, select or clear checkboxes for individual files.</li> + <li>Click <span class="uicontrol">Filter Types</span> to filter the current selection for files of a specific type.</li> + <li>Click <span class="uicontrol">Select All</span> to select all resources in the directory, then go through and deselect the ones that you do not want to add.</li> + <li>Click <span class="uicontrol">Deselect All</span> to deselect all resources in the directory, then go through and choose individual resources to add.</li> + </ul> </li> + <li class="stepexpand"><span>Specify the Workbench project or folder that will be the import destination.</span></li> -<li class="stepexpand"><span>When you have finished specifying your import options, click <span class="uicontrol">Finish.</span></span></li> + +<li class="stepexpand"><span>When you have finished specifying your import options, click <span class="uicontrol">Finish.</span></span> +</li> + </ol> + <div class="section"><p>After you have imported a WSDL file into the workbench and opened it in the WSDL editor, you can edit it.</p> <p>Alternately, you can import -a WSDL file using the WSDL Explorer. For more information, refer to: <a href="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdlexp.html"> Using the WSDL Explorer</a>. </p> +a WSDL file using the WSDL Explorer. For more information, refer to: <a href="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdlexp.html">Using the WSDL Explorer</a>. </p> </div> -<div class="section"><strong>Known limitation when importing WSDL:</strong> On some Windows<sup>®</sup> systems, + +<div class="section"><strong>Known limitation when importing WSDL:</strong> On some Windows<sup>®</sup> systems, the "Import to File System" operation may result in saving the HTML file rather than the desired WSDL files. The workaround and fix for this problem is documented -in Microsoft<sup>®</sup> Knowledge +in Microsoft<sup>®</sup> Knowledge Base article Q281119. A dialog box may ask if you want to save "WSDLFileDownloader", the message is incorrect and does not affect the actual name of the file saved. If the file extension displays XML when selecting the save location for the WSDL document, ignore the incorrect extension and continue the save. The file will be saved with the WSDL extension.</div> + </div> + <div> <div class="linklist"><strong>Related concepts</strong><br /> @@ -80,7 +106,8 @@ will be saved with the WSDL extension.</div> <div class="linklist"><strong>Related tasks</strong><br /> <div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div> -<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created outside Rational Developer products into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> +<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> </div> + </body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetbind.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetbind.dita new file mode 100644 index 000000000..2b801d379 --- /dev/null +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetbind.dita @@ -0,0 +1,89 @@ +<?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="tsetbind" xml:lang="en-us"> +<title>Setting a binding</title> +<shortdesc>A binding is a top level WSDL object that provides a concrete specification +regarding the transmission of messages to and from a web service. A binding +references exactly one port type. The structure of a binding corresponds very +closely to that of the port type. The binding contains extensibility elements +(for example, soap, http, and mime) that specify protocol specific details. +Each port within a service references exactly one binding.</shortdesc> +<taskbody> +<context><p>You can create a new binding, reuse an existing one, or import +one.</p></context> +</taskbody> +<task id="createnewbind"> +<title>Creating a new binding</title> +<taskbody> +<context><p>To create a new binding for your port, follow these steps:</p></context> +<steps> +<step><cmd>In the Graph view, right-click your port and click <b>Set Binding</b>.</cmd> +</step> +<step><cmd>Select the <b>Create a new binding</b> radio button.</cmd></step> +<step><cmd>Type the name of the binding in <uicontrol>Name</uicontrol> field.</cmd> +<info>The name should be unique among all bindings defined within the enclosing +WSDL document. Click <b>Finish.</b></info></step> +<step><cmd>In order to see the binding you need to ensure the hide/show binding +button <image alt="hide/show binding button" href="../images/show-hide-binding.gif"> +</image> is toggled so that bindings are showing.</cmd></step> +<step><cmd>A <b>Port Type</b> is a named set of abstract operations and the +abstract messages involved.</cmd><info>You can either create a new port type +for your binding, reuse an existing one, or import one. Refer to the related +tasks for more details.</info></step> +<step><cmd>Type any information about the binding you want the user to read +in the <b>Documentation</b> field.</cmd></step> +</steps> +<result><p> <b>Tip</b>: You can also create a new binding for your port using +the Outline view.</p></result> +</taskbody> +</task> +<task id="reusebinding"> +<title>Reusing a binding for a port</title> +<taskbody> +<context><p>To reuse a binding for your port, follow these steps:</p></context> +<steps> +<step><cmd>In the Graph view, select your port.</cmd></step> +<step><cmd>From the <b>Binding</b> drop down list, select the binding you +want to use.</cmd></step> +</steps> +</taskbody> +</task> +<task id="regeneratingabinding"> +<title>Regenerating a binding</title> +<taskbody> +<context>To regenerate a binding:</context> +<steps> +<step><cmd>Right-click the binding you want to regenerate.</cmd></step> +<step><cmd>Select <uicontrol>Generate Binding Content</uicontrol>.</cmd></step> +<step><cmd>Specify an required binding information. If you are modifying an +existing binding, ensure that you select <uicontrol>Overwrite existing binding +information</uicontrol>.</cmd></step> +</steps> +</taskbody> +</task> +<task id="impbinding"> +<title>Import an existing binding</title> +<taskbody> +<context>To import an existing binding for your port, follow these steps:</context> +<steps> +<step><cmd>In the Graph view, right-click your port and click <b>Set Binding.</b></cmd> +</step> +<step><cmd>Click the <b>Import binding from a file</b> check box. Click <b>Browse</b>.</cmd> +</step> +<step><cmd>Select the file that contains the binding you want to use. Click + <b>OK</b>.</cmd></step> +</steps> +</taskbody> +<related-links> +<linklist><title>Related concepts</title><?Pub Caret?> +<link href="../concepts/cwsdled.dita" scope="local"></link> +</linklist> +<linklist><title>Related tasks</title> +<link href="tcrtwsdl.dita" scope="local"></link> +<link href="tedtwsdl.dita" scope="local"></link> +</linklist> +</related-links> +</task> +</task> +<?Pub *0000003826?> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetbind.html b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetbind.html index c53655ffb..8df3388c7 100644 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetbind.html +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetbind.html @@ -1,88 +1,149 @@ -<?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> +<?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> -<!-- /******************************************************************************* - * 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" /> +<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="Setting a binding" /> +<meta name="abstract" content="A binding is a top level WSDL object that provides a concrete specification regarding the transmission of messages to and from a web service. A binding references exactly one port type. The structure of a binding corresponds very closely to that of the port type. The binding contains extensibility elements (for example, soap, http, and mime) that specify protocol specific details. Each port within a service references exactly one binding." /> +<meta name="description" content="A binding is a top level WSDL object that provides a concrete specification regarding the transmission of messages to and from a web service. A binding references exactly one port type. The structure of a binding corresponds very closely to that of the port type. The binding contains extensibility elements (for example, soap, http, and mime) that specify protocol specific details. Each port within a service references exactly one binding." /> +<meta content="XHTML" name="DC.Format" /> +<meta content="tsetbind" 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>Setting a binding</title> </head> <body id="tsetbind"><a name="tsetbind"><!-- --></a> + <h1 class="topictitle1">Setting a binding</h1> + + <div><p>A binding is a top level WSDL object that provides a concrete specification regarding the transmission of messages to and from a web service. A binding references exactly one port type. The structure of a binding corresponds very closely to that of the port type. The binding contains extensibility elements (for example, soap, http, and mime) that specify protocol specific details. Each port within a service references exactly one binding.</p> + <div class="section"><p>You can create a new binding, reuse an existing one, or import one.</p> </div> + </div> + +<div class="nested1" id="createnewbind"><a name="createnewbind"><!-- --></a> +<h2 class="topictitle2">Creating a new binding</h2> + <div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created outside Rational Developer products into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div> -</div> -</div><div class="nested1" id="createnewbind"><a name="createnewbind"><!-- --></a><h2 class="topictitle2">Creating a new binding</h2> -<div><div class="section"><p>To create a new binding for your port, follow these steps:</p> +<div class="section"><p>To create a new binding for your port, follow these steps:</p> </div> -<ol><li class="stepexpand"><span>In the Graph view, right-click your port and click <strong>Set Binding</strong>.</span></li> + +<ol> +<li class="stepexpand"><span>In the Graph view, right-click your port and click <strong>Set Binding</strong>.</span> +</li> + <li class="stepexpand"><span>Select the <strong>Create a new binding</strong> radio button.</span></li> -<li class="stepexpand"><span>Type the name of the binding in <span class="uicontrol">Name</span> field.</span> The name should be unique among all bindings defined within the enclosing + +<li class="stepexpand"><span>Type the name of the binding in <span class="uicontrol">Name</span> field.</span> + The name should be unique among all bindings defined within the enclosing WSDL document. Click <strong>Finish.</strong></li> + <li class="stepexpand"><span>In order to see the binding you need to ensure the hide/show binding -button <img src="../images/show-hide-binding.gif" alt="hide/show binding button" /> is -toggled so that bindings are showing.</span></li> +button <img src="../images/show-hide-binding.gif" alt="hide/show binding button" /> is toggled so that bindings are showing.</span></li> + <li class="stepexpand"><span>A <strong>Port Type</strong> is a named set of abstract operations and the abstract messages involved.</span> You can either create a new port type for your binding, reuse an existing one, or import one. Refer to the related tasks for more details.</li> + <li class="stepexpand"><span>Type any information about the binding you want the user to read in the <strong>Documentation</strong> field.</span></li> + </ol> + <div class="section"><p> <strong>Tip</strong>: You can also create a new binding for your port using the Outline view.</p> </div> + +</div> + +<div> +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div> +</div> </div> </div> -<div class="nested1" id="reusebinding"><a name="reusebinding"><!-- --></a><h2 class="topictitle2">Reusing a binding for a port</h2> -<div><div class="section"><p>To reuse a binding for your port, follow these steps:</p> + +<div class="nested1" id="reusebinding"><a name="reusebinding"><!-- --></a> +<h2 class="topictitle2">Reusing a binding for a port</h2> + +<div> +<div class="section"><p>To reuse a binding for your port, follow these steps:</p> </div> -<ol><li><span>In the Graph view, select your port.</span></li> + +<ol> +<li><span>In the Graph view, select your port.</span></li> + <li><span>From the <strong>Binding</strong> drop down list, select the binding you want to use.</span></li> + </ol> + </div> + </div> -<div class="nested1" id="regeneratingabinding"><a name="regeneratingabinding"><!-- --></a><h2 class="topictitle2">Regenerating a binding</h2> -<div><div class="section">To regenerate a binding:</div> -<ol><li><span>Right-click the binding you want to regenerate.</span></li> + +<div class="nested1" id="regeneratingabinding"><a name="regeneratingabinding"><!-- --></a> +<h2 class="topictitle2">Regenerating a binding</h2> + +<div> +<div class="section">To regenerate a binding:</div> + +<ol> +<li><span>Right-click the binding you want to regenerate.</span></li> + <li><span>Select <span class="uicontrol">Generate Binding Content</span>.</span></li> + <li><span>Specify an required binding information. If you are modifying an existing binding, ensure that you select <span class="uicontrol">Overwrite existing binding information</span>.</span></li> + </ol> + </div> + </div> -<div class="nested1" id="impbinding"><a name="impbinding"><!-- --></a><h2 class="topictitle2">Import an existing binding</h2> -<div><div class="section">To import an existing binding for your port, follow these steps:</div> -<ol><li><span>In the Graph view, right-click your port and click <strong>Set Binding.</strong></span></li> -<li><span>Click the <strong>Import binding from a file</strong> check box. Click <strong>Browse</strong>.</span></li> + +<div class="nested1" id="impbinding"><a name="impbinding"><!-- --></a> +<h2 class="topictitle2">Import an existing binding</h2> + +<div> +<div class="section">To import an existing binding for your port, follow these steps:</div> + +<ol> +<li><span>In the Graph view, right-click your port and click <strong>Set Binding.</strong></span> +</li> + +<li><span>Click the <strong>Import binding from a file</strong> check box. Click <strong>Browse</strong>.</span> +</li> + <li><span>Select the file that contains the binding you want to use. Click <strong>OK</strong>.</span></li> + </ol> + </div> + <div> +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div> +</div> + <div class="linklist"><strong>Related concepts</strong><br /> <div><a href="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></div></div> @@ -90,8 +151,10 @@ information</span>.</span></li> <div class="linklist"><strong>Related tasks</strong><br /> <div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div> -<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created outside Rational Developer products into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> -</div></div> +<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> +</div> +</div> + </body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetprtt.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetprtt.dita new file mode 100644 index 000000000..ea94736c0 --- /dev/null +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetprtt.dita @@ -0,0 +1,86 @@ +<?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="tsetprtt" xml:lang="en-us"> +<title>Setting a port type</title> +<shortdesc>A port type is a named set of abstract operations and the abstract +messages involved. Each operation refers to an input message and output messages. +A port type is reference by a binding object. Each binding references exactly +one port type. Since each port refers to exactly one binding, each port has +exactly one port type.</shortdesc> +<taskbody> +<context><p>You can create a port type by right clicking on the port types +group and selecting <uicontrol>Add Child > portType</uicontrol> . As a convenience +you can also add a port type via a binding or port object. This allows you +to create a port type and modify the binding to reference to the new port +type in one action. You can either create a new port type for your binding, +re-use an existing one, or import one</p></context> +</taskbody> +<task id="createporttype"> +<title>Create a new port type</title> +<taskbody> +<context><p>If you want to create a new port type for your binding, follow +these steps:</p></context> +<steps> +<step><cmd>In the Graph view, right-click on a binding or port object (note +that port must reference a binding) and click <b>Set Port Type.</b></cmd> +</step> +<step><cmd>Click the <b>Create a new port type</b> radio button.</cmd></step> +<step><cmd>Type the name of the port type in the <b>Name of port type</b> field.</cmd> +<info>The name should be unique name among all port types defined within in +the enclosing WSDL document. Click <b>Finish</b>.</info></step> +<step><cmd>Click the port type. Type any information about the port type you +wish the user to read in the </cmd><info><b>Documentation</b> field.</info> +</step> +</steps> +<result><p> <b>Tip</b>: You can also create a new port type for your binding +using the Outline view.</p><p>Once you have created a port type, you can add +operations to it, which can send and receive messages.</p></result> +</taskbody> +</task> +<task id="reuseporttype"> +<title>Reuse a port type for a binding</title> +<taskbody> +<context><p>If you want to reuse a port type for your binding, follow these +steps:</p></context> +<steps> +<step><cmd>In the Graph view, right-click on a binding or port object (note +that port must reference a binding) and click <b>Set Port Type.</b></cmd> +</step> +<step><cmd>Click the <b>Select an existing port type</b> radio button.</cmd> +</step> +<step><cmd>The existing bindings will be listed. Select one and click <b>Finish</b>.</cmd> +</step> +</steps> +</taskbody> +</task> +<task id="importporttype"> +<title>Import a port type for a binding</title> +<taskbody> +<context><p>.If you want to import an existing port type for your binding, +follow these steps:</p></context> +<steps> +<step><cmd>In the Graph view, right-click on a binding or port object (note +that port must reference a binding) and click <b>Set Port Type.</b></cmd> +</step> +<step><cmd>Click the <b>Import port type from a file</b> radio button. Click + <b>Browse</b>.</cmd></step> +<step><cmd>Select the file that contains the port type you want to use. Click + <b>OK</b>.</cmd></step> +<step><cmd>The bindings in the file will be listed. Select one and click <b>Finish</b>.</cmd> +</step> +<step><cmd>Click the port type. Type any information about the port type +you wish the user to read in the <b>Documentation</b> field.</cmd></step> +</steps> +</taskbody> +<related-links> +<linklist><title>Related concepts</title> +<link href="../concepts/cwsdled.dita" scope="local"></link> +</linklist> +<linklist><title>Related tasks</title> +<link href="tcrtwsdl.dita" scope="local"></link> +<link href="tedtwsdl.dita" scope="local"></link> +</linklist> +</related-links> +</task> +</task> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetprtt.html b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetprtt.html index 105e521b6..0c5a12539 100644 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetprtt.html +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetprtt.html @@ -1,29 +1,34 @@ -<?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> +<?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> -<!-- /******************************************************************************* - * 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" /> +<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="Setting a port type" /> +<meta name="abstract" content="A port type is a named set of abstract operations and the abstract messages involved. Each operation refers to an input message and output messages. A port type is reference by a binding object. Each binding references exactly one port type. Since each port refers to exactly one binding, each port has exactly one port type." /> +<meta name="description" content="A port type is a named set of abstract operations and the abstract messages involved. Each operation refers to an input message and output messages. A port type is reference by a binding object. Each binding references exactly one port type. Since each port refers to exactly one binding, each port has exactly one port type." /> +<meta content="XHTML" name="DC.Format" /> +<meta content="tsetprtt" 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>Setting a port type</title> </head> <body id="tsetprtt"><a name="tsetprtt"><!-- --></a> + <h1 class="topictitle1">Setting a port type</h1> + + <div><p>A port type is a named set of abstract operations and the abstract messages involved. Each operation refers to an input message and output messages. A port type is reference by a binding object. Each binding references exactly one port type. Since each port refers to exactly one binding, each port has exactly one port type.</p> + <div class="section"><p>You can create a port type by right clicking on the port types group and selecting <span class="uicontrol">Add Child > portType</span> . As a convenience you can also add a port type via a binding or port object. This allows you @@ -31,57 +36,108 @@ to create a port type and modify the binding to reference to the new port type in one action. You can either create a new port type for your binding, re-use an existing one, or import one</p> </div> + </div> + +<div class="nested1" id="createporttype"><a name="createporttype"><!-- --></a> +<h2 class="topictitle2">Create a new port type</h2> + <div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created outside Rational Developer products into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div> -</div> -</div><div class="nested1" id="createporttype"><a name="createporttype"><!-- --></a><h2 class="topictitle2">Create a new port type</h2> -<div><div class="section"><p>If you want to create a new port type for your binding, follow +<div class="section"><p>If you want to create a new port type for your binding, follow these steps:</p> </div> -<ol><li class="stepexpand"><span>In the Graph view, right-click on a binding or port object (note -that port must reference a binding) and click <strong>Set Port Type.</strong></span></li> + +<ol> +<li class="stepexpand"><span>In the Graph view, right-click on a binding or port object (note +that port must reference a binding) and click <strong>Set Port Type.</strong></span> +</li> + <li class="stepexpand"><span>Click the <strong>Create a new port type</strong> radio button.</span></li> -<li class="stepexpand"><span>Type the name of the port type in the <strong>Name of port type</strong> field.</span> The name should be unique name among all port types defined within in + +<li class="stepexpand"><span>Type the name of the port type in the <strong>Name of port type</strong> field.</span> + The name should be unique name among all port types defined within in the enclosing WSDL document. Click <strong>Finish</strong>.</li> -<li class="stepexpand"><span>Click the port type. Type any information about the port type -you wish the user to read in the </span> <strong>Documentation</strong> field. </li> + +<li class="stepexpand"><span>Click the port type. Type any information about the port type you +wish the user to read in the </span> <strong>Documentation</strong> field. +</li> + </ol> + <div class="section"><p> <strong>Tip</strong>: You can also create a new port type for your binding using the Outline view.</p> <p>Once you have created a port type, you can add operations to it, which can send and receive messages.</p> </div> + +</div> + +<div> +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div> +</div> </div> </div> -<div class="nested1" id="reuseporttype"><a name="reuseporttype"><!-- --></a><h2 class="topictitle2">Reuse a port type for a binding</h2> -<div><div class="section"><p>If you want to reuse a port type for your binding, follow these + +<div class="nested1" id="reuseporttype"><a name="reuseporttype"><!-- --></a> +<h2 class="topictitle2">Reuse a port type for a binding</h2> + +<div> +<div class="section"><p>If you want to reuse a port type for your binding, follow these steps:</p> </div> -<ol><li><span>In the Graph view, right-click on a binding or port object (note -that port must reference a binding) and click <strong>Set Port Type.</strong></span></li> -<li><span>Click the <strong>Select an existing port type</strong> radio button.</span></li> -<li><span>The existing bindings will be listed. Select one and click <strong>Finish</strong>.</span></li> + +<ol> +<li><span>In the Graph view, right-click on a binding or port object (note +that port must reference a binding) and click <strong>Set Port Type.</strong></span> +</li> + +<li><span>Click the <strong>Select an existing port type</strong> radio button.</span> +</li> + +<li><span>The existing bindings will be listed. Select one and click <strong>Finish</strong>.</span> +</li> + </ol> + </div> + </div> -<div class="nested1" id="importporttype"><a name="importporttype"><!-- --></a><h2 class="topictitle2">Import a port type for a binding</h2> -<div><div class="section"><p>.If you want to import an existing port type for your binding, + +<div class="nested1" id="importporttype"><a name="importporttype"><!-- --></a> +<h2 class="topictitle2">Import a port type for a binding</h2> + +<div> +<div class="section"><p>.If you want to import an existing port type for your binding, follow these steps:</p> </div> -<ol><li><span>In the Graph view, right-click on a binding or port object (note -that port must reference a binding) and click <strong>Set Port Type.</strong></span></li> + +<ol> +<li><span>In the Graph view, right-click on a binding or port object (note +that port must reference a binding) and click <strong>Set Port Type.</strong></span> +</li> + <li><span>Click the <strong>Import port type from a file</strong> radio button. Click <strong>Browse</strong>.</span></li> + <li><span>Select the file that contains the port type you want to use. Click <strong>OK</strong>.</span></li> -<li><span>The bindings in the file will be listed. Select one and click <strong>Finish</strong>.</span></li> -<li><span>Click the port type. Type any information about the port type + +<li><span>The bindings in the file will be listed. Select one and click <strong>Finish</strong>.</span> +</li> + +<li><span>Click the port type. Type any information about the port type you wish the user to read in the <strong>Documentation</strong> field.</span></li> + </ol> + </div> + <div> +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div> +</div> + <div class="linklist"><strong>Related concepts</strong><br /> <div><a href="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></div></div> @@ -89,8 +145,10 @@ you wish the user to read in the <strong>Documentation</strong> field.</span></ <div class="linklist"><strong>Related tasks</strong><br /> <div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div> -<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created outside Rational Developer products into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> -</div></div> +<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div> +</div> +</div> + </body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/wswsdleditorc_toc.ditamap b/docs/org.eclipse.wst.wsdl.ui.doc.user/wswsdleditorc_toc.ditamap new file mode 100644 index 000000000..7de60ab8f --- /dev/null +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/wswsdleditorc_toc.ditamap @@ -0,0 +1,8 @@ +<?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#wswsdleditorc" +id="wswsdleditorc" title="wswsdleditorc"> +<topicref href="concepts/cwsdled.dita" navtitle="Web Services Description Language (WSDL) editor"> +</topicref> +</map> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/wswsdleditort_toc.ditamap b/docs/org.eclipse.wst.wsdl.ui.doc.user/wswsdleditort_toc.ditamap new file mode 100644 index 000000000..d966a71b9 --- /dev/null +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/wswsdleditort_toc.ditamap @@ -0,0 +1,27 @@ +<?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#wswsdleditort" +id="wswsdleditort" title="wswsdleditort"> +<topicref href="tasks/timpwsdl.dita" navtitle="Importing WSDL files"></topicref> +<topicref href="tasks/tcrtwsdl.dita" navtitle="Creating WSDL files"></topicref> +<topicref href="concepts/cwsdled.dita" navtitle="Web Services Description Language (WSDL) editor"> +<topicref href="tasks/tedtwsdl.dita" navtitle="Editing WSDL files"> +<topicref href="tasks/taddsrvc.dita" navtitle="Adding a service"></topicref> +<topicref href="tasks/taddport.dita" navtitle="Adding a port to a service"> +</topicref> +<topicref href="tasks/tsetprtt.dita" navtitle="Setting a port type"></topicref> +<topicref href="tasks/tsetbind.dita" navtitle="Setting a binding"></topicref> +<topicref href="tasks/taddoper.dita" navtitle="Adding an operation"></topicref> +<topicref href="tasks/taddmess.dita" navtitle="Adding a message"></topicref> +<topicref href="tasks/taddpart.dita" navtitle="Adding a part to a message"> +</topicref> +<topicref href="tasks/tcrtimpt.dita" navtitle="Creating an import statement"> +</topicref> +<topicref href="tasks/tcrttype.dita" navtitle="Creating a new type for your WSDL file"> +</topicref> +</topicref> +</topicref> +<topicref href="../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdlexp.dita" +navtitle="Exploring WSDL using the Web Services Explorer" scope="peer"></topicref> +</map> diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/wswsdleditort_toc.xml b/docs/org.eclipse.wst.wsdl.ui.doc.user/wswsdleditort_toc.xml index e8f72e4d3..d984e088d 100644 --- a/docs/org.eclipse.wst.wsdl.ui.doc.user/wswsdleditort_toc.xml +++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/wswsdleditort_toc.xml @@ -1,20 +1,22 @@ -<?xml version="1.0" encoding="utf-8"?> -<?NLS TYPE="org.eclipse.help.toc"?> +<?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#wswsdleditort" label="wswsdleditort" topic="tasks/timpwsdl.html"> - <topic label="Importing a WSDL file" href="tasks/timpwsdl.html"/> - <topic label="Creating a new WSDL file" href="tasks/tcrtwsdl.html"/> - <topic label="Editing WSDL files with the WSDL Editor" href="concepts/cwsdled.html"> - <topic label="Editing WSDL files" href="tasks/tedtwsdl.html"> - <topic label="Adding a service" href="tasks/taddsrvc.html"/> - <topic label="Adding a port to a service" href="tasks/taddport.html"/> - <topic label="Setting a port type" href="tasks/tsetprtt.html"/> - <topic label="Setting a binding" href="tasks/tsetbind.html"/> - <topic label="Adding an operation" href="tasks/taddoper.html"/> - <topic label="Adding a message" href="tasks/taddmess.html"/> - <topic label="Adding a part to a message" href="tasks/taddpart.html"/> - <topic label="Creating an import statement" href="tasks/tcrtimpt.html"/> - <topic label="Creating a new type for your WSDL file" href="tasks/tcrttype.html"/> - </topic> - </topic> - <topic label="Exploring WSDL using the Web Services Explorer" href="../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdlexp.html"/> -</toc>
\ No newline at end of file +<topic label="Importing a WSDL file" href="tasks/timpwsdl.html"/> +<topic label="Creating a new WSDL file" href="tasks/tcrtwsdl.html"/> +<topic label="Editing WSDL files with the WSDL Editor" href="concepts/cwsdled.html"> +<topic label="Editing WSDL files" href="tasks/tedtwsdl.html"> +<topic label="Adding a service" href="tasks/taddsrvc.html"/> +<topic label="Adding a port to a service" href="tasks/taddport.html"/> +<topic label="Setting a port type" href="tasks/tsetprtt.html"/> +<topic label="Setting a binding" href="tasks/tsetbind.html"/> +<topic label="Adding an operation" href="tasks/taddoper.html"/> +<topic label="Adding a message" href="tasks/taddmess.html"/> +<topic label="Adding a part to a message" href="tasks/taddpart.html"/> +<topic label="Creating an import statement" href="tasks/tcrtimpt.html"/> +<topic label="Creating a new type for your WSDL file" href="tasks/tcrttype.html"/> +</topic> +</topic> +<topic label="Exploring WSDL using the Web Services Explorer" href="../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdlexp.html"/> +</toc> diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/.cvsignore b/docs/org.eclipse.wst.wsi.ui.doc.user/.cvsignore index 93439c6ce..385a69c66 100644 --- a/docs/org.eclipse.wst.wsi.ui.doc.user/.cvsignore +++ b/docs/org.eclipse.wst.wsi.ui.doc.user/.cvsignore @@ -1,2 +1,3 @@ -build.xml org.eclipse.wst.wsi.ui.doc.user_1.0.0.jar +bak +temp diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/build.xml b/docs/org.eclipse.wst.wsi.ui.doc.user/build.xml new file mode 100644 index 000000000..a0adb1f99 --- /dev/null +++ b/docs/org.eclipse.wst.wsi.ui.doc.user/build.xml @@ -0,0 +1,59 @@ +<?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="wswsitest_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.wst.wsi.ui.doc.user/myplugin.xml b/docs/org.eclipse.wst.wsi.ui.doc.user/myplugin.xml new file mode 100644 index 000000000..10fcb0df6 --- /dev/null +++ b/docs/org.eclipse.wst.wsi.ui.doc.user/myplugin.xml @@ -0,0 +1,27 @@ +<?xml version="1.0"?> +<?eclipse version="3.0"?> +<!-- /******************************************************************************* + * 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 + *******************************************************************************/ --> +<!-- ================================================= --> +<!-- This is the plugin for declaring the help --> +<!-- contributions for using the tool. --> +<!-- ================================================= --> + +<plugin> + +<extension point="org.eclipse.help.toc"> + <toc file="wswsitest_toc.xml"/> + + +</extension> + + +</plugin>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/org.eclipse.wst.wsi.ui.doc.user.maplist b/docs/org.eclipse.wst.wsi.ui.doc.user/org.eclipse.wst.wsi.ui.doc.user.maplist new file mode 100644 index 000000000..3d58a2657 --- /dev/null +++ b/docs/org.eclipse.wst.wsi.ui.doc.user/org.eclipse.wst.wsi.ui.doc.user.maplist @@ -0,0 +1,8 @@ +<maplist version="3.6.2"> + <nav> + <map file="wswsitest_toc.ditamap"/> + </nav> + <link> + <map file="wswsitest_toc.ditamap"/> + </link> +</maplist> diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.dita b/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.dita new file mode 100644 index 000000000..d1f2204a5 --- /dev/null +++ b/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.dita @@ -0,0 +1,88 @@ +<?xml version="1.0" encoding="utf-8"?> +<!--Arbortext, Inc., 1988-2005, v.4002--> +<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd"> +<task id="tmonitor" xml:lang="en-us"> +<title>Using the TCP/IP Monitor to test Web services</title> +<titlealts> +<searchtitle>Using the TCP/IP or SOAP monitor to test Web services</searchtitle> +</titlealts> +<shortdesc>Once you have created your Web service and Web service client, +you can monitor the Web service's SOAP traffic using the TCP/IP Monitor.</shortdesc> +<taskbody> +<prereq><p> Prerequisites: </p><ul> +<li>Generate a Web service</li> +<li>Generate a Proxy and a sample application</li> +</ul></prereq> +<context><p>When creating a Web service using the Web service or Web service +client wizards, you can select to set up and run the TCP/IP Monitor automatically. +Alternately, you can set up the TCP/IP Monitor manually by completing the +following steps:</p></context> +<steps> +<step><cmd>In the sample application, invoke the getEndPoint method. Record +this endpoint. The default endpoint for a Web service is: http://localhost:<port>/<web +module context root>/services/<port></cmd></step><?Pub Caret1?> +<step><cmd>Create a server to act as the TCP/IP Monitor:</cmd> +<substeps> +<substep><cmd>From the Window menu, select <uicontrol>Preferences</uicontrol>. </cmd> +</substep> +<substep><cmd>In the Preferences window, expand Internet and then select <uicontrol>TCP/IP +Monitor</uicontrol>. </cmd></substep> +<substep><cmd>Select the <uicontrol>Show TCP/IP Monitor View when there is +activity</uicontrol> check box. </cmd></substep> +<substep><cmd>Under the TCP/IP Monitors lists, click <uicontrol>Add</uicontrol>. +A New Monitor dialog opens.</cmd></substep> +<substep><cmd>Specify the following settings: </cmd></substep> +</substeps> +<choicetable> +<chhead><choptionhd>Option</choptionhd><chdeschd>Description</chdeschd></chhead> +<chrow><choption>Local monitoring port</choption><chdesc>Specify a unique +port number on your local machine.</chdesc></chrow> +<chrow><choption>Host name</choption><chdesc>Specify the host name or IP address +of the machine where the server is running.</chdesc></chrow> +<chrow><choption>Port</choption><chdesc>Specify the port number of the remote +server.</chdesc></chrow> +<chrow><choption>Type</choption><chdesc>Specify whether the request type from +the Web browser are sent by HTTP or TCP/IP. If the HTTP option is selected +the requests from the Web browser are modified so that the HTTP header points +to the remote machine and separated if multiple HTTP requests are received +in the same connection. If the TCP/IP option is selected, all the requests +are sent byte for byte. </chdesc></chrow> +</choicetable> +</step> +<step><cmd>In order to route the Web service through the monitor, the endpoint +of the Web service client needs to be changed. The TCP/IP Monitor listens +on port 9081. In the Web browser window used in step 1, invoke the setEndPoint +method, and change the endpoint so that it directs to port 9081. For example, +the default would be: <codeph>http://localhost:9081/web_module_context_root/servlet/rpcrouter</codeph> Invoke +the getEndPoint method again to ensure that your change has been implemented.</cmd> +</step> +<step><cmd>Select a Web service method in the Methods pane. Invoke this method.</cmd> +</step> +<step><cmd>Change to the TCP/IP Monitor view by selecting the TCP/IP Monitor +tab in the Servers view. This will display request and response pairs that +are being routed through the TCP/IP Monitor. It will look similar to the following +picture: <image alt="Screen capture of request and response traffic" href="../images/traffic.gif" +placement="break"></image></cmd></step> +<step><cmd>To ensure that your Web service SOAP traffic is WS-I compliant, +you can generate a log file by clicking the <image alt="WS-I validation icon" +href="../images/wsivalico.gif"></image> icon. In the dialog box that opens, +select a name for the log file and specify where you want it to be stored. </cmd> +</step> +</steps> +<result>This log file will be validated for WS-I compliance. You can open +the log file in an XML editor to examine its contents.</result> +</taskbody> +<related-links> +<linklist><title>Related Concepts</title> +<link href="../../org.eclipse.jst.ws.doc.user/concepts/csoap.dita" scope="peer"> +<linktext>SOAP</linktext></link> +<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsiover.dita" scope="peer"> +<linktext>WS-I</linktext></link> +</linklist> +<linklist><title>Related Tasks</title> +<link href="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.dita" scope="peer"> +<linktext>Setting the level of WS-I compliance</linktext></link> +</linklist> +</related-links> +</task> +<?Pub *0000004710?> diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.html b/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.html index 0d58ba47e..8f5a2275e 100644 --- a/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.html +++ b/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.html @@ -1,93 +1,135 @@ -<?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> +<?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> -<!-- /******************************************************************************* - * 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" /> +<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> +<meta name="copyright" content="(C) Copyright 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright 2005" /> +<meta content="public" name="security" /> +<meta content="index,follow" name="Robots" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta content="task" name="DC.Type" /> +<meta name="DC.Title" content="Using the TCP/IP Monitor to test Web services" /> +<meta name="abstract" content="Once you have created your Web service and Web service client, you can monitor the Web service's SOAP traffic using the TCP/IP Monitor." /> +<meta name="description" content="Once you have created your Web service and Web service client, you can monitor the Web service's SOAP traffic using the TCP/IP Monitor." /> +<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/csoap.html" /> +<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsiover.html" /> +<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.html" /> +<meta content="XHTML" name="DC.Format" /> +<meta content="tmonitor" name="DC.Identifier" /> +<meta content="en-us" name="DC.Language" /> +<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> <title>Using the TCP/IP or SOAP monitor to test Web services</title> </head> <body id="tmonitor"><a name="tmonitor"><!-- --></a> + <h1 class="topictitle1">Using the TCP/IP Monitor to test Web services</h1> + + + <div><p>Once you have created your Web service and Web service client, you can monitor the Web service's SOAP traffic using the TCP/IP Monitor.</p> + <div class="p"><p> Prerequisites: </p> -<ul><li>Generate a Web service</li> +<ul> +<li>Generate a Web service</li> + <li>Generate a Proxy and a sample application</li> + </ul> </div> + <div class="section"><p>When creating a Web service using the Web service or Web service client wizards, you can select to set up and run the TCP/IP Monitor automatically. Alternately, you can set up the TCP/IP Monitor manually by completing the following steps:</p> </div> -<ol><li class="stepexpand">In the sample application, invoke the getEndPoint method. Record -this endpoint. The default endpoint for a Web service is: http://localhost:<port>/<web module -context root>/services/<port> + +<ol> +<li><span>In the sample application, invoke the getEndPoint method. Record +this endpoint. The default endpoint for a Web service is: http://localhost:<port>/<web +module context root>/services/<port></span></li> + +<li><span>Create a server to act as the TCP/IP Monitor:</span> +<ol type="a"> +<li><span>From the Window menu, select <span class="uicontrol">Preferences</span>. </span> </li> -<li class="stepexpand"><span>Create a server to act as the TCP/IP Monitor:</span><ol type="a"><li><span>From the Window menu, select <span class="uicontrol">Preferences</span>. </span></li> + <li><span>In the Preferences window, expand Internet and then select <span class="uicontrol">TCP/IP Monitor</span>. </span></li> + <li><span>Select the <span class="uicontrol">Show TCP/IP Monitor View when there is activity</span> check box. </span></li> + <li><span>Under the TCP/IP Monitors lists, click <span class="uicontrol">Add</span>. A New Monitor dialog opens.</span></li> + <li><span>Specify the following settings: </span></li> + </ol> -<table border="1" frame="hsides" rules="rows" cellpadding="4" cellspacing="0" summary="" class="choicetableborder"> -<thead><tr><th valign="bottom" align="left" id="d0e68-option">Option</th> -<th valign="bottom" align="left" id="d0e68-desc">Description</th></tr></thead> -<tbody><tr><td valign="top" headers="d0e68-option" id="d0e75"><strong>Local monitoring port</strong></td> -<td valign="top" headers="d0e68-desc d0e75">Specify a unique + +<table class="choicetableborder" summary="" cellspacing="0" cellpadding="4" rules="rows" frame="hsides" border="1"> +<thead><tr><th valign="bottom" id="N100BA-option">Option</th> +<th valign="bottom" id="N100BA-desc">Description</th></tr></thead> +<tbody> + +<tr><td valign="top" headers="N100BA-option" id="N100D3"><strong>Local monitoring port</strong></td> +<td valign="top" headers="N100BA-desc N100D3">Specify a unique port number on your local machine.</td> </tr> -<tr><td valign="top" headers="d0e68-option" id="d0e80"><strong>Host name</strong></td> -<td valign="top" headers="d0e68-desc d0e80">Specify the host name or IP address + +<tr><td valign="top" headers="N100BA-option" id="N100E2"><strong>Host name</strong></td> +<td valign="top" headers="N100BA-desc N100E2">Specify the host name or IP address of the machine where the server is running.</td> </tr> -<tr><td valign="top" headers="d0e68-option" id="d0e85"><strong>Port</strong></td> -<td valign="top" headers="d0e68-desc d0e85">Specify the port number of the remote + +<tr><td valign="top" headers="N100BA-option" id="N100F1"><strong>Port</strong></td> +<td valign="top" headers="N100BA-desc N100F1">Specify the port number of the remote server.</td> </tr> -<tr><td valign="top" headers="d0e68-option" id="d0e90"><strong>Type</strong></td> -<td valign="top" headers="d0e68-desc d0e90">Specify whether the request type from + +<tr><td valign="top" headers="N100BA-option" id="N10100"><strong>Type</strong></td> +<td valign="top" headers="N100BA-desc N10100">Specify whether the request type from the Web browser are sent by HTTP or TCP/IP. If the HTTP option is selected the requests from the Web browser are modified so that the HTTP header points to the remote machine and separated if multiple HTTP requests are received in the same connection. If the TCP/IP option is selected, all the requests are sent byte for byte. </td> </tr> + </tbody></table> + </li> -<li class="stepexpand"><span>In order to route the Web service through the monitor, the endpoint + +<li><span>In order to route the Web service through the monitor, the endpoint of the Web service client needs to be changed. The TCP/IP Monitor listens on port 9081. In the Web browser window used in step 1, invoke the setEndPoint method, and change the endpoint so that it directs to port 9081. For example, the default would be: <samp class="codeph">http://localhost:9081/web_module_context_root/servlet/rpcrouter</samp> Invoke -the getEndPoint method again to ensure that your change has been implemented.</span></li> -<li class="stepexpand"><span>Select a Web service method in the Methods pane. Invoke this method.</span></li> -<li class="stepexpand"><span>Change to the TCP/IP Monitor view by selecting the TCP/IP Monitor +the getEndPoint method again to ensure that your change has been implemented.</span> +</li> + +<li><span>Select a Web service method in the Methods pane. Invoke this method.</span> +</li> + +<li><span>Change to the TCP/IP Monitor view by selecting the TCP/IP Monitor tab in the Servers view. This will display request and response pairs that are being routed through the TCP/IP Monitor. It will look similar to the following picture: <br /><img src="../images/traffic.gif" alt="Screen capture of request and response traffic" /><br /></span></li> -<li class="stepexpand"><span>To ensure that your Web service SOAP traffic is WS-I compliant, + +<li><span>To ensure that your Web service SOAP traffic is WS-I compliant, you can generate a log file by clicking the <img src="../images/wsivalico.gif" alt="WS-I validation icon" /> icon. In the dialog box that opens, -select a name for the log file and specify where you want it to be stored. </span></li> +select a name for the log file and specify where you want it to be stored. </span> +</li> + </ol> + <div class="section">This log file will be validated for WS-I compliance. You can open the log file in an XML editor to examine its contents.</div> + </div> + <div> <div class="linklist"><strong>Related Concepts</strong><br /> @@ -98,5 +140,6 @@ the log file in an XML editor to examine its contents.</div> <div><a href="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.html">Setting the level of WS-I compliance</a></div></div> </div> + </body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsdlval.dita b/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsdlval.dita new file mode 100644 index 000000000..ae708f129 --- /dev/null +++ b/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsdlval.dita @@ -0,0 +1,50 @@ +<?xml version="1.0" encoding="utf-8"?> +<!--Arbortext, Inc., 1988-2005, v.4002--> +<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd"> +<task id="twsdlval" xml:lang="en-us"> +<title>Validating WSDL files</title> +<titlealts> +<searchtitle>Validating WSDL files</searchtitle> +</titlealts> +<shortdesc>If you have created a WSDL file through the Web services wizard +the WSDL that is generated should be valid. However, if you have imported +a WSDL file, or if you are creating a WSDL file, you should validate the WSDL +to ensure it is valid.</shortdesc> +<taskbody> +<context><?Pub Caret?><p>If you have selected Require or Suggest WS-I Compliance +on the WS-I Compliance preference page, the validation also checks WS-I compliance. +If you have selected Ignore WS-I Compliance the validator will only check +the validity of the WSDL. For more information on setting WS-I compliance +levels, refer to: <xref href="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.dita" +scope="peer"> Setting the level of WS-I compliance</xref>.</p><p>The WSDL +Validator compares the WSDL file in your project to the W3C <xref format="html" +href="http://www.w3.org/TR/wsdl" scope="external">Web Services Description +Language (WSDL) 1.1</xref> specifications, and the WS-I compliance settings +that you have selected.</p><p>To validate your WSDL, complete the following +steps:</p></context> +<steps> +<step><cmd>Select a WSDL file in the <b>Project Navigator</b> view.</cmd> +</step> +<step><cmd>Right-click the WSDL file, and select <b>Validate WSDL file.</b></cmd> +</step> +</steps> +<result>Any problems encountered while validating the file will be shown in +the <b>Tasks</b> view.<p>When you rebuild a project or save a resource, the +WSDL Validator can be set to run automatically. To do this, from the Window +menu, select <b>Preferences</b> > <b>Validation</b>. Ensure that the check +box beside WSDL Validator is selected.</p></result> +</taskbody> +<related-links> +<linklist><title>Related Concepts</title> +<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.dita" scope="peer"> +<linktext>WSDL</linktext></link> +<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsiover.dita" scope="peer"> +<linktext>WS-I</linktext></link> +</linklist> +<linklist><title>Related Tasks</title> +<link href="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.dita" scope="peer"> +<linktext>Setting WS-I compliance</linktext></link> +</linklist> +</related-links> +</task> +<?Pub *0000002471?> diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsdlval.html b/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsdlval.html index 9309a247f..8eb6d2b23 100644 --- a/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsdlval.html +++ b/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsdlval.html @@ -1,50 +1,67 @@ -<?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> +<?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> -<!-- /******************************************************************************* - * 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" /> +<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> +<meta name="copyright" content="(C) Copyright 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright 2005" /> +<meta content="public" name="security" /> +<meta content="index,follow" name="Robots" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta content="task" name="DC.Type" /> +<meta name="DC.Title" content="Validating WSDL files" /> +<meta name="abstract" content="If you have created a WSDL file through the Web services wizard the WSDL that is generated should be valid. However, if you have imported a WSDL file, or if you are creating a WSDL file, you should validate the WSDL to ensure it is valid." /> +<meta name="description" content="If you have created a WSDL file through the Web services wizard the WSDL that is generated should be valid. However, if you have imported a WSDL file, or if you are creating a WSDL file, you should validate the WSDL to ensure it is valid." /> +<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.html" /> +<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsiover.html" /> +<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.html" /> +<meta content="XHTML" name="DC.Format" /> +<meta content="twsdlval" name="DC.Identifier" /> +<meta content="en-us" name="DC.Language" /> +<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> <title>Validating WSDL files</title> </head> <body id="twsdlval"><a name="twsdlval"><!-- --></a> + <h1 class="topictitle1">Validating WSDL files</h1> -<div><div class="section"><p>If you have created a WSDL file through the Web services wizard + + + +<div><p>If you have created a WSDL file through the Web services wizard the WSDL that is generated should be valid. However, if you have imported a WSDL file, or if you are creating a WSDL file, you should validate the WSDL to ensure it is valid.</p> -<p>If you have selected Require or Suggest WS-I -Compliance on the WS-I Compliance preference page, the validation also checks -WS-I compliance. If you have selected Ignore WS-I Compliance the validator -will only check the validity of the WSDL. For more information on setting -WS-I compliance levels, refer to: <a href="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.html"> Setting the level of WS-I compliance</a>.</p> + +<div class="section"><p>If you have selected Require or Suggest WS-I Compliance +on the WS-I Compliance preference page, the validation also checks WS-I compliance. +If you have selected Ignore WS-I Compliance the validator will only check +the validity of the WSDL. For more information on setting WS-I compliance +levels, refer to: <a href="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.html">Setting the level of WS-I compliance</a>.</p> <p>The WSDL -Validator compares the WSDL file in your project to the W3C <a href="http://www.w3.org/TR/wsdl" target="_blank">Web Services Description -Language (WSDL) 1.1</a> specifications, and the WS-I compliance settings +Validator compares the WSDL file in your project to the W3C <a href="http://www.w3.org/TR/wsdl" target="_blank">Web Services Description Language (WSDL) 1.1</a> specifications, and the WS-I compliance settings that you have selected.</p> <p>To validate your WSDL, complete the following steps:</p> </div> -<ol><li><span>Select a WSDL file in the <strong>Project Navigator</strong> view.</span></li> -<li><span>Right-click the WSDL file, and select <strong>Validate WSDL file.</strong></span></li> + +<ol> +<li><span>Select a WSDL file in the <strong>Project Navigator</strong> view.</span> +</li> + +<li><span>Right-click the WSDL file, and select <strong>Validate WSDL file.</strong></span> +</li> + </ol> + <div class="section">Any problems encountered while validating the file will be shown in the <strong>Tasks</strong> view.<p>When you rebuild a project or save a resource, the WSDL Validator can be set to run automatically. To do this, from the Window menu, select <strong>Preferences</strong> > <strong>Validation</strong>. Ensure that the check box beside WSDL Validator is selected.</p> </div> + </div> + <div> <div class="linklist"><strong>Related Concepts</strong><br /> @@ -55,5 +72,6 @@ box beside WSDL Validator is selected.</p> <div><a href="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.html">Setting WS-I compliance</a></div></div> </div> + </body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsival.dita b/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsival.dita new file mode 100644 index 000000000..462bbbbaf --- /dev/null +++ b/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsival.dita @@ -0,0 +1,47 @@ +<?xml version="1.0" encoding="utf-8"?> +<!--Arbortext, Inc., 1988-2005, v.4002--> +<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd"> +<task id="twsival" xml:lang="en-us"> +<title>Validating WS-I Web service traffic compliance</title> +<titlealts> +<searchtitle>Validating WS-I Web service traffic compliance</searchtitle> +</titlealts> +<shortdesc>As well as setting the level of WS-I compliance during Web services +creation, you can validate WS-I compliance of the SOAP traffic a Web service +produces through the TCP/IP Monitor.</shortdesc> +<taskbody> +<prereq> Prerequisites: Before you can use the validation tool to ensure that +your Web service SOAP traffic is WS-I compliant, you must have completed the +following steps:<ul> +<li>Generate a Web service.</li> +<li> <xref href="twsdlval.dita">Validate the WSDL that is produced.</xref> </li> +<li>Generate a Proxy and a sample application. </li> +<li> <xref href="tmonitor.dita">Set up the TCP/IP Monitor.</xref> Ensure that +your Web service sample application traffic is directed through the TCP/IP +Monitor.</li> +</ul></prereq> +<context><p>To validate your Web service, complete the following steps:</p></context> +<steps> +<step><cmd>Invoke a method in your Web service sample application to generate +traffic through the TCP/IP Monitor.</cmd></step> +<step><cmd>To ensure that your Web service SOAP traffic is WS-I compliant, +you can generate a log file by clicking the <image alt="Validate icon" href="../images/wsivalico.gif"> +</image> icon.</cmd></step> +<step><cmd>In the dialog box that opens, select a name for the log file and +specify where you want it to be stored.</cmd></step> +</steps> +<result> This log file will show whether or not messages sent to and from +your Web service are WS-I compliant, and list any non-compliant elements. +You can open the log file in an XML editor to examine its contents.</result> +</taskbody> +<related-links> +<linklist><title>Related Concepts</title> +<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsiover.dita" scope="peer"> +<linktext>WS-I</linktext></link> +</linklist> +<linklist><title>Related Tasks</title> +<link href="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.dita" scope="peer"> +<linktext>Setting the level of WS-I compliance</linktext></link> +</linklist> +</related-links> +</task> diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsival.html b/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsival.html index 08287c1c9..3896d2721 100644 --- a/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsival.html +++ b/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsival.html @@ -1,50 +1,72 @@ -<?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> +<?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> -<!-- /******************************************************************************* - * 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" /> +<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> +<meta name="copyright" content="(C) Copyright 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright 2005" /> +<meta content="public" name="security" /> +<meta content="index,follow" name="Robots" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta content="task" name="DC.Type" /> +<meta name="DC.Title" content="Validating WS-I Web service traffic compliance" /> +<meta name="abstract" content="As well as setting the level of WS-I compliance during Web services creation, you can validate WS-I compliance of the SOAP traffic a Web service produces through the TCP/IP Monitor." /> +<meta name="description" content="As well as setting the level of WS-I compliance during Web services creation, you can validate WS-I compliance of the SOAP traffic a Web service produces through the TCP/IP Monitor." /> +<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsiover.html" /> +<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.html" /> +<meta content="XHTML" name="DC.Format" /> +<meta content="twsival" name="DC.Identifier" /> +<meta content="en-us" name="DC.Language" /> +<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> <title>Validating WS-I Web service traffic compliance</title> </head> <body id="twsival"><a name="twsival"><!-- --></a> + <h1 class="topictitle1">Validating WS-I Web service traffic compliance</h1> + + + <div><p>As well as setting the level of WS-I compliance during Web services creation, you can validate WS-I compliance of the SOAP traffic a Web service produces through the TCP/IP Monitor.</p> -<div class="p"> Prerequisites: Before you can use the validation tool to ensure -that your Web service SOAP traffic is WS-I compliant, you must have completed -the following steps:<ul><li>Generate a Web service.</li> + +<div class="p"> Prerequisites: Before you can use the validation tool to ensure that +your Web service SOAP traffic is WS-I compliant, you must have completed the +following steps:<ul> +<li>Generate a Web service.</li> + <li> <a href="twsdlval.html">Validate the WSDL that is produced.</a> </li> + <li>Generate a Proxy and a sample application. </li> + <li> <a href="tmonitor.html">Set up the TCP/IP Monitor.</a> Ensure that your Web service sample application traffic is directed through the TCP/IP Monitor.</li> + </ul> </div> + <div class="section"><p>To validate your Web service, complete the following steps:</p> </div> -<ol><li><span>Invoke a method in your Web service sample application to generate + +<ol> +<li><span>Invoke a method in your Web service sample application to generate traffic through the TCP/IP Monitor.</span></li> + <li><span>To ensure that your Web service SOAP traffic is WS-I compliant, you can generate a log file by clicking the <img src="../images/wsivalico.gif" alt="Validate icon" /> icon.</span></li> + <li><span>In the dialog box that opens, select a name for the log file and specify where you want it to be stored.</span></li> + </ol> + <div class="section"> This log file will show whether or not messages sent to and from your Web service are WS-I compliant, and list any non-compliant elements. You can open the log file in an XML editor to examine its contents.</div> + </div> + <div> <div class="linklist"><strong>Related Concepts</strong><br /> @@ -54,5 +76,6 @@ You can open the log file in an XML editor to examine its contents.</div> <div><a href="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.html">Setting the level of WS-I compliance</a></div></div> </div> + </body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/wswsitest_toc.ditamap b/docs/org.eclipse.wst.wsi.ui.doc.user/wswsitest_toc.ditamap new file mode 100644 index 000000000..fd982c9ac --- /dev/null +++ b/docs/org.eclipse.wst.wsi.ui.doc.user/wswsitest_toc.ditamap @@ -0,0 +1,11 @@ +<?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#wswsitest" +id="wswsitest" title="wswsitest"> +<topicref href="tasks/twsdlval.dita" navtitle="Validating WSDL"></topicref> +<topicref href="tasks/tmonitor.dita" navtitle="Testing Web services with the TCP/IP Monitor"> +</topicref> +<topicref href="tasks/twsival.dita" navtitle="Validating WS-I compliance of Web service SOAP traffic"> +</topicref> +</map> diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/wswsitest_toc.xml b/docs/org.eclipse.wst.wsi.ui.doc.user/wswsitest_toc.xml index 008174183..a1020aec7 100644 --- a/docs/org.eclipse.wst.wsi.ui.doc.user/wswsitest_toc.xml +++ b/docs/org.eclipse.wst.wsi.ui.doc.user/wswsitest_toc.xml @@ -1,17 +1,9 @@ -<?xml version="1.0" encoding="utf-8"?> +<?xml version="1.0" encoding="UTF-8"?> + <?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 - *******************************************************************************/ --> -<toc label="wswsitest" link_to="../org.eclipse.jst.ws.doc.user/webservice_toc.xml#wswsitest" topic="tasks/twsdlval.html"> - <topic label="Validating WSDL files" href="tasks/twsdlval.html"/> - <topic label="Using the TCP/IP Monitor to test Web services" href="tasks/tmonitor.html"/> - <topic label="Validating WS-I Web service traffic compliance" href="tasks/twsival.html"/> -</toc>
\ No newline at end of file + +<toc link_to="../org.eclipse.jst.ws.doc.user/webservice_toc.xml#wswsitest" label="wswsitest" topic="tasks/twsdlval.html"> +<topic label="Validating WSDL files" href="tasks/twsdlval.html"/> +<topic label="Using the TCP/IP Monitor to test Web services" href="tasks/tmonitor.html"/> +<topic label="Validating WS-I Web service traffic compliance" href="tasks/twsival.html"/> +</toc> |
