This commit was manufactured by cvs2svn to create tag 'R2_0_2'.
diff --git a/docs/org.eclipse.jst.ws.axis.infopop/.cvsignore b/docs/org.eclipse.jst.ws.axis.infopop/.cvsignore
new file mode 100644
index 0000000..c14487c
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.infopop/.cvsignore
@@ -0,0 +1 @@
+build.xml
diff --git a/docs/org.eclipse.jst.ws.axis.infopop/.project b/docs/org.eclipse.jst.ws.axis.infopop/.project
new file mode 100644
index 0000000..ac4579a
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.infopop/.project
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.jst.ws.axis.infopop</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ <buildCommand>
+ <name>org.eclipse.pde.ManifestBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.pde.SchemaBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ </buildSpec>
+ <natures>
+ <nature>org.eclipse.pde.PluginNature</nature>
+ </natures>
+</projectDescription>
diff --git a/docs/org.eclipse.jst.ws.axis.infopop/META-INF/MANIFEST.MF b/docs/org.eclipse.jst.ws.axis.infopop/META-INF/MANIFEST.MF
new file mode 100644
index 0000000..dcebf3d
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.infopop/META-INF/MANIFEST.MF
@@ -0,0 +1,8 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: %pluginName
+Bundle-SymbolicName: org.eclipse.jst.ws.axis.infopop; singleton:=true
+Bundle-Version: 1.0.203.qualifier
+Bundle-Vendor: %pluginProvider
+Bundle-Localization: plugin
+Eclipse-LazyStart: true
diff --git a/docs/org.eclipse.jst.ws.axis.infopop/about.html b/docs/org.eclipse.jst.ws.axis.infopop/about.html
new file mode 100644
index 0000000..73db36e
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.infopop/about.html
@@ -0,0 +1,34 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<HTML>
+
+<head>
+<title>About</title>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+</head>
+
+<BODY lang="EN-US">
+
+<H3>About This Content</H3>
+
+<P>June 06, 2007</P>
+
+<H3>License</H3>
+
+<P>The Eclipse Foundation makes available all content in this plug-in
+("Content"). Unless otherwise indicated below, the Content is provided to you
+under the terms and conditions of the Eclipse Public License Version 1.0
+("EPL"). A copy of the EPL is available at
+<A href="http://www.eclipse.org/org/documents/epl-v10.php">http://www.eclipse.org/org/documents/epl-v10.php</A>.
+For purposes of the EPL, "Program" will mean the Content.</P>
+
+<P>If you did not receive this Content directly from the Eclipse Foundation, the
+Content is being redistributed by another party ("Redistributor") and different
+terms and conditions may apply to your use of any object code in the Content.
+Check the Redistributors license that was provided with the Content. If no such
+license exists, contact the Redistributor. Unless otherwise indicated below, the
+terms and conditions of the EPL still apply to any source code in the Content
+and such source code may be obtained at
+<A href="http://www.eclipse.org/">http://www.eclipse.org/</A>.</P>
+
+</BODY>
+</HTML>
diff --git a/docs/org.eclipse.jst.ws.axis.infopop/axisconsumptionui-f1Contexts.xml b/docs/org.eclipse.jst.ws.axis.infopop/axisconsumptionui-f1Contexts.xml
new file mode 100644
index 0000000..edec21d
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.infopop/axisconsumptionui-f1Contexts.xml
@@ -0,0 +1,90 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?NLS TYPE="org.eclipse.help.contexts"?>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<contexts>
+
+<!--WebServiceAxisProxyPage.java-->
+
+<context id="PWJB0003">
+<!--Folder field of the WSDL to Java Bindings Page-->
+<description>Select the project in which the Web service will be created.</description>
+</context>
+
+<context id="PWJB0009">
+<!--Indicates whether to generate a proxy or not-->
+<description>Select this check box 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.</description>
+</context>
+
+<context id="PWJB0016">
+<!--Show Mappings checkbox of the Bean Methods Page-->
+<description>Select this check box to customize the mappings between packages and namespaces.</description>
+</context>
+
+<!--WebServiceAxisMappingsPage.java-->
+
+<context id="PWJM0001">
+<!--WSDL to Java Mappings Page-->
+<description>Use this panel to add customized package to namespace mappings.</description>
+</context>
+
+<!--WebServiceAxisPreferencePage.java-->
+
+<context id="PPAE0001">
+<!--Axis Emitter Preference Page-->
+<description>Use this panel to add customized package to namespace mappings.</description>
+</context>
+
+<context id="PPAE0002">
+<!--Generate code for all elements-->
+<description>By default, WSDL2Java only generates code for those elements in the WSDL file
+that are referenced.</description>
+</context>
+
+<context id="PPAE0003">
+<!--Emits separate Helper classes for metadata-->
+<description>If you select this option WSDL2Java will create a separate helper class that
+contains the metadata rather than including it in the skeleton.</description>
+</context>
+
+<context id="PPAE0004">
+<!--Prefers building beans to straight arrays for wrapped XML array types-->
+<description>If you would rather a specific JavaBean class (ArrayOfString) be generated
+for these types of schemas, select this option.</description>
+</context>
+
+<context id="PPAE0005">
+<!--Add scope to deploy.wsdd-->
+<description>This indicates how to deploy the server implementation. Application uses one
+instance of the implementation class for all requests. Request creates a new
+instance of the implementation class for each request. Session creates a new
+instance of the implementation class for each session.</description>
+</context>
+
+<context id="PPAE0006">
+<!--Timeout-->
+<description>The default is 45. Use -1 to disable the timeout.</description>
+</context>
+
+<context id="PPAE0007">
+<!--Look for allowed methods in inherited class-->
+<description>If this option is specified, the Java2WSDL parser will look into extended
+classes to determine the list of methods to export into the WSDL file.</description>
+</context>
+
+<context id="PPAE0010">
+<!--validate against JAXRPC-->
+<description>If selected, the tools will examine the Java service class and its
+value types to determine if it satisfies important requirements of the JAX-RPC
+specification.</description>
+</context>
+
+</contexts>
diff --git a/docs/org.eclipse.jst.ws.axis.infopop/axiscreationui-f1Contexts.xml b/docs/org.eclipse.jst.ws.axis.infopop/axiscreationui-f1Contexts.xml
new file mode 100644
index 0000000..8e6ddf6
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.infopop/axiscreationui-f1Contexts.xml
@@ -0,0 +1,100 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?NLS TYPE="org.eclipse.help.contexts"?>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<contexts>
+<!--WebServiceAxisBeanClassPage.java-->
+
+<context id="PBCL0001">
+<!--Bean Selection Page-->
+<description>Use this page to select the Java bean from which you will create your Web service.</description>
+</context>
+
+<context id="PBCL0002">
+<!--Bean Selection field of the Bean Selection Page-->
+<description>Enter the name of the Java bean to be used to create the Web service. Defaults the selected Java bean. Click <b>Browse classes </b>to view the bean class of the selected Java bean. The bean class is a model or template (an abstract data type) that can be instantiated to create objects with a common definition and therefore, common properties, operations, and behavior. Click <b>Browse files </b>to select a Java bean from the project.</description>
+</context>
+
+<context id="PBCL0003">
+<!--Bean Class Browse button of the Bean Selection Page-->
+<description>Click to view the bean class of the selected Java bean.</description>
+</context>
+
+<context id="PBCL0004">
+<!--Bean Resource Browse button of the Bean Selection Page-->
+<description>Click this button to browse to a Java bean on your system to be used to create a Web service.</description>
+</context>
+
+<!--WebServiceAxisBeanConfigPage.java-->
+<context id="PBCF0001">
+<!--Bean Identity Page-->
+<description>On this page you can select the name of the WSDL file that will be generated, and the methods that will be included in the Web service.</description>
+</context>
+<context id="PBCF0002">
+<!--URI field of the Bean Config Page-->
+<description>This field contains the unique identifier of the Web service. It is read-only.</description>
+</context>
+<context id="PBCF0007">
+<!--WSDL File field of the Bean Config Page-->
+<description>This field contains the name of the WSDL file that will be generated. Accept the default or enter a new name.</description>
+</context>
+
+<context id="PBME0002">
+<!--Methods tree of the Bean Methods Page-->
+<description>Select from the available Java bean methods which ones to include in your Web service.</description>
+</context>
+<context id="PBME0010">
+<!--Select All button of the Bean Methods Page-->
+<description>Click this button to include all listed methods in your Web service.</description>
+</context>
+<context id="PBME0011">
+<!--Deselect All button of the Bean Methods Page-->
+<description>Click this button to remove all listed methods from your Web service.</description>
+</context>
+
+<context id="PBCF0016">
+<!--Show Mappings checkbox of the Bean Methods Page-->
+<description>Select this check box to customize the mappings between packages and namespaces.</description>
+</context>
+
+
+<!--WebServiceSkeletonAxisConfigPage.java-->
+
+<context id="PBSC0001">
+<!--Skeleton Config Page-->
+<description>Use this page to specify information about the Java bean skeleton being created.</description>
+</context>
+<context id="PBCF0002">
+<!--URI field of the Bean Config Page-->
+<description>This field lists the SOAP body namespace and unique identifier of the Web service being created.</description>
+</context>
+<context id="PBCF0006">
+<!--WSDL Folder field in the Bean Config Page-->
+<description>This field lists the location of the WSDL file being generated.</description>
+</context>
+<context id="PBCF0007">
+<!--WSDL File field of the Bean Config Page-->
+<description>Enter the name of the WSDL file being created, or accept the default.</description>
+</context>
+<context id="PBSC0004">
+<!--Skeleton Folder field of the Skeleton Config Page-->
+<description>Enter the location where the Java bean skeleton will be created, or accept the default.</description>
+</context>
+<context id="PBSC0005">
+<!--Skeleton Folder Browse button of the Skeleton Config Page-->
+<description>Use this button to browse to the location where you want the Java bean skeleton to be created.</description>
+</context>
+<context id="PBCF0016">
+<!--Show Mappings checkbox of the Bean Methods Page-->
+<description>Select this check box to customize the mappings between packages and namespaces.</description>
+</context>
+
+</contexts>
diff --git a/docs/org.eclipse.jst.ws.axis.infopop/build.properties b/docs/org.eclipse.jst.ws.axis.infopop/build.properties
new file mode 100644
index 0000000..c42b45a
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.infopop/build.properties
@@ -0,0 +1,7 @@
+bin.includes = axisconsumptionui-f1Contexts.xml,\
+ axiscreationui-f1Contexts.xml,\
+ plugin.xml,\
+ plugin.properties,\
+ about.html,\
+ META-INF/
+src.includes = build.properties
diff --git a/docs/org.eclipse.jst.ws.axis.infopop/plugin.properties b/docs/org.eclipse.jst.ws.axis.infopop/plugin.properties
new file mode 100644
index 0000000..3950bae
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.infopop/plugin.properties
@@ -0,0 +1,3 @@
+# properties file for org.eclipse.jst.ws.axis.infopop
+pluginName = Web services Axis context sensitive help
+pluginProvider = Eclipse.org
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.ws.axis.infopop/plugin.xml b/docs/org.eclipse.jst.ws.axis.infopop/plugin.xml
new file mode 100644
index 0000000..3c0dc11
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.infopop/plugin.xml
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?NLS TYPE="org.eclipse.help.toc"?>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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.contexts">
+ <contexts file="axisconsumptionui-f1Contexts.xml" plugin="org.eclipse.jst.ws.axis.consumption.ui"/>
+ <contexts file="axiscreationui-f1Contexts.xml" plugin="org.eclipse.jst.ws.axis.creation.ui"/>
+ </extension>
+</plugin>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/.cvsignore b/docs/org.eclipse.jst.ws.axis.ui.doc.user/.cvsignore
new file mode 100644
index 0000000..5e1193f
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/.cvsignore
@@ -0,0 +1,4 @@
+org.eclipse.jst.ws.axis.ui.doc.user_1.0.0.jar
+bak
+temp
+build.xml
diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/.project b/docs/org.eclipse.jst.ws.axis.ui.doc.user/.project
new file mode 100644
index 0000000..e75aa99
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/.project
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.jst.ws.axis.ui.doc.user</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ <buildCommand>
+ <name>org.eclipse.pde.ManifestBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.pde.SchemaBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ </buildSpec>
+ <natures>
+ <nature>org.eclipse.pde.PluginNature</nature>
+ </natures>
+</projectDescription>
diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/DocBuild.xml b/docs/org.eclipse.jst.ws.axis.ui.doc.user/DocBuild.xml
new file mode 100644
index 0000000..2df477f
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/DocBuild.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.2" />
+
+ <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/META-INF/MANIFEST.MF b/docs/org.eclipse.jst.ws.axis.ui.doc.user/META-INF/MANIFEST.MF
new file mode 100644
index 0000000..96dba64
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/META-INF/MANIFEST.MF
@@ -0,0 +1,7 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: %pluginName
+Bundle-SymbolicName: org.eclipse.jst.ws.axis.ui.doc.user; singleton:=true
+Bundle-Version: 1.0.300.qualifier
+Bundle-Vendor: %pluginProvider
+Bundle-Localization: plugin
diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/about.html b/docs/org.eclipse.jst.ws.axis.ui.doc.user/about.html
new file mode 100644
index 0000000..73db36e
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/about.html
@@ -0,0 +1,34 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<HTML>
+
+<head>
+<title>About</title>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+</head>
+
+<BODY lang="EN-US">
+
+<H3>About This Content</H3>
+
+<P>June 06, 2007</P>
+
+<H3>License</H3>
+
+<P>The Eclipse Foundation makes available all content in this plug-in
+("Content"). Unless otherwise indicated below, the Content is provided to you
+under the terms and conditions of the Eclipse Public License Version 1.0
+("EPL"). A copy of the EPL is available at
+<A href="http://www.eclipse.org/org/documents/epl-v10.php">http://www.eclipse.org/org/documents/epl-v10.php</A>.
+For purposes of the EPL, "Program" will mean the Content.</P>
+
+<P>If you did not receive this Content directly from the Eclipse Foundation, the
+Content is being redistributed by another party ("Redistributor") and different
+terms and conditions may apply to your use of any object code in the Content.
+Check the Redistributors license that was provided with the Content. If no such
+license exists, contact the Redistributor. Unless otherwise indicated below, the
+terms and conditions of the EPL still apply to any source code in the Content
+and such source code may be obtained at
+<A href="http://www.eclipse.org/">http://www.eclipse.org/</A>.</P>
+
+</BODY>
+</HTML>
diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/build.properties b/docs/org.eclipse.jst.ws.axis.ui.doc.user/build.properties
new file mode 100644
index 0000000..c5992ce
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/build.properties
@@ -0,0 +1,17 @@
+bin.includes = plugin.properties,\
+ plugin.xml,\
+ wsaxisbuild_toc.xml,\
+ org.eclipse.jst.ws.axis.ui.doc.userindex.xml,\
+ about.html,\
+ concepts/*.htm*,\
+ tasks/*.htm*,\
+ index/,\
+ META-INF/
+src.includes = build.properties,\
+ *.maplist,\
+ *.ditamap,\
+ concepts/*.dita,\
+ tasks/*.dita
+bin.excludes = DocBuild.xml,\
+ myPlugin*.xml
+
\ No newline at end of file
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 0000000..e33b8f6
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/concepts/caxistover.dita
@@ -0,0 +1,48 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>Axis runtime environment<indexterm>Web services<indexterm>overview</indexterm></indexterm></indexterm>
+<indexterm>Web services<indexterm>Axis runtime environment</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<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
new file mode 100644
index 0000000..1527b60
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/concepts/caxistover.html
@@ -0,0 +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 lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="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 content="Axis runtime environment, Web services, overview" name="DC.subject" />
+<meta content="Axis runtime environment, Web services, overview" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../tasks/twsbeana.html" />
+<meta scheme="URI" name="DC.Relation" content="../tasks/tsklwsdla.html" />
+<meta scheme="URI" name="DC.Relation" content="../tasks/tsampappa.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/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/common.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 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
+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 class="linklist"><strong>Related Concepts</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services</a></div>
+<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/cjaxrpc.html">JAX-RPC</a></div></div>
+
+<div class="linklist"><strong>Related Tasks</strong><br />
+
+<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/index/_2.cfs b/docs/org.eclipse.jst.ws.axis.ui.doc.user/index/_2.cfs
new file mode 100644
index 0000000..40e8403
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/index/_2.cfs
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/index/deletable b/docs/org.eclipse.jst.ws.axis.ui.doc.user/index/deletable
new file mode 100644
index 0000000..e423242
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/index/deletable
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/index/indexed_contributions b/docs/org.eclipse.jst.ws.axis.ui.doc.user/index/indexed_contributions
new file mode 100644
index 0000000..a60e31f
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/index/indexed_contributions
@@ -0,0 +1,3 @@
+#This is a generated file; do not edit.
+#Wed May 09 14:12:49 EDT 2007
+org.eclipse.jst.ws.axis.ui.doc.user=org.eclipse.jst.ws.axis.ui.doc.user\n1.0.300.qualifier
diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/index/indexed_dependencies b/docs/org.eclipse.jst.ws.axis.ui.doc.user/index/indexed_dependencies
new file mode 100644
index 0000000..1787e64
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/index/indexed_dependencies
@@ -0,0 +1,4 @@
+#This is a generated file; do not edit.
+#Wed May 09 14:12:49 EDT 2007
+lucene=1.4.103.v20060601
+analyzer=org.eclipse.help.base\#3.2.0.v20060601?locale\=en
diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/index/indexed_docs b/docs/org.eclipse.jst.ws.axis.ui.doc.user/index/indexed_docs
new file mode 100644
index 0000000..07b9884
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/index/indexed_docs
@@ -0,0 +1,4 @@
+#This is a generated file; do not edit.
+#Wed May 09 14:12:49 EDT 2007
+/org.eclipse.jst.ws.axis.ui.doc.user/concepts/caxistover.html=0
+/org.eclipse.jst.ws.axis.ui.doc.user/tasks/ttomcatserv.html=0
diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/index/segments b/docs/org.eclipse.jst.ws.axis.ui.doc.user/index/segments
new file mode 100644
index 0000000..19b5d0c
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/index/segments
Binary files differ
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 0000000..0e5140b
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/myplugin.xml
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?NLS TYPE="org.eclipse.help.toc"?>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2007 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * IBM Corporation - initial API and implementation
+ *******************************************************************************/ -->
+<plugin>
+
+ <extension point="org.eclipse.help.toc">
+ <toc file="wsaxisbuild_toc.xml" />
+ <index path="index/"/>
+ </extension>
+
+ <extension point="org.eclipse.help.index">
+ <index file="org.eclipse.jst.ws.axis.ui.doc.userindex.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 0000000..4a43822
--- /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/org.eclipse.jst.ws.axis.ui.doc.userindex.html b/docs/org.eclipse.jst.ws.axis.ui.doc.user/org.eclipse.jst.ws.axis.ui.doc.userindex.html
new file mode 100644
index 0000000..9f88c20
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/org.eclipse.jst.ws.axis.ui.doc.userindex.html
@@ -0,0 +1,70 @@
+<?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" />
+<meta name="copyright" content="(C) Copyright IBM Corporation 2007" />
+<meta name="security" content="public" />
+<meta name="Robots" content="index,follow" />
+<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 name="DC.Format" content="XHTML" />
+<!-- All rights reserved. Licensed Materials Property of IBM -->
+<!-- US Government Users Restricted Rights -->
+<!-- Use, duplication or disclosure restricted by -->
+<!-- GSA ADP Schedule Contract with IBM Corp. -->
+<link rel="stylesheet" type="text/css" href="ibmdita.css" />
+<title>Index</title>
+</head>
+<body>
+<h1>Index</h1>
+<strong>A</strong>
+<ul class="indexlist">
+<li>Axis runtime environment
+<ul class="indexlist">
+<li><a href="tasks/ttomcatserv.html#creatinganapachetomcatserver">creating an Apache Tomcat server</a>
+</li>
+<li><a href="tasks/tsklwsdla.html#tsklwsdla">skeleton Web services</a>
+</li>
+<li><a href="tasks/tsampappa.html#tsampappa">Web service clients</a>
+</li>
+<li>Web services
+<ul class="indexlist">
+<li><a href="tasks/twsbeana.html#twsbeana">Java beans</a>
+</li>
+<li><a href="concepts/caxistover.html#axisoverview">overview</a>
+</li>
+</ul>
+</li>
+</ul>
+</li>
+</ul>
+<strong>T</strong>
+<ul class="indexlist">
+<li>Tomcat server
+<ul class="indexlist">
+<li><a href="tasks/ttomcatserv.html#creatinganapachetomcatserver">creating servers for Web services</a>
+</li>
+</ul>
+</li>
+</ul>
+<strong>W</strong>
+<ul class="indexlist">
+<li>Web services
+<ul class="indexlist">
+<li><a href="concepts/caxistover.html#axisoverview">Axis runtime environment</a>
+<ul class="indexlist">
+<li><a href="tasks/twsbeana.html#twsbeana">creating a Web service</a>
+</li>
+<li><a href="tasks/tsklwsdla.html#tsklwsdla">skeleton Web services</a>
+</li>
+<li><a href="tasks/tsampappa.html#tsampappa">Web service clients</a>
+</li>
+</ul>
+</li>
+<li><a href="tasks/ttomcatserv.html#creatinganapachetomcatserver">creating an Apache Tomcat server</a>
+</li>
+</ul>
+</li>
+</ul>
+</body></html>
diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/org.eclipse.jst.ws.axis.ui.doc.userindex.xml b/docs/org.eclipse.jst.ws.axis.ui.doc.user/org.eclipse.jst.ws.axis.ui.doc.userindex.xml
new file mode 100644
index 0000000..f456e14
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/org.eclipse.jst.ws.axis.ui.doc.userindex.xml
@@ -0,0 +1,44 @@
+<?xml version="1.0" encoding="utf-8"?>
+<index>
+ <entry keyword="Axis runtime environment">
+ <entry keyword="Web services">
+ <entry keyword="overview">
+ <topic href="concepts/caxistover.html#axisoverview" title="Creating Web services with the Apache Axis run-time environment"/>
+ </entry>
+ <entry keyword="Java beans">
+ <topic href="tasks/twsbeana.html#twsbeana" title="Creating a Web service from a Java bean using the Apache Axis run-time environment"/>
+ </entry>
+ </entry>
+ <entry keyword="skeleton Web services">
+ <topic href="tasks/tsklwsdla.html#tsklwsdla" title="Creating a Java bean skeleton from a WSDL document using the Apache Axis run-time environment"/>
+ </entry>
+ <entry keyword="Web service clients">
+ <topic href="tasks/tsampappa.html#tsampappa" title="Generating a Java client proxy and a sample application from a WSDL document using the Axis run-time environment"/>
+ </entry>
+ <entry keyword="creating an Apache Tomcat server">
+ <topic href="tasks/ttomcatserv.html#creatinganapachetomcatserver" title="Creating an Apache Tomcat server and Web project"/>
+ </entry>
+ </entry>
+ <entry keyword="Web services">
+ <entry keyword="Axis runtime environment">
+ <topic href="concepts/caxistover.html#axisoverview" title="Creating Web services with the Apache Axis run-time environment"/>
+ <entry keyword="creating a Web service">
+ <topic href="tasks/twsbeana.html#twsbeana" title="Creating a Web service from a Java bean using the Apache Axis run-time environment"/>
+ </entry>
+ <entry keyword="skeleton Web services">
+ <topic href="tasks/tsklwsdla.html#tsklwsdla" title="Creating a Java bean skeleton from a WSDL document using the Apache Axis run-time environment"/>
+ </entry>
+ <entry keyword="Web service clients">
+ <topic href="tasks/tsampappa.html#tsampappa" title="Generating a Java client proxy and a sample application from a WSDL document using the Axis run-time environment"/>
+ </entry>
+ </entry>
+ <entry keyword="creating an Apache Tomcat server">
+ <topic href="tasks/ttomcatserv.html#creatinganapachetomcatserver" title="Creating an Apache Tomcat server and Web project"/>
+ </entry>
+ </entry>
+ <entry keyword="Tomcat server">
+ <entry keyword="creating servers for Web services">
+ <topic href="tasks/ttomcatserv.html#creatinganapachetomcatserver" title="Creating an Apache Tomcat server and Web project"/>
+ </entry>
+ </entry>
+</index>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/plugin.properties b/docs/org.eclipse.jst.ws.axis.ui.doc.user/plugin.properties
new file mode 100644
index 0000000..786fb87
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/plugin.properties
@@ -0,0 +1,15 @@
+###############################################################################
+# Copyright (c) 2001, 2005 IBM Corporation and others.
+# All rights reserved. This program and the accompanying materials
+# are made available under the terms of the Eclipse Public License v1.0
+# which accompanies this distribution, and is available at
+# http://www.eclipse.org/legal/epl-v10.html
+#
+# Contributors:
+# IBM Corporation - initial API and implementation
+###############################################################################
+# NLS_MESSAGEFORMAT_VAR
+# NLS_ENCODING=UTF-8
+
+pluginName = Axis Web services documentation
+pluginProvider = Eclipse.org
diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/plugin.xml b/docs/org.eclipse.jst.ws.axis.ui.doc.user/plugin.xml
new file mode 100644
index 0000000..0e5140b
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/plugin.xml
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?NLS TYPE="org.eclipse.help.toc"?>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2007 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * IBM Corporation - initial API and implementation
+ *******************************************************************************/ -->
+<plugin>
+
+ <extension point="org.eclipse.help.toc">
+ <toc file="wsaxisbuild_toc.xml" />
+ <index path="index/"/>
+ </extension>
+
+ <extension point="org.eclipse.help.index">
+ <index file="org.eclipse.jst.ws.axis.ui.doc.userindex.xml"/>
+</extension>
+</plugin>
\ No newline at end of file
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 0000000..f218477
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsampappa.dita
@@ -0,0 +1,132 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>Axis runtime environment<indexterm>Web service clients</indexterm></indexterm>
+<indexterm>Web services<indexterm>Axis runtime environment<indexterm>Web service clients</indexterm></indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<taskbody>
+<prereq><p>Prerequisites:</p><ol>
+<li conref="twsbeana.dita#twsbeana/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: </cmd>
+<substeps>
+<substep><cmd>Enter the URI to the WSDL, WSIL, or HTML file that will be used
+to generate the client.</cmd></substep>
+<substep><cmd>Select the type of proxy to be generated</cmd></substep>
+<substep><cmd>Select the stages of Web services development that you want
+to complete using the slider:</cmd><info><ul>
+<li>Develop: this will develop the WSDL definition and implementation of the
+Web service. This includes such tasks as creating the modules which will contain
+the generated code and Java files, as well as copying the Axis JARs..</li>
+<li>Assemble: this ensures the project that will host the Web service or client
+gets associated to an EAR when required by the target application server.</li>
+<li>Deploy: this will create the deployment code for the service.</li>
+<li>Install: this will install and configure the Web module and EARs on the
+target server.</li>
+<li>Start: this will start the server once the service has been installed
+on it. The server-config.wsdd file will be generated.</li>
+<li>Test: this will provide various options for testing the service, such
+as using the Web Service Explorer or sample JSPs.</li>
+</ul></info></substep>
+<substep><cmd>Select your server: the default server is displayed. If you
+want to deploy your client to a different server click the link to specify
+a different server.</cmd></substep>
+<substep><cmd>Select your runtime: the default runtime is displayed. If you
+want to deploy your client to a different runtime click the link to specify
+a different runtime.</cmd></substep>
+<substep><cmd>Select the client project: the project containing the project
+selected in your workspace is displayed. To select a different project and
+EAR click on the project link.</cmd><info>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.</info></substep>
+<substep><cmd>Monitor the Web service: this will 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. Alternately
+you can 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></cmd></substep>
+</substeps>
+</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>. Alternately, you can click <b>Import</b> to
+import custom mapping pairs from a <systemoutput>.properties</systemoutput> file.
+The content of the properties file must be of the format <codeph><varname>namespace=package</varname></codeph>.</cmd>
+</step>
+<step><cmd>Web Service Client Test page: This page displays if you selected
+to test your client. 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 outputclass="wsclienttestoptions">
+<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 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
new file mode 100644
index 0000000..e2a0edb
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsampappa.html
@@ -0,0 +1,189 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="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 content="Axis runtime environment, Web service clients, Web services" name="DC.subject" />
+<meta content="Axis runtime environment, Web service clients, Web services" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../concepts/caxistover.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/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/common.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
+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
+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
+> 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>
+
+<li><span>Web Services page: </span>
+<ol type="a">
+<li class="substepexpand"><span>Enter the URI to the WSDL, WSIL, or HTML file that will be used
+to generate the client.</span></li>
+
+<li class="substepexpand"><span>Select the type of proxy to be generated</span></li>
+
+<li class="substepexpand"><span>Select the stages of Web services development that you want
+to complete using the slider:</span> <ul>
+<li>Develop: this will develop the WSDL definition and implementation of the
+Web service. This includes such tasks as creating the modules which will contain
+the generated code and Java files, as well as copying the Axis JARs..</li>
+
+<li>Assemble: this ensures the project that will host the Web service or client
+gets associated to an EAR when required by the target application server.</li>
+
+<li>Deploy: this will create the deployment code for the service.</li>
+
+<li>Install: this will install and configure the Web module and EARs on the
+target server.</li>
+
+<li>Start: this will start the server once the service has been installed
+on it. The server-config.wsdd file will be generated.</li>
+
+<li>Test: this will provide various options for testing the service, such
+as using the Web Service Explorer or sample JSPs.</li>
+
+</ul>
+</li>
+
+<li class="substepexpand"><span>Select your server: the default server is displayed. If you
+want to deploy your client to a different server click the link to specify
+a different server.</span></li>
+
+<li class="substepexpand"><span>Select your runtime: the default runtime is displayed. If you
+want to deploy your client to a different runtime click the link to specify
+a different runtime.</span></li>
+
+<li class="substepexpand"><span>Select the client project: the project containing the project
+selected in your workspace is displayed. To select a different project and
+EAR click on the project link.</span> 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 class="substepexpand"><span>Monitor the Web service: this will 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. Alternately
+you can 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></span></li>
+
+</ol>
+
+</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>. Alternately, you can click <strong>Import</strong> to
+import custom mapping pairs from a <tt class="sysout">.properties</tt> file.
+The content of the properties file must be of the format <samp class="codeph"><var class="varname">namespace=package</var></samp>.</span>
+</li>
+
+<li><span>Web Service Client Test page: This page displays if you selected
+to test your client. Select the test facility that you will use to test the
+proxy, and the methods that you want included in the proxy. Note that the
+Universal Test Client (UTC) is only compatible with Web service clients deployed
+on WebSphere<sup>®</sup> 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 class="wsclienttestoptions">
+<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 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>
+
+</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 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 class="linklist"><strong>Related Concepts</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div>
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div></div>
+
+<div class="linklist"><strong>Related Tasks</strong><br />
+
+<div><a href="../../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="../../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/tasks/tsklwsdla.dita b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsklwsdla.dita
new file mode 100644
index 0000000..1eec941
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsklwsdla.dita
@@ -0,0 +1,124 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>Axis runtime environment<indexterm>skeleton Web services</indexterm></indexterm>
+<indexterm>Web services<indexterm>Axis runtime environment<indexterm>skeleton Web services</indexterm></indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<taskbody>
+<prereq><p>Prerequisites:</p><ol>
+<li conref="twsbeana.dita#twsbeana/createtomcatlink"></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 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, and select the artifact from which the service will
+be created.</cmd>
+<substeps conref="twsbeana.dita#twsbeana/createstep4ul">
+<substep><cmd></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>. Alternately, you can click <b>Import</b> to
+import custom mapping pairs from a <systemoutput>.properties</systemoutput> file.
+The content of the properties file must be of the format <codeph><varname>namespace=package</varname></codeph>.
+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 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 conref="twsbeana.dita#twsbeana/axiswscreateresult">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 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
new file mode 100644
index 0000000..43a973e
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsklwsdla.html
@@ -0,0 +1,223 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="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 content="Axis runtime environment, skeleton Web services, Web services" name="DC.subject" />
+<meta content="Axis runtime environment, skeleton Web services, Web services" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../concepts/caxistover.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/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/common.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>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 run-time
+environment:</div>
+
+<ol>
+<li><span>Switch to the J2EE perspective (<span class="uicontrol">Window > Open Perspective
+> J2EE</span>).</span></li>
+
+<li><span>In the Project Explorer view, select the WSDL file that you created
+or imported into the Web Content folder of your Web project.</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</span> wizard. Click <span class="uicontrol">Next</span>.</span>
+</li>
+
+<li><span>Web Services page: select <span class="uicontrol">Top down Java bean Web service</span> as
+your Web service type, and select the artifact from which the service will
+be created.</span>
+<ol type="a">
+<li class="substepexpand"><span>Select the stages of Web services development that you want
+to complete using the slider:</span> <ul>
+<li>Develop: this will develop the WSDL definition and implementation of the
+Web service. This includes such tasks as creating the modules which will contain
+the generated code, WSDL files, deployment descriptors, and Java files when
+appropriate.</li>
+
+<li>Assemble: this ensures the project that will host the Web service or client
+gets associated to an EAR when required by the target application server.</li>
+
+<li>Deploy: this will create the deployment code for the service.</li>
+
+<li>Install: this will install and configure the Web module and EARs on the
+target server.</li>
+
+<li>Start: this will start the server once the service has been installed
+on it. The server-config.wsdd file will be generated.</li>
+
+<li>Test: this will provide various options for testing the service, such
+as using the Web Service Explorer or sample JSPs.</li>
+
+</ul>
+</li>
+
+<li class="substepexpand"><span>Select your server: the default server is displayed. If you
+want to deploy your service to a different server click the link to specify
+a different server.</span></li>
+
+<li class="substepexpand"><span>Select your runtime: the default runtime is displayed. If you
+want to deploy your service to a different runtime click the link to specify
+a different runtime.</span></li>
+
+<li class="substepexpand"><span>Select the service project: the project containing the project
+selected in your workspace is displayed. To select a different project and
+EAR click on the project link.</span> 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 class="substepexpand"><span>If you want to create a client, select the type of proxy to
+be generated and repeat the above steps for the client.</span></li>
+
+<li class="substepexpand"><span>Publish the Web service: this will launch the Web Services Explorer
+to publish your Web service to a UDDI registry.</span></li>
+
+<li class="substepexpand"><span>Monitor the Web service: this will 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. Alternately
+you can 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></span></li>
+
+</ol>
+
+</li>
+
+<li><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>
+
+<li><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>. Alternately, you can click <strong>Import</strong> to
+import custom mapping pairs from a <tt class="sysout">.properties</tt> file.
+The content of the properties file must be of the format <samp class="codeph"><var class="varname">namespace=package</var></samp>.
+Click <span class="uicontrol">Next</span>.</span></li>
+
+<li><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>
+
+<li><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><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
+in 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><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"><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,
+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 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. Follow
+the instructions in <var class="varname">Publishing the Web service</var> to complete
+this task.</li>
+
+</ul>
+</div>
+</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 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 class="linklist"><strong>Related Concepts</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div>
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div></div>
+
+<div class="linklist"><strong>Related Tasks</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/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="../../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/tasks/ttomcatserv.dita b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/ttomcatserv.dita
new file mode 100644
index 0000000..e168755
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/ttomcatserv.dita
@@ -0,0 +1,62 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>Axis runtime environment<indexterm>creating an Apache Tomcat server</indexterm></indexterm>
+<indexterm>Tomcat server<indexterm>creating servers for Web services</indexterm></indexterm>
+<indexterm>Web services<indexterm>creating an Apache Tomcat server</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<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 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>Project Name: enter a project name</li>
+<li>Target runtime: Tomcat server v3.x, 4.x or 5.x depending on the version
+you installed. If it is not listed, click New and browse to the location where
+it is installed.</li>
+<li>Ensure that <uicontrol>Add project to an EAR</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>
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
new file mode 100644
index 0000000..7c1f23b
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/ttomcatserv.html
@@ -0,0 +1,101 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="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="Axis runtime environment, creating an Apache Tomcat server, Tomcat server, creating servers for Web services, Web services" name="DC.subject" />
+<meta content="Axis runtime environment, creating an Apache Tomcat server, Tomcat server, creating servers for Web services, Web services" name="keywords" />
+<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/common.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
+> Next</span>.</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
+would be the home directory for JDK 1.4.1. Click <span class="uicontrol">OK</span> 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.</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>Project Name: enter a project name</li>
+
+<li>Target runtime: Tomcat server v3.x, 4.x or 5.x depending on the version
+you installed. If it is not listed, click New and browse to the location where
+it is installed.</li>
+
+<li>Ensure that <span class="uicontrol">Add project to an EAR</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>
+
+
+</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 0000000..df8969c
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/twsbeana.dita
@@ -0,0 +1,171 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>Axis runtime environment<indexterm>Web services<indexterm>Java beans</indexterm></indexterm></indexterm>
+<indexterm>Web services<indexterm>Axis runtime environment<indexterm>creating a Web service</indexterm></indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<taskbody>
+<prereq><p>Prerequisites:<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 bean into the <tm tmclass="special" tmowner="Sun Microsystems, Inc."
+tmtype="tm" trademark="Java">Java</tm> source folder of the Web project. To
+import, select the <b>Java Resources: src</b> folder, and from the file menu
+select <menucascade><uicontrol>Import</uicontrol><uicontrol>General</uicontrol>
+<uicontrol>File System</uicontrol></menucascade> and browse to where your
+package is.</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, and enter the URI to the WSDL, WSIL, or HTML file that
+will be used to generate the service.</cmd>
+<substeps id="createstep4ul">
+<substep><cmd>Select the stages of Web services development that you want
+to complete using the slider:</cmd><info><ul>
+<li>Develop: this will develop the WSDL definition and implementation of the
+Web service. This includes such tasks as creating the modules which will contain
+the generated code, WSDL files, deployment descriptors, and Java files when
+appropriate.</li>
+<li>Assemble: this ensures the project that will host the Web service or client
+gets associated to an EAR when required by the target application server.</li>
+<li>Deploy: this will create the deployment code for the service.</li>
+<li>Install: this will install and configure the Web module and EARs on the
+target server.</li>
+<li>Start: this will start the server once the service has been installed
+on it. The server-config.wsdd file will be generated.</li>
+<li>Test: this will provide various options for testing the service, such
+as using the Web Service Explorer or sample JSPs.</li>
+</ul></info></substep>
+<substep><cmd>Select your server: the default server is displayed. If you
+want to deploy your service to a different server click the link to specify
+a different server.</cmd></substep>
+<substep><cmd>Select your runtime: the default runtime is displayed. If you
+want to deploy your service to a different runtime click the link to specify
+a different runtime.</cmd></substep>
+<substep><cmd>Select the service project: the project containing the project
+selected in your workspace is displayed. To select a different project and
+EAR click on the project link.</cmd><info>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.</info></substep>
+<substep><cmd>If you want to create a client, select the type of proxy to
+be generated and repeat the above steps for the client.</cmd></substep>
+<substep><cmd>Publish the Web service: this will launch the Web Services Explorer
+to publish your Web service to a UDDI registry.</cmd></substep>
+<substep><cmd>Monitor the Web service: this will 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. Alternately
+you can 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></cmd></substep>
+</substeps>
+</step>
+<step><cmd>Web Service <tm tmclass="special" tmowner="Sun Microsystems, Inc."
+tmtype="tm" trademark="Java">Java</tm> Bean Identity page: the Web service
+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>. Alternately, you can click <b>Import</b> to
+import custom mapping pairs from a <systemoutput>.properties</systemoutput> file.
+The content of the properties file must be of the format <codeph><varname>package=namespace</varname></codeph>.</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 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 id="axiswscreateresult"><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 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></result>
+<postreq><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></postreq>
+</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
new file mode 100644
index 0000000..6991480
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/twsbeana.html
@@ -0,0 +1,238 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="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 content="Axis runtime environment, Web services, Java beans, creating a Web service" name="DC.subject" />
+<meta content="Axis runtime environment, Web services, Java beans, creating a Web service" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../concepts/caxistover.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/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/common.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 id="twsbeana__createtomcatlink"><a name="twsbeana__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 bean into the Java™ source folder of the Web project. To
+import, select the <strong>Java Resources: src</strong> folder, and from the file menu
+select <span class="menucascade"><span class="uicontrol">Import</span> > <span class="uicontrol">General</span>
+ > <span class="uicontrol">File System</span></span> and browse to where your
+package is.</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
+> 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>
+
+<li class="stepexpand"><span>Web Services page: select <span class="uicontrol">Bottom up Java bean Web service</span> as
+your Web service type, and enter the URI to the WSDL, WSIL, or HTML file that
+will be used to generate the service.</span>
+<a name="twsbeana__createstep4ul"><!-- --></a><ol type="a" id="twsbeana__createstep4ul">
+<li class="substepexpand"><span>Select the stages of Web services development that you want
+to complete using the slider:</span> <ul>
+<li>Develop: this will develop the WSDL definition and implementation of the
+Web service. This includes such tasks as creating the modules which will contain
+the generated code, WSDL files, deployment descriptors, and Java files when
+appropriate.</li>
+
+<li>Assemble: this ensures the project that will host the Web service or client
+gets associated to an EAR when required by the target application server.</li>
+
+<li>Deploy: this will create the deployment code for the service.</li>
+
+<li>Install: this will install and configure the Web module and EARs on the
+target server.</li>
+
+<li>Start: this will start the server once the service has been installed
+on it. The server-config.wsdd file will be generated.</li>
+
+<li>Test: this will provide various options for testing the service, such
+as using the Web Service Explorer or sample JSPs.</li>
+
+</ul>
+</li>
+
+<li class="substepexpand"><span>Select your server: the default server is displayed. If you
+want to deploy your service to a different server click the link to specify
+a different server.</span></li>
+
+<li class="substepexpand"><span>Select your runtime: the default runtime is displayed. If you
+want to deploy your service to a different runtime click the link to specify
+a different runtime.</span></li>
+
+<li class="substepexpand"><span>Select the service project: the project containing the project
+selected in your workspace is displayed. To select a different project and
+EAR click on the project link.</span> 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 class="substepexpand"><span>If you want to create a client, select the type of proxy to
+be generated and repeat the above steps for the client.</span></li>
+
+<li class="substepexpand"><span>Publish the Web service: this will launch the Web Services Explorer
+to publish your Web service to a UDDI registry.</span></li>
+
+<li class="substepexpand"><span>Monitor the Web service: this will 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. Alternately
+you can 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></span></li>
+
+</ol>
+
+</li>
+
+<li class="stepexpand"><span>Web Service Java Bean Identity page: the Web service
+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>. Alternately, you can click <strong>Import</strong> to
+import custom mapping pairs from a <tt class="sysout">.properties</tt> file.
+The content of the properties file must be of the format <samp class="codeph"><var class="varname">package=namespace</var></samp>.</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>
+
+<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
+in 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
+from Java. ClassNotFound: <bean name></samp>. This error can be safely
+ignored.</li>
+
+</ol>
+
+<div class="section" id="twsbeana__axiswscreateresult"><a name="twsbeana__axiswscreateresult"><!-- --></a><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,
+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 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. Follow
+the instructions in <var class="varname">Publishing the Web service</var> to complete
+this task.</li>
+
+</ul>
+</div>
+</div>
+
+<div class="section"><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.</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 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 class="linklist"><strong>Related Concepts</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div>
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div></div>
+
+<div class="linklist"><strong>Related Tasks</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/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="../../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 0000000..26af6b5
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/wsaxisbuild_toc.ditamap
@@ -0,0 +1,28 @@
+<?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">
+<topicmeta>
+<copyright>
+<copyryear year="2000"/>
+<copyryear year="2006"/>
+<copyrholder> 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</copyrholder>
+</copyright>
+</topicmeta>
+<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
new file mode 100644
index 0000000..13dfd78
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/wsaxisbuild_toc.xml
@@ -0,0 +1,7 @@
+<?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.infopop/.cvsignore b/docs/org.eclipse.jst.ws.consumption.infopop/.cvsignore
new file mode 100644
index 0000000..c14487c
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.infopop/.cvsignore
@@ -0,0 +1 @@
+build.xml
diff --git a/docs/org.eclipse.jst.ws.consumption.infopop/.project b/docs/org.eclipse.jst.ws.consumption.infopop/.project
new file mode 100644
index 0000000..440bda3
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.infopop/.project
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.jst.ws.consumption.infopop</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ <buildCommand>
+ <name>org.eclipse.pde.ManifestBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.pde.SchemaBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ </buildSpec>
+ <natures>
+ <nature>org.eclipse.pde.PluginNature</nature>
+ </natures>
+</projectDescription>
diff --git a/docs/org.eclipse.jst.ws.consumption.infopop/META-INF/MANIFEST.MF b/docs/org.eclipse.jst.ws.consumption.infopop/META-INF/MANIFEST.MF
new file mode 100644
index 0000000..d2cb3d0
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.infopop/META-INF/MANIFEST.MF
@@ -0,0 +1,7 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: %pluginName
+Bundle-SymbolicName: org.eclipse.jst.ws.consumption.infopop; singleton:=true
+Bundle-Version: 1.0.203.qualifier
+Bundle-Vendor: %pluginProvider
+Bundle-Localization: plugin
diff --git a/docs/org.eclipse.jst.ws.consumption.infopop/about.html b/docs/org.eclipse.jst.ws.consumption.infopop/about.html
new file mode 100644
index 0000000..73db36e
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.infopop/about.html
@@ -0,0 +1,34 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<HTML>
+
+<head>
+<title>About</title>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+</head>
+
+<BODY lang="EN-US">
+
+<H3>About This Content</H3>
+
+<P>June 06, 2007</P>
+
+<H3>License</H3>
+
+<P>The Eclipse Foundation makes available all content in this plug-in
+("Content"). Unless otherwise indicated below, the Content is provided to you
+under the terms and conditions of the Eclipse Public License Version 1.0
+("EPL"). A copy of the EPL is available at
+<A href="http://www.eclipse.org/org/documents/epl-v10.php">http://www.eclipse.org/org/documents/epl-v10.php</A>.
+For purposes of the EPL, "Program" will mean the Content.</P>
+
+<P>If you did not receive this Content directly from the Eclipse Foundation, the
+Content is being redistributed by another party ("Redistributor") and different
+terms and conditions may apply to your use of any object code in the Content.
+Check the Redistributors license that was provided with the Content. If no such
+license exists, contact the Redistributor. Unless otherwise indicated below, the
+terms and conditions of the EPL still apply to any source code in the Content
+and such source code may be obtained at
+<A href="http://www.eclipse.org/">http://www.eclipse.org/</A>.</P>
+
+</BODY>
+</HTML>
diff --git a/docs/org.eclipse.jst.ws.consumption.infopop/build.properties b/docs/org.eclipse.jst.ws.consumption.infopop/build.properties
new file mode 100644
index 0000000..e19612f
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.infopop/build.properties
@@ -0,0 +1,7 @@
+bin.includes = plugin.xml,\
+ wsconsumptionui-f1Contexts.xml,\
+ wscreationui-f1Contexts.xml,\
+ about.html,\
+ META-INF/,\
+ plugin.properties
+src.includes = build.properties
diff --git a/docs/org.eclipse.jst.ws.consumption.infopop/plugin.properties b/docs/org.eclipse.jst.ws.consumption.infopop/plugin.properties
new file mode 100644
index 0000000..07977b2
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.infopop/plugin.properties
@@ -0,0 +1,3 @@
+! Plug-in properties
+pluginName = Web services UI
+pluginProvider = Eclipse.org
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.ws.consumption.infopop/plugin.xml b/docs/org.eclipse.jst.ws.consumption.infopop/plugin.xml
new file mode 100644
index 0000000..cc9d1f8
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.infopop/plugin.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, 2007 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * IBM Corporation - initial API and implementation
+ *******************************************************************************/ -->
+<plugin>
+
+ <extension point="org.eclipse.help.contexts">
+ <contexts file="wsconsumptionui-f1Contexts.xml" plugin="org.eclipse.jst.ws.consumption.ui"/>
+ <contexts file="wscreationui-f1Contexts.xml" plugin="org.eclipse.jst.ws.creation.ui"/>
+ </extension>
+</plugin>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.ws.consumption.infopop/wsconsumptionui-f1Contexts.xml b/docs/org.eclipse.jst.ws.consumption.infopop/wsconsumptionui-f1Contexts.xml
new file mode 100644
index 0000000..7ccce3f
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.infopop/wsconsumptionui-f1Contexts.xml
@@ -0,0 +1,460 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?NLS TYPE="org.eclipse.help.contexts"?>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2007 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * IBM Corporation - initial API and implementation
+ *******************************************************************************/ -->
+<contexts>
+<!-- new v6 preference page-->
+<context id="SRPF0001">
+<description>Select the default Web server to be used for Web service creation.</description>
+</context>
+<context id="SRPF0002">
+<!--runtime preference on the server runtime preference page-->
+<description>Select the default server run-time environment to be used for Web service creation.</description>
+</context>
+<context id="SRPF0003">
+<!--J2EE version preference on the server runtime preference page-->
+<description>Select the default J2EE version to be used for Web service creation.</description>
+</context>
+
+<!-- new v6 handler wizard-->
+<context id="AHDL0001">
+<!--Handler config page-->
+<description>Use this wizard to add and remove handlers for a Web service. The order in which they are listed represents the order in which the handlers will be acted upon.</description>
+</context>
+
+<!--WebServiceWizNewFirstPage-->
+<context id="WSWSCEN0001">
+<!-- First Page-->
+<description>On this page select the artifact from which your Web client will be created, and the stages of Web services development that you want
+to complete:
+- Develop: this will create the client code
+- Assemble: this ensures that the project that will host the client gets associated to an EAR when required by the target application server
+- Deploy: this will create the deployment code for the client
+- Install: this will install the client on the chosen server
+- Start: this will start the server once the client has been installed on it
+- Test: this will provide various options for testing the client
+Select the server and runtime for your Web client, and whether or not you want to publish or monitor the service.
+</description>
+</context>
+
+<context id="WSWSCEN0014">
+<!--Monitor checkbox of the First Page-->
+<description>Monitor the Web service: this will 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.</description>
+</context>
+
+<context id="WSWSCEN0020">
+<!--Service implementation field of the First Page-->
+<description>Enter the URI to the WSDL, WSIL, or HTML file that
+will be used to generate the service</description>
+</context>
+
+<context id="WSWSCEN0022">
+<!--Server link of the First Page-->
+<description>Select your server: the default server is displayed. If you
+want to deploy your service to a different server click the link to specify
+a different server.</description>
+</context>
+
+<context id="WSWSCEN0023">
+<!--runtime link of the First Page-->
+<description>Select your runtime: the default runtime is displayed. If you
+want to deploy your service to a different runtime click the link to specify
+a different runtime.</description>
+</context>
+
+<context id="WSWSCEN0024">
+<!--projects link of the First Page-->
+<description>Select the service project: the project containing the project
+selected in your workspace is displayed. To select a different project and
+EAR click on the project link. 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.</description>
+</context>
+
+<context id="WSWSCEN0025">
+<!--client type combo of the First Page-->
+<description>The Java bean client proxy that is generated provides a remote procedure call interface to the Web service.</description>
+</context>
+
+<context id="WSWSCEN0026">
+<!--Client slider of the First Page-->
+<description>Select the stages of Web services client development that you want
+to complete using the slider:
+- Develop: this will create the client code
+- Assemble: this ensures that the project that will host the client gets associated to an EAR when required by the target application server
+- Deploy: this will create the deployment code for the client
+- Install: this will install the client on the chosen server
+- Start: this will start the server once the client has been installed on it
+- Test: this will provide various options for testing the client
+</description>
+</context>
+
+<context id="WSWSCEN0030">
+<!--file overwrite checkbox of the First Page-->
+<description>This allows you to overwrite files without receiving a warning message asking for confirmation when overwriting files.</description>
+</context>
+
+
+
+<context id="WSIL0001">
+<!-- WSIL Import Page-->
+<description>Enter the required information to generate a standardized WSDL reference (WSIL) document in your project.</description>
+</context>
+
+<context id="WSIL0002">
+<!-- WSIL Text field-->
+<description>Enter the name of the WSIL document being generated, or accept the default.</description>
+</context>
+
+<context id="WSIL0003">
+<!-- WSIL browse button-->
+<description>Browse to the location of a WSDL or WSIL file from which the new WSIL document will be generated.</description>
+</context>
+
+<context id="WSIL0004">
+<!-- WSIL table-->
+<description>This lists all the WSDL URIs that will be included in the WSIL document.</description>
+</context>
+
+<context id="PWPR0001">
+<!-- Project Page -->
+<description>Select the type of Web service you want to generate and any file and folder options for your Web service.</description>
+</context>
+
+<context id="PWPR0003">
+<!--Overwrite files without warning (checkbox)-->
+<description>Allows you to overwrite files without receiving a warning message asking for confirmation when overwriting files.</description>
+</context>
+
+<context id="PWPR0004">
+<!--Create folders when necessary (checkbox)-->
+<description>Select to create folders and folder structures without receiving a warning message asking for confirmation.</description>
+</context>
+
+<context id="PWPR0005">
+<!-- Generate Proxy check box of the Project Page -->
+<description>The generated Java bean proxy provides a remote procedure call interface to the Web service.</description>
+</context>
+
+<context id="PWPR0006">
+<!-- Test Proxy check box of the Project Page -->
+<description>Select this check box to test the generated proxy.</description>
+</context>
+
+<context id="PWPR0009">
+<!-- Start Web Project check box check box of the Project Page -->
+<description>Click to start the server. If you leave the box unchecked you will have to manually start the server.</description>
+</context>
+
+<context id="PWPR0010">
+<!-- Web Service Type combo box of the Project Page -->
+<description>Select the type of Web service you want to build. Your selection will affect the files available for selection.</description>
+</context>
+
+<context id="PWPR0011">
+<!-- Wizard Scenario Service group of the Project Page -->
+<description>Select the type of Web service you want to build. Your selection will affect the files available for selection.</description>
+</context>
+
+<context id="PWPR0011">
+<!-- Test service checkbox of the project page -->
+<description>Select this check box to launch the Web service in the Web Services Explorer in order to examine it.</description>
+</context>
+
+<context id="PWPR0012">
+<!-- Launch UDDI check box of the Project Page -->
+<description>Select this checkbox to launch the Web Services Explorer in order to publish the Web service to a UDDI registry.</description>
+</context>
+
+<context id="PWPR0013">
+<!-- Wizard Scenario Client group of the Project Page -->
+<description>The generated Java bean proxy provides a remote procedure call interface to the Web service.</description>
+</context>
+
+<context id="PWPR0014">
+<!-- Web Service Client Type combo box of the Project Page -->
+<description>Select the client proxy type. The generated Java bean proxy provides a remote procedure call interface to the Web service.</description>
+</context>
+
+<context id="PWPR0015">
+<!-- Check Out Files check box of the Project Page -->
+<description>Select to check out files without receiving a warning message asking for confirmation.</description>
+</context>
+
+
+<!--WebServiceTPBeanClassPage.java-->
+<context id="PBCL0001">
+<!--PBCL0001 for the Bean Selection Page-->
+<description>Use this page to select the Java bean or class used to create the Web service.</description>
+</context>
+<context id="PBCL0002">
+<!--PBCL0002 for the Bean Selection field of the Bean Selection Page-->
+<description>Enter the name of the Java bean to be used to create the Web service. Defaults the selected Java bean. Click <b>Browse classes </b>to view the bean class of the selected Java bean. The bean class is a model or template (an abstract data type) that can be instantiated to create objects with a common definition and therefore, common properties, operations, and behavior. Click <b>Browse files </b>to select a Java bean from the project.</description>
+</context>
+<context id="PBCL0003">
+<!--PBCL0003 for the Bean Class Browse button of the Bean Selection Page-->
+<description>Click to view the bean class of the selected Java bean.</description>
+</context>
+<context id="PBCL0004">
+<!--PBCL0004 for the Bean Resource Browse button of the Bean Selection Page-->
+<description>Browse to the correct Java bean to be used to create the Web service.</description>
+</context>
+
+<context id="PWPB0001">
+<!-- UDDI Publish Page -->
+<description>Select to launch the Web Services Explorer to allow you to publish the Web service.</description>
+</context>
+
+<context id="PWPB0002">
+<!-- UDDI Launch check box of the UDDI Publish Page-->
+<description>If selected will launch the Web Services Explorer to allow you to publish the Web service.</description>
+</context>
+
+
+<context id="PEBD0001">
+<!-- EAR Projects drop-down box -->
+<description>Select from the listed EAR projects.</description>
+</context>
+
+<context id="PEBD0002">
+<!-- Table containing all of the bean names -->
+<description>Select from the listed Java beans.</description>
+</context>
+
+<!--WebServiceTPBeanClassPage.java-->
+<context id="PBCL0001">
+<!--PBCL0001 for the Bean Selection Page-->
+<description>Use this page to select the Java bean or class used to create the Web service.</description>
+</context>
+
+<context id="PBCL0002">
+<!--PBCL0002 for the Bean Selection field of the Bean Selection Page-->
+<description>Enter the name of the Java bean to be used to create the Web service. Defaults the selected Java bean. Click <b>Browse classes </b>to view the bean class of the selected Java bean. The bean class is a model or template (an abstract data type) that can be instantiated to create objects with a common definition and therefore, common properties, operations, and behavior. Click <b>Browse files </b>to select a Java bean from the project.</description>
+</context>
+
+<context id="PBCL0003">
+<!--PBCL0003 for the Bean Class Browse button of the Bean Selection Page-->
+<description>Click to view the bean class of the selected Java bean.</description>
+</context>
+
+<context id="PBCL0004">
+<!--PBCL0004 for the Bean Resource Browse button of the Bean Selection Page-->
+<description>Browse to the correct Java bean to be used to create the Web service.</description>
+</context>
+
+
+<context id="PCON0001">
+<!-- WSDL Selection Page-->
+<description>Use this page to select the WSDL, WSIL, or HTML document that will be used to create the Web service.</description>
+</context>
+
+<context id="PCON0002">
+<!-- WSDL Document text field of the WSDL Selection Page-->
+<description>Enter the path to a WSDL, WSIL, or HTML document.</description>
+</context>
+
+<context id="PCON0003">
+<!-- WSDL Resource Browse button of the WSDL Selection Page-->
+<description>Browse to the location of a WSDL, WSIL, or HTML document.</description>
+</context>
+
+<context id="PCON0004">
+<!-- Generate WSIL button of the WSDL Selection Page-->
+<description>Select this check box to generate a standardized WSDL reference (WSIL) document in your project.</description>
+</context>
+
+<context id="PCON0005">
+<!-- WSIL Document text field of the WSDL Selection Page-->
+<description>Enter the path to an existing WSIL document, or select the location where the WSIL document will be created.</description>
+</context>
+
+<context id="PCON0006">
+<!-- WSIL Resource Browse button of the WSDL Selection Page-->
+<description>Browse to the location of an existing WSIL document</description>
+</context>
+
+<context id="PWRS0001">
+<!-- Run-time/servers in the Web Service type-->
+<description>Select the scenario configuration for run-time environments, servers, and projects.</description>
+</context>
+
+<context id="PWRS0002">
+<!-- Run-time/servers in the Web Service type-->
+<description>Select the scenario configuration for run-time environments, servers, and projects.</description>
+</context>
+
+<context id="PWRS0004">
+<!-- service-side run-time environment selection of the run-time environment selection Page-->
+<description>This is the server-side run-time environment which the Web service will use.</description>
+</context>
+
+<context id="PWRS0005">
+<!-- service-side server selection of the run-time environment selection Page-->
+<description>This is the server-side server on which the Web service will run.</description>
+</context>
+
+<context id="PWRS0006">
+<!-- service-side Web project combo box of the run-time environment selection Page-->
+<description>Select the Web project or EJB project in which the Web service will be created. The wizard will create the Web project for you if it does not already exist. If you are using an EJB project, it must already exist.</description>
+</context>
+
+<context id="PWRS0007">
+<!--service-side EJB project combo box of the run-time environment selection Page-->
+<description>Select the EJB project in which the Web service will be created.</description>
+</context>
+
+<context id="PWRS0003">
+<!-- client-side run-time environment selection of the run-time environment selection Page-->
+<description>This is the client-side run-time environment which the Web service will use.</description>
+</context>
+
+<context id="PWRS0009">
+<!-- client-side server selection of the run-time environment selection Page-->
+<description>This is the client-side server on which the Web service will run.</description>
+</context>
+
+<context id="PWRS0010">
+<!-- service-side Web project combo box of the run-time environment selection Page-->
+<description>Select the project in which the Web service client will be created. The wizard will generate this project if it does not already exist.</description>
+</context>
+
+<context id="PWRS0011">
+<!-- client type combo box of the server run-time environment selection Page -->
+<description>Select from the listed project types the type of project that you want created to contain your Web service client.</description>
+</context>
+
+<context id="PWRS0012">
+<!-- EAR combo box of the server run-time environment selection Page -->
+<description>Select from the listed EAR projects. It is recommended that you select different EARs for the client and the service to avoid runtime errors. The wizard will create the EAR for you if it does not already exist.</description>
+</context>
+
+
+<context id="PWSM0001">
+<!-- Sample Page -->
+<description>The sample Web application demonstrates how to code the proxy file.</description>
+</context>
+
+<context id="PWSM0002">
+<!-- Test check box of the Sample Page -->
+<description>If selected will launch the sample Web application in the Web browser.</description>
+</context>
+
+<context id="PWSM0003">
+<!-- Test Type Combo box of the Sample Page -->
+<description>The sample Web application demonstrates how to code the proxy file.</description>
+</context>
+
+<context id="PWSM0005">
+<!-- Methods tree of the Sample Page -->
+<description>The methods that can be invoked on the service object and encoding styles for the method inputs and outputs. Only selected methods will be available for invocation and documented in the WSDL. Select encoding styles for input parameters and output return. The methods list will display supported methods for a selected service object.</description>
+</context>
+
+<context id="PWSM0006">
+<!-- Select All button of the Sample Page -->
+<description>Click this button to add all the available methods to the Web service sample proxy.</description>
+</context>
+
+<context id="PWSM0007">
+<!-- Deselect All button of the Sample Page -->
+<description>Click this button to remove all the available methods to the Web service sample proxy.</description>
+</context>
+
+<context id="PWSM0008">
+<!-- JSP Folder field of the Sample Page -->
+<description>Folder into which your Web service JSPs are deposited.</description>
+</context>
+
+<context id="PWSM0009">
+<!-- JSP Folder Browse button of the Sample Page -->
+<description>Click to find the folder into which your Web service JSPs are deposited.</description>
+</context>
+
+<context id="PWSM0010">
+<!-- Project combo box of the Sample Page -->
+<description>Select an existing project into which your sample will be generated.</description>
+</context>
+
+<context id="PWSM0014">
+<!-- Folder field of the Sample Page -->
+<description>Folder into which the fully qualified proxy is generated. Defaults to the source folder inside of your Web project.</description>
+</context>
+
+<context id="PWSM0015">
+<!-- Run test check box of the Sample Page -->
+<description>Select this check box to run the sample application on the server.</description>
+</context>
+
+<context id="PWSM0016">
+<!-- EAR combo box of the Sample Page -->
+<description>Select the EAR in which you want your Web service sample application created.</description>
+</context>
+
+
+<context id="PWWS0001">
+<!-- WSDL Selection Page-->
+<description>Use this page to select the WSDL, WSIL, or HTML document that will be used to create the Web service.</description>
+</context>
+
+<context id="PWWS0002">
+<!-- WSDL Document text field of the WSDL Selection Page-->
+<description>Enter the path to a WSDL, WSIL, or HTML document.</description>
+</context>
+
+<context id="PWWS0003">
+<!-- WSDL Resource Browse button of the WSDL Selection Page-->
+<description>Browse to the location of a WSDL, WSIL, or HTML document.</description>
+</context>
+
+
+<context id="DBAS0001">
+<!-- HTTP basic authentication user name -->
+<description>Enter the user name used for HTTP basic authentication.</description>
+</context>
+
+<context id="DBAS0002">
+<!-- HTTP basic authentication password -->
+<description>Enter the password used for HTTP basic authentication.</description>
+</context>
+
+<!--TopologyPreferencePage.java-->
+
+<context id="PTPP0001">
+<!--PTPP0001 for the Topology Preference Page-->
+<description>These tables respresents the the types of projects available into which you can generate
+a Web service or client. You cannot add or remove project types, however you can change the order in which
+they appear in the Web services wizard. This is useful if you are creating several Web services that use
+the same type of service or client project because you can set that service or client project type as the default. To change
+the order, select a project type and use the up and down arrows to move it within the list. Changing the
+order of the list does not restrict your ability to select any of the options.
+If you select the check box, by default the Web services wizard will generate the Web services
+server and client code into different EARs. It is recommended that you enable this feature.
+</description>
+</context>
+
+<context id="PTPP0002">
+<!--PTPP0002 for the Topology Preference Page-->
+<description>This table respresents the the types of projects available into which you can generate a
+Web services client. You cannot add or remove project types, however you can change the order
+in which they appear in the Web services wizard. This is useful if you are creating several Web
+services that use the same type of client project because you can set that client project type as
+the default. To change the order, select a project type and use the up and down arrows to move it
+within the list. Changing the order of the list does not restrict your ability to select any of the options.</description>
+</context>
+
+<context id="PTPP0005">
+<!--PTPP0002 for the Topology Preference Page-->
+<description>If you select this check box, by default the Web services wizard will generate the Web services server and client code into different EARs. It is recommended that you enable this feature.</description>
+</context>
+
+
+</contexts>
diff --git a/docs/org.eclipse.jst.ws.consumption.infopop/wscreationui-f1Contexts.xml b/docs/org.eclipse.jst.ws.consumption.infopop/wscreationui-f1Contexts.xml
new file mode 100644
index 0000000..d2ccfe8
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.infopop/wscreationui-f1Contexts.xml
@@ -0,0 +1,172 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?NLS TYPE="org.eclipse.help.contexts"?>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2007 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * IBM Corporation - initial API and implementation
+ *******************************************************************************/ -->
+<contexts>
+
+<context id="PWRS0002">
+<!-- Run-time/servers in the Web Service type-->
+<description>Select the scenario configuration for run-time environments, servers, and projects.</description>
+</context>
+
+<context id="PWPR0001">
+<!-- Project Page -->
+<description>Select the type of Web service you want to generate and any file and folder options for your Web service.</description>
+</context>
+
+<context id="PWPR0005">
+<!-- Generate Proxy check box of the Project Page -->
+<description>The generated Java bean proxy provides a remote procedure call interface to the Web service.</description>
+</context>
+
+<context id="PWPR0009">
+<!-- Start Web Project check box check box of the Project Page -->
+<description>Click to start the server. If you leave the box unchecked you will have to manually start the server.</description>
+</context>
+
+<context id="PWPR0010">
+<!-- Web Service Type combo box of the Project Page -->
+<description>Select the type of Web service you want to build. Your selection will affect the files available for selection.</description>
+</context>
+
+<context id="PWPR0011">
+<!-- Wizard Scenario Service group of the Project Page -->
+<description>Select the type of Web service you want to build. Your selection will affect the files available for selection.</description>
+</context>
+
+<context id="PWPR0013">
+<!-- Test service checkbox of the project page -->
+<description>Select this check box to launch the Web service in the Web Services Explorer in order to examine it.</description>
+</context>
+
+<context id="PWPR0012">
+<!-- Launch UDDI check box of the Project Page -->
+<description>Select this checkbox to launch the Web Services Explorer in order to publish the Web service to a UDDI registry.</description>
+</context>
+
+<context id="PWPR0014">
+<!-- Web Service Client Type combo box of the Project Page -->
+<description>Select the client proxy type. The generated Java bean proxy provides a remote procedure call interface to the Web service.</description>
+</context>
+
+
+
+<context id="PSTP0001">
+<!-- Test Type Combo box of the Service Test Page-->
+<description>Select the test facility in which you would like to test the Web service being created.</description>
+</context>
+
+<context id="PSTP0002">
+<!-- Launch button of the Service Test Page-->
+<description>Click this to launch the Web service in a browser window to test it.</description>
+</context>
+
+<!--WebServiceWizNewFirstPage-->
+
+<context id="WSWSCEN0001">
+<!-- First Page-->
+<description>On this page select the artifact from which your Web service or client will be created, and the stages of Web services development that you want
+to complete:
+- Develop: this will create the service code
+- Assemble: this ensures that the project that will host the Web service or client gets associated to an EAR when required by the target application server
+- Deploy: this will create the deployment code for the service
+- Install: this will install the service on the chosen server
+- Start: this will start the server once the service has been installed on it
+- Test: this will provide various options for testing the service
+Select the server and runtime for your Web service or client, and whether or not you want to publish or monitor the service.
+</description>
+</context>
+
+<context id="WSWSCEN0010">
+<!--Web service type combo box of the First Page-->
+<description>Select the type of Web service you want to create. A bottom-up service creates a service from a Java bean or EJB, while a top-down service will create
+a service from a WSDL file and then create a skeleton Java bean or EJB for you to implement later.</description>
+</context>
+
+<context id="WSWSCEN0014">
+<!--Monitor checkbox of the First Page-->
+<description>Monitor the Web service: this will 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.</description>
+</context>
+
+<context id="WSWSCEN0012">
+<!--Launch UDDI check box of the First Page-->
+<description>Publish the Web service: this will launch the Web Services Explorer
+to publish your Web service to a UDDI registry.</description>
+</context>
+
+<context id="WSWSCEN0020">
+<!--Service implementation field of the First Page-->
+<description>Enter the URI to the WSDL, WSIL, or HTML file that
+will be used to generate the service</description>
+</context>
+
+<context id="WSWSCEN0021">
+<!--Service slider of the First Page-->
+<description>Select the stages of Web services development that you want
+to complete using the slider:
+- Develop: this will create the service code
+- Assemble: this ensures that the project that will host the Web service or client gets associated to an EAR when required by the target application server
+- Deploy: this will create the deployment code for the service
+- Install: this will install the service on the chosen server
+- Start: this will start the server once the service has been installed on it
+- Test: this will provide various options for testing the service
+</description>
+</context>
+
+<context id="WSWSCEN0022">
+<!--Server link of the First Page-->
+<description>Select your server: the default server is displayed. If you
+want to deploy your service to a different server click the link to specify
+a different server.</description>
+</context>
+
+<context id="WSWSCEN0023">
+<!--runtime link of the First Page-->
+<description>Select your runtime: the default runtime is displayed. If you
+want to deploy your service to a different runtime click the link to specify
+a different runtime.</description>
+</context>
+
+<context id="WSWSCEN0024">
+<!--projects link of the First Page-->
+<description>Select the service project: the project containing the project
+selected in your workspace is displayed. To select a different project and
+EAR click on the project link. 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.</description>
+</context>
+
+<context id="WSWSCEN0025">
+<!--client type combo of the First Page-->
+<description>The Java bean client proxy that is generated provides a remote procedure call interface to the Web service.</description>
+</context>
+
+<context id="WSWSCEN0026">
+<!--Client slider of the First Page-->
+<description>Select the stages of Web services client development that you want
+to complete using the slider:
+- Develop: this will create the client code
+- Assemble: this ensures that the project that will host the Web service or client gets associated to an EAR when required by the target application server
+- Deploy: this will create the deployment code for the client
+- Install: this will install the client on the chosen server
+- Start: this will start the server once the client has been installed on it
+- Test: this will provide various options for testing the client
+</description>
+</context>
+
+<context id="WSWSCEN0030">
+<!--file overwrite checkbox of the First Page-->
+<description>This allows you to overwrite files without receiving a warning message asking for confirmation when overwriting files.</description>
+</context>
+
+</contexts>
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/.cvsignore b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/.cvsignore
new file mode 100644
index 0000000..d540fb2
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/.cvsignore
@@ -0,0 +1,5 @@
+org.eclipse.jst.ws.consumption.ui.doc.user_1.0.0.jar
+bak
+temp
+DitaLink.cat
+build.xml
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/.project b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/.project
new file mode 100644
index 0000000..0b3dcb1
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/.project
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.jst.ws.consumption.ui.doc.user</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ <buildCommand>
+ <name>org.eclipse.pde.ManifestBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.pde.SchemaBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ </buildSpec>
+ <natures>
+ <nature>org.eclipse.pde.PluginNature</nature>
+ </natures>
+</projectDescription>
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/DocBuild.xml b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/DocBuild.xml
new file mode 100644
index 0000000..23a513f
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/DocBuild.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.2" />
+
+ <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="wsconsumptiont_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/META-INF/MANIFEST.MF b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/META-INF/MANIFEST.MF
new file mode 100644
index 0000000..41a4a69
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/META-INF/MANIFEST.MF
@@ -0,0 +1,8 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: %pluginName
+Bundle-SymbolicName: org.eclipse.jst.ws.consumption.ui.doc.user; singleton:=true
+Bundle-Version: 1.0.300.qualifier
+Bundle-Vendor: %pluginProvider
+Bundle-Localization: plugin
+Eclipse-LazyStart: true
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/about.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/about.html
new file mode 100644
index 0000000..73db36e
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/about.html
@@ -0,0 +1,34 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<HTML>
+
+<head>
+<title>About</title>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+</head>
+
+<BODY lang="EN-US">
+
+<H3>About This Content</H3>
+
+<P>June 06, 2007</P>
+
+<H3>License</H3>
+
+<P>The Eclipse Foundation makes available all content in this plug-in
+("Content"). Unless otherwise indicated below, the Content is provided to you
+under the terms and conditions of the Eclipse Public License Version 1.0
+("EPL"). A copy of the EPL is available at
+<A href="http://www.eclipse.org/org/documents/epl-v10.php">http://www.eclipse.org/org/documents/epl-v10.php</A>.
+For purposes of the EPL, "Program" will mean the Content.</P>
+
+<P>If you did not receive this Content directly from the Eclipse Foundation, the
+Content is being redistributed by another party ("Redistributor") and different
+terms and conditions may apply to your use of any object code in the Content.
+Check the Redistributors license that was provided with the Content. If no such
+license exists, contact the Redistributor. Unless otherwise indicated below, the
+terms and conditions of the EPL still apply to any source code in the Content
+and such source code may be obtained at
+<A href="http://www.eclipse.org/">http://www.eclipse.org/</A>.</P>
+
+</BODY>
+</HTML>
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/build.properties b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/build.properties
new file mode 100644
index 0000000..febd402
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/build.properties
@@ -0,0 +1,20 @@
+bin.includes = plugin.properties,\
+ plugin.xml,\
+ wsconsumptionbuild_toc.xml,\
+ wsconsumptiont_toc.xml,\
+ org.eclipse.jst.ws.consumption.ui.doc.userindex.xml,\
+ about.html,\
+ images/,\
+ concepts/*.htm*,\
+ tasks/*.htm*,\
+ ref/*.htm*,\
+ index/,\
+ META-INF/
+src.includes = build.properties,\
+ *.maplist,\
+ *.ditamap,\
+ concepts/*.dita,\
+ tasks/*.dita,\
+ ref/*.dita
+bin.excludes = DocBuild.xml,\
+ myPlugin*.xml
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 0000000..baabb38
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cuddi.dita
@@ -0,0 +1,92 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>UDDI</indexterm><indexterm>Universal Description, Discovery,
+and Integration </indexterm><indexterm>Web services<indexterm>UDDI</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<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>
+</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
new file mode 100644
index 0000000..0b12e40
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cuddi.html
@@ -0,0 +1,120 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="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 content="UDDI, Universal Description, Discovery, and Integration, Web services" name="DC.subject" />
+<meta content="UDDI, Universal Description, Discovery, and Integration, Web services" name="keywords" />
+<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="../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/common.css" type="text/css" rel="stylesheet" />
+<title>Universal Description, Discovery, and Integration (UDDI)</title>
+</head>
+<body id="cuddi"><a name="cuddi"><!-- --></a>
+
+
+<h1 class="topictitle1">Universal Description, Discovery, and Integration (UDDI)</h1>
+
+
+
+
+<div><p>Universal Description, Discovery, and Integration (UDDI) specification
+defines a way to publish and discover information about Web services.</p>
+
+<div class="p">UDDI has two functions: <ul>
+<li>It is a SOAP-based protocol that defines how clients communicate with
+UDDI registries.</li>
+
+<li>It is a particular set of global replicated registries.</li>
+
+</ul>
+</div>
+
+<p>UDDI includes an XML schema for SOAP messages that defines a set of documents
+to describe business and services information, a common set of APIs for querying
+and publishing information to the directories, and an API for replicating
+directory entries between peer UDDI nodes.</p>
+
+<p>For more information on UDDI refer to <a href="http://www.uddi.org" target="_blank">www.uddi.org</a></p>
+
+<div class="section"><h4 class="sectiontitle">UDDI registries</h4><p>UDDI manages the discovery of Web
+services by relying on a distributed registry of businesses and their service
+descriptions implemented in a common XML format. Before you can publish your
+business entity and Web service to a public registry, you must first register
+your business entity with a UDDI registry.</p>
+<p>UDDI registries come in two
+forms: public and private. Both types comply to the same specifications.
+A private registry enables you to publish and test your internal e-business
+applications in a secure, private environment.</p>
+<p>A public registry
+is a collection of peer directories that contain information about businesses
+and services. It locates services that are registered at one of its peer nodes
+and facilitates the discovery of published Web services. Data is replicated
+at each of the registries on a regular basis. This ensures consistency in
+service description formats and makes it easy to track changes as they occur. IBM<sup>®</sup> maintains
+two public registries called the IBM UDDI Business Registry and the IBM UDDI Test
+Registry. The IBM UDDI
+Test Registry allows you to develop your Web service and experience the UDDI
+registration process without placing your Web service in an official registry.
+Use the IBM UDDI
+Test Registry to experiment with UDDI, and to test and validate your Web service.
+For more information on the IBM's public registries, refer to <a href="http://uddi.ibm.com" target="_blank">http://uddi.ibm.com</a> For
+a list of public registries, refer to <a href="http://www.uddi.org/register.html" target="_blank">http://www.uddi.org/register.html</a></p>
+<p>A private
+registry allows you to publish and test your internal applications in a secure,
+private environment.</p>
+<p>The UDDI Business Registry acts as a B2B directory
+linking marketplaces, buyers, and sellers. The information provided in the
+registry consists of three components: white pages, yellow pages, and green
+pages. White pages include the business name, contact information, and a text
+description of the business's services. Yellow pages include industrial categorizations
+based on standard taxonomies such as NAICS, ISO 3166, and UNSPSC. Green pages
+include references to specifications for Web services and pointers to various
+file and URL-based discovery mechanisms. This makes it easy for businesses
+to integrate across marketplaces. Because it is registered, information is
+made available across all applications. For more information on NAICS refer
+to <a href="http://www.naics.com" target="_blank">www.naics.com</a> For
+more information on UNSPSC refer to <a href="http://www.unspsc.org" target="_blank">www.unspsc.org</a> For more information on ISO 3166 refer
+to <a href="http://www.iso.org/iso/en/prods-services/iso3166ma/index.html" target="_blank">http://www.iso.org/iso/en/prods-services/iso3166ma/index.html</a></p>
+<p>Businesses
+populate the registry with descriptions of the services that they support.
+UDDI assigns a unique identifier to each service description and business
+registration. These become the service and business keys respectively. Search
+engines, and applications query the registry to discover services. UDDI servers
+are a directory of available services and service providers.</p>
+</div>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related Concepts</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div>
+<div><a href="cwsdlud.html" title="The Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services. UDDI has two functions: (1) it is a SOAP-based protocol that defines how UDDI clients communicate with registries, and (2) it is a particular set of globally replicated registries.">Relationship between UDDI and WSDL</a></div>
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsilud.html">Relationship between UDDI and WSIL</a></div></div>
+
+<div class="linklist"><strong>Related Tasks</strong><br />
+
+<div><a href="../tasks/tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div></div>
+
+<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 0000000..fecbf45
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cwsdlud.dita
@@ -0,0 +1,111 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>UDDI<indexterm>relationship with WSDL</indexterm></indexterm>
+<indexterm>WSDL<indexterm>relationship with UDDI</indexterm></indexterm></keywords>
+</metadata></prolog>
+<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
new file mode 100644
index 0000000..8dbf57c
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cwsdlud.html
@@ -0,0 +1,156 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="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 content="UDDI, relationship with WSDL, WSDL, relationship with UDDI" name="DC.subject" />
+<meta content="UDDI, relationship with WSDL, WSDL, relationship with UDDI" name="keywords" />
+<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/common.css" type="text/css" rel="stylesheet" />
+<title>Relationship between UDDI and WSDL</title>
+</head>
+<body id="cwsdlud"><a name="cwsdlud"><!-- --></a>
+
+
+<h1 class="topictitle1">Relationship between UDDI and WSDL</h1>
+
+
+
+<div><p>The Universal Description, Discovery, and Integration (UDDI) specification
+defines a way to publish and discover information about Web services. UDDI
+has two functions: (1) it is a SOAP-based protocol that defines how UDDI clients
+communicate with registries, and (2) it is a particular set of globally replicated
+registries.</p>
+
+<p>Registering a service involves four core data structure types:</p>
+
+<ul>
+<li>The <tt class="sysout">businessEntity</tt> data type contains information
+about the business that has a published service.</li>
+
+<li>The <tt class="sysout">businessService</tt> data type is a description
+of a Web service.</li>
+
+<li>The <tt class="sysout">bindingTemplate</tt> data type contains technical
+information for determining the entry point and construction specifications
+for invoking a Web service.</li>
+
+<li>The <tt class="sysout">tModel</tt> data type provides a reference
+system to assist in the discovery of Web services and acts as a technical
+specification for a Web service.</li>
+
+</ul>
+
+<p>For more information on the UDDI data types, refer to the related reference
+topics at the end of this topic.</p>
+
+<p>Web Services Description Language (WSDL) is an XML-based standard specification
+for describing Web services. WSDL defines an XML format for describing network
+services as a set of endpoints that operate on messages that contain either
+document-oriented or procedure-oriented information.</p>
+
+<p>The WSDL service description can be structured in many ways. However, to
+assist with publishing and finding WSDL service descriptions in a UDDI registry,
+WSDL documents consist of two main parts: </p>
+
+<ul>
+<li>The service interface definition describes the abstract type interface
+and its protocol binding, known as the WSDL binding document</li>
+
+<li>The service implementation definition describes the service access location
+information, known as the WSDL service document</li>
+
+</ul>
+
+<p>When creating Web services with the Apache Axis run-time environment, the
+Web services tools create a single WSDL document when generating Web services
+from Java™ beans
+or EJBs. This WSDL document contains both the service interface and implementation
+documents.</p>
+
+<p>A service interface is described by a WSDL document that contains the types,
+import, message, portType, and binding elements. A service interface contains
+the WSDL service definition that will be used to implement one or more services.
+It is an abstract definition of a Web service, and is used to describe a specific
+type of service. This document can reference another service interface document
+using an import element. The Web services tools in this product generate a
+service interface document that contains only the message and portType elements
+that are referenced by the binding document that contains only bindings for
+the portType.</p>
+
+<p>The service implementation document contains the service elements. A service
+implementation document contains a description of a service that implements
+a service interface. At least one of the import elements will contain a reference
+to the WSDL service interface document; however monolithic WSDL such as that
+created using the Axis run-time environment does not have imports. A service
+implementation document can contain references to more than one service interface
+document.</p>
+
+<p>A service provider hosts a Web service and makes it accessible using protocols
+such as SOAP/HTTP and SOAP/JMS. The Web service is described by the WSDL documents
+that are stored on the provider's server or in a special repository. The WSDL
+documents are referenced by UDDI business services (service documents) and
+tModels (binding documents). These pointers enable discovery of a Web service
+by a service requestor.</p>
+
+<p>Figure 1. Relationship between UDDI and WSDL.</p>
+
+<p> <img src="../images/wsdluddi.gif" alt="Illustration of the relationship between UDDI and WSDL." /> </p>
+
+<p>Figure 1 illustrates the relationship between UDDI and WSDL. The WSDL service
+element references the WSDL binding element. The URL of the document containing
+the WSDL binding element is published to the UDDI business registry as a tModel.
+The URL of the document containing the WSDL service element is published to
+the UDDI business registry as a businessService and contains information about
+the bindingTemplate. For more information on UDDI registry data structure
+types, refer to the related reference section at the end of this document.
+Note that the import portion of the diagram is optional depending on the run-time
+environment; monolithic WSDL such as that created using the Axis run-time
+environment does not have imports.</p>
+
+<p>The service implementation describes an instance of a service. The instance
+is defined using a WSDL service element. The service element in a service
+implementation document is used to publish a UDDI businessService. When publishing
+a WSDL service description, a service interface must be published as a tModel
+before a service implementation is published as a businessService.</p>
+
+<p>A service implementation is published in a UDDI registry as part of a businessService
+with one or more bindingTemplate elements. The businessService is published
+by the service provider. A new businessService is created for a service element
+that is defined in the service implementation document. A new bindingTemplate
+element is created within a businessService for each port element that is
+defined within a service element.</p>
+
+<p>For more information on the relationship between WSDL and UDDI refer to
+ <a href="http://uddi.org/bestpractices.html" target="_blank">uddi.org/bestpractices.html</a>.</p>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related Concepts</strong><br />
+
+<div><a href="cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div>
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.html">Web Services Description Language (WSDL)</a></div></div>
+
+<div class="linklist"><strong>Related Reference</strong><br />
+
+<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div>
+<div><a href="../../org.eclipse.jst.ws.doc.user/ref/rwsdl.html">Web Services Description Language (WSDL)</a></div></div>
+</div>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/addfav.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/addfav.gif
new file mode 100644
index 0000000..48895f4
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/addfav.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/adduddi.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/adduddi.gif
new file mode 100644
index 0000000..8399bb0
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/adduddi.gif
Binary files differ
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
new file mode 100644
index 0000000..3cbe40c
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/beaninfojsp.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/bindnode.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/bindnode.gif
new file mode 100644
index 0000000..7bf5d03
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/bindnode.gif
Binary files differ
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
new file mode 100644
index 0000000..d84a5bb
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/browsebutton.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/busasst.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/busasst.gif
new file mode 100644
index 0000000..3fdcbb0
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/busasst.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/fav.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/fav.gif
new file mode 100644
index 0000000..debfabd
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/fav.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/find.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/find.gif
new file mode 100644
index 0000000..6dc3ebe
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/find.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/fswsdlicon.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/fswsdlicon.gif
new file mode 100644
index 0000000..3060e55
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/fswsdlicon.gif
Binary files differ
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
new file mode 100644
index 0000000..237bdd2
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/login.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/loginicon.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/loginicon.gif
new file mode 100644
index 0000000..ed510ca
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/loginicon.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/logouticon.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/logouticon.gif
new file mode 100644
index 0000000..d7709cf
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/logouticon.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/mptwsdlicon.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/mptwsdlicon.gif
new file mode 100644
index 0000000..905e655
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/mptwsdlicon.gif
Binary files differ
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
new file mode 100644
index 0000000..2f4b509
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/newjsp.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/opnode.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/opnode.gif
new file mode 100644
index 0000000..a8eb349
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/opnode.gif
Binary files differ
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
new file mode 100644
index 0000000..652e4ea
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/proxyonjsp.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/publish2.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/publish2.gif
new file mode 100644
index 0000000..14a11a5
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/publish2.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/pubserv.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/pubserv.gif
new file mode 100644
index 0000000..31d36b7
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/pubserv.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/refserv.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/refserv.gif
new file mode 100644
index 0000000..f5c015b
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/refserv.gif
Binary files differ
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
new file mode 100644
index 0000000..6e884d2
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/runjsf.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/scenario7.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/scenario7.gif
new file mode 100644
index 0000000..a36531e
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/scenario7.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/servnode.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/servnode.gif
new file mode 100644
index 0000000..e51233d
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/servnode.gif
Binary files differ
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
new file mode 100644
index 0000000..d5edaeb
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/soapudws.cdr
Binary files differ
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
new file mode 100644
index 0000000..2352f01
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddi.cdr
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddi.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddi.gif
new file mode 100644
index 0000000..7a02c09
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddi.gif
Binary files differ
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
new file mode 100644
index 0000000..e8da32a
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddiref.cdr
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddiref.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddiref.gif
new file mode 100644
index 0000000..7c148a7
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddiref.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddiview.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddiview.gif
new file mode 100644
index 0000000..0601bc8
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddiview.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlbnddetl.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlbnddetl.gif
new file mode 100644
index 0000000..002262f
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlbnddetl.gif
Binary files differ
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
new file mode 100644
index 0000000..ef54568
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdldetail.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdldtlicon.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdldtlicon.gif
new file mode 100644
index 0000000..d8ee67c
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdldtlicon.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlexp.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlexp.gif
new file mode 100644
index 0000000..92ef10a
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlexp.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlfavicon.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlfavicon.gif
new file mode 100644
index 0000000..f9acc3d
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlfavicon.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlicon.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlicon.gif
new file mode 100644
index 0000000..9aec326
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlicon.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlnode.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlnode.gif
new file mode 100644
index 0000000..7b7521a
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlnode.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlop.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlop.gif
new file mode 100644
index 0000000..287dd4a
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlop.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlopret.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlopret.gif
new file mode 100644
index 0000000..2c83e35
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlopret.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlopretx.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlopretx.gif
new file mode 100644
index 0000000..0f5d577
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlopretx.gif
Binary files differ
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
new file mode 100644
index 0000000..537c1c0
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlpage.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlservdet.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlservdet.gif
new file mode 100644
index 0000000..987cb85
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlservdet.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlstatx.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlstatx.gif
new file mode 100644
index 0000000..91ba787
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlstatx.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdltemp.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdltemp.gif
new file mode 100644
index 0000000..99bd207
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdltemp.gif
Binary files differ
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
new file mode 100644
index 0000000..8949098
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdluddi.cdr
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdluddi.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdluddi.gif
new file mode 100644
index 0000000..febb7d5
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdluddi.gif
Binary files differ
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
new file mode 100644
index 0000000..b5e6e03
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsilpage.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsilview.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsilview.gif
new file mode 100644
index 0000000..789d689
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsilview.gif
Binary files differ
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
new file mode 100644
index 0000000..0e5d5f0
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsinjsp.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wswizicon.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wswizicon.gif
new file mode 100644
index 0000000..3b17aa7
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wswizicon.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/index/_k.cfs b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/index/_k.cfs
new file mode 100644
index 0000000..3e5652c
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/index/_k.cfs
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/index/deletable b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/index/deletable
new file mode 100644
index 0000000..e423242
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/index/deletable
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/index/indexed_contributions b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/index/indexed_contributions
new file mode 100644
index 0000000..c1c260b
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/index/indexed_contributions
@@ -0,0 +1,3 @@
+#This is a generated file; do not edit.
+#Wed May 09 14:13:16 EDT 2007
+org.eclipse.jst.ws.consumption.ui.doc.user=org.eclipse.jst.ws.consumption.ui.doc.user\n1.0.300.qualifier
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/index/indexed_dependencies b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/index/indexed_dependencies
new file mode 100644
index 0000000..14ef7ba
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/index/indexed_dependencies
@@ -0,0 +1,4 @@
+#This is a generated file; do not edit.
+#Wed May 09 14:13:16 EDT 2007
+lucene=1.4.103.v20060601
+analyzer=org.eclipse.help.base\#3.2.0.v20060601?locale\=en
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/index/indexed_docs b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/index/indexed_docs
new file mode 100644
index 0000000..901aae3
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/index/indexed_docs
@@ -0,0 +1,21 @@
+#This is a generated file; do not edit.
+#Wed May 09 14:13:16 EDT 2007
+/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tlogexp.html=0
+/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/taddreg.html=0
+/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tdiscov.html=0
+/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/treg.html=0
+/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tgenwsil.html=0
+/org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cwsdlud.html=0
+/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tassert.html=0
+/org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cuddi.html=0
+/org.eclipse.jst.ws.consumption.ui.doc.user/ref/ruddi.html=0
+/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tupdate.html=0
+/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.html=0
+/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdlexp.html=0
+/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tunpub.html=0
+/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tstrtexp.html=0
+/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbkmrk.html=0
+/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpublish.html=0
+/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbusproj.html=0
+/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpubent.html=0
+/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/ttestwsdl.html=0
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/index/segments b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/index/segments
new file mode 100644
index 0000000..19b5d0c
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/index/segments
Binary files differ
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 0000000..d31fb14
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/myplugin.xml
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?eclipse version="3.0"?>
+<?NLS TYPE="org.eclipse.help.toc"?>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2007 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * IBM Corporation - initial API and implementation
+ *******************************************************************************/ -->
+<plugin>
+
+ <extension point="org.eclipse.help.toc">
+ <toc file="wsconsumptionbuild_toc.xml"/>
+ <toc file="wsconsumptiont_toc.xml" />
+ <index path="index/"/>
+ </extension>
+ <extension point="org.eclipse.help.index">
+ <index file="org.eclipse.jst.ws.consumption.ui.doc.userindex.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 0000000..aec04b0
--- /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/org.eclipse.jst.ws.consumption.ui.doc.userindex.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/org.eclipse.jst.ws.consumption.ui.doc.userindex.html
new file mode 100644
index 0000000..82527a6
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/org.eclipse.jst.ws.consumption.ui.doc.userindex.html
@@ -0,0 +1,179 @@
+<?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" />
+<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="security" content="public" />
+<meta name="Robots" content="index,follow" />
+<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 name="DC.Format" content="XHTML" />
+<link rel="stylesheet" type="text/css" href="../org.eclipse.wst.doc.user/ibmdita.css" />
+<link rel="stylesheet" type="text/css" href="../org.eclipse.wst.doc.user/common.css" />
+<title>Index</title>
+</head>
+<body>
+<h1>Index</h1>
+<a name="IDX0_42" href="#IDX1_42">B</a>
+<a name="IDX0_44" href="#IDX1_44">D</a>
+<a name="IDX0_52" href="#IDX1_52">R</a>
+<a name="IDX0_53" href="#IDX1_53">S</a>
+<a name="IDX0_55" href="#IDX1_55">U</a>
+<a name="IDX0_57" href="#IDX1_57">W</a>
+<hr></hr>
+<strong><a name="IDX1_42" href="#IDX0_42">B</a></strong>
+<ul class="indexlist">
+<li>business entities
+<ul class="indexlist">
+<li><a href="tasks/tuddiexp.html#tuddiexp">publishing</a>
+</li>
+<li><a href="tasks/tpubent.html#tpubent">publishing to UDDI</a>
+</li>
+<li><a href="tasks/tunpub.html#tunpub">removing from a UDDI registry</a>
+</li>
+<li><a href="tasks/tupdate.html#tupdate">updating in a UDDI registry</a>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a name="IDX1_44" href="#IDX0_44">D</a></strong>
+<ul class="indexlist">
+<li>data structure types
+<ul class="indexlist">
+<li><a href="ref/ruddi.html#ruddi">UDDI registry</a>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a name="IDX1_52" href="#IDX0_52">R</a></strong>
+<ul class="indexlist">
+<li>registries
+<ul class="indexlist">
+<li><a href="tasks/taddreg.html#taddreg">adding to the Web Services Explorer</a>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a name="IDX1_53" href="#IDX0_53">S</a></strong>
+<ul class="indexlist">
+<li>service interfaces
+<ul class="indexlist">
+<li><a href="tasks/tunpub.html#tunpub">removing from a UDDI registry</a>
+</li>
+<li><a href="tasks/tupdate.html#tupdate">updating UDDI registries</a>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a name="IDX1_55" href="#IDX0_55">U</a></strong>
+<ul class="indexlist">
+<li><a href="concepts/cuddi.html#cuddi">UDDI</a>
+<ul class="indexlist">
+<li><a href="ref/ruddi.html#ruddi">data structure types</a>
+</li>
+<li><a href="tasks/tdiscov.html#tdiscov">discovering Web services</a>
+</li>
+<li><a href="tasks/tlogexp.html#tlogexp">logging into a registry</a>
+</li>
+<li><a href="tasks/tassert.html#tassert">managing publisher assertions</a>
+</li>
+<li><a href="tasks/tbusproj.html#tbusproj">managing services</a>
+</li>
+<li><a href="tasks/tpubent.html#tpubent">publishing a business entity</a>
+</li>
+<li><a href="tasks/tpublish.html#tpublish">publishing a Web service</a>
+</li>
+<li><a href="tasks/treg.html#treg">registering with a registry</a>
+</li>
+<li><a href="concepts/cwsdlud.html#cwsdlud">relationship with WSDL</a>
+</li>
+<li><a href="tasks/tunpub.html#tunpub">removing services from a registry</a>
+</li>
+</ul>
+</li>
+<li><a href="concepts/cuddi.html#cuddi">Universal Description, Discovery, and Integration</a>
+</li>
+</ul>
+<strong><a name="IDX1_57" href="#IDX0_57">W</a></strong>
+<ul class="indexlist">
+<li>Web Service Explorer
+<ul class="indexlist">
+<li><a href="tasks/tbkmrk.html#tbkmrk">adding Favorites</a>
+</li>
+</ul>
+</li>
+<li>Web services
+<ul class="indexlist">
+<li><a href="tasks/taddreg.html#taddreg">adding a registry to the Web Services Explorer</a>
+</li>
+<li><a href="tasks/tdiscov.html#tdiscov">discovering</a>
+</li>
+<li><a href="tasks/twsdlexp.html#twsdlexp">exploring WSDL</a>
+</li>
+<li><a href="tasks/tgenwsil.html#tgenwsil">generating WSIL</a>
+</li>
+<li><a href="tasks/tbusproj.html#tbusproj">managing services</a>
+</li>
+<li><a href="tasks/tpubent.html#tpubent">publishing a business entity</a>
+</li>
+<li><a href="tasks/tpublish.html#tpublish">publishing to a UDDI registry</a>
+</li>
+<li><a href="tasks/treg.html#treg">registering with a UDDI registry</a>
+</li>
+<li><a href="tasks/tunpub.html#tunpub">removing from a UDDI registry</a>
+</li>
+<li><a href="tasks/ttestwsdl.html#ttestwsdl">testing with the Web Services Explorer</a>
+</li>
+<li><a href="concepts/cuddi.html#cuddi">UDDI</a>
+</li>
+<li><a href="tasks/tupdate.html#tupdate">updating UDDI registries</a>
+</li>
+</ul>
+</li>
+<li>Web Services
+<ul class="indexlist">
+<li>publishing
+<ul class="indexlist">
+<li><a href="tasks/tuddiexp.html#tuddiexp">overview</a>
+</li>
+</ul>
+</li>
+</ul>
+</li>
+<li>Web Services Explorer
+<ul class="indexlist">
+<li><a href="tasks/taddreg.html#taddreg">adding a registry</a>
+</li>
+<li><a href="tasks/tstrtexp.html#tstrtexp">launching</a>
+</li>
+<li><a href="tasks/tlogexp.html#tlogexp">logging into a UDDI registry</a>
+</li>
+<li><a href="tasks/tuddiexp.html#tuddiexp">publishing Web services</a>
+</li>
+</ul>
+</li>
+<li>WSDL
+<ul class="indexlist">
+<li><a href="tasks/tbkmrk.html#tbkmrk">adding to Favorites</a>
+</li>
+<li><a href="tasks/twsdlexp.html#twsdlexp">exploring</a>
+</li>
+<li><a href="concepts/cwsdlud.html#cwsdlud">relationship with UDDI</a>
+</li>
+<li><a href="tasks/ttestwsdl.html#ttestwsdl">testing with the Web Services Explorer</a>
+</li>
+</ul>
+</li>
+<li>WSIL
+<ul class="indexlist">
+<li><a href="tasks/tbkmrk.html#tbkmrk">adding to Favorites</a>
+</li>
+<li><a href="tasks/tdiscov.html#tdiscov">discovering Web services</a>
+</li>
+<li><a href="tasks/tgenwsil.html#tgenwsil">generating</a>
+</li>
+</ul>
+</li>
+</ul>
+</body></html>
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/org.eclipse.jst.ws.consumption.ui.doc.userindex.xml b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/org.eclipse.jst.ws.consumption.ui.doc.userindex.xml
new file mode 100644
index 0000000..ed74e7d
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/org.eclipse.jst.ws.consumption.ui.doc.userindex.xml
@@ -0,0 +1,160 @@
+<?xml version="1.0" encoding="utf-8"?>
+<index>
+ <entry keyword="UDDI">
+ <topic href="concepts/cuddi.html#cuddi" title="Universal Description, Discovery, and Integration (UDDI)"/>
+ <entry keyword="relationship with WSDL">
+ <topic href="concepts/cwsdlud.html#cwsdlud" title="Relationship between UDDI and WSDL"/>
+ </entry>
+ <entry keyword="discovering Web services">
+ <topic href="tasks/tdiscov.html#tdiscov" title="Discovering Web Services"/>
+ </entry>
+ <entry keyword="registering with a registry">
+ <topic href="tasks/treg.html#treg" title="Registering with a UDDI registry"/>
+ </entry>
+ <entry keyword="logging into a registry">
+ <topic href="tasks/tlogexp.html#tlogexp" title="Logging in to a UDDI registry"/>
+ </entry>
+ <entry keyword="publishing a business entity">
+ <topic href="tasks/tpubent.html#tpubent" title="Publishing a business entity"/>
+ </entry>
+ <entry keyword="publishing a Web service">
+ <topic href="tasks/tpublish.html#tpublish" title="Publishing a Web service"/>
+ </entry>
+ <entry keyword="data structure types">
+ <topic href="ref/ruddi.html#ruddi" title="Data structure types (UDDI registry)"/>
+ </entry>
+ <entry keyword="removing services from a registry">
+ <topic href="tasks/tunpub.html#tunpub" title="Removing a business entity, Web service, or service interface from a registry"/>
+ </entry>
+ <entry keyword="managing services">
+ <topic href="tasks/tbusproj.html#tbusproj" title="Managing referenced services"/>
+ </entry>
+ <entry keyword="managing publisher assertions">
+ <topic href="tasks/tassert.html#tassert" title="Managing publisher assertions"/>
+ </entry>
+ </entry>
+ <entry keyword="Universal Description, Discovery, and Integration">
+ <topic href="concepts/cuddi.html#cuddi" title="Universal Description, Discovery, and Integration (UDDI)"/>
+ </entry>
+ <entry keyword="Web services">
+ <entry keyword="UDDI">
+ <topic href="concepts/cuddi.html#cuddi" title="Universal Description, Discovery, and Integration (UDDI)"/>
+ </entry>
+ <entry keyword="discovering">
+ <topic href="tasks/tdiscov.html#tdiscov" title="Discovering Web Services"/>
+ </entry>
+ <entry keyword="exploring WSDL">
+ <topic href="tasks/twsdlexp.html#twsdlexp" title="Exploring WSDL using the WSDL Explorer"/>
+ </entry>
+ <entry keyword="testing with the Web Services Explorer">
+ <topic href="tasks/ttestwsdl.html#ttestwsdl" title="Testing WSDL documents and Web services using the WSDL Explorer"/>
+ </entry>
+ <entry keyword="registering with a UDDI registry">
+ <topic href="tasks/treg.html#treg" title="Registering with a UDDI registry"/>
+ </entry>
+ <entry keyword="adding a registry to the Web Services Explorer">
+ <topic href="tasks/taddreg.html#taddreg" title="Adding a Registry to the Web Services Explorer"/>
+ </entry>
+ <entry keyword="publishing a business entity">
+ <topic href="tasks/tpubent.html#tpubent" title="Publishing a business entity"/>
+ </entry>
+ <entry keyword="publishing to a UDDI registry">
+ <topic href="tasks/tpublish.html#tpublish" title="Publishing a Web service"/>
+ </entry>
+ <entry keyword="updating UDDI registries">
+ <topic href="tasks/tupdate.html#tupdate" title="Updating a business entity, Web service, or service interface"/>
+ </entry>
+ <entry keyword="removing from a UDDI registry">
+ <topic href="tasks/tunpub.html#tunpub" title="Removing a business entity, Web service, or service interface from a registry"/>
+ </entry>
+ <entry keyword="managing services">
+ <topic href="tasks/tbusproj.html#tbusproj" title="Managing referenced services"/>
+ </entry>
+ <entry keyword="generating WSIL">
+ <topic href="tasks/tgenwsil.html#tgenwsil" title="Generating a WSIL file"/>
+ </entry>
+ </entry>
+ <entry keyword="WSDL">
+ <entry keyword="relationship with UDDI">
+ <topic href="concepts/cwsdlud.html#cwsdlud" title="Relationship between UDDI and WSDL"/>
+ </entry>
+ <entry keyword="exploring">
+ <topic href="tasks/twsdlexp.html#twsdlexp" title="Exploring WSDL using the WSDL Explorer"/>
+ </entry>
+ <entry keyword="testing with the Web Services Explorer">
+ <topic href="tasks/ttestwsdl.html#ttestwsdl" title="Testing WSDL documents and Web services using the WSDL Explorer"/>
+ </entry>
+ <entry keyword="adding to Favorites">
+ <topic href="tasks/tbkmrk.html#tbkmrk" title="Adding a registry, business entity, business service, service interface, WSIL, or WSDL service to Favorites"/>
+ </entry>
+ </entry>
+ <entry keyword="WSIL">
+ <entry keyword="discovering Web services">
+ <topic href="tasks/tdiscov.html#tdiscov" title="Discovering Web Services"/>
+ </entry>
+ <entry keyword="adding to Favorites">
+ <topic href="tasks/tbkmrk.html#tbkmrk" title="Adding a registry, business entity, business service, service interface, WSIL, or WSDL service to Favorites"/>
+ </entry>
+ <entry keyword="generating">
+ <topic href="tasks/tgenwsil.html#tgenwsil" title="Generating a WSIL file"/>
+ </entry>
+ </entry>
+ <entry keyword="Web Services">
+ <entry keyword="publishing">
+ <entry keyword="overview">
+ <topic href="tasks/tuddiexp.html#tuddiexp" title="Publishing Web services and business entities"/>
+ </entry>
+ </entry>
+ </entry>
+ <entry keyword="business entities">
+ <entry keyword="publishing">
+ <topic href="tasks/tuddiexp.html#tuddiexp" title="Publishing Web services and business entities"/>
+ </entry>
+ <entry keyword="publishing to UDDI">
+ <topic href="tasks/tpubent.html#tpubent" title="Publishing a business entity"/>
+ </entry>
+ <entry keyword="updating in a UDDI registry">
+ <topic href="tasks/tupdate.html#tupdate" title="Updating a business entity, Web service, or service interface"/>
+ </entry>
+ <entry keyword="removing from a UDDI registry">
+ <topic href="tasks/tunpub.html#tunpub" title="Removing a business entity, Web service, or service interface from a registry"/>
+ </entry>
+ </entry>
+ <entry keyword="Web Services Explorer">
+ <entry keyword="publishing Web services">
+ <topic href="tasks/tuddiexp.html#tuddiexp" title="Publishing Web services and business entities"/>
+ </entry>
+ <entry keyword="launching">
+ <topic href="tasks/tstrtexp.html#tstrtexp" title="Launching the Web Services Explorer"/>
+ </entry>
+ <entry keyword="logging into a UDDI registry">
+ <topic href="tasks/tlogexp.html#tlogexp" title="Logging in to a UDDI registry"/>
+ </entry>
+ <entry keyword="adding a registry">
+ <topic href="tasks/taddreg.html#taddreg" title="Adding a Registry to the Web Services Explorer"/>
+ </entry>
+ </entry>
+ <entry keyword="registries">
+ <entry keyword="adding to the Web Services Explorer">
+ <topic href="tasks/taddreg.html#taddreg" title="Adding a Registry to the Web Services Explorer"/>
+ </entry>
+ </entry>
+ <entry keyword="data structure types">
+ <entry keyword="UDDI registry">
+ <topic href="ref/ruddi.html#ruddi" title="Data structure types (UDDI registry)"/>
+ </entry>
+ </entry>
+ <entry keyword="service interfaces">
+ <entry keyword="updating UDDI registries">
+ <topic href="tasks/tupdate.html#tupdate" title="Updating a business entity, Web service, or service interface"/>
+ </entry>
+ <entry keyword="removing from a UDDI registry">
+ <topic href="tasks/tunpub.html#tunpub" title="Removing a business entity, Web service, or service interface from a registry"/>
+ </entry>
+ </entry>
+ <entry keyword="Web Service Explorer">
+ <entry keyword="adding Favorites">
+ <topic href="tasks/tbkmrk.html#tbkmrk" title="Adding a registry, business entity, business service, service interface, WSIL, or WSDL service to Favorites"/>
+ </entry>
+ </entry>
+</index>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/plugin.properties b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/plugin.properties
new file mode 100644
index 0000000..2df4674
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/plugin.properties
@@ -0,0 +1,15 @@
+###############################################################################
+# Copyright (c) 2001, 2005 IBM Corporation and others.
+# All rights reserved. This program and the accompanying materials
+# are made available under the terms of the Eclipse Public License v1.0
+# which accompanies this distribution, and is available at
+# http://www.eclipse.org/legal/epl-v10.html
+#
+# Contributors:
+# IBM Corporation - initial API and implementation
+###############################################################################
+# NLS_MESSAGEFORMAT_VAR
+# NLS_ENCODING=UTF-8
+
+pluginName = Web service consumption documentation
+pluginProvider = Eclipse.org
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/plugin.xml b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/plugin.xml
new file mode 100644
index 0000000..d31fb14
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/plugin.xml
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?eclipse version="3.0"?>
+<?NLS TYPE="org.eclipse.help.toc"?>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2007 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * IBM Corporation - initial API and implementation
+ *******************************************************************************/ -->
+<plugin>
+
+ <extension point="org.eclipse.help.toc">
+ <toc file="wsconsumptionbuild_toc.xml"/>
+ <toc file="wsconsumptiont_toc.xml" />
+ <index path="index/"/>
+ </extension>
+ <extension point="org.eclipse.help.index">
+ <index file="org.eclipse.jst.ws.consumption.ui.doc.userindex.xml"/>
+</extension>
+</plugin>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/ref/ruddi.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/ref/ruddi.dita
new file mode 100644
index 0000000..e976fef
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/ref/ruddi.dita
@@ -0,0 +1,77 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>UDDI<indexterm>data structure types</indexterm></indexterm>
+<indexterm>data structure types<indexterm>UDDI registry</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<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>
+<link href="../tasks/tuddiexp.dita"></link>
+</linklist>
+</related-links>
+</reference>
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
new file mode 100644
index 0000000..c31c683
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/ref/ruddi.html
@@ -0,0 +1,112 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="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 content="UDDI, data structure types, UDDI registry" name="DC.subject" />
+<meta content="UDDI, data structure types, UDDI registry" name="keywords" />
+<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/common.css" type="text/css" rel="stylesheet" />
+<title>Data structure types (UDDI registry)</title>
+</head>
+<body id="ruddi"><a name="ruddi"><!-- --></a>
+
+
+<h1 class="topictitle1">Data structure types (UDDI registry)</h1>
+
+
+
+<div><p>Once you have registered and logged in to the UDDI registry that
+you want to use, you can register your Web service. Registration of a service
+involves four core data structure types: business information, service information,
+binding information, and information describing the specifications for services.
+The relationship between these data types is described in Figure 1.</p>
+
+<div class="section"><blockquote> <p> <span class="uicontrol">Business information.</span> Information
+that is contained in a <tt class="sysout">businessEntity</tt> structure.
+The <tt class="sysout">businessEntity</tt> contains information about
+the business that has published the service, such as business name, description,
+contacts and identifiers.</p>
+ <p> <span class="uicontrol">Service information.</span> Information
+that describes a group of Web services. It is contained in a <tt class="sysout">businessService</tt> structure.
+The <tt class="sysout">businessService</tt> contains information about
+families of technical services. It groups a set of Web services related
+to either a business process or group of services.</p>
+ <p> <span class="uicontrol">Binding
+information.</span> Information represented by the <tt class="sysout">bindingTemplate</tt> structure.
+The <tt class="sysout">bindingTemplate</tt> holds technical information
+for determining the entry point and construction specifications for invoking
+a Web service. The <tt class="sysout">bindingTemplate</tt> provides
+the Web service descriptions relevant for application developers that want
+to find and invoke a Web service. The <tt class="sysout">bindingTemplate</tt> points
+to a service implementation descriptions, for example via a URL.</p>
+ <p> <span class="uicontrol">Information
+describing the specifications for services.</span> Metadata about the
+various specifications implemented by a given Web service represented by the
+ <tt class="sysout">tModel</tt>. The <tt class="sysout">tModel</tt> provides
+a reference system to assist in the discovery of Web services.</p>
+ </blockquote>
+<p>Figure
+1. Relationship between data types.</p>
+<p> <img src="../images/uddi.gif" alt="Figure 1 illustrates the relationship between the business entity, business service, binding template, and tmodel." /> </p>
+<p>Each child structure has a unique
+parent structure. This means that each <tt class="sysout">businessService</tt> structure
+is owned by a specific <tt class="sysout">businessEntity</tt>. In turn,
+each <tt class="sysout">bindingTemplate</tt> is owned by a specific
+ <tt class="sysout">businessService</tt>. Each <tt class="sysout">bindingTemplate</tt> structure
+references to unique instances of <tt class="sysout">tModel</tt> structures;
+however, since references can be repeated within several parent structures,
+there can be many references to <tt class="sysout">tModels</tt> from
+different Entity-Service-Template parents, as seen in Figure 2.</p>
+<p>Figure
+2. References to tModel.</p>
+<p> <img src="../images/uddiref.gif" alt="Figure 2 illustrates the multiple references to a tModel." /> </p>
+</div>
+
+<div class="section"><h4 class="sectiontitle">Publisher assertions</h4><p>A publisher assertion is a
+way in UDDI to associate businessEntity structures. The publisher assertion
+defines a group of businessEntity structures. Many businesses are not effectively
+represented by a single businessEntity. A publisher assertion allows for the
+association between businessEntity structures. For example, a large company
+may have several subsidiaries that have different descriptions but are still
+closely coupled and want to make their relationships visible in UDDI registries.</p>
+</div>
+
+<div class="section"><h4 class="sectiontitle">Service projections</h4><p>A service projection enables
+a business entity to reference a service that was published by another business
+entity. By using the businessService structure as a projection to an already
+published businessService, businesses can share or reuse services. Service
+projections are managed centrally as part of the referencing businessEntity.
+This means that any changes made to the businessService by any of the referencing
+businessEntity structures are valid for all of the referencing businessEntity
+structures.</p>
+</div>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related Concepts</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div>
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div></div>
+
+<div class="linklist"><strong>Related Tasks</strong><br />
+
+<div><a href="../tasks/tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div></div>
+</div>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/taddreg.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/taddreg.dita
new file mode 100644
index 0000000..7015ecc
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/taddreg.dita
@@ -0,0 +1,78 @@
+<?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">
+<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>
+<prolog><metadata>
+<keywords><indexterm>Web services<indexterm>adding a registry to the Web Services
+Explorer</indexterm></indexterm><indexterm>Web Services Explorer<indexterm>adding
+a registry</indexterm></indexterm><indexterm>registries<indexterm>adding to
+the Web Services Explorer</indexterm></indexterm></keywords>
+</metadata></prolog>
+<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>
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
new file mode 100644
index 0000000..85b22d4
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/taddreg.html
@@ -0,0 +1,115 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="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 content="Web services, adding a registry to the Web Services Explorer, Web Services Explorer, adding a registry, registries, adding to the Web Services Explorer" name="DC.subject" />
+<meta content="Web services, adding a registry to the Web Services Explorer, Web Services Explorer, adding a registry, registries, adding to the Web Services Explorer" name="keywords" />
+<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/common.css" type="text/css" rel="stylesheet" />
+<title>Adding a Registry to the Web Services Explorer</title>
+</head>
+<body id="taddreg"><a name="taddreg"><!-- --></a>
+
+
+<h1 class="topictitle1">Adding a Registry to the Web Services Explorer</h1>
+
+
+
+
+<div><p>Although the Web Services Explorer comes populated with several
+registries, you can also add additional registries to your list of favorites.</p>
+
+<div class="p"><div class="p">Prerequisites:<ol>
+<li><a href="treg.html">Register with a registry</a></li>
+
+<li><a href="tstrtexp.html">Launch the Web Services Explorer</a></li>
+
+</ol>
+</div>
+</div>
+
+<div class="section"><p>When you are ready to publish your business entity and Web service,
+add a production registry to the Web Services Explorer. In order to publish
+your business entity and Web service to a production registry, you must first
+register with the registry. The registry will provide instructions for registering.
+For more information on registries, refer to <a href="treg.html">Registering with a registry</a>.</p>
+<p>The UDDI Business Registry is a set of global
+replicated registries. For a list of public registries refer to <a href="http://www.UDDI.org/register.html" target="_blank">www.uddi.org/register.html</a></p>
+<p>The IBM<sup>®</sup> UDDI Business
+Registry is a public production registry maintained by IBM. For more information on the IBM UDDI Business
+Registry refer to <a href="http://uddi.ibm.com" target="_blank">http://uddi.ibm.com</a></p>
+</div>
+
+<ol>
+<li><span>To add a Registry to the Web Services Explorer from Favorites,
+do the following:</span>
+<ol type="a">
+<li><span>Click the <span class="uicontrol">Favorites</span> icon <img src="../images/fav.gif" alt="Picture of the Favorites icon." /> in the main toolbar.</span></li>
+
+<li><span>Expand <span class="uicontrol">Favorite UDDI Registries</span>.</span>
+</li>
+
+<li><span>Select a registry then click the <span class="uicontrol">Add to UDDI Page</span> icon
+ <img src="../images/adduddi.gif" alt="Picture of the Add to UDDI Page icon." /> in the Actions pane.</span></li>
+
+</ol>
+
+</li>
+
+<li><span>To add a Registry to the Web Services Explorer manually, do the
+following:</span>
+<ol type="a">
+<li><span>In the UDDI Navigator pane, click the <span class="uicontrol">UDDI Main</span> node.</span>
+</li>
+
+<li><span>In the Actions pane, enter the Registry name and Inquiry URL
+of the registry you want to add.</span></li>
+
+<li><span>Click <span class="uicontrol">Go</span>.</span></li>
+
+</ol>
+
+</li>
+
+</ol>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related Concepts</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div>
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div>
+<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div>
+
+<div class="linklist"><strong>Related Tasks</strong><br />
+
+<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div>
+<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div>
+<div><a href="treg.html" title="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use.">Registering with a UDDI registry</a></div></div>
+
+<div class="linklist"><strong>Related Reference</strong><br />
+
+<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div>
+</div>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tassert.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tassert.dita
new file mode 100644
index 0000000..8498da7
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tassert.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="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>
+<prolog><metadata>
+<keywords><indexterm>UDDI<indexterm>managing publisher assertions</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<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>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>
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
new file mode 100644
index 0000000..301b176
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tassert.html
@@ -0,0 +1,99 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="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 content="UDDI, managing publisher assertions" name="DC.subject" />
+<meta content="UDDI, managing publisher assertions" name="keywords" />
+<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/common.css" type="text/css" rel="stylesheet" />
+<title>Managing publisher assertions</title>
+</head>
+<body id="tassert"><a name="tassert"><!-- --></a>
+
+
+<h1 class="topictitle1">Managing publisher assertions</h1>
+
+
+
+<div><p>A publisher assertion is a way in UDDI to associate businessEntity
+structures. The publisher assertion defines a group of businessEntity
+structures. Many businesses are not effectively represented by a single businessEntity.
+A publisher assertion allows for associations to be formed between several
+businessEntity structures. For example, a large company may have several subsidiaries
+that have different descriptions but are still closely coupled and want to
+make their relationships visible in UDDI registries.</p>
+
+<div class="p">Prerequisites:<ol>
+<li><a href="treg.html">Register with a registry</a></li>
+
+<li><a href="tstrtexp.html">Launch the Web Services Explorer</a></li>
+
+<li><a href="taddreg.html">Add the registry to the Web Services Explorer</a></li>
+
+</ol>
+</div>
+
+<div class="section"><p>For more information on publisher assertions, refer to the <a href="http://www.uddi.org/specification.html" target="_blank">UDDI Version 2.0 Programmer's API Specification</a> and the <a href="http://www.uddi.org/specification.html" target="_blank">UDDI Version 2.0 Data Structure Specification</a>.</p>
+<p>To
+manage publisher assertions, do the following:</p>
+</div>
+
+<ol>
+<li><span>In the Navigator pane, select the business entity for which you
+want to manage referenced businesses.</span></li>
+
+<li><span>In the Actions pane toolbar, click the <span class="uicontrol">Manage Publisher
+Assertions</span> icon <img src="../images/busasst.gif" alt="Picture of the Manage Publisher Assertions icon." />.</span></li>
+
+<li><span>On the Manage Publisher Assertions page you can add, remove, and
+maintain relationships with other business entities.</span></li>
+
+</ol>
+
+<div class="section"><p> <span class="uicontrol">Important:</span> A business entity that is referenced
+by another business entity must in turn reference that business entity in
+order to make the publisher assertion public. A one-way reference is considered
+an incomplete publisher assertion and is visible only to the owner of the
+business entity.</p>
+</div>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related Concepts</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div>
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div>
+<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div>
+
+<div class="linklist"><strong>Related Tasks</strong><br />
+
+<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div>
+<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div>
+<div><a href="treg.html" title="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use.">Registering with a UDDI registry</a></div></div>
+
+<div class="linklist"><strong>Related Reference</strong><br />
+
+<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div>
+</div>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbkmrk.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbkmrk.dita
new file mode 100644
index 0000000..e9dc690
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbkmrk.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="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>
+<shortdesc>You can add a registry, business entity, business service, service
+interface, WSIL, or WSDL service to the Web Service Explorer Favorites if
+you plan to access them in the future.</shortdesc>
+<prolog><metadata>
+<keywords><indexterm>Web Service Explorer<indexterm>adding Favorites</indexterm></indexterm>
+<indexterm>WSIL<indexterm>adding to Favorites</indexterm></indexterm><indexterm>WSDL<indexterm>adding
+to Favorites</indexterm></indexterm></keywords>
+</metadata></prolog>
+<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 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>
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
new file mode 100644
index 0000000..2746cf2
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbkmrk.html
@@ -0,0 +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">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="Adding a registry, business entity, business service, service interface, WSIL, or WSDL service to Favorites" />
+<meta name="abstract" content="You can add a registry, business entity, business service, service interface, WSIL, or WSDL service to the Web Service Explorer Favorites if you plan to access them in the future." />
+<meta name="description" content="You can add a registry, business entity, business service, service interface, WSIL, or WSDL service to the Web Service Explorer Favorites if you plan to access them in the future." />
+<meta content="Web Service Explorer, adding Favorites, WSIL, adding to Favorites, WSDL, adding to Favorites" name="DC.subject" />
+<meta content="Web Service Explorer, adding Favorites, WSIL, adding to Favorites, WSDL, adding to Favorites" name="keywords" />
+<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/common.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><p>You can add a registry, business entity, business service, service
+interface, WSIL, or WSDL service to the Web Service Explorer Favorites if
+you plan to access them in the future.</p>
+
+<div class="p">Prerequisite: <ul>
+<li><a href="tstrtexp.html">Launch the Web Services Explorer</a></li>
+
+</ul>
+</div>
+
+<div class="section"><p>To add a registry, business entity, Web service, service interface,
+WSIL, or WSDL to Favorites using the Web Services Explorer:</p>
+</div>
+
+<ol>
+<li><span>Navigate through the registry hierarchy to find the registry, business
+entity, Web service, service interface or the WSIL page to find the WSIL or
+WSDL service you want to add to Favorites.</span></li>
+
+<li><span>Select the business entity, Web service, service interface, WSIL,
+or WSDL service.</span></li>
+
+<li><span>In the Actions icon bar, click the <span class="uicontrol">Add to favorites</span> icon
+ <img src="../images/addfav.gif" alt="Picture of the Add to favorites icon." />.</span></li>
+
+</ol>
+
+<div class="section"><p>Any favorites that you add are saved by the Web Services Explorer
+to </p>
+<p> <var class="varname">X</var>:\workspace\.metadata\.plugins\com.ibm.etools.webservice.explorer\favorites.wsil</p>
+<p>Where
+ <var class="varname">X</var> is the directory where your workspace folder is located.
+If you are migrating from an earlier version of the product, your favorites
+will be automatically migrated to this location.</p>
+</div>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related Concepts</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div>
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div>
+<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div>
+
+<div class="linklist"><strong>Related Tasks</strong><br />
+
+<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div>
+<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div>
+<div><a href="treg.html" title="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use.">Registering with a UDDI registry</a></div></div>
+
+<div class="linklist"><strong>Related Reference</strong><br />
+
+<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div>
+</div>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbusproj.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbusproj.dita
new file mode 100644
index 0000000..94c5d55
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbusproj.dita
@@ -0,0 +1,54 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>Web services<indexterm>managing services</indexterm></indexterm>
+<indexterm>UDDI<indexterm>managing services</indexterm></indexterm></keywords>
+</metadata></prolog>
+<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>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>
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
new file mode 100644
index 0000000..72240e3
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbusproj.html
@@ -0,0 +1,90 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="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 content="Web services, managing services, UDDI" name="DC.subject" />
+<meta content="Web services, managing services, UDDI" name="keywords" />
+<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/common.css" type="text/css" rel="stylesheet" />
+<title>Managing referenced services</title>
+</head>
+<body id="tbusproj"><a name="tbusproj"><!-- --></a>
+
+
+<h1 class="topictitle1">Managing referenced services</h1>
+
+
+
+<div><p>A service projection enables a business entity to reference a service
+that was published by another business entity. By using the businessService
+structure as a projection to an already published businessService, businesses
+can share or reuse services. Service projections are managed centrally
+as part of the referencing businessEntity.</p>
+
+<div class="p">Prerequisites:<ol>
+<li><a href="treg.html">Register with a registry</a></li>
+
+<li><a href="tstrtexp.html">Launch the Web Services Explorer</a></li>
+
+<li><a href="taddreg.html">Add the registry to the Web Services Explorer</a></li>
+
+</ol>
+</div>
+
+<div class="section"><p>For more information on referenced services, refer to the <a href="http://www.uddi.org/specification.html" target="_blank">UDDI Version 2.0 Programmer's API Specification</a> and the <a href="http://www.uddi.org/specification.html" target="_blank">UDDI Version 2.0 Data Structure Specification</a>.</p>
+<p>To
+manage referenced services, do the following:</p>
+</div>
+
+<ol>
+<li><span>In the Navigator pane, select the business entity for which you
+want to manage referenced services.</span></li>
+
+<li><span>In the Actions pane toolbar, click the <span class="uicontrol">Manage Referenced
+Services</span> icon <img src="../images/refserv.gif" alt="Picture of the Manage Referenced Services icon." />.</span></li>
+
+<li><span>On the Manage Referenced Services page you can add, remove, and
+maintain services that are referenced by the business entity.</span></li>
+
+</ol>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related Concepts</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div>
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div>
+<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div>
+
+<div class="linklist"><strong>Related Tasks</strong><br />
+
+<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div>
+<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div>
+<div><a href="treg.html" title="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use.">Registering with a UDDI registry</a></div></div>
+
+<div class="linklist"><strong>Related Reference</strong><br />
+
+<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div>
+</div>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tdiscov.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tdiscov.dita
new file mode 100644
index 0000000..2959f7f
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tdiscov.dita
@@ -0,0 +1,177 @@
+<?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,
+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>
+<prolog><metadata>
+<keywords><indexterm>Web services<indexterm>discovering</indexterm></indexterm>
+<indexterm>UDDI<indexterm>discovering Web services</indexterm></indexterm>
+<indexterm>WSIL<indexterm>discovering Web services</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<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>.
+ .</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
new file mode 100644
index 0000000..8d61ebb
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tdiscov.html
@@ -0,0 +1,275 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="Discovering Web Services" />
+<meta name="abstract" content="Web services can be located through a public 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, 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="Web services, discovering, UDDI, discovering Web services, WSIL" name="DC.subject" />
+<meta content="Web services, discovering, UDDI, discovering Web services, WSIL" name="keywords" />
+<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/common.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,
+a private business registry, or a WSIL document. UDDI manages the discovery
+of Web services by relying on a distributed registry of businesses and their
+service descriptions implemented in a common XML format.</p>
+
+<div class="p"><div class="p">Prerequisites:<ol>
+<li><a href="treg.html">Register with a registry</a></li>
+
+<li><a href="tstrtexp.html">Launch the Web Services Explorer</a></li>
+
+<li><a href="taddreg.html">Add the registry to the Web Services Explorer</a></li>
+
+</ol>
+</div>
+</div>
+
+<div class="section"><p>Web Services Inspection Language (WSIL) is a service discovery
+mechanism that is an alternative to UDDI as well as complementary to UDDI.
+WSIL allows you to go directly to the service provider and ask for the services
+it provides. For more information on the Web Services Inspection Language
+specification, refer to <a href="http://www-106.ibm.com/developerworks/webservices/library/ws-wsilspec.html" target="_blank">www.ibm.com/developerworks/webservices/library/ws-wsilspec.html</a>.
+ .</p>
+<p>You can discover a Web service in two ways using the Web Services
+Explorer:</p>
+</div>
+
+<div class="section"><ul>
+<li> <a href="#tdiscov__discover_from_uddi">Discovering a Web service from a UDDI registry</a> </li>
+
+<li> <a href="#tdiscov__discover_from_wsil">Discovering a Web service from a WSIL document</a> </li>
+
+</ul>
+</div>
+
+</div>
+
+<div class="nested1" xml:lang="en-us" id="discover_from_uddi"><a name="discover_from_uddi"><!-- --></a>
+<h2 class="topictitle2"> Discovering a Web Service from a UDDI Registry</h2>
+
+<div>
+<div class="section"><p>The registry contains URL references to Web service WSDL documents.
+In order to discover a Web service the URL to the Web service WSDL document
+must be resolvable. To locate Web service descriptions:</p>
+</div>
+
+<ol>
+<li><span>Launch the Web Services Explorer</span></li>
+
+<li><span>Click <span class="uicontrol">UDDI Main</span>.</span></li>
+
+<li><span>In the Actions pane select a registry from the drop-down list and
+click <span class="uicontrol">Go</span>.</span></li>
+
+<li><span>In the Actions pane toolbar click the <strong>Find</strong> icon <img src="../images/find.gif" alt="A picture of the Find icon." />.</span>
+</li>
+
+<li><span>In the Actions pane, enter the name of the query, what you are
+searching for, the type of search that you want to perform, and any query
+information: </span>
+<ol type="a">
+<li class="substepexpand"><span> <strong>Search for</strong> This list allows you to search for
+businesses, services, or service interfaces. </span> <ul>
+<li> <strong>Businesses</strong> Once you locate a business in the registry, use the
+icons in the Action pane toolbar to do the following:<ul>
+<li>View and edit business details</li>
+
+<li>Get the services associated with that business</li>
+
+<li>Publish a service</li>
+
+<li>Manage referenced services</li>
+
+<li>Manage publisher assertions</li>
+
+<li>Add the business to Favorites</li>
+
+<li>Unpublish the business</li>
+
+</ul>
+</li>
+
+<li> <strong>Services</strong> Once you locate a service in the registry, use the icons
+in the Action pane toolbar to do the following: <ul>
+<li>View and edit service details</li>
+
+<li>Get the business associated with that service</li>
+
+<li>Get the service interfaces associated with that service</li>
+
+<li>Import the service WSDL file to the Eclipse workbench</li>
+
+<li>Import the service WSDL file to the file system</li>
+
+<li>Launch the Web Service wizards</li>
+
+<li>Add the service to Favorites</li>
+
+<li>Unpublish the service</li>
+
+</ul>
+</li>
+
+<li> <strong>Service interfaces</strong> Once you locate a service interface in the
+registry, use the icons in the Action pane toolbar to do the following: <ul>
+<li>View and edit interface details</li>
+
+<li>Get the services associated with that service interface</li>
+
+<li>Get the businesses associated with that service interface</li>
+
+<li>Import the service interface WSDL file to the Eclipse workbench</li>
+
+<li>Import the service interface WSDL file to the file system</li>
+
+<li>Launch the Web Service wizards</li>
+
+<li>Add the service interface to Favorites</li>
+
+<li>Unpublish the service interface</li>
+
+</ul>
+</li>
+
+</ul>
+</li>
+
+<li class="substepexpand"><span> <strong>Type of search</strong> These radio buttons allow you to
+specify a simple or advanced search, or a search by a Universal Unique Identifier
+(UUID). </span> <dl>
+<dt class="dlterm">Simple</dt>
+
+<dd>Type the name of the businesses, services, or service interfaces for which
+you are searching. <strong>Note:</strong> The search set size is set to 100 and the
+maximum number of returned results is set to 10 by default. If you would
+like to override the defaults, use the Advanced search.</dd>
+
+
+<dt class="dlterm">Advanced </dt>
+
+<dd>Allows you to enter more search options to focus the scope of your search.
+Select this option if you would like to search for multiple businesses or
+services.</dd>
+
+
+<dt class="dlterm">UUID </dt>
+
+<dd>Allow you to enter the UUID key. The UUID key is the identifier that is
+associated with the published object.</dd>
+
+</dl>
+</li>
+
+</ol>
+
+</li>
+
+<li><span>Once you have searched and discovered the business service description
+you desired, select the service or the service interface and click the <strong>Import</strong> icon
+to: </span>
+<ul>
+<li>import the WSDL document into your Web project</li>
+
+<li>import the WSDL document into the WSDL Explorer for testing</li>
+
+<li>launch the Web Service Skeleton Creation wizard or Web Service Client
+wizard directly from the Web Services Explorer.</li>
+
+</ul>
+
+</li>
+
+</ol>
+
+</div>
+
+</div>
+
+<div class="nested1" xml:lang="en-us" id="discover_from_wsil"><a name="discover_from_wsil"><!-- --></a>
+<h2 class="topictitle2"> Discovering a Web Service from a WSIL Document</h2>
+
+<div>
+<div class="section"><p>To locate Web service descriptions:</p>
+</div>
+
+<ol>
+<li class="stepexpand"><span>From the Web Services Explorer toolbar, click the <strong>WSIL Page</strong> icon
+ <img src="../images/wsilview.gif" alt="Picture of the WSIL Page icon." />.</span></li>
+
+<li class="stepexpand"><span>In the Navigator pane, click <strong>WSIL Main</strong>.</span></li>
+
+<li class="stepexpand"><span>In the <strong>URL to document</strong> field of the Actions pane enter
+the URL to the WSIL document or HTTP document that contains links to a WSIL
+document. Details on how an HTTP file can contain links to WSIL can be found
+here: http://www.ibm.com/developerworks/webservices/library/ws-wsilspec.html</span>
+</li>
+
+<li class="stepexpand"><span>Once you have located the WSIL document, use the icons in the Action
+pane toolbar to do the following:</span>
+<ul>
+<li>View WSIL document details</li>
+
+<li>List all of the WSDL services associated with that WSIL document</li>
+
+<li>List all of the UDDI services associated with that WSIL document</li>
+
+<li>List all of the UDDI businesses associated with that WSIL document</li>
+
+<li>List all of the WSIL links associated with that WSIL document</li>
+
+<li>Import the WSIL document to the file system</li>
+
+<li>Add the WSIL document to Favorites</li>
+
+</ul>
+
+ <strong>Important:</strong> If the Web Services Explorer does not display the
+project that you would like to import your WSDL file to, ensure that you have
+created the project and/or click the <strong>Refresh</strong> icon.</li>
+
+</ol>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related Concepts</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div>
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div>
+<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div>
+
+<div class="linklist"><strong>Related Tasks</strong><br />
+
+<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div>
+<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div>
+<div><a href="treg.html" title="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use.">Registering with a UDDI registry</a></div>
+<div><a href="../../org.eclipse.jst.ws.doc.user/tasks/toverws.html"> Developing Web services</a></div></div>
+
+<div class="linklist"><strong>Related Reference</strong><br />
+
+<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div>
+</div>
+</div>
+
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tgenwsil.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tgenwsil.dita
new file mode 100644
index 0000000..a9d32f9
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tgenwsil.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="tgenwsil" xml:lang="en-us">
+<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>
+<prolog><metadata>
+<keywords><indexterm>Web services<indexterm>generating WSIL</indexterm></indexterm>
+<indexterm>WSIL<indexterm>generating</indexterm></indexterm></keywords>
+</metadata></prolog>
+<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>
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
new file mode 100644
index 0000000..ab114a4
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tgenwsil.html
@@ -0,0 +1,115 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" />
+<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="Web services, generating WSIL, WSIL, generating" name="DC.subject" />
+<meta content="Web services, generating WSIL, WSIL, generating" name="keywords" />
+<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/common.css" type="text/css" rel="stylesheet" />
+<title>Generating a WSIL file</title>
+</head>
+<body id="tgenwsil"><a name="tgenwsil"><!-- --></a>
+
+
+<h1 class="topictitle1">Generating a WSIL file</h1>
+
+
+
+
+<div><p>Web Services Inspection Language (WSIL) is a service discovery
+mechanism that is an alternative to UDDI as well as complementary to UDDI.
+WSIL can be generated at any point in the Web service development cycle once
+the WSDL file for the Web service has been created.</p>
+
+<div class="p"><strong>Prerequisites:</strong> In order to generate a WSIL file, you need to
+know the URL to a WSDL file.</div>
+
+<div class="section"><p>WSIL helps synchronize this process by maintaining references
+to WSDL URLs. Web services tools that process WSDL documents - such as the
+Web Service Client and Creation wizards - will accept a WSIL document as a
+substitute for WSDL. This allows you to create a standardized WSDL reference
+(WSIL) document in your project during Web service client generation, then
+at a later time easily regenerate the client from that reference document.
+No copies of the WSDL or WSDL URLs are required.</p>
+<p>You can generate a
+WSIL file from a pre-existing WSDL file or during Web service creation or
+consumption.</p>
+</div>
+
+</div>
+
+<div class="nested1" xml:lang="en-us" id="d0e27"><a name="d0e27"><!-- --></a>
+<h2 class="topictitle2">Generating a WSIL file though the import utility</h2>
+
+<div>
+<div class="section"><p>To generate a WSIL file through the import utility:</p>
+</div>
+
+<ol>
+<li><span>Optional: Select the WSDL document for which you want to create
+a WSIL file.</span></li>
+
+<li><span>From the <strong>File</strong> menu, select <strong>Import</strong> > <strong>WSIL >
+Next</strong>. The WSIL Import window opens.</span></li>
+
+<li><span>If you have selected to perform step 1, the WSIL URI field should
+be prefilled with the name of your WSDL file, where the extension has been
+changed from <tt class="sysout">.wsdl</tt> to <tt class="sysout">.wsil</tt>.
+The WSDL section should contain the URLs to the selected WSDL files. You can
+also enter additional WSDL URLs. Alternately, you can browse to the location
+of a WSIL file, or manually enter the location of the WSIL and WSDL files
+in the appropriate locations.</span></li>
+
+<li><span>Click Finish. A WSIL file will be generated in the specified location.</span>
+</li>
+
+</ol>
+
+</div>
+
+</div>
+
+<div class="nested1" xml:lang="en-us" id="d0e62"><a name="d0e62"><!-- --></a>
+<h2 class="topictitle2">Generating a WSIL file through the Web Services Explorer</h2>
+
+<div>
+<div class="section"><p>To generate a WSIL file through the Web Services Explorer:</p>
+</div>
+
+<ol>
+<li><span>Open the Web Services Explorer.</span></li>
+
+<li><span>Open the WSDL Explorer by clicking this icon: <img src="../images/wsdlicon.gif" alt="icon used to launch the web services explorer" /></span></li>
+
+<li><span>Open a WSDL file.</span></li>
+
+<li><span>Select the WSDL file that you have opened in the Navigator pane,
+and from the available actions, choose to import a WSDL file to the workbench
+by clicking this icon: <img src="../images/mptwsdlicon.gif" alt="icon used to import a file" /></span></li>
+
+<li><span>Select <strong>Import as a service reference to a WSIL document</strong>.</span>
+</li>
+
+<li><span>Enter a name for the WSIL file that you want to generate, and click
+ <strong>Go</strong>.</span></li>
+
+</ol>
+
+</div>
+
+</div>
+
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tlogexp.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tlogexp.dita
new file mode 100644
index 0000000..dd0f0e7
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tlogexp.dita
@@ -0,0 +1,55 @@
+<?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="tlogexp" xml:lang="en-us">
+<title>Logging in to a UDDI registry</title>
+<shortdesc>If you have published your Web service to a UDDI registry you can
+log into the registry and manage the service through the Web Services Explorer.</shortdesc>
+<prolog><metadata>
+<keywords><indexterm>UDDI<indexterm>logging into a registry</indexterm></indexterm>
+<indexterm>Web Services Explorer<indexterm>logging into a UDDI registry</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<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>Once you have selected a registry, you can scroll to the <uicontrol>Other
+Actions</uicontrol> section of the page and select <uicontrol>Login</uicontrol>,
+or use the login button at the top of the Explorer: <image href="../images/loginicon.gif">
+<alt>screen capture of the login icon</alt></image>.</cmd></step>
+<step><cmd>Enter the URL (if it has not been prefilled for you), the user
+ID, and the password for the registry and click <uicontrol>Go</uicontrol>.</cmd>
+</step>
+<step><cmd>The Summary of Business page displays. It lists all the businesses
+associated with the registry.</cmd></step>
+</steps>
+<result><p>When you have successfully logged in, the Status pane displays
+a message indicating you were successful.</p></result>
+<postreq>To log out of the registry click the Logout button: <image href="../images/logouticon.gif">
+<alt>screen capture of the logout icon</alt></image>.</postreq>
+</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" scope="peer">
+<linktext> Developing Web services</linktext></link>
+</linklist>
+<linklist><title>Related Reference</title>
+<link href="../ref/ruddi.dita"></link>
+</linklist>
+</related-links>
+</task>
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tlogexp.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tlogexp.html
new file mode 100644
index 0000000..806ed3f
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tlogexp.html
@@ -0,0 +1,93 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="Logging in to a UDDI registry" />
+<meta name="abstract" content="If you have published your Web service to a UDDI registry you can log into the registry and manage the service through the Web Services Explorer." />
+<meta name="description" content="If you have published your Web service to a UDDI registry you can log into the registry and manage the service through the Web Services Explorer." />
+<meta content="UDDI, logging into a registry, Web Services Explorer, logging into a UDDI registry" name="DC.subject" />
+<meta content="UDDI, logging into a registry, Web Services Explorer, logging into a UDDI registry" name="keywords" />
+<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="../../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="tlogexp" name="DC.Identifier" />
+<meta content="en-us" name="DC.Language" />
+<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
+<title>Logging in to a UDDI registry</title>
+</head>
+<body id="tlogexp"><a name="tlogexp"><!-- --></a>
+
+
+<h1 class="topictitle1">Logging in to a UDDI registry</h1>
+
+
+
+<div><p>If you have published your Web service to a UDDI registry you can
+log into the registry and manage the service through the Web Services Explorer.</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 class="section"><p>To Log in to the registry:</p>
+</div>
+
+<ol>
+<li><span>Once you have selected a registry, you can scroll to the <span class="uicontrol">Other
+Actions</span> section of the page and select <span class="uicontrol">Login</span>,
+or use the login button at the top of the Explorer: <img src="../images/loginicon.gif" alt="screen capture of the login icon" />.</span></li>
+
+<li><span>Enter the URL (if it has not been prefilled for you), the user
+ID, and the password for the registry and click <span class="uicontrol">Go</span>.</span>
+</li>
+
+<li><span>The Summary of Business page displays. It lists all the businesses
+associated with the registry.</span></li>
+
+</ol>
+
+<div class="section"><p>When you have successfully logged in, the Status pane displays
+a message indicating you were successful.</p>
+</div>
+
+<div class="section">To log out of the registry click the Logout button: <img src="../images/logouticon.gif" alt="screen capture of the logout icon" />.</div>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related Concepts</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div>
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div>
+<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div>
+
+<div class="linklist"><strong>Related Tasks</strong><br />
+
+<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div>
+<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div>
+<div><a href="treg.html" title="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use.">Registering with a UDDI registry</a></div>
+<div><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/tpubent.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpubent.dita
new file mode 100644
index 0000000..30afdc1
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpubent.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="tpubent" xml:lang="en-us">
+<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>
+<prolog><metadata>
+<keywords><indexterm>UDDI<indexterm>publishing a business entity</indexterm></indexterm>
+<indexterm>Web services<indexterm>publishing a business entity</indexterm></indexterm>
+<indexterm>business entities<indexterm>publishing to UDDI</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<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>
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
new file mode 100644
index 0000000..63a5ba1
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpubent.html
@@ -0,0 +1,160 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="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="UDDI, publishing a business entity, Web services, business entities, publishing to UDDI" name="DC.subject" />
+<meta content="UDDI, publishing a business entity, Web services, business entities, publishing to UDDI" name="keywords" />
+<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/common.css" type="text/css" rel="stylesheet" />
+<title>Publishing a business entity</title>
+</head>
+<body id="tpubent"><a name="tpubent"><!-- --></a>
+
+
+<h1 class="topictitle1">Publishing a business entity</h1>
+
+
+
+<div><p>A business entity contains information about the business that
+has published a service. Before you can publish a business service,
+you must publish a business entity.</p>
+
+<div class="p">Prerequisites:<ol>
+<li><a href="treg.html">Register with a registry</a></li>
+
+<li><a href="tstrtexp.html">Launch the Web Services Explorer</a></li>
+
+<li><a href="taddreg.html">Add the registry to the Web Services Explorer</a></li>
+
+</ol>
+</div>
+
+<div class="section"><p>You can publish a business entity using two different publication
+formats: simple and advanced.</p>
+<blockquote> <p> <span class="uicontrol">Simple</span> Allows
+you to enter the minimal amount of information required to publish your business
+entity. A simple publish only allows you to specify only one name and
+one business description.</p>
+<p> <span class="uicontrol">Advanced </span> Allows you
+to enter more information about your business entity. An advanced publish
+allows you to specify multiple names and descriptions for multi-lingual support.</p>
+ </blockquote>
+</div>
+
+</div>
+
+<div class="nested1" xml:lang="en-us" id="d0e74"><a name="d0e74"><!-- --></a>
+<h2 class="topictitle2">Publish a business entity using the simple option</h2>
+
+<div>
+<div class="section"><p>To publish a business entity using the simple option:</p>
+</div>
+
+<ol>
+<li><span>In the Web Services Explorer, select UDDI Main and select the registry
+to which you want to publish the business entity.</span></li>
+
+<li><span>In the Navigator pane, select the business entity for which
+you want to publish the business service.</span></li>
+
+<li><span>In the Actions pane toolbar, click the <strong>Publish</strong> icon <img src="../images/publish2.gif" alt="Picture of the Publish icon." />.</span>
+</li>
+
+<li><span>Select the <strong>Simple</strong> radio button.</span></li>
+
+<li><span>Enter the publish URL, your user ID, password, WSDL URL, business
+name, and business description in the respective fields.</span></li>
+
+<li><span>Click <strong>Go</strong> to publish your business entity.</span></li>
+
+</ol>
+
+<div class="section"><p>The IBM<sup>®</sup> Web
+Services Explorer is automatically updated with your published Web service.
+The registry contains pointers to the URL of the WSDL service document of
+the Web service. Businesses can now discover and integrate with your Web service.</p>
+</div>
+
+</div>
+
+</div>
+
+<div class="nested1" xml:lang="en-us" id="d0e113"><a name="d0e113"><!-- --></a>
+<h2 class="topictitle2">Publish a business entity using the advanced option</h2>
+
+<div>
+<div class="section"><p>To publish a business entity using the advanced option:</p>
+</div>
+
+<ol>
+<li><span>In the Web Services Explorer Navigator pane, select the business
+entity for which you want to publish the business service.</span></li>
+
+<li><span>In the Actions pane toolbar, click the <strong>Publish Service</strong> icon
+ <img src="../images/pubserv.gif" alt="Picture of the Publish Service icon." />.</span></li>
+
+<li><span>Select the <strong>Advanced</strong> radio button.</span></li>
+
+<li><span>Enter the publish URL, your user ID, password, and WSDL URL in
+the respective fields.</span></li>
+
+<li><span>Click <strong>Add</strong> to create business names.</span></li>
+
+<li><span>Click <strong>Add</strong> to create business descriptions.</span></li>
+
+<li><span>Click <span class="uicontrol">Add</span> to create an identifier. For example,
+an identifier for your business entity may be your business phone number.
+The key name would be "Phone Number" and the key value would be your business
+telephone number. </span></li>
+
+<li><span>Click <strong>Add</strong> to create categories. Enter your business categories.
+Select a category type from the drop down list. Click <strong>Browse</strong> to open
+the Categories pane. Navigate through the hierarchical taxonomy and select
+the appropriate classification for your business service, then exit the Categories
+pane.</span></li>
+
+<li><span>Click <strong>Go</strong> to publish your business entity.</span></li>
+
+</ol>
+
+<div class="section"><p>The Web Services Explorer is automatically updated with your published
+Web service. The registry contains pointers to the URL of the WSDL service
+document of the Web service. Businesses can now discover and integrate with
+your Web service.</p>
+</div>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related Concepts</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div>
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div>
+<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div>
+
+<div class="linklist"><strong>Related Tasks</strong><br />
+
+<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div>
+<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div>
+<div><a href="treg.html" title="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use.">Registering with a UDDI registry</a></div></div>
+
+<div class="linklist"><strong>Related Reference</strong><br />
+
+<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div>
+</div>
+</div>
+
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpublish.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpublish.dita
new file mode 100644
index 0000000..9eb0419
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpublish.dita
@@ -0,0 +1,107 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>UDDI<indexterm>publishing a Web service</indexterm></indexterm>
+<indexterm>Web services<indexterm>publishing to a UDDI registry</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<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 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>
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
new file mode 100644
index 0000000..086cfb5
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpublish.html
@@ -0,0 +1,166 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="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="UDDI, publishing a Web service, Web services, publishing to a UDDI registry" name="DC.subject" />
+<meta content="UDDI, publishing a Web service, Web services, publishing to a UDDI registry" name="keywords" />
+<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/common.css" type="text/css" rel="stylesheet" />
+<title>Publishing a Web service</title>
+</head>
+<body id="tpublish"><a name="tpublish"><!-- --></a>
+
+
+<h1 class="topictitle1">Publishing a Web service</h1>
+
+
+
+
+<div><p>The Web service, also known as the business service, describes
+a Web service's endpoint and where its WSDL file resides. The WSDL file lists
+the operations that service provides.</p>
+
+<div class="p">Prerequisites:<ol>
+<li> <a href="treg.html">Register with a registry</a>.</li>
+
+<li> <a href="tstrtexp.html">Launch the Web Services Explorer</a>.</li>
+
+<li> <a href="taddreg.html">Add the registry to the Web Services Explorer</a>.</li>
+
+<li>Create a Web service.</li>
+
+<li>Deploy the Web service.</li>
+
+<li> <a href="tpubent.html">Publish a Business Entity</a>.</li>
+
+</ol>
+</div>
+
+<div class="section"><p>You can publish a business service using two different publication
+formats: simple and advanced.</p>
+</div>
+
+</div>
+
+<div class="nested1" xml:lang="en-us" id="d0e74"><a name="d0e74"><!-- --></a>
+<h2 class="topictitle2">Publish a business service using the simple option</h2>
+
+<div>
+<div class="section"><p>To publish a Web service using the simple option:</p>
+</div>
+
+<ol>
+<li><span>In the Web Services Explorer Navigator pane, select the business
+entity for which you want to publish the business service.</span></li>
+
+<li><span>In the Actions pane toolbar, click the <strong>Publish Service</strong> icon
+ <img src="../images/pubserv.gif" alt="Picture of the Publish Service icon." />.</span></li>
+
+<li><span>Select the <strong>Simple</strong> radio button.</span></li>
+
+<li><span>Enter the publish URL, your user ID, password, WSDL URL, business
+name, and business description in the respective fields.</span></li>
+
+<li><span>Click <strong>Go</strong> to publish your business entity.</span></li>
+
+</ol>
+
+<div class="section"><p> <strong>Important:</strong> Ensure that you select the service document,
+since the service element is the basis for the Business Service that you will
+publish. You cannot publish a Business Service using a WSDL document that
+does not have service elements.</p>
+<p>The Web Services Explorer is automatically
+updated with your published Web service. The registry contains pointers to
+the URL of the WSDL service document of the Web service. Businesses can now
+discover and integrate with your Web service.</p>
+</div>
+
+</div>
+
+</div>
+
+<div class="nested1" xml:lang="en-us" id="d0e113"><a name="d0e113"><!-- --></a>
+<h2 class="topictitle2">Publish a business service using the advanced option</h2>
+
+<div>
+<div class="section"><p>To publish a Web service using the advanced option:</p>
+</div>
+
+<ol>
+<li><span>In the Web Services Explorer Navigator pane, select the business
+entity for which you want to publish the business service.</span></li>
+
+<li><span>In the Actions pane toolbar, click the <strong>Publish Service</strong> icon
+ <img src="../images/pubserv.gif" alt="Picture of the Publish Service icon." />.</span></li>
+
+<li><span>Select the <strong>Advanced</strong> radio button.</span></li>
+
+<li><span>Enter the publish URL, your user ID, password, and WSDL URL in
+the respective fields.</span></li>
+
+<li><span>Click <strong>Get</strong> or <span class="uicontrol">Find</span> to associate the
+service with a business entity.</span></li>
+
+<li><span>Click <strong>Get</strong> or <span class="uicontrol">Find</span> to associate a
+specific service interface with the service.</span></li>
+
+<li><span>Click <strong>Add</strong> to create business service names.</span></li>
+
+<li><span>Click <strong>Add</strong> to create business service descriptions.</span>
+</li>
+
+<li><span>Click <strong>Add</strong> to create categories. Enter your business service
+categories. Select a category type from the drop down list. Click <strong>Browse</strong> to
+open the Categories pane. Navigate through the hierarchical taxonomy
+and select the appropriate classification for your business service, then
+exit the Categories pane.</span></li>
+
+<li><span>Click <strong>Go</strong> to publish your business entity.</span></li>
+
+</ol>
+
+<div class="section"><p> <strong>Important:</strong> Ensure that you select the service document,
+since the service element is the basis for the Business Service that you will
+publish. You cannot publish a Business Service using a WSDL document
+that does not have service elements.</p>
+<p>The Web Services Explorer is automatically
+updated with your published Web service. The registry contains pointers to
+the URL of the WSDL service document of the Web service. Businesses can now
+discover and integrate with your Web service.</p>
+</div>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related Concepts</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div>
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div>
+<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div>
+
+<div class="linklist"><strong>Related Tasks</strong><br />
+
+<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div>
+<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div>
+<div><a href="treg.html" title="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use.">Registering with a UDDI registry</a></div></div>
+
+<div class="linklist"><strong>Related Reference</strong><br />
+
+<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div>
+</div>
+</div>
+
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/treg.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/treg.dita
new file mode 100644
index 0000000..0fb6abd
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/treg.dita
@@ -0,0 +1,54 @@
+<?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">
+<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>
+<prolog><metadata>
+<keywords><indexterm>UDDI<indexterm>registering with a registry</indexterm></indexterm>
+<indexterm>Web services<indexterm>registering with a UDDI registry</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<taskbody>
+<context><p>There are many different private registries with which you can
+register. 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>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. The details page of each registry will
+have registration instructions.</p><p>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>
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
new file mode 100644
index 0000000..827a0d5
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/treg.html
@@ -0,0 +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 lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="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 content="UDDI, registering with a registry, Web services, registering with a UDDI registry" name="DC.subject" />
+<meta content="UDDI, registering with a registry, Web services, registering with a UDDI registry" name="keywords" />
+<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/common.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 private registries with which you can
+register. 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>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. The details page of each registry will
+have registration instructions.</p>
+<p>The public production registries are
+listed under Favorites. The Web Services Explorer does not preload any registries
+by default. You can preload registries from the favorites section of
+the Web Services Explorer or by using the Unit Test UDDI wizard. You can also
+preload and configure private registries using the Unit Test UDDI wizard.
+On the Open Registry page of the Web Services Explorer, you can select from
+public registries and registries listed in your favorites to automatically
+fill in the information required to open a particular registry.</p>
+</div>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related Concepts</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div>
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div>
+<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div>
+
+<div class="linklist"><strong>Related Tasks</strong><br />
+
+<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div>
+<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div></div>
+
+<div class="linklist"><strong>Related Reference</strong><br />
+
+<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div>
+</div>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tstrtexp.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tstrtexp.dita
new file mode 100644
index 0000000..7edc104
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tstrtexp.dita
@@ -0,0 +1,119 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>Web Services Explorer<indexterm>launching</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<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 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>
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
new file mode 100644
index 0000000..11b0239
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tstrtexp.html
@@ -0,0 +1,186 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="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="Web Services Explorer, launching" name="DC.subject" />
+<meta content="Web Services Explorer, launching" name="keywords" />
+<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/common.css" type="text/css" rel="stylesheet" />
+<title>Launching the Web Services Explorer</title>
+</head>
+<body id="tstrtexp"><a name="tstrtexp"><!-- --></a>
+
+
+<h1 class="topictitle1">Launching the Web Services Explorer</h1>
+
+
+
+
+<div><p>The Web services tools allows you to launch the Web Services Explorer
+in several ways.</p>
+
+<div class="section"><ul>
+<li>From the main toolbar in the J2EE perspective.</li>
+
+<li>By using the Web service wizards.</li>
+
+<li>By using the Import wizard.</li>
+
+<li>By using the Export wizard.</li>
+
+<li>From the Run menu in the J2EE perspective.</li>
+
+<li>From a WSDL file.</li>
+
+</ul>
+</div>
+
+</div>
+
+<div class="nested1" xml:lang="en-us" id="d0e38"><a name="d0e38"><!-- --></a>
+<h2 class="topictitle2">Launching the Web Services Explorer from the main toolbar</h2>
+
+<div>
+<div class="section"><p>To launch the Web Services Explorer from the main toolbar, ensure
+that you are in the J2EE perspective and click the <strong>Launch the Web Services
+Explorer</strong> icon <img src="../images/uddiview.gif" alt="Picture of the Launch Web Services Explorer icon." />. The Web Services Explorer opens without
+any registries displayed in the Navigator pane. You can now <a href="taddreg.html">add a registry</a> to the Web Services Explorer.</p>
+</div>
+
+</div>
+
+</div>
+
+<div class="nested1" xml:lang="en-us" id="d0e50"><a name="d0e50"><!-- --></a>
+<h2 class="topictitle2">Launching the Web Services Explorer using the Web Services Wizard</h2>
+
+<div>
+<div class="section"><p>To launch the Web Services Explorer from the Web Services Wizard,
+select the <strong>Test the Web Service</strong> check box in the first page of the
+Web Services Wizard. Proceed with the wizard and then in the Web Service Test
+Page, choose <strong>Web Services Explorer</strong> as the test facility and click
+on the <strong>Launch</strong> button. If you launch the Web Services Explorer using
+this method, it will automatically preload the WSDL (and its child nodes)
+in the WSDL page.</p>
+</div>
+
+</div>
+
+</div>
+
+<div class="nested1" xml:lang="en-us" id="d0e63"><a name="d0e63"><!-- --></a>
+<h2 class="topictitle2">Launching the Web Services Explorer using the Import wizard</h2>
+
+<div>
+<div class="section"><p>To launch the Web Services Explorer using the Import wizard, do
+the following:</p>
+</div>
+
+<ol>
+<li><span>From the main menu, click <strong>File > Import</strong>. The Import wizard
+opens.</span></li>
+
+<li><span>Select <strong>Web Service</strong> and click <strong>Next</strong>. The Web service
+import wizard opens.</span></li>
+
+<li><span>Click <strong>Finish</strong>.</span></li>
+
+</ol>
+
+<div class="section"><p>The Web Services Explorer opens. If you selected a registry on
+the Web Service Publication page of the Web service Import wizard, you will
+see the registry displayed in the Navigator pane.</p>
+</div>
+
+</div>
+
+</div>
+
+<div class="nested1" xml:lang="en-us" id="d0e95"><a name="d0e95"><!-- --></a>
+<h2 class="topictitle2">Launching the Web Services Explorer using the Export wizard</h2>
+
+<div>
+<div class="section"><p>To launch the Web Services Explorer using the Export wizard, do
+the following:</p>
+</div>
+
+<ol>
+<li><span>From the main menu, click <strong>File > Export</strong>. The Export wizard
+opens.</span></li>
+
+<li><span>Select <strong>Web Service</strong> and click <strong>Next</strong>. The Web Service
+Export wizard opens.</span></li>
+
+<li><span>Click <strong>Finish</strong>. The Web Services Explorer opens.</span></li>
+
+</ol>
+
+<div class="section"><p>The Web Services Explorer opens. If you selected a registry
+on the Web Service Publication page of the Web Service Export wizard, you
+will see the registry displayed in the Navigator pane.</p>
+</div>
+
+</div>
+
+</div>
+
+<div class="nested1" xml:lang="en-us" id="d0e127"><a name="d0e127"><!-- --></a>
+<h2 class="topictitle2">Launching the Web Services Explorer from the Run menu</h2>
+
+<div>
+<div class="section"><p>To launch the Web Services Explorer from the main menu, ensure
+that you are in the J2EE perspective and click <strong>Run > Launch the Web Services
+Explorer</strong>. The Import wizard opens. The Web Services Explorer opens.
+The Web Services Explorer opens without any registries displayed in the Navigator
+pane.</p>
+</div>
+
+</div>
+
+</div>
+
+<div class="nested1" xml:lang="en-us" id="d0e134"><a name="d0e134"><!-- --></a>
+<h2 class="topictitle2">Launching the Web Services Explorer from a WSDL file</h2>
+
+<div>
+<div class="section"><p>To launch the Web Services Explorer from a WSDL file, select the
+WSDL file and right-click and choose <strong>Web Services > Test with Web Services
+Explorer</strong> or <strong>Publish WSDL file</strong>. The Web Services Explorer
+opens. The <strong>Test with Web Services Explorer</strong> action will preload the
+WSDL in the WSDL page.</p>
+</div>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related Concepts</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div>
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div>
+<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div>
+
+<div class="linklist"><strong>Related Tasks</strong><br />
+
+<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div>
+<div><a href="treg.html" title="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use.">Registering with a UDDI registry</a></div></div>
+
+<div class="linklist"><strong>Related Reference</strong><br />
+
+<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div>
+</div>
+</div>
+
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/ttestwsdl.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/ttestwsdl.dita
new file mode 100644
index 0000000..325031c
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/ttestwsdl.dita
@@ -0,0 +1,103 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>WSDL<indexterm>testing with the Web Services Explorer</indexterm></indexterm>
+<indexterm>Web services<indexterm>testing with the Web Services Explorer</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<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 converts temperature from Celsius to
+Fahrenheit or Fahrenheit to Celsius. <image alt="Screen capture of the WSDL Main pane of the Web Services Explorer"
+href="../images/wsdltemp.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>CtoF</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>temp</systemoutput> parameter) and the type of information
+the parameter is looking for (in this example <systemoutput>temp</systemoutput> is
+requesting an integer).<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 integer 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>
+<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>
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
new file mode 100644
index 0000000..9921b8b
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/ttestwsdl.html
@@ -0,0 +1,137 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" />
+<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 content="WSDL, testing with the Web Services Explorer, Web services" name="DC.subject" />
+<meta content="WSDL, testing with the Web Services Explorer, Web services" name="keywords" />
+<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/common.css" type="text/css" rel="stylesheet" />
+<title>Using the WSDL Explorer</title>
+</head>
+<body id="ttestwsdl"><a name="ttestwsdl"><!-- --></a>
+
+
+<h1 class="topictitle1">Testing WSDL documents and Web services using the WSDL Explorer</h1>
+
+
+
+
+<div><p>WSDL documents allow developers to expose their applications as
+network-accessible services on the Internet. Through UDDI and WSIL, other
+applications can discover WSDL documents and bind with them to execute transactions
+or perform other business processes. The Web Services Explorer allows you
+to explore, import, and test WSDL documents.</p>
+
+<div class="p">Prerequisites: To use the WSDL Explorer:<ul>
+<li>You must have a valid URL for a WSDL document.</li>
+
+<li>You must launch the Web Services Explorer: <a href="tstrtexp.html">Launch the Web Services Explorer</a></li>
+
+</ul>
+</div>
+
+<div class="section"><p>The WSDL Explorer allows you to explore, and test WSDL documents.
+For more information on exploring WSDL documents using the WSDL Explorer,
+refer to <a href="twsdlexp.html">Using the WSDL Explorer</a> .</p>
+<p>To
+test a Web service using the WSDL Explorer:</p>
+</div>
+
+<ol>
+<li class="stepexpand"><span>To launch the WSDL Explorer, complete the following steps:</span>
+<ol type="a">
+<li><span>In the Web Services Explorer, switch to the WSDL Explorer by
+clicking the icon in the upper right-hand corner <img src="../images/wsdlicon.gif" alt="Icon to launch the WSDL Explorer" />. </span></li>
+
+</ol>
+
+</li>
+
+<li class="stepexpand"><span>Select WSDL Main in the Navigator pane, enter or browse to an existing
+WSDL URL in the right-hand pane, and click <strong>Go</strong>. For this example the
+WSDL being used is a Web Service which converts temperature from Celsius to
+Fahrenheit or Fahrenheit to Celsius. <br /><img src="../images/wsdltemp.gif" alt="Screen capture of the WSDL Main pane of the Web Services Explorer" /><br /> The following nodes
+will be added to the WSDL tree: </span> <ul>
+<li>The WSDL node: <img src="../images/wsdlnode.gif" alt="WSDL node icon" /></li>
+
+<li>The service node (which represents a service element within the WSDL file):
+ <img src="../images/servnode.gif" alt="Service node icon" /></li>
+
+<li>The binding node: <img src="../images/bindnode.gif" alt="Binding node icon" /></li>
+
+<li>The operation node: <img src="../images/opnode.gif" alt="Operation node icon" /></li>
+
+</ul>
+</li>
+
+<li class="stepexpand"><span>In the WSDL Binding Details pane, click the operation (in this
+example the <tt class="sysout">CtoF</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">temp</tt> parameter) and the type of information
+the parameter is looking for (in this example <tt class="sysout">temp</tt> is
+requesting an integer).<br /><img src="../images/wsdlop.gif" alt="Invoke a WSDL Operation pane of the Web Services Explorer" /><br /> The Form view allows
+you to enter the parameters for the Web service operation call. Parameters
+names are displayed as links whose action is to display a dialog describing
+embedded XML Schema Definition Language (XSD) information. More information
+about XSD can be found here: <a href="http://www.eclipse.org/xsd/">http://www.eclipse.org/xsd/</a>
+ <br /><img src="../images/scenario7.gif" alt="Screen capture of the XSD Information Dialog" /><br /> </li>
+
+</ul>
+</li>
+
+<li class="stepexpand"><span>Enter your integer and click <strong>Go</strong>. The result is returned
+in the Status pane. <br /><img src="../images/wsdlopret.gif" alt="Screen capture of an invoked WSDL operation showing the result in the Status pane" /><br /> </span></li>
+
+<li class="stepexpand"><span>If you are using SOAP as your binding method, clicking Source or
+Form in the upper right-hand corner will toggle the display between the Form
+view (shown above) and the Source view, which displays the SOAP message in
+the XML format. You can also enter the same information as in the form, only
+in XML format (this is suggested for advanced users only). The Explorer does
+validate the XML if you modify it, but not the parameter values you enter.
+ <br /><img src="../images/wsdlopretx.gif" alt="Source view of the Invoke a WSDL Operation pane." /><br /></span></li>
+
+<li class="stepexpand"><span>If you are using SOAP as your binding type, you will also have
+the option of toggling the Status pane between the Source and Form views.
+The Source view shows the SOAP request and response envelopes, including the
+parameters you have entered to test the service and the returned value. <br /><img src="../images/wsdlstatx.gif" alt="Screen capture of the source view of the SOAP request and response envelopes" /><br /> </span></li>
+
+</ol>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related Concepts</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div>
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div>
+<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div>
+
+<div class="linklist"><strong>Related Tasks</strong><br />
+
+<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div>
+<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div>
+<div><a href="../../org.eclipse.jst.ws.doc.user/tasks/toverws.html"> Developing Web services</a></div></div>
+</div>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.dita
new file mode 100644
index 0000000..ad8bd38
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.dita
@@ -0,0 +1,130 @@
+<?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">
+<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>
+<prolog><metadata>
+<keywords><indexterm>Web Services<indexterm>publishing<indexterm>overview</indexterm></indexterm></indexterm>
+<indexterm>business entities<indexterm>publishing</indexterm></indexterm>
+<indexterm>Web Services Explorer<indexterm>publishing Web services</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<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="tlogexp.dita"></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.</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.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>
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
new file mode 100644
index 0000000..1ba1a20
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.html
@@ -0,0 +1,189 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="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 content="Web Services, publishing, overview, business entities, Web Services Explorer, publishing Web services" name="DC.subject" />
+<meta content="Web Services, publishing, overview, business entities, Web Services Explorer, publishing Web services" name="keywords" />
+<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.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/common.css" type="text/css" rel="stylesheet" />
+<title>Publishing Web services and business entities with the Web Services
+Explorer</title>
+</head>
+<body id="tuddiexp"><a name="tuddiexp"><!-- --></a>
+
+
+<h1 class="topictitle1">Publishing Web services and business entities</h1>
+
+
+
+
+<div><p>Through UDDI and WSIL, other applications can discover WSDL documents
+and bind with them to execute transactions or perform other business processes. </p>
+
+<div class="section"><p>UDDI enables the discovery of Web services by providing a distributed
+registry of businesses and their service descriptions, implemented in a common
+XML format. In order for a service requestor to discover a service,
+a service provider must first publish a business entity and at least one business
+service, and service interface in a UDDI registry. The Web Services
+Explorer is a Web application that supports the publication, discovery, and
+maintenance of business entities, business services, and service interfaces.</p>
+<p>WSIL
+enables the discovery of Web services by defining a distributed service discovery
+method that supplies references to service descriptions at the service provider's
+point-of-offering, by specifying how to inspect a Web site for available Web
+services. The WSIL specification defines the locations on a Web site
+where you can look for Web service descriptions. Since WSIL focuses on
+distributed service discovery, the WSIL specification complements UDDI by
+facilitating the discovery of services that are available on Web sites that
+may not be listed yet in a UDDI registry. The Web Services Explorer allows
+you to generate and explore WSIL documents.</p>
+<p>The favorites page of the
+Web Services Explorer allows you to store the location of UDDI registries,
+business entities, Web services, service interfaces, as well as WSIL and WSDL
+documents.</p>
+<p>Use the Web Services Explorer to do any of the following
+tasks:</p>
+<ul>
+<li> <a href="taddreg.html">Add a registry to the Web Services Explorer</a> </li>
+
+<li> <a href="tbkmrk.html">Adding a registry, business entity, business service, service interface, WSIL, or WSDL service to Favorites</a> </li>
+
+<li><a href="tlogexp.html" title="If you have published your Web service to a UDDI registry you can log into the registry and manage the service through the Web Services Explorer.">Logging in to a UDDI registry</a></li>
+
+<li> <a href="tdiscov.html">Discover a Web service</a> </li>
+
+<li> <a href="tpubent.html">Publish a business entity to a registry</a> </li>
+
+<li> <a href="tpublish.html">Publish a business service to a registry</a> </li>
+
+<li> <a href="tunpub.html">Remove a business entity, business service, or service interface from a registry</a> </li>
+
+<li> <a href="tupdate.html">Update a business entity, business service, or service interface</a> </li>
+
+<li> <a href="tbusproj.html">Manage referenced services</a> </li>
+
+<li> <a href="tassert.html">Manage publisher assertions</a> </li>
+
+</ul>
+<p>Prerequisites:</p>
+</div>
+
+<ol>
+<li class="stepexpand"><span>Before you can use the Web Services Explorer to perform any of
+these functions, you must <a href="treg.html">register with a public registry</a>.
+There are many different registries with which you can register.</span>
+</li>
+
+<li class="stepexpand"><span>Ensure that you are using a supported Web browser.</span> The
+following Web browsers and versions are supported:<ul>
+<li>Internet Explorer: 6.0 and up</li>
+
+<li>Mozilla: 1.2.1 and up</li>
+
+</ul>
+</li>
+
+<li class="stepexpand"><span> <a href="tstrtexp.html">Launch the Web Services Explorer</a>.</span>
+</li>
+
+</ol>
+
+<div class="section"><div class="p"><strong>Known limitations of the Web Services Explorer:</strong><ul>
+<li>The taxonomy categories in the Web Services Explorer are not translated
+since they must match those in the standards adhered to by UDDI (ISO, UNSPSC
+7.3, NAICS).</li>
+
+<li>The Web Services Explorer will launch without the browser toolbar which
+shows, amongst other things, the URL to the Web application. This URL should
+only be used by users with accessibility needs. The URL to the Web Services
+Explorer Web application can be obtained through the following steps:<ol>
+<li>From the Window menu, select Preferences.</li>
+
+<li>In the Preferences dialog, select <span class="uicontrol">Web Browser</span> in
+the left pane.</li>
+
+<li>On the right, select <span class="uicontrol">Use external Web Browser</span>.</li>
+
+<li>In the <span class="uicontrol">Location: text</span> field, browse or type in
+the full path of the Internet Explorer executable. (for example, C:\Program
+Files\Internet Explorer\iexplore.exe).</li>
+
+<li>Click <span class="uicontrol">Apply</span> followed by <span class="uicontrol">OK</span>.</li>
+
+</ol>
+ Note that this preference will now apply to any browser windows that
+are launched by the user or by the tools themselves (such as the Universal
+Test Client). The Web Services Explorer will now launch in an external browser
+and its URL should be in the Address field. This can then be pasted or opened
+using am accessibility assisting browser.</li>
+
+<li>When performing an advanced find or publish in the UDDI page of the Web
+Services Explorer, the items in the drop down list for picking a language
+in conjunction with a name or description is sorted according to the operating
+system's locale settings. On Windows<sup>®</sup>, this order may be managed through
+the Control Panel. To do this:<ol>
+<li>Open the Control Panel.</li>
+
+<li>Launch the Regional Options control panel applet.</li>
+
+<li>In the General tab of the resulting dialog, there may be a "Sorting order"
+drop-down list. If so, pick a sorting order and then click <span class="uicontrol">Apply</span> followed
+by <span class="uicontrol">OK</span>.</li>
+
+<li>In the Web Services Explorer, the new sorting order comes into effect
+once the page reloads. This can be accomplished by pressing the back arrow
+followed by the forward arrow in the main toolbar.</li>
+
+</ol>
+Note: The instructions above apply to Windows 2000. On Windows XP,
+the tab mentioned in step 3 is called "Regional Options". Beside the language
+drop-down, there is a <span class="uicontrol">Customize</span> button. When this is
+clicked, a new dialog appears. A sorting tab will allow users to pick the
+sorting method if applicable.</li>
+
+</ul>
+</div>
+</div>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related Concepts</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div>
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div>
+<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div>
+
+<div class="linklist"><strong>Related Tasks</strong><br />
+
+<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div>
+<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div>
+<div><a href="twsdlexp.html" title="">Exploring WSDL using the WSDL Explorer</a></div>
+<div><a href="../../org.eclipse.jst.ws.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 0000000..831d6b6
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tunpub.dita
@@ -0,0 +1,63 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>Web services<indexterm>removing from a UDDI registry</indexterm></indexterm>
+<indexterm>service interfaces<indexterm>removing from a UDDI registry</indexterm></indexterm>
+<indexterm>business entities<indexterm>removing from a UDDI registry</indexterm></indexterm>
+<indexterm>UDDI<indexterm>removing services from a registry</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<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 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>
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
new file mode 100644
index 0000000..ffd85d6
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tunpub.html
@@ -0,0 +1,102 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="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 content="Web services, removing from a UDDI registry, service interfaces, business entities, UDDI, removing services from a registry" name="DC.subject" />
+<meta content="Web services, removing from a UDDI registry, service interfaces, business entities, UDDI, removing services from a registry" name="keywords" />
+<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/common.css" type="text/css" rel="stylesheet" />
+<title>Removing a business entity, Web service, or service interface
+from a registry</title>
+</head>
+<body id="tunpub"><a name="tunpub"><!-- --></a>
+
+
+<h1 class="topictitle1">Removing a business entity, Web service, or service interface from
+a registry</h1>
+
+
+
+
+<div><p>After you have published a business entity, Web service, or service
+interface, you can remove or unpublish it through the Web Services Explorer.</p>
+
+<div class="p">Prerequisites:<ol>
+<li> <a href="tpubent.html">Publish a business entity</a>.</li>
+
+<li> <a href="tpublish.html">Publish a Web service</a>.</li>
+
+<li> <a href="tpublish.html">Publish a service interface</a>.</li>
+
+<li> <a href="tstrtexp.html">Launch the Web Services Explorer</a>.</li>
+
+</ol>
+</div>
+
+<div class="section">To unpublish a business entity, Web service, or service interface
+using the Web Services Explorer:</div>
+
+<ol>
+<li><span>Navigate through the registry hierarchy to find the business entity,
+Web service, or service interface you want to unpublish. Select the business
+entity, Web service, or service interface.</span></li>
+
+<li><span>In the Actions icon bar, click the <span class="uicontrol">Unpublish</span> icon.</span>
+</li>
+
+<li><span>Enter the publish URL, your user ID, and password, if necessary,
+then click <span class="uicontrol">Go</span>.</span></li>
+
+</ol>
+
+<div class="section"><p>The business entity, Web service, or service interface is removed
+from the registry and the Web Services Explorer is automatically updated with
+your change.</p>
+</div>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related Concepts</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div>
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div>
+<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div>
+
+<div class="linklist"><strong>Related Tasks</strong><br />
+
+<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div>
+<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div>
+<div><a href="tpubent.html" title="A business entity contains information about the business that has published a service. Before you can publish a business service, you must publish a business entity.">Publishing a business entity</a></div>
+<div><a href="tpublish.html" title="The Web service, also known as the business service, describes a Web service's endpoint and where its WSDL file resides. The WSDL file lists the operations that service provides.">Publishing a Web service</a></div>
+<div><a href="tunpub.html" title="After you have published a business entity, Web service, or service interface, you can remove or unpublish it through the Web Services Explorer.">Removing a business entity, Web service, or service interface from a registry</a></div>
+<div><a href="tupdate.html" title="After you have published a business entity, Web service, or service interface, you can update it through the Web Services Explorer.">Updating a business entity, Web service, or service interface</a></div></div>
+
+<div class="linklist"><strong>Related Reference</strong><br />
+
+<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div>
+</div>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tupdate.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tupdate.dita
new file mode 100644
index 0000000..c4fdd25
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tupdate.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="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>
+<prolog><metadata>
+<keywords><indexterm>business entities<indexterm>updating in a UDDI registry</indexterm></indexterm>
+<indexterm>Web services<indexterm>updating UDDI registries</indexterm></indexterm>
+<indexterm>service interfaces<indexterm>updating UDDI registries</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<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 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>
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
new file mode 100644
index 0000000..3317959
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tupdate.html
@@ -0,0 +1,98 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="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 content="business entities, updating in a UDDI registry, Web services, updating UDDI registries, service interfaces" name="DC.subject" />
+<meta content="business entities, updating in a UDDI registry, Web services, updating UDDI registries, service interfaces" name="keywords" />
+<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/common.css" type="text/css" rel="stylesheet" />
+<title>Updating a business entity, Web service, or service interface</title>
+</head>
+<body id="tupdate"><a name="tupdate"><!-- --></a>
+
+
+<h1 class="topictitle1">Updating a business entity, Web service, or service interface</h1>
+
+
+
+<div><p>After you have published a business entity, Web service, or service
+interface, you can update it through the Web Services Explorer.</p>
+
+<div class="p">Prerequisites:<ol>
+<li> <a href="tpubent.html">Publish a business entity</a>.</li>
+
+<li> <a href="tpublish.html">Publish a Web service</a>.</li>
+
+<li> <a href="tpublish.html">Publish a service interface</a>.</li>
+
+<li> <a href="tstrtexp.html">Launch the Web Services Explorer</a>.</li>
+
+</ol>
+</div>
+
+<div class="section">To update a business entity, Web service, or service interface using
+the Web Services Explorer:</div>
+
+<ol>
+<li><span>Navigate through the registry hierarchy to find the business entity,
+Web service, or service interface you want to update. Select the business
+entity, Web service, or service interface.</span></li>
+
+<li><span>In the Actions icon bar, click the <span class="uicontrol">Details</span> icon.</span>
+</li>
+
+<li><span>Make any necessary changes and enter your publish URL, your user
+ID, and password, if necessary, then click <span class="uicontrol">Go</span>.</span>
+</li>
+
+</ol>
+
+<div class="section"><p>The business entity, Web service, or service interface is updated
+in the registry and the Web Services Explorer is automatically updated with
+your change.</p>
+</div>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related Concepts</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div>
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div>
+<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div>
+
+<div class="linklist"><strong>Related Tasks</strong><br />
+
+<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div>
+<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div>
+<div><a href="tpubent.html" title="A business entity contains information about the business that has published a service. Before you can publish a business service, you must publish a business entity.">Publishing a business entity</a></div>
+<div><a href="tpublish.html" title="The Web service, also known as the business service, describes a Web service's endpoint and where its WSDL file resides. The WSDL file lists the operations that service provides.">Publishing a Web service</a></div>
+<div><a href="tunpub.html" title="After you have published a business entity, Web service, or service interface, you can remove or unpublish it through the Web Services Explorer.">Removing a business entity, Web service, or service interface from a registry</a></div></div>
+
+<div class="linklist"><strong>Related Reference</strong><br />
+
+<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div>
+</div>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdlexp.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdlexp.dita
new file mode 100644
index 0000000..0494c89
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdlexp.dita
@@ -0,0 +1,142 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>WSDL<indexterm>exploring</indexterm></indexterm><indexterm>Web
+services<indexterm>exploring WSDL</indexterm></indexterm></keywords>
+</metadata></prolog>
+<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>Show WSDL details: <image alt="WSDL Details icon" href="../images/wsdldtlicon.gif">
+</image></li>
+<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>
+</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: <image alt="Add WSDL to Favorites icon"
+href="../images/wsdlfavicon.gif"></image></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>
+<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>
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
new file mode 100644
index 0000000..38d39e1
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdlexp.html
@@ -0,0 +1,200 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="Exploring WSDL using the WSDL Explorer" />
+<meta content="WSDL, exploring, Web services, exploring WSDL" name="DC.subject" />
+<meta content="WSDL, exploring, Web services, exploring WSDL" name="keywords" />
+<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/common.css" type="text/css" rel="stylesheet" />
+<title>Exploring WSDL using the WSDL Explorer</title>
+</head>
+<body id="twsdlexp"><a name="twsdlexp"><!-- --></a>
+
+
+<h1 class="topictitle1">Exploring WSDL using the WSDL Explorer</h1>
+
+
+<div>
+<div class="p">Prerequisites: To use the WSDL Explorer, you must have a valid URL
+for a WSDL document.</div>
+
+<div class="section">The WSDL Explorer allows you to explore, and test WSDL documents.
+The following actions are available in the WSDL Explorer:<ul>
+<li>Show WSDL details: <img src="../images/wsdldtlicon.gif" alt="WSDL Details icon" /></li>
+
+<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>
+
+</ul>
+</div>
+
+</div>
+
+<div class="nested1" xml:lang="en-us" id="d0e47"><a name="d0e47"><!-- --></a>
+<h2 class="topictitle2">Launching the WSDL Explorer</h2>
+
+<div>
+<div class="section"><p>To launch the WSDL Explorer, complete the following steps:</p>
+</div>
+
+<ol>
+<li><span> <a href="tstrtexp.html">Launch the Web Services Explorer</a>.</span>
+</li>
+
+<li><span>Switch to the WSDL Explorer by clicking the icon in the upper right-hand
+corner <img src="../images/wsdlicon.gif" alt="Icon to launch the WSDL Explorer" />.</span></li>
+
+</ol>
+
+</div>
+
+</div>
+
+<div class="nested1" xml:lang="en-us" id="d0e64"><a name="d0e64"><!-- --></a>
+<h2 class="topictitle2">Importing a WSDL file to your workspace</h2>
+
+<div>
+<div class="section"><p>To import the WSDL file to the Workbench:</p>
+</div>
+
+<ol>
+<li><span>Click this icon: <img src="../images/mptwsdlicon.gif" alt="Import WSDL to the Workbench icon" />.</span></li>
+
+<li><span>Select the project into which you want to import the WSDL.</span>
+</li>
+
+<li><span>If you want to generate a WSIL file from the WSDL, select <strong>Import
+as a service reference to a WSIL document</strong>.</span></li>
+
+<li><span>Click <strong>Go</strong>.</span></li>
+
+</ol>
+
+</div>
+
+</div>
+
+<div class="nested1" xml:lang="en-us" id="d0e90"><a name="d0e90"><!-- --></a>
+<h2 class="topictitle2">Importing a WSDL file to your file system</h2>
+
+<div>
+<div class="section"><p>To import the WSDL file to your file system, click this icon:
+ <img src="../images/fswsdlicon.gif" alt="Import WSDL to your file system icon" />. Specify where you want the WSDL file saved on your system.</p>
+</div>
+
+</div>
+
+</div>
+
+<div class="nested1" xml:lang="en-us" id="d0e96"><a name="d0e96"><!-- --></a>
+<h2 class="topictitle2">Launching the Web services wizard</h2>
+
+<div>
+<div class="section"><p>To launch the Web Service Wizard, click this icon: <img src="../images/wswizicon.gif" alt="Launch the Web Service Wizard icon" />. You can select if you want to create
+a Web service client or a Skeleton Web service from the WSDL file. Click <strong>Go</strong> to
+launch the wizard.</p>
+</div>
+
+</div>
+
+</div>
+
+<div class="nested1" xml:lang="en-us" id="d0e105"><a name="d0e105"><!-- --></a>
+<h2 class="topictitle2">Adding a WSDL file to your favorites</h2>
+
+<div>
+<div class="section"><p>To add the WSDL file to Favorites, click this icon: <img src="../images/wsdlfavicon.gif" alt="Add WSDL to Favorites icon" /></p>
+<p>. The Status pane displays
+that the WSDL was successfully added to your list of favorites. </p>
+</div>
+
+</div>
+
+</div>
+
+<div class="nested1" xml:lang="en-us" id="d0e110"><a name="d0e110"><!-- --></a>
+<h2 class="topictitle2">Exploring WSDL documents using the WSDL Explorer:</h2>
+
+<div>
+<ol>
+<li class="stepexpand"><span>Select WSDL Main in the Navigator pane, enter or browse to an existing
+WSDL URL in the right-hand pane, and click <strong>Go</strong>. Note that the Explorer
+will only allow you to browse for WSDL files that reside in the <samp class="codeph">WebContent/WSDL</samp> folder
+of a project. To explore WSDL files stored in other locations within your
+workspace, type the name of the WSDL file or select the file in the workspace,
+right-click and select <span class="menucascade"><span class="uicontrol">Web Services </span> > <span class="uicontrol"> Launch
+Web Services Explorer</span></span>. For this example the WSDL
+being used is a Web Service which returns a temperature for any entered zip
+code. <br /><img src="../images/wsdlexp.gif" alt="" /><br />
+The following nodes will be added to the WSDL tree: </span> <ul>
+<li>The WSDL node: <img src="../images/wsdlnode.gif" alt="WSDL node icon" /></li>
+
+<li>The service node (which represents a service element within the WSDL file):
+ <img src="../images/servnode.gif" alt="Service node icon" /></li>
+
+<li>The binding node: <img src="../images/bindnode.gif" alt="Binding node icon" /></li>
+
+<li>The operation node: <img src="../images/opnode.gif" alt="Operation node icon" /></li>
+
+</ul>
+</li>
+
+<li class="stepexpand"><span>Clicking the Service node in the Navigator pane (in this example
+this would be the <tt class="sysout">TemperatureService</tt> node) displays
+all the bindings for this service, as well as their type and a brief description
+of the binding if the WSDL provider has included one in the Actions pane.
+Three types of bindings are supported: SOAP, HTTP Get, and HTTP Post. <br /><img src="../images/wsdlservdet.gif" alt="" /><br /> The WSDL
+used in this example only has one binding, <tt class="sysout">TemperatureBinding</tt>,
+which is represented as the <tt class="sysout">TemperaturePortType</tt> node
+in the WSDL tree in the Navigator pane.</span></li>
+
+<li class="stepexpand"><span>Clicking a displayed binding or its node displays the WSDL binding
+details in the Actions pane. This includes the operations and endpoints available
+for this service. <br /><img src="../images/wsdlbnddetl.gif" alt="" /><br /> In this view you can add or remove endpoints for the service. To
+add an endpoint, click <strong>Add</strong>, enter the URL for the endpoint, and click
+ <strong>Go</strong>. The Status pane should say that the endpoints were successfully
+updated. To remove an endpoint, select its checkbox, and click <strong>Remove</strong>.</span>
+</li>
+
+</ol>
+
+<div class="section"><div class="note"><span class="notetitle">Note:</span> When the
+Web Services Explorer loads WSDL files that use multiple inline schemas, warning
+messages will be generated for types that are referenced across these schemas.
+The warning message will be similar to: <samp class="codeph">Reference of type <<em>qualified_type_name</em>>
+isn't resolved.</samp></div>
+</div>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related Concepts</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div>
+<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div>
+
+<div class="linklist"><strong>Related Tasks</strong><br />
+
+<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div>
+<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div>
+<div><a href="../../org.eclipse.jst.ws.doc.user/tasks/toverws.html"> Developing Web services</a></div></div>
+</div>
+</div>
+
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptionbuild_toc.ditamap b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptionbuild_toc.ditamap
new file mode 100644
index 0000000..1092c2c
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptionbuild_toc.ditamap
@@ -0,0 +1,41 @@
+<?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/tlogexp.dita" navtitle="Logging into 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
new file mode 100644
index 0000000..805740e
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptionbuild_toc.xml
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<?NLS TYPE="org.eclipse.help.toc"?>
+
+<toc link_to="../org.eclipse.jst.ws.doc.user/webservice_toc.xml#wsconsumptiont" label="wsconsumptiont" topic="concepts/cuddi.html">
+<topic label="Universal Description, Discovery, and Integration (UDDI)" href="concepts/cuddi.html"/>
+<topic label="Relationship between UDDI and WSDL" href="concepts/cwsdlud.html"/>
+<topic label="Discovering Web Services" href="tasks/tdiscov.html"/>
+<topic label="Exploring WSDL using the WSDL Explorer" href="tasks/twsdlexp.html"/>
+<topic label="Testing WSDL documents and Web services using the WSDL Explorer" href="tasks/ttestwsdl.html"/>
+<topic label="Publishing Web services and business entities" href="tasks/tuddiexp.html">
+<topic label="Launching the Web Services Explorer" href="tasks/tstrtexp.html"/>
+<topic label="Registering with a UDDI registry" href="tasks/treg.html"/>
+<topic label="Logging in to a UDDI registry" href="tasks/tlogexp.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 0000000..4c2c85b
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptiont_toc.ditamap
@@ -0,0 +1,30 @@
+<?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="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/tlogexp.dita" navtitle="Logging into 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>
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptiont_toc.xml b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptiont_toc.xml
new file mode 100644
index 0000000..f2e60b4
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptiont_toc.xml
@@ -0,0 +1,21 @@
+<?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="tasks/tuddiexp.html">
+<topic label="Publishing Web services and business entities" href="tasks/tuddiexp.html">
+<topic label="Launching the Web Services Explorer" href="tasks/tstrtexp.html"/>
+<topic label="Registering with a UDDI registry" href="tasks/treg.html"/>
+<topic label="Logging in to a UDDI registry" href="tasks/tlogexp.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>
+</toc>
diff --git a/docs/org.eclipse.jst.ws.doc.user/.cvsignore b/docs/org.eclipse.jst.ws.doc.user/.cvsignore
new file mode 100644
index 0000000..c6a7b23
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/.cvsignore
@@ -0,0 +1,5 @@
+org.eclipse.jst.ws.doc.user_1.0.0.jar
+bak
+temp
+build.xml
+out
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.ws.doc.user/.project b/docs/org.eclipse.jst.ws.doc.user/.project
new file mode 100644
index 0000000..b0cfef7
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/.project
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.jst.ws.doc.user</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ <buildCommand>
+ <name>org.eclipse.pde.ManifestBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.pde.SchemaBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ </buildSpec>
+ <natures>
+ <nature>org.eclipse.pde.PluginNature</nature>
+ </natures>
+</projectDescription>
diff --git a/docs/org.eclipse.jst.ws.doc.user/DocBuild.xml b/docs/org.eclipse.jst.ws.doc.user/DocBuild.xml
new file mode 100644
index 0000000..123957c
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/DocBuild.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.2" />
+
+ <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/META-INF/MANIFEST.MF b/docs/org.eclipse.jst.ws.doc.user/META-INF/MANIFEST.MF
new file mode 100644
index 0000000..ad15e38
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/META-INF/MANIFEST.MF
@@ -0,0 +1,7 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: %pluginName
+Bundle-SymbolicName: org.eclipse.jst.ws.doc.user; singleton:=true
+Bundle-Version: 1.0.300.qualifier
+Bundle-Vendor: %pluginProvider
+Bundle-Localization: plugin
diff --git a/docs/org.eclipse.jst.ws.doc.user/about.html b/docs/org.eclipse.jst.ws.doc.user/about.html
new file mode 100644
index 0000000..73db36e
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/about.html
@@ -0,0 +1,34 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<HTML>
+
+<head>
+<title>About</title>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+</head>
+
+<BODY lang="EN-US">
+
+<H3>About This Content</H3>
+
+<P>June 06, 2007</P>
+
+<H3>License</H3>
+
+<P>The Eclipse Foundation makes available all content in this plug-in
+("Content"). Unless otherwise indicated below, the Content is provided to you
+under the terms and conditions of the Eclipse Public License Version 1.0
+("EPL"). A copy of the EPL is available at
+<A href="http://www.eclipse.org/org/documents/epl-v10.php">http://www.eclipse.org/org/documents/epl-v10.php</A>.
+For purposes of the EPL, "Program" will mean the Content.</P>
+
+<P>If you did not receive this Content directly from the Eclipse Foundation, the
+Content is being redistributed by another party ("Redistributor") and different
+terms and conditions may apply to your use of any object code in the Content.
+Check the Redistributors license that was provided with the Content. If no such
+license exists, contact the Redistributor. Unless otherwise indicated below, the
+terms and conditions of the EPL still apply to any source code in the Content
+and such source code may be obtained at
+<A href="http://www.eclipse.org/">http://www.eclipse.org/</A>.</P>
+
+</BODY>
+</HTML>
diff --git a/docs/org.eclipse.jst.ws.doc.user/build.properties b/docs/org.eclipse.jst.ws.doc.user/build.properties
new file mode 100644
index 0000000..0395e57
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/build.properties
@@ -0,0 +1,19 @@
+bin.includes = plugin.properties,\
+ plugin.xml,\
+ webservice_toc.xml,\
+ org.eclipse.jst.ws.doc.userindex.xml,\
+ about.html,\
+ images/,\
+ concepts/*.htm*,\
+ tasks/*.htm*,\
+ ref/*.htm*,\
+ index/,\
+ META-INF/
+src.includes = build.properties,\
+ *.maplist,\
+ *.ditamap,\
+ concepts/*.dita,\
+ tasks/*.dita,\
+ ref/*.dita
+bin.excludes = DocBuild.xml,\
+ myPlugin*.xml
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 0000000..d3b5b27
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cjaxrpc.dita
@@ -0,0 +1,66 @@
+<?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">
+<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>
+<prolog><metadata>
+<keywords><indexterm>JAX-RPC<indexterm>Web services</indexterm></indexterm>
+<indexterm>Web services<indexterm>JAX-RPC</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<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>
diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cjaxrpc.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cjaxrpc.html
new file mode 100644
index 0000000..f1202d4
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cjaxrpc.html
@@ -0,0 +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 lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="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 content="JAX-RPC, Web services" name="DC.subject" />
+<meta content="JAX-RPC, Web services" name="keywords" />
+<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/common.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
+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.</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" 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.
+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 Java 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 Java 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 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="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" 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>
+
+</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 0000000..189a307
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cjsr109.dita
@@ -0,0 +1,41 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>JSR 109 Java specification</indexterm>
+<indexterm>JSR 921 Java specification</indexterm>
+<indexterm>Web services<indexterm>Java specification requests</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<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
new file mode 100644
index 0000000..0a4dd2e
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cjsr109.html
@@ -0,0 +1,64 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="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 content="JSR 109 Java specification, JSR 921 Java specification, Web services, Java specification requests" name="DC.subject" />
+<meta content="JSR 109 Java specification, JSR 921 Java specification, Web services, Java specification requests" name="keywords" />
+<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/common.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>
+
+</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" 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>
+
+</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 0000000..4237c27
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/concepts/csoap.dita
@@ -0,0 +1,108 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>SOAP<indexterm>overview</indexterm></indexterm>
+<indexterm>Web services<indexterm>SOAP</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<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.3, 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
new file mode 100644
index 0000000..2eaf618
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/concepts/csoap.html
@@ -0,0 +1,154 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="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 content="SOAP, overview, Web services" name="DC.subject" />
+<meta content="SOAP, overview, Web services" name="keywords" />
+<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/common.css" type="text/css" rel="stylesheet" />
+<title>SOAP</title>
+</head>
+<body id="csoap"><a name="csoap"><!-- --></a>
+
+
+<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. 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
+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> <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
+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> <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>
+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.</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
+know as serialization and deserialization.</p>
+<p>The SOAP specification defines
+the SOAP encoding style:</p>
+<blockquote> <p> <span class="uicontrol">SOAP encoding:</span>
+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>
+ </blockquote>
+<p>WSDL defines the
+Literal XML encoding style:</p>
+<blockquote> <p> <span class="uicontrol">Literal XML:</span>
+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>
+ </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,
+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
+ <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<sup>®</sup> project called SOAP4J, as well as Apache
+Axis and the IBM WebSphere<sup>®</sup> run-time
+environment. The provided Web services tools support Apache SOAP 2.3, Axis
+1.3, 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>
+</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" 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/cws.dita b/docs/org.eclipse.jst.ws.doc.user/concepts/cws.dita
new file mode 100644
index 0000000..b0e6286
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cws.dita
@@ -0,0 +1,93 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>Web services<indexterm>overview</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<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.ibm.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
new file mode 100644
index 0000000..80d7ce1
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cws.html
@@ -0,0 +1,137 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="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 content="Web services, overview" name="DC.subject" />
+<meta content="Web services, overview" name="keywords" />
+<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/common.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>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>
+
+<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
+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> <span class="uicontrol">Business
+integration.</span> 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> <span class="uicontrol">Business process
+externalization.</span> 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>
+ </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
+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> <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.ibm.com/developerworks/webservices</a></p>
+</div>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related Concepts</strong><br />
+
+<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, 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 0000000..b18f7fb
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsbtmup.dita
@@ -0,0 +1,38 @@
+<?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">
+<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>
+<prolog><metadata>
+<keywords><indexterm>bottom-up Web services<indexterm>overview</indexterm></indexterm>
+<indexterm>Web services<indexterm>bottom-up</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<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>
diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsbtmup.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsbtmup.html
new file mode 100644
index 0000000..c2bfaf4
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsbtmup.html
@@ -0,0 +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">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="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 content="bottom-up Web services, overview, Web services, bottom-up" name="DC.subject" />
+<meta content="bottom-up Web services, overview, Web services, bottom-up" name="keywords" />
+<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/common.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="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" 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 0000000..cc89e9f
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsdl.dita
@@ -0,0 +1,73 @@
+<?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="cwsdl" xml:lang="en-us">
+<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>
+<prolog><metadata>
+<keywords><indexterm>WSDL<indexterm>overview</indexterm></indexterm><indexterm>Web
+services<indexterm>WSDL</indexterm></indexterm></keywords>
+</metadata></prolog>
+<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>
diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsdl.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsdl.html
new file mode 100644
index 0000000..c5f8199
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsdl.html
@@ -0,0 +1,102 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="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 content="WSDL, overview, Web services" name="DC.subject" />
+<meta content="WSDL, overview, Web services" name="keywords" />
+<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/common.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
+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 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>
+<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" 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 0000000..2b10f23
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsil.dita
@@ -0,0 +1,84 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>WSIL<indexterm>overview</indexterm></indexterm><indexterm>Web
+services<indexterm>WSIL</indexterm></indexterm></keywords>
+</metadata></prolog>
+<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
new file mode 100644
index 0000000..4720f01
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsil.html
@@ -0,0 +1,120 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="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 content="WSIL, overview, Web services" name="DC.subject" />
+<meta content="WSIL, overview, Web services" name="keywords" />
+<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/common.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>
+
+<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>
+
+<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> <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>
+<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" 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/cwsilud.dita b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsilud.dita
new file mode 100644
index 0000000..6a58a0b
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsilud.dita
@@ -0,0 +1,72 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>UDDI<indexterm>relationship with WSIL</indexterm></indexterm>
+<indexterm>WSIL<indexterm>relationship with UDDI</indexterm></indexterm></keywords>
+</metadata></prolog>
+<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"><linktext> Developing Web
+services</linktext></link>
+</linklist>
+</related-links>
+</concept>
diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsilud.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsilud.html
new file mode 100644
index 0000000..533c44d
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsilud.html
@@ -0,0 +1,104 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="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 content="UDDI, relationship with WSIL, WSIL, relationship with UDDI" name="DC.subject" />
+<meta content="UDDI, relationship with WSIL, WSIL, relationship with UDDI" name="keywords" />
+<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/common.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
+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>
+
+<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="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" 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 />
+
+<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 0000000..5cd0a18
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.dita
@@ -0,0 +1,48 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>Web services<indexterm>tools overview</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<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 clients 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>
diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html
new file mode 100644
index 0000000..ec0887d
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html
@@ -0,0 +1,75 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="concept" name="DC.Type" />
+<meta name="DC.Title" content="Tools for Web services development" />
+<meta content="Web services, tools overview" name="DC.subject" />
+<meta content="Web services, tools overview" name="keywords" />
+<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/common.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
+development:</p>
+
+<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 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 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>
+
+<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, 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/cwsiover.dita b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsiover.dita
new file mode 100644
index 0000000..a075524
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsiover.dita
@@ -0,0 +1,41 @@
+<?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">
+<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>
+<prolog><metadata>
+<keywords><indexterm>Web services interoperability<indexterm>traffic compliance</indexterm></indexterm>
+<indexterm>interoperability<indexterm>Web service traffic compliance</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<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>
diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsiover.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsiover.html
new file mode 100644
index 0000000..98ea14b
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsiover.html
@@ -0,0 +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">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="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 content="Web services interoperability, traffic compliance, interoperability, Web service traffic compliance" name="DC.subject" />
+<meta content="Web services interoperability, traffic compliance, interoperability, Web service traffic compliance" name="keywords" />
+<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/common.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
+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 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>
+<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 are not WS-I compliant.">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.jst.ws.doc.user/concepts/cwsstandards.dita b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsstandards.dita
new file mode 100644
index 0000000..f49a95f
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsstandards.dita
@@ -0,0 +1,222 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>Web services<indexterm>standards</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<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 1.1 (SOAP 1.2 is not supported by the
+Web services tools), 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 this development
+environment. 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
new file mode 100644
index 0000000..2ac5036
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsstandards.html
@@ -0,0 +1,315 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="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 content="Web services, standards" name="DC.subject" />
+<meta content="Web services, standards" name="keywords" />
+<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/common.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), 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
+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>
+
+<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 <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
+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 1.1 (SOAP 1.2 is not supported by the
+Web services tools), 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 this development
+environment. 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>
+
+<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>
+
+<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 summary="" cellspacing="0" cellpadding="4" frame="border" border="1" rules="all">
+<thead align="left">
+<tr>
+<th valign="top" width="47.73869346733669%" id="N101B4">Technology or specification</th>
+
+<th valign="top" width="52.26130653266332%" id="N101BC">Version or level supported</th>
+
+</tr>
+
+</thead>
+
+<tbody>
+<tr>
+<td colspan="2" valign="top" headers="N101B4 N101BC "><strong>Transports</strong></td>
+
+</tr>
+
+<tr>
+<td valign="top" width="47.73869346733669%" headers="N101B4 ">HTTP/HTTPS</td>
+
+<td valign="top" width="52.26130653266332%" headers="N101BC ">v1.0 and v1.1</td>
+
+</tr>
+
+<tr>
+<td valign="top" width="47.73869346733669%" headers="N101B4 ">JMS</td>
+
+<td valign="top" width="52.26130653266332%" headers="N101BC "> </td>
+
+</tr>
+
+<tr>
+<td colspan="2" valign="top" headers="N101B4 N101BC "><strong>Messaging</strong></td>
+
+</tr>
+
+<tr>
+<td valign="top" width="47.73869346733669%" headers="N101B4 ">SOAP specification</td>
+
+<td valign="top" width="52.26130653266332%" headers="N101BC ">v1.1</td>
+
+</tr>
+
+<tr>
+<td valign="top" width="47.73869346733669%" headers="N101B4 ">SOAP Attachements</td>
+
+<td valign="top" width="52.26130653266332%" headers="N101BC "> </td>
+
+</tr>
+
+<tr>
+<td colspan="2" valign="top" headers="N101B4 N101BC "><strong>Description</strong></td>
+
+</tr>
+
+<tr>
+<td valign="top" width="47.73869346733669%" headers="N101B4 ">UDDI</td>
+
+<td valign="top" width="52.26130653266332%" headers="N101BC ">v2.0</td>
+
+</tr>
+
+<tr>
+<td valign="top" width="47.73869346733669%" headers="N101B4 ">WSDL</td>
+
+<td valign="top" width="52.26130653266332%" headers="N101BC ">v1.1</td>
+
+</tr>
+
+<tr>
+<td valign="top" width="47.73869346733669%" headers="N101B4 ">WSIL</td>
+
+<td valign="top" width="52.26130653266332%" headers="N101BC ">v1.0</td>
+
+</tr>
+
+<tr>
+<td colspan="2" valign="top" headers="N101B4 N101BC "><strong>Security</strong></td>
+
+</tr>
+
+<tr>
+<td valign="top" width="47.73869346733669%" headers="N101B4 ">WS-Security</td>
+
+<td valign="top" width="52.26130653266332%" headers="N101BC ">OASIS Standard 1.0</td>
+
+</tr>
+
+<tr>
+<td colspan="2" valign="top" headers="N101B4 N101BC "><strong>Ineroperability</strong></td>
+
+</tr>
+
+<tr>
+<td valign="top" width="47.73869346733669%" headers="N101B4 ">WS-I Basic Profile</td>
+
+<td valign="top" width="52.26130653266332%" headers="N101BC ">1.1.2</td>
+
+</tr>
+
+<tr>
+<td valign="top" width="47.73869346733669%" headers="N101B4 ">WS-I Simple SOAP Binding Profile</td>
+
+<td valign="top" width="52.26130653266332%" headers="N101BC ">1.0.3</td>
+
+</tr>
+
+<tr>
+<td valign="top" width="47.73869346733669%" headers="N101B4 ">WS-I Attachments Profile</td>
+
+<td valign="top" width="52.26130653266332%" headers="N101BC ">1.0</td>
+
+</tr>
+
+<tr>
+<td valign="top" width="47.73869346733669%" headers="N101B4 "><strong>Other Standards</strong></td>
+
+<td valign="top" width="52.26130653266332%" headers="N101BC "> </td>
+
+</tr>
+
+<tr>
+<td valign="top" width="47.73869346733669%" headers="N101B4 ">JAX-RPC</td>
+
+<td valign="top" width="52.26130653266332%" headers="N101BC ">v1.0 for J2EE 1.3, v1.1 for J2EE 1.4</td>
+
+</tr>
+
+<tr>
+<td valign="top" width="47.73869346733669%" headers="N101B4 ">JSR 109</td>
+
+<td valign="top" width="52.26130653266332%" headers="N101BC ">J2EE 1.3</td>
+
+</tr>
+
+<tr>
+<td valign="top" width="47.73869346733669%" headers="N101B4 ">JSR 921</td>
+
+<td valign="top" width="52.26130653266332%" headers="N101BC ">J2EE 1.4</td>
+
+</tr>
+
+</tbody>
+
+</table>
+</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" 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>
+
+</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 0000000..cc1676d
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwstopdown.dita
@@ -0,0 +1,39 @@
+<?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">
+<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>
+<prolog><metadata>
+<keywords><indexterm>top-down Web services<indexterm>creating</indexterm></indexterm>
+<indexterm>Web services<indexterm>top-down</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<conbody>
+<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>
+<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. By creating the WSDL file first you will ultimately
+have more control over the Web service, and can eliminate interoperability
+issues that may arise when creating a Web service using the bottom-up method.</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>
diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwstopdown.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwstopdown.html
new file mode 100644
index 0000000..1124a8b
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwstopdown.html
@@ -0,0 +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 lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="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 content="top-down Web services, creating, Web services, top-down" name="DC.subject" />
+<meta content="top-down Web services, creating, Web services, top-down" name="keywords" />
+<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/common.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>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>
+
+<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. By creating the WSDL file first you will ultimately
+have more control over the Web service, and can eliminate interoperability
+issues that may arise when creating a Web service using the bottom-up method.</p>
+
+</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" 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/images/roles.gif b/docs/org.eclipse.jst.ws.doc.user/images/roles.gif
new file mode 100644
index 0000000..05e9987
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/images/roles.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.doc.user/images/soapudws.gif b/docs/org.eclipse.jst.ws.doc.user/images/soapudws.gif
new file mode 100644
index 0000000..efb42f5
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/images/soapudws.gif
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.doc.user/index/_w.cfs b/docs/org.eclipse.jst.ws.doc.user/index/_w.cfs
new file mode 100644
index 0000000..e8eb6fb
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/index/_w.cfs
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.doc.user/index/deletable b/docs/org.eclipse.jst.ws.doc.user/index/deletable
new file mode 100644
index 0000000..e423242
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/index/deletable
Binary files differ
diff --git a/docs/org.eclipse.jst.ws.doc.user/index/indexed_contributions b/docs/org.eclipse.jst.ws.doc.user/index/indexed_contributions
new file mode 100644
index 0000000..8a87d8d
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/index/indexed_contributions
@@ -0,0 +1,3 @@
+#This is a generated file; do not edit.
+#Wed May 09 14:13:37 EDT 2007
+org.eclipse.jst.ws.doc.user=org.eclipse.jst.ws.doc.user\n1.0.300.qualifier
diff --git a/docs/org.eclipse.jst.ws.doc.user/index/indexed_dependencies b/docs/org.eclipse.jst.ws.doc.user/index/indexed_dependencies
new file mode 100644
index 0000000..02fe41d
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/index/indexed_dependencies
@@ -0,0 +1,4 @@
+#This is a generated file; do not edit.
+#Wed May 09 14:13:37 EDT 2007
+lucene=1.4.103.v20060601
+analyzer=org.eclipse.help.base\#3.2.0.v20060601?locale\=en
diff --git a/docs/org.eclipse.jst.ws.doc.user/index/indexed_docs b/docs/org.eclipse.jst.ws.doc.user/index/indexed_docs
new file mode 100644
index 0000000..229f8fd
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/index/indexed_docs
@@ -0,0 +1,31 @@
+#This is a generated file; do not edit.
+#Wed May 09 14:13:37 EDT 2007
+/org.eclipse.jst.ws.doc.user/concepts/cwsbtmup.html=0
+/org.eclipse.jst.ws.doc.user/../org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cuddi.html=0
+/org.eclipse.jst.ws.doc.user/../org.eclipse.jst.ws.axis.ui.doc.user/tasks/ttomcatserv.html=0
+/org.eclipse.jst.ws.doc.user/../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tdiscov.html=0
+/org.eclipse.jst.ws.doc.user/concepts/cwstopdown.html=0
+/org.eclipse.jst.ws.doc.user/ref/rwspref.html=0
+/org.eclipse.jst.ws.doc.user/../org.eclipse.wst.wsi.ui.doc.user/tasks/twsdlval.html=0
+/org.eclipse.jst.ws.doc.user/tasks/twsicomply.html=0
+/org.eclipse.jst.ws.doc.user/../org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsklwsdla.html=0
+/org.eclipse.jst.ws.doc.user/concepts/cwsdl.html=0
+/org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html=0
+/org.eclipse.jst.ws.doc.user/ref/rwsdl.html=0
+/org.eclipse.jst.ws.doc.user/../org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.html=0
+/org.eclipse.jst.ws.doc.user/../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tgenwsil.html=0
+/org.eclipse.jst.ws.doc.user/../org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsampappa.html=0
+/org.eclipse.jst.ws.doc.user/concepts/csoap.html=0
+/org.eclipse.jst.ws.doc.user/../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/ttestwsdl.html=0
+/org.eclipse.jst.ws.doc.user/tasks/toverws.html=0
+/org.eclipse.jst.ws.doc.user/concepts/cwsstandards.html=0
+/org.eclipse.jst.ws.doc.user/concepts/cws.html=0
+/org.eclipse.jst.ws.doc.user/../org.eclipse.jst.ws.axis.ui.doc.user/concepts/caxistover.html=0
+/org.eclipse.jst.ws.doc.user/concepts/cjaxrpc.html=0
+/org.eclipse.jst.ws.doc.user/concepts/cwsiover.html=0
+/org.eclipse.jst.ws.doc.user/../org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cwsdlud.html=0
+/org.eclipse.jst.ws.doc.user/../org.eclipse.wst.wsi.ui.doc.user/tasks/twsival.html=0
+/org.eclipse.jst.ws.doc.user/concepts/cwsil.html=0
+/org.eclipse.jst.ws.doc.user/../org.eclipse.jst.ws.axis.ui.doc.user/tasks/twsbeana.html=0
+/org.eclipse.jst.ws.doc.user/concepts/cwsilud.html=0
+/org.eclipse.jst.ws.doc.user/concepts/cjsr109.html=0
diff --git a/docs/org.eclipse.jst.ws.doc.user/index/segments b/docs/org.eclipse.jst.ws.doc.user/index/segments
new file mode 100644
index 0000000..19b5d0c
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/index/segments
Binary files differ
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 0000000..ef8b20b
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/myplugin.xml
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?eclipse version="3.0"?>
+<?NLS TYPE="org.eclipse.help.toc"?>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2007 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * IBM Corporation - initial API and implementation
+ *******************************************************************************/ -->
+<plugin>
+
+ <extension point="org.eclipse.help.toc">
+ <toc file="webservice_toc.xml" />
+ <index path="index/"/>
+ </extension>
+ <extension point="org.eclipse.help.index">
+ <index file="org.eclipse.jst.ws.doc.userindex.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 0000000..b266991
--- /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/org.eclipse.jst.ws.doc.userindex.html b/docs/org.eclipse.jst.ws.doc.user/org.eclipse.jst.ws.doc.userindex.html
new file mode 100644
index 0000000..cf9505e
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/org.eclipse.jst.ws.doc.userindex.html
@@ -0,0 +1,164 @@
+<?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" />
+<meta name="copyright" content="(C) Copyright IBM Corporation 2007" />
+<meta name="security" content="public" />
+<meta name="Robots" content="index,follow" />
+<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 name="DC.Format" content="XHTML" />
+<!-- All rights reserved. Licensed Materials Property of IBM -->
+<!-- US Government Users Restricted Rights -->
+<!-- Use, duplication or disclosure restricted by -->
+<!-- GSA ADP Schedule Contract with IBM Corp. -->
+<link rel="stylesheet" type="text/css" href="ibmdita.css" />
+<title>Index</title>
+</head>
+<body>
+<h1>Index</h1>
+<a name="IDX0_42" href="#IDX1_42">B</a>
+<a name="IDX0_49" href="#IDX1_49">I</a>
+<a name="IDX0_4A" href="#IDX1_4A">J</a>
+<a name="IDX0_50" href="#IDX1_50">P</a>
+<a name="IDX0_53" href="#IDX1_53">S</a>
+<a name="IDX0_54" href="#IDX1_54">T</a>
+<a name="IDX0_55" href="#IDX1_55">U</a>
+<a name="IDX0_57" href="#IDX1_57">W</a>
+<hr></hr>
+<strong><a name="IDX1_42" href="#IDX0_42">B</a></strong>
+<ul class="indexlist">
+<li>bottom-up Web services
+<ul class="indexlist">
+<li><a href="concepts/cwsbtmup.html#creatingbottom-upwebservices">overview</a>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a name="IDX1_49" href="#IDX0_49">I</a></strong>
+<ul class="indexlist">
+<li>interoperability
+<ul class="indexlist">
+<li><a href="concepts/cwsiover.html#cwsiover">Web service traffic compliance</a>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a name="IDX1_4A" href="#IDX0_4A">J</a></strong>
+<ul class="indexlist">
+<li>JAX-RPC
+<ul class="indexlist">
+<li><a href="concepts/cjaxrpc.html#cjaxrpc">Web services</a>
+</li>
+</ul>
+</li>
+<li><a href="concepts/cjsr109.html#cjsr109">JSR 109 Java specification</a>
+</li>
+<li><a href="concepts/cjsr109.html#cjsr109">JSR 921 Java specification</a>
+</li>
+</ul>
+<strong><a name="IDX1_50" href="#IDX0_50">P</a></strong>
+<ul class="indexlist">
+<li>preferences
+<ul class="indexlist">
+<li><a href="ref/rwspref.html#rwspref">Web services</a>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a name="IDX1_53" href="#IDX0_53">S</a></strong>
+<ul class="indexlist">
+<li>SOAP
+<ul class="indexlist">
+<li><a href="concepts/csoap.html#csoap">overview</a>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a name="IDX1_54" href="#IDX0_54">T</a></strong>
+<ul class="indexlist">
+<li>top-down Web services
+<ul class="indexlist">
+<li><a href="concepts/cwstopdown.html#creatingtop-downwebservices">creating</a>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a name="IDX1_55" href="#IDX0_55">U</a></strong>
+<ul class="indexlist">
+<li>UDDI
+<ul class="indexlist">
+<li><a href="concepts/cwsilud.html#cwsilud">relationship with WSIL</a>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a name="IDX1_57" href="#IDX0_57">W</a></strong>
+<ul class="indexlist">
+<li>Web services
+<ul class="indexlist">
+<li><a href="concepts/cwsbtmup.html#creatingbottom-upwebservices">bottom-up</a>
+</li>
+<li>creating
+<ul class="indexlist">
+<li><a href="tasks/toverws.html#toverws">overview</a>
+</li>
+</ul>
+</li>
+<li><a href="tasks/twsicomply.html#twsicomply">interoperability compliance</a>
+</li>
+<li><a href="concepts/cjsr109.html#cjsr109">Java specification requests</a>
+</li>
+<li><a href="concepts/cjaxrpc.html#cjaxrpc">JAX-RPC</a>
+</li>
+<li><a href="concepts/cws.html#cws">overview</a>
+</li>
+<li><a href="ref/rwspref.html#rwspref">preferences</a>
+</li>
+<li><a href="concepts/csoap.html#csoap">SOAP</a>
+</li>
+<li><a href="concepts/cwsstandards.html#webservicesstandards">standards</a>
+</li>
+<li><a href="concepts/cwsinwsa.html#cwsinwsa">tools overview</a>
+</li>
+<li><a href="concepts/cwstopdown.html#creatingtop-downwebservices">top-down</a>
+</li>
+<li><a href="concepts/cwsdl.html#cwsdl">WSDL</a>
+</li>
+<li><a href="ref/rwsdl.html#rwsdl">WSDL reference</a>
+</li>
+<li><a href="concepts/cwsil.html#cwsil">WSIL</a>
+</li>
+</ul>
+</li>
+<li>Web services interoperability
+<ul class="indexlist">
+<li><a href="concepts/cwsiover.html#cwsiover">traffic compliance</a>
+</li>
+</ul>
+</li>
+<li>WSDL
+<ul class="indexlist">
+<li><a href="concepts/cwsdl.html#cwsdl">overview</a>
+</li>
+<li><a href="ref/rwsdl.html#rwsdl">reference</a>
+</li>
+</ul>
+</li>
+<li>WSI
+<ul class="indexlist">
+<li><a href="tasks/twsicomply.html#twsicomply">setting compliance</a>
+</li>
+</ul>
+</li>
+<li>WSIL
+<ul class="indexlist">
+<li><a href="concepts/cwsil.html#cwsil">overview</a>
+</li>
+<li><a href="concepts/cwsilud.html#cwsilud">relationship with UDDI</a>
+</li>
+</ul>
+</li>
+</ul>
+</body></html>
diff --git a/docs/org.eclipse.jst.ws.doc.user/org.eclipse.jst.ws.doc.userindex.xml b/docs/org.eclipse.jst.ws.doc.user/org.eclipse.jst.ws.doc.userindex.xml
new file mode 100644
index 0000000..9d6673a
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/org.eclipse.jst.ws.doc.userindex.xml
@@ -0,0 +1,116 @@
+<?xml version="1.0" encoding="utf-8"?>
+<index>
+ <entry keyword="Web services">
+ <entry keyword="overview">
+ <topic href="concepts/cws.html#cws" title="Web services overview"/>
+ </entry>
+ <entry keyword="standards">
+ <topic href="concepts/cwsstandards.html#webservicesstandards" title="Web services standards"/>
+ </entry>
+ <entry keyword="WSDL">
+ <topic href="concepts/cwsdl.html#cwsdl" title="Web Services Description Language (WSDL)"/>
+ </entry>
+ <entry keyword="WSDL reference">
+ <topic href="ref/rwsdl.html#rwsdl" title="Web Services Description Language (WSDL) reference"/>
+ </entry>
+ <entry keyword="SOAP">
+ <topic href="concepts/csoap.html#csoap" title="SOAP"/>
+ </entry>
+ <entry keyword="WSIL">
+ <topic href="concepts/cwsil.html#cwsil" title="Web Services Inspection Language (WSIL)"/>
+ </entry>
+ <entry keyword="JAX-RPC">
+ <topic href="concepts/cjaxrpc.html#cjaxrpc" title="JAX-RPC"/>
+ </entry>
+ <entry keyword="Java specification requests">
+ <topic href="concepts/cjsr109.html#cjsr109" title="JSR 109 and JSR 921- Implementing Enterprise Web services"/>
+ </entry>
+ <entry keyword="tools overview">
+ <topic href="concepts/cwsinwsa.html#cwsinwsa" title="Tools for Web services development"/>
+ </entry>
+ <entry keyword="preferences">
+ <topic href="ref/rwspref.html#rwspref" title="Web services preferences"/>
+ </entry>
+ <entry keyword="interoperability compliance">
+ <topic href="tasks/twsicomply.html#twsicomply" title="Setting the level of WS-I compliance"/>
+ </entry>
+ <entry keyword="creating">
+ <entry keyword="overview">
+ <topic href="tasks/toverws.html#toverws" title="Developing Web services"/>
+ </entry>
+ </entry>
+ <entry keyword="top-down">
+ <topic href="concepts/cwstopdown.html#creatingtop-downwebservices" title="Creating top-down Web services"/>
+ </entry>
+ <entry keyword="bottom-up">
+ <topic href="concepts/cwsbtmup.html#creatingbottom-upwebservices" title="Creating bottom-up Web services"/>
+ </entry>
+ </entry>
+ <entry keyword="WSDL">
+ <entry keyword="overview">
+ <topic href="concepts/cwsdl.html#cwsdl" title="Web Services Description Language (WSDL)"/>
+ </entry>
+ <entry keyword="reference">
+ <topic href="ref/rwsdl.html#rwsdl" title="Web Services Description Language (WSDL) reference"/>
+ </entry>
+ </entry>
+ <entry keyword="SOAP">
+ <entry keyword="overview">
+ <topic href="concepts/csoap.html#csoap" title="SOAP"/>
+ </entry>
+ </entry>
+ <entry keyword="WSIL">
+ <entry keyword="overview">
+ <topic href="concepts/cwsil.html#cwsil" title="Web Services Inspection Language (WSIL)"/>
+ </entry>
+ <entry keyword="relationship with UDDI">
+ <topic href="concepts/cwsilud.html#cwsilud" title="Relationship between UDDI and WSIL"/>
+ </entry>
+ </entry>
+ <entry keyword="UDDI">
+ <entry keyword="relationship with WSIL">
+ <topic href="concepts/cwsilud.html#cwsilud" title="Relationship between UDDI and WSIL"/>
+ </entry>
+ </entry>
+ <entry keyword="JAX-RPC">
+ <entry keyword="Web services">
+ <topic href="concepts/cjaxrpc.html#cjaxrpc" title="JAX-RPC"/>
+ </entry>
+ </entry>
+ <entry keyword="JSR 109 Java specification">
+ <topic href="concepts/cjsr109.html#cjsr109" title="JSR 109 and JSR 921- Implementing Enterprise Web services"/>
+ </entry>
+ <entry keyword="JSR 921 Java specification">
+ <topic href="concepts/cjsr109.html#cjsr109" title="JSR 109 and JSR 921- Implementing Enterprise Web services"/>
+ </entry>
+ <entry keyword="preferences">
+ <entry keyword="Web services">
+ <topic href="ref/rwspref.html#rwspref" title="Web services preferences"/>
+ </entry>
+ </entry>
+ <entry keyword="Web services interoperability">
+ <entry keyword="traffic compliance">
+ <topic href="concepts/cwsiover.html#cwsiover" title="Web services interoperability (WS-I)"/>
+ </entry>
+ </entry>
+ <entry keyword="interoperability">
+ <entry keyword="Web service traffic compliance">
+ <topic href="concepts/cwsiover.html#cwsiover" title="Web services interoperability (WS-I)"/>
+ </entry>
+ </entry>
+ <entry keyword="WSI">
+ <entry keyword="setting compliance">
+ <topic href="tasks/twsicomply.html#twsicomply" title="Setting the level of WS-I compliance"/>
+ </entry>
+ </entry>
+ <entry keyword="top-down Web services">
+ <entry keyword="creating">
+ <topic href="concepts/cwstopdown.html#creatingtop-downwebservices" title="Creating top-down Web services"/>
+ </entry>
+ </entry>
+ <entry keyword="bottom-up Web services">
+ <entry keyword="overview">
+ <topic href="concepts/cwsbtmup.html#creatingbottom-upwebservices" title="Creating bottom-up Web services"/>
+ </entry>
+ </entry>
+</index>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.ws.doc.user/plugin.properties b/docs/org.eclipse.jst.ws.doc.user/plugin.properties
new file mode 100644
index 0000000..27cc7aa
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/plugin.properties
@@ -0,0 +1,15 @@
+###############################################################################
+# Copyright (c) 2001, 2005 IBM Corporation and others.
+# All rights reserved. This program and the accompanying materials
+# are made available under the terms of the Eclipse Public License v1.0
+# which accompanies this distribution, and is available at
+# http://www.eclipse.org/legal/epl-v10.html
+#
+# Contributors:
+# IBM Corporation - initial API and implementation
+###############################################################################
+# NLS_MESSAGEFORMAT_VAR
+# NLS_ENCODING=UTF-8
+
+pluginName = Web Services UI
+pluginProvider = Eclipse.org
diff --git a/docs/org.eclipse.jst.ws.doc.user/plugin.xml b/docs/org.eclipse.jst.ws.doc.user/plugin.xml
new file mode 100644
index 0000000..122acd0
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/plugin.xml
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?eclipse version="3.0"?>
+<?NLS TYPE="org.eclipse.help.toc"?>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2007 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * IBM Corporation - initial API and implementation
+ *******************************************************************************/ -->
+<plugin>
+
+ <extension point="org.eclipse.help.toc">
+ <toc file="webservice_toc.xml" />
+ <index path="index/"/>
+ </extension>
+ <extension point="org.eclipse.help.index">
+ <index file="org.eclipse.jst.ws.doc.userindex.xml"/>
+ </extension>
+</plugin>
\ No newline at end of file
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 0000000..6fceb7d
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/ref/rwsdl.dita
@@ -0,0 +1,55 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>WSDL<indexterm>reference</indexterm></indexterm><indexterm>Web
+services<indexterm>WSDL reference</indexterm></indexterm></keywords>
+</metadata></prolog>
+<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>
+</reference>
diff --git a/docs/org.eclipse.jst.ws.doc.user/ref/rwsdl.html b/docs/org.eclipse.jst.ws.doc.user/ref/rwsdl.html
new file mode 100644
index 0000000..bade3f6
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/ref/rwsdl.html
@@ -0,0 +1,92 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="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 content="WSDL, reference, Web services, WSDL reference" name="DC.subject" />
+<meta content="WSDL, reference, Web services, WSDL reference" name="keywords" />
+<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/common.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
+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="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/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 class="linklist"><strong>Related Tasks</strong><br />
+
+<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>
+
+</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 0000000..73e8f39
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/ref/rwspref.dita
@@ -0,0 +1,156 @@
+<?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>
+<shortdesc>Before you begin developing Web services or clients, you can optimize
+the workbench for Web services development by setting a variety of preferences.</shortdesc>
+<prolog><metadata>
+<keywords><indexterm>preferences<indexterm>Web services</indexterm></indexterm>
+<indexterm>Web services<indexterm>preferences</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<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> or <uicontrol>Web and XML</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="axisemitterpref">
+<dt>Axis Emitter</dt>
+<dd>This page allows you to set the following preferences used when creating
+or consuming Axis Web services.</dd>
+<dd><b>WSDL2Java</b><ul>
+<li>Generate code for all elements: By default, WSDL2Java only generates code
+for those elements in the WSDL file that are referenced. For additional information
+regarding how referencing works refer to the Axis reference guide: <xref href="http://ws.apache.org/axis/java/reference.html"
+scope="external"></xref></li>
+<li>Emits separate Helper classes for metadata: If you select this option
+WSDL2Java will create a separate helper class that contains the metadata rather
+than including it in the skeleton.</li>
+<li>Prefers building beans to straight arrays for wrapped XML array types:
+The default behavior is to map this XML construct: <codeblock><element name="array">
+ <complexType>
+ <sequence>
+ <element name="item" type="xs:string"/>
+ </sequence>
+ </complexType>
+</element></codeblock>to a Java String array (String[]). If you would rather
+a specific JavaBean class (ArrayOfString) be generated for these types of
+schemas, select this option. </li>
+<li>Add scope to deploy.wsdd: This indicates how to deploy the server implementation.
+Application uses one instance of the implementation class for all requests.
+Request creates a new instance of the implementation class for each request.
+Session creates a new instance of the implementation class for each session.</li>
+<li>Timeout in seconds: The default is 45. Use -1 to disable the timeout.</li>
+</ul></dd>
+<dd><b>Java2WSDL</b><ul>
+<li>Look for allowed methods in inherited class: If this option is specified,
+the Java2WSDL parser will look into extended classes to determine the list
+of methods to export into the WSDL file. </li>
+<li>Analyze the service class for compliance to JAX-RPC before generating
+code: If selected, the tools will examine the Java service class and its value
+types to determine if it satisfies important requirements of the JAX-RPC specification.</li>
+</ul></dd>
+</dlentry><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="wsicompliance">
+<dt>Profile Compliance and Validation</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: <xref href="http://www.ws-i.org/"
+scope="external"></xref></dd>
+<dd>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.</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.<ul>
+<li>Overwrite files without warning: selecting this will allow the wizards
+to overwrite any existing files in the workspace without prompting. If it
+is not selected you will be prompted each time a file needs to be overwritten.</li>
+<li>Create folders when necessary: selecting this enables the wizards to create
+any required folders.</li>
+<li>Check out files without warning: select to check out files without receiving
+a warning message asking for confirmation.</li>
+<li>Merge generated skeleton file: this check box is disabled by default.
+ If this check box is enabled, when a skeleton file of the same name already
+exists in the workspace, the newly generated skeleton file will merge with
+the existing skeleton file. Enable this to preserve code that you have already
+modified in the existing skeleton files.<p>Note that when this preference
+is enabled, if you change the return type of an interface, the resulting skeleton
+file will have a method returning the type as defined in the new interface
+but would have a method body from the original skeleton file (which would
+be returning a different type). This will result in an compilation error
+that the you will have to correct manually.</p></li>
+</ul></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 and client you want to be selected by default.</li>
+<li>which phases of the Web service lifecycle you want to complete in 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 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>
+<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></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>
diff --git a/docs/org.eclipse.jst.ws.doc.user/ref/rwspref.html b/docs/org.eclipse.jst.ws.doc.user/ref/rwspref.html
new file mode 100644
index 0000000..99609e3
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/ref/rwspref.html
@@ -0,0 +1,236 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" />
+<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 name="abstract" content="Before you begin developing Web services or clients, you can optimize the workbench for Web services development by setting a variety of preferences." />
+<meta name="description" content="Before you begin developing Web services or clients, you can optimize the workbench for Web services development by setting a variety of preferences." />
+<meta content="preferences, Web services" name="DC.subject" />
+<meta content="preferences, Web services" name="keywords" />
+<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/common.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><p>Before you begin developing Web services or clients, you can optimize
+the workbench for Web services development by setting a variety of preferences.</p>
+
+<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 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"><a name="rwspref__axisemitterpref"><!-- --></a>Axis Emitter</dt>
+
+<dd>This page allows you to set the following preferences used when creating
+or consuming Axis Web services.</dd>
+
+<dd class="ddexpand"><strong>WSDL2Java</strong><ul>
+<li>Generate code for all elements: By default, WSDL2Java only generates code
+for those elements in the WSDL file that are referenced. For additional information
+regarding how referencing works refer to the Axis reference guide: <a href="http://ws.apache.org/axis/java/reference.html" target="_blank">http://ws.apache.org/axis/java/reference.html</a></li>
+
+<li>Emits separate Helper classes for metadata: If you select this option
+WSDL2Java will create a separate helper class that contains the metadata rather
+than including it in the skeleton.</li>
+
+<li>Prefers building beans to straight arrays for wrapped XML array types:
+The default behavior is to map this XML construct: <pre><element name="array">
+ <complexType>
+ <sequence>
+ <element name="item" type="xs:string"/>
+ </sequence>
+ </complexType>
+</element></pre>
+to a Java String array (String[]). If you would rather
+a specific JavaBean class (ArrayOfString) be generated for these types of
+schemas, select this option. </li>
+
+<li>Add scope to deploy.wsdd: This indicates how to deploy the server implementation.
+Application uses one instance of the implementation class for all requests.
+Request creates a new instance of the implementation class for each request.
+Session creates a new instance of the implementation class for each session.</li>
+
+<li>Timeout in seconds: The default is 45. Use -1 to disable the timeout.</li>
+
+</ul>
+</dd>
+
+<dd class="ddexpand"><strong>Java2WSDL</strong><ul>
+<li>Look for allowed methods in inherited class: If this option is specified,
+the Java2WSDL parser will look into extended classes to determine the list
+of methods to export into the WSDL file. </li>
+
+<li>Analyze the service class for compliance to JAX-RPC before generating
+code: If selected, the tools will examine the Java service class and its value
+types to determine if it satisfies important requirements of the JAX-RPC specification.</li>
+
+</ul>
+</dd>
+
+
+<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"><a name="rwspref__wsicompliance"><!-- --></a>Profile Compliance and Validation</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: <a href="http://www.ws-i.org/" target="_blank">http://www.ws-i.org/</a></dd>
+
+<dd class="ddexpand">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.</dd>
+
+
+<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"><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.<ul>
+<li>Overwrite files without warning: selecting this will allow the wizards
+to overwrite any existing files in the workspace without prompting. If it
+is not selected you will be prompted each time a file needs to be overwritten.</li>
+
+<li>Create folders when necessary: selecting this enables the wizards to create
+any required folders.</li>
+
+<li>Check out files without warning: select to check out files without receiving
+a warning message asking for confirmation.</li>
+
+<li>Merge generated skeleton file: this check box is disabled by default.
+ If this check box is enabled, when a skeleton file of the same name already
+exists in the workspace, the newly generated skeleton file will merge with
+the existing skeleton file. Enable this to preserve code that you have already
+modified in the existing skeleton files.<p>Note that when this preference
+is enabled, if you change the return type of an interface, the resulting skeleton
+file will have a method returning the type as defined in the new interface
+but would have a method body from the original skeleton file (which would
+be returning a different type). This will result in an compilation error
+that the you will have to correct manually.</p>
+</li>
+
+</ul>
+</dd>
+
+
+<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 and client you want to be selected by default.</li>
+
+<li>which phases of the Web service lifecycle you want to complete in 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 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"><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"><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"><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>
+
+</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>
+</div>
+
+<div class="linklist"><strong>Related Concepts</strong><br />
+
+<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 0000000..6e045f5
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/tasks/toverws.dita
@@ -0,0 +1,54 @@
+<?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">
+<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>
+<prolog><metadata>
+<keywords><indexterm>Web services<indexterm>creating<indexterm>overview</indexterm></indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<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">
+<linktext>Creating a new WSDL file</linktext></link>
+<link href="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.dita"
+scope="peer"><linktext>Publishing Web services and business entities</linktext>
+</link>
+</linklist>
+</related-links>
+</task>
diff --git a/docs/org.eclipse.jst.ws.doc.user/tasks/toverws.html b/docs/org.eclipse.jst.ws.doc.user/tasks/toverws.html
new file mode 100644
index 0000000..ce452df
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/tasks/toverws.html
@@ -0,0 +1,87 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="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 content="Web services, creating, overview" name="DC.subject" />
+<meta content="Web services, creating, overview" name="keywords" />
+<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/common.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>
+
+<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
+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" 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>
+<div><a href="../concepts/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="../../org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtwsdl.html">Creating a new 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>
+</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 0000000..46216b6
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/tasks/twsicomply.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="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
+are not WS-I compliant.</shortdesc>
+<prolog><metadata>
+<keywords><indexterm>Web services<indexterm>interoperability compliance</indexterm></indexterm>
+<indexterm>WSI<indexterm>setting compliance</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<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 <b>Profile Compliance and Validation</b>, 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>Profile Compliance and Validation</b> from the component
+tree on the left-hand side of the panel.</cmd></step>
+<step><cmd>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
new file mode 100644
index 0000000..fabf06f
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/tasks/twsicomply.html
@@ -0,0 +1,114 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="Setting the level of WS-I compliance" />
+<meta name="abstract" content="The Web services WS-I validation tools support the level of WS-I compliance outlined in the WS-I Basic Profile 1.1, the WS-I Simple SOAP Binding Profile 1.0 (WS-I SSBP), and the WS-I Attachments Profile 1.0 (WS-I AP). You can choose to make your Web service compliant or non-compliant, depending on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols are not WS-I compliant." />
+<meta name="description" content="The Web services WS-I validation tools support the level of WS-I compliance outlined in the WS-I Basic Profile 1.1, the WS-I Simple SOAP Binding Profile 1.0 (WS-I SSBP), and the WS-I Attachments Profile 1.0 (WS-I AP). You can choose to make your Web service compliant or non-compliant, depending on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols are not WS-I compliant." />
+<meta content="Web services, interoperability compliance, WSI, setting compliance" name="DC.subject" />
+<meta content="Web services, interoperability compliance, WSI, setting compliance" name="keywords" />
+<meta content="XHTML" name="DC.Format" />
+<meta content="twsicomply" name="DC.Identifier" />
+<meta content="en-us" name="DC.Language" />
+<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
+<title>Setting the level of WS-I compliance</title>
+</head>
+<body id="twsicomply"><a name="twsicomply"><!-- --></a>
+
+
+<h1 class="topictitle1">Setting the level of WS-I compliance</h1>
+
+
+
+<div><p>The Web services WS-I validation tools support the level of WS-I
+compliance outlined in the WS-I Basic Profile 1.1, the WS-I Simple SOAP Binding
+Profile 1.0 (WS-I SSBP), and the WS-I Attachments Profile 1.0 (WS-I AP). You
+can choose to make your Web service compliant or non-compliant, depending
+on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols
+are not WS-I compliant.</p>
+
+<div class="section"><p>You can set the level of compliance for either the Basic Profile
+and the Simple SOAP Binding Profile, or for the Attachments Profile. You can
+select from three levels of compliance with WS-I specifications:</p>
+<ul>
+<li>Require WS-I compliance - this level prevents you from creating a non-compliant
+Web service.</li>
+
+<li>Suggest WS-I compliance - this level allows you to create a non-compliant
+Web service, but provides a visible warning stating how the service is non-compliant.</li>
+
+<li>Ignore WS-I compliance - this level allows you to create a non-compliant
+Web service and does not notify you of non-compliance.</li>
+
+</ul>
+<p>You can set the level of WS-I compliance at the workspace level, or
+at the project level.</p>
+</div>
+
+</div>
+
+<div class="nested1" xml:lang="en-us" id="sdgfsdgs"><a name="sdgfsdgs"><!-- --></a>
+<h2 class="topictitle2">Set the level of WS-I compliance for the workspace</h2>
+
+<div>
+<div class="section"><p>To set the level of WS-I compliance for the workspace:</p>
+</div>
+
+<ol>
+<li><span>From the <strong>Window</strong> menu, select <strong>Preferences</strong>.</span>
+</li>
+
+<li><span>Select <strong>Web Services</strong> from the component tree on the left-hand
+side of the panel.</span></li>
+
+<li><span>Under <strong>Profile Compliance and Validation</strong>, select the level
+of compliance you want from the drop-down lists.</span></li>
+
+<li><span>Click <strong>Apply</strong>, then click <strong>OK</strong>.</span></li>
+
+</ol>
+
+</div>
+
+</div>
+
+<div class="nested1" xml:lang="en-us" id="xvgdsgfsg"><a name="xvgdsgfsg"><!-- --></a>
+<h2 class="topictitle2">Set the level of WS-I compliance for a project</h2>
+
+<div>
+<div class="section"><p>To set the level of WS-I compliance for a project:</p>
+</div>
+
+<ol>
+<li><span>In the Project Navigator, right click and select <strong>Properties</strong>.</span>
+</li>
+
+<li><span>Select <strong>Profile Compliance and Validation</strong> from the component
+tree on the left-hand side of the panel.</span></li>
+
+<li><span>Select the level of compliance you want from the drop-down lists,
+or select to have the project share the same level of WS-I compliance as the
+workspace</span></li>
+
+<li><span>Click <strong>Apply</strong>, then click <strong>OK</strong>.</span></li>
+
+</ol>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related Concepts</strong><br />
+
+<div><a href="../concepts/cwsiover.html" title="WS-I is an organization designed to promote Web service interoperability across platforms, operating systems, and programming languages.">Web services interoperability (WS-I)</a></div></div>
+</div>
+</div>
+
+
+</body>
+</html>
\ 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 0000000..8ea946c
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/webservice_toc.ditamap
@@ -0,0 +1,91 @@
+<?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">
+<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>
+<anchor id="extending_ws_client_creation"/></topicref>
+<navref mapref="../org.eclipse.wst.command.env.doc.user/wsaxisant_toc.ditamap"/>
+</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
new file mode 100644
index 0000000..b5d76c3
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.doc.user/webservice_toc.xml
@@ -0,0 +1,62 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<?NLS TYPE="org.eclipse.help.toc"?>
+
+<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="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="Developing 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"/>
+<anchor id="extending_ws_client_creation"/>
+</topic>
+<link toc="../org.eclipse.wst.command.env.doc.user/wsaxisant_toc.xml"/>
+</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.jst.ws.infopop/.cvsignore b/docs/org.eclipse.jst.ws.infopop/.cvsignore
new file mode 100644
index 0000000..c14487c
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.infopop/.cvsignore
@@ -0,0 +1 @@
+build.xml
diff --git a/docs/org.eclipse.jst.ws.infopop/.project b/docs/org.eclipse.jst.ws.infopop/.project
new file mode 100644
index 0000000..e6b5d69
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.infopop/.project
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.jst.ws.infopop</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ <buildCommand>
+ <name>org.eclipse.pde.ManifestBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.pde.SchemaBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ </buildSpec>
+ <natures>
+ <nature>org.eclipse.pde.PluginNature</nature>
+ </natures>
+</projectDescription>
diff --git a/docs/org.eclipse.jst.ws.infopop/META-INF/MANIFEST.MF b/docs/org.eclipse.jst.ws.infopop/META-INF/MANIFEST.MF
new file mode 100644
index 0000000..c29c76a
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.infopop/META-INF/MANIFEST.MF
@@ -0,0 +1,7 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: %Bundle-Name.0
+Bundle-SymbolicName: org.eclipse.jst.ws.infopop; singleton:=true
+Bundle-Version: 1.0.203.qualifier
+Bundle-Vendor: %Bundle-Vendor.0
+Bundle-Localization: plugin
diff --git a/docs/org.eclipse.jst.ws.infopop/about.html b/docs/org.eclipse.jst.ws.infopop/about.html
new file mode 100644
index 0000000..73db36e
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.infopop/about.html
@@ -0,0 +1,34 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<HTML>
+
+<head>
+<title>About</title>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+</head>
+
+<BODY lang="EN-US">
+
+<H3>About This Content</H3>
+
+<P>June 06, 2007</P>
+
+<H3>License</H3>
+
+<P>The Eclipse Foundation makes available all content in this plug-in
+("Content"). Unless otherwise indicated below, the Content is provided to you
+under the terms and conditions of the Eclipse Public License Version 1.0
+("EPL"). A copy of the EPL is available at
+<A href="http://www.eclipse.org/org/documents/epl-v10.php">http://www.eclipse.org/org/documents/epl-v10.php</A>.
+For purposes of the EPL, "Program" will mean the Content.</P>
+
+<P>If you did not receive this Content directly from the Eclipse Foundation, the
+Content is being redistributed by another party ("Redistributor") and different
+terms and conditions may apply to your use of any object code in the Content.
+Check the Redistributors license that was provided with the Content. If no such
+license exists, contact the Redistributor. Unless otherwise indicated below, the
+terms and conditions of the EPL still apply to any source code in the Content
+and such source code may be obtained at
+<A href="http://www.eclipse.org/">http://www.eclipse.org/</A>.</P>
+
+</BODY>
+</HTML>
diff --git a/docs/org.eclipse.jst.ws.infopop/build.properties b/docs/org.eclipse.jst.ws.infopop/build.properties
new file mode 100644
index 0000000..27bfb4e
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.infopop/build.properties
@@ -0,0 +1,5 @@
+bin.includes = plugin.xml,\
+ webserviceui-f1Contexts.xml,\
+ about.html,\
+ META-INF/,\
+ plugin.properties
diff --git a/docs/org.eclipse.jst.ws.infopop/plugin.properties b/docs/org.eclipse.jst.ws.infopop/plugin.properties
new file mode 100644
index 0000000..3611afc
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.infopop/plugin.properties
@@ -0,0 +1,3 @@
+# properties file for org.eclipse.jst.ws.infopop
+Bundle-Vendor.0 = Eclipse.org
+Bundle-Name.0 = Web services UI
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.ws.infopop/plugin.xml b/docs/org.eclipse.jst.ws.infopop/plugin.xml
new file mode 100644
index 0000000..03e4a94
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.infopop/plugin.xml
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?eclipse version="3.0"?>
+<?NLS TYPE="org.eclipse.help.toc"?>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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.contexts">
+ <contexts file="webserviceui-f1Contexts.xml" plugin="org.eclipse.jst.ws.ui"/>
+ </extension>
+</plugin>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.ws.infopop/webserviceui-f1Contexts.xml b/docs/org.eclipse.jst.ws.infopop/webserviceui-f1Contexts.xml
new file mode 100644
index 0000000..e7981de
--- /dev/null
+++ b/docs/org.eclipse.jst.ws.infopop/webserviceui-f1Contexts.xml
@@ -0,0 +1,116 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?NLS TYPE="org.eclipse.help.contexts"?>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<contexts>
+
+<!--DRES: Resource Selection Dialog-->
+<context id="DRES0001">
+<!--Resource Type drop down-->
+<description>Select a resource from which to create a Web service.</description>
+</context>
+<context id="DRES0002">
+<!--Resource tree-->
+<description>Lists the resources that can be turned into a Web service.</description>
+</context>
+
+<!--PPRM: Resource Management Preference page-->
+
+<context id="PPRM0001">
+<!--main page-->
+<description>The Resource Management preferences enable you to determine the defaults that you want to use when creating your Web service.</description>
+</context>
+
+<context id="PPRM0002">
+<!--File overwrite check box-->
+<description>This checkbox allows you to overwrite files without receiving a warning message asking for confirmation when overwriting files.</description>
+</context>
+<context id="PPRM0003">
+<!--Create folders check box-->
+<description>Select this checkbox to create folders and folder structures without receiving a warning message asking for confirmation.</description>
+</context>
+<context id="PPRM0004">
+<!--Check out files check box-->
+<description>Select this checkbox to check out files without receiving a warning message asking for confirmation.</description>
+</context>
+
+<context id="PPRM0005">
+<!--Skeleton merge-->
+<description>This check box is disabled by default. If this check box is enabled, when a skeleton
+file of the same name already exists in the workspace, the newly generated skeleton file will merge
+with the existing skeleton file. Enable this to preserve code that you have already modified in the
+existing skeleton files.
+<br />
+Note that when this preference is enabled, if you change the return type
+of an interface, the resulting skeleton file will have a method returning the
+type as defined in the new interface but would have a method body from the
+original skeleton file (which would be returning a different type). This will
+result in an compilation error that the you will have to correct manually.
+
+</description>
+</context>
+
+<!--PPSD: Scenario Defaults Preference page-->
+
+<!--ScenarioDefaultsPreferencePage.java-->
+<context id="PPSD0001">
+<!--PPSD0001 for the Scenario Defaults Preference Page-->
+<description>Use this page to select the default settings for the Web services wizard.</description>
+</context>
+<context id="PPSD0002">
+<!--PPSD0002 for the launch sample check box on the Scenario Defaults Preference Page-->
+<description>The Scenario Defaults preferences enable you to determine the defaults that you want to use when creating your Web service. The sample Web application demonstrates how to code the proxy file. Select this check box to launch sample application after it is created.</description>
+</context>
+<context id="PPSD0004">
+<!--PPSD0004 for the sample JSP type combo box on the Scenario Defaults Preference Page-->
+<description>Select the type of sample JSP to be created.</description>
+</context>
+<context id="PPSD0003">
+<!--PPSD0003 for the web explorer type combo box on the Scenario Defaults Preference Page-->
+<description>The Scenario Defaults preferences enable you to determine the defaults that you want to use when creating your Web service. Select from the available Web services explorers.</description>
+</context>
+<context id="PPSD0005">
+<!--PPSD0005 for the User-defined UDDI Category Data Column Delimiter text field on the Scenario Defaults Preference Page-->
+<description>Enter the character you want to use as a column delimiter for user-defined UDDI Category data.</description>
+</context>
+<context id="PPSD0006">
+<!--PPSD0006 for the User-defined UDDI Category Data String Delimiter text field on the Scenario Defaults Preference Page-->
+<description>Enter the character you want to use as a string delimiter for user-defined UDDI Category data.</description>
+</context>
+
+
+<context id="PPAD0004">
+<!-- Hide generate client check box-->
+<description>Select this check box to hide the option of generating a Web service client when you right-click a file in the Project Explorer or Navigator.</description>
+</context>
+
+<context id="PPAD0005">
+<!-- Hide generate sample check box-->
+<description>Select this check box to hide the option of generating sample JSP code for the Web service when you right-click a file in the Project Explorer or Navigator.</description>
+</context>
+
+<context id="PPAD0006">
+<!-- create web service check box-->
+<description>Select this check box to hide the option of generating a Web service client when you right-click a file in the Project Explorer or Navigator.</description>
+</context>
+
+<context id="PPAD0008">
+<!-- generate skeleton check box-->
+<description>Select this check box to hide the option of generating skeleton Java classes when you right-click a file in the Project Explorer or Navigator. 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.</description>
+</context>
+
+<context id="PPAD0009">
+<!-- publish WSDL check box-->
+<description>Select this check box to hide the option of publishing the Web service's WSDL file to a UDDI registry when you right-click a file in the Project Explorer or Navigator.</description>
+</context>
+
+
+</contexts>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.command.env.doc.user/.cvsignore b/docs/org.eclipse.wst.command.env.doc.user/.cvsignore
new file mode 100644
index 0000000..a84668c
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/.cvsignore
@@ -0,0 +1,3 @@
+org.eclipse.wst.command.env.doc.user_1.0.0.jar
+bak
+temp
diff --git a/docs/org.eclipse.wst.command.env.doc.user/.project b/docs/org.eclipse.wst.command.env.doc.user/.project
new file mode 100644
index 0000000..ff3950b
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/.project
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.wst.command.env.doc.user</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ <buildCommand>
+ <name>org.eclipse.pde.ManifestBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.pde.SchemaBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ </buildSpec>
+ <natures>
+ <nature>org.eclipse.pde.PluginNature</nature>
+ </natures>
+</projectDescription>
diff --git a/docs/org.eclipse.wst.command.env.doc.user/DocBuild.xml b/docs/org.eclipse.wst.command.env.doc.user/DocBuild.xml
new file mode 100644
index 0000000..b6540fe
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/DocBuild.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.2" />
+
+ <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="wsaxisant_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.command.env.doc.user/META-INF/MANIFEST.MF b/docs/org.eclipse.wst.command.env.doc.user/META-INF/MANIFEST.MF
new file mode 100644
index 0000000..626b66d
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/META-INF/MANIFEST.MF
@@ -0,0 +1,8 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: %pluginName
+Bundle-SymbolicName: org.eclipse.wst.command.env.doc.user;singleton:=true
+Bundle-Version: 1.5.1.qualifier
+Bundle-Vendor: %pluginProvider
+Bundle-Localization: plugin
+Eclipse-LazyStart: true
diff --git a/docs/org.eclipse.wst.command.env.doc.user/about.html b/docs/org.eclipse.wst.command.env.doc.user/about.html
new file mode 100644
index 0000000..73db36e
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/about.html
@@ -0,0 +1,34 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<HTML>
+
+<head>
+<title>About</title>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+</head>
+
+<BODY lang="EN-US">
+
+<H3>About This Content</H3>
+
+<P>June 06, 2007</P>
+
+<H3>License</H3>
+
+<P>The Eclipse Foundation makes available all content in this plug-in
+("Content"). Unless otherwise indicated below, the Content is provided to you
+under the terms and conditions of the Eclipse Public License Version 1.0
+("EPL"). A copy of the EPL is available at
+<A href="http://www.eclipse.org/org/documents/epl-v10.php">http://www.eclipse.org/org/documents/epl-v10.php</A>.
+For purposes of the EPL, "Program" will mean the Content.</P>
+
+<P>If you did not receive this Content directly from the Eclipse Foundation, the
+Content is being redistributed by another party ("Redistributor") and different
+terms and conditions may apply to your use of any object code in the Content.
+Check the Redistributors license that was provided with the Content. If no such
+license exists, contact the Redistributor. Unless otherwise indicated below, the
+terms and conditions of the EPL still apply to any source code in the Content
+and such source code may be obtained at
+<A href="http://www.eclipse.org/">http://www.eclipse.org/</A>.</P>
+
+</BODY>
+</HTML>
diff --git a/docs/org.eclipse.wst.command.env.doc.user/build.properties b/docs/org.eclipse.wst.command.env.doc.user/build.properties
new file mode 100644
index 0000000..2774ce3
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/build.properties
@@ -0,0 +1,13 @@
+bin.includes = plugin.properties,\
+ plugin.xml,\
+ wsaxisant_toc.xml,\
+ about.html,\
+ topics/*.htm*,\
+ index/,\
+ META-INF/
+src.includes = build.properties,\
+ *.maplist,\
+ *.ditamap,\
+ topics/*.dita
+bin.excludes = DocBuild.xml,\
+ myPlugin*.xml
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.command.env.doc.user/index/_6.cfs b/docs/org.eclipse.wst.command.env.doc.user/index/_6.cfs
new file mode 100644
index 0000000..a592a1f
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/index/_6.cfs
Binary files differ
diff --git a/docs/org.eclipse.wst.command.env.doc.user/index/deletable b/docs/org.eclipse.wst.command.env.doc.user/index/deletable
new file mode 100644
index 0000000..e423242
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/index/deletable
Binary files differ
diff --git a/docs/org.eclipse.wst.command.env.doc.user/index/indexed_contributions b/docs/org.eclipse.wst.command.env.doc.user/index/indexed_contributions
new file mode 100644
index 0000000..55570d0
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/index/indexed_contributions
@@ -0,0 +1,3 @@
+#This is a generated file; do not edit.
+#Wed May 09 14:13:58 EDT 2007
+org.eclipse.wst.command.env.doc.user=org.eclipse.wst.command.env.doc.user\n1.5.0.qualifier
diff --git a/docs/org.eclipse.wst.command.env.doc.user/index/indexed_dependencies b/docs/org.eclipse.wst.command.env.doc.user/index/indexed_dependencies
new file mode 100644
index 0000000..6b9de52
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/index/indexed_dependencies
@@ -0,0 +1,4 @@
+#This is a generated file; do not edit.
+#Wed May 09 14:13:58 EDT 2007
+lucene=1.4.103.v20060601
+analyzer=org.eclipse.help.base\#3.2.0.v20060601?locale\=en
diff --git a/docs/org.eclipse.wst.command.env.doc.user/index/indexed_docs b/docs/org.eclipse.wst.command.env.doc.user/index/indexed_docs
new file mode 100644
index 0000000..64a6cb0
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/index/indexed_docs
@@ -0,0 +1,8 @@
+#This is a generated file; do not edit.
+#Wed May 09 14:13:58 EDT 2007
+/org.eclipse.wst.command.env.doc.user/topics/rbuwsa.html=0
+/org.eclipse.wst.command.env.doc.user/topics/twbwsa.html=0
+/org.eclipse.wst.command.env.doc.user/topics/rtdwsa.html=0
+/org.eclipse.wst.command.env.doc.user/topics/rwsclienta.html=0
+/org.eclipse.wst.command.env.doc.user/topics/twbwsclienta.html=0
+/org.eclipse.wst.command.env.doc.user/topics/cwsaxisant.html=0
diff --git a/docs/org.eclipse.wst.command.env.doc.user/index/segments b/docs/org.eclipse.wst.command.env.doc.user/index/segments
new file mode 100644
index 0000000..19b5d0c
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/index/segments
Binary files differ
diff --git a/docs/org.eclipse.wst.command.env.doc.user/myplugin.xml b/docs/org.eclipse.wst.command.env.doc.user/myplugin.xml
new file mode 100644
index 0000000..9f59873
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/myplugin.xml
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?eclipse version="3.0"?>
+<?NLS TYPE="org.eclipse.help.toc"?>
+
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2007 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * IBM Corporation - initial API and implementation
+ *******************************************************************************/ -->
+
+<plugin>
+ <extension
+ point="org.eclipse.help.toc">
+ <toc file="wsaxisant_toc.xml" />
+ <index path="index/"/>
+ </extension>
+
+</plugin>
diff --git a/docs/org.eclipse.wst.command.env.doc.user/org.eclipse.wst.command.env.doc.user.maplist b/docs/org.eclipse.wst.command.env.doc.user/org.eclipse.wst.command.env.doc.user.maplist
new file mode 100644
index 0000000..265f263
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/org.eclipse.wst.command.env.doc.user.maplist
@@ -0,0 +1,8 @@
+<maplist version="3.6.2">
+ <nav>
+ <map file="wsaxisant_toc.ditamap"/>
+ </nav>
+ <link>
+ <map file="wsaxisant_toc.ditamap"/>
+ </link>
+</maplist>
diff --git a/docs/org.eclipse.wst.command.env.doc.user/plugin.properties b/docs/org.eclipse.wst.command.env.doc.user/plugin.properties
new file mode 100644
index 0000000..c5c2dac
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/plugin.properties
@@ -0,0 +1,15 @@
+###############################################################################
+# Copyright (c) 2001, 2006 IBM Corporation and others.
+# All rights reserved. This program and the accompanying materials
+# are made available under the terms of the Eclipse Public License v1.0
+# which accompanies this distribution, and is available at
+# http://www.eclipse.org/legal/epl-v10.html
+#
+# Contributors:
+# IBM Corporation - initial API and implementation
+###############################################################################
+# NLS_MESSAGEFORMAT_VAR
+# NLS_ENCODING=UTF-8
+
+pluginName = Web services Axis Ant task documentation
+pluginProvider = Eclipse.org
diff --git a/docs/org.eclipse.wst.command.env.doc.user/plugin.xml b/docs/org.eclipse.wst.command.env.doc.user/plugin.xml
new file mode 100644
index 0000000..9f59873
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/plugin.xml
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?eclipse version="3.0"?>
+<?NLS TYPE="org.eclipse.help.toc"?>
+
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2007 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * IBM Corporation - initial API and implementation
+ *******************************************************************************/ -->
+
+<plugin>
+ <extension
+ point="org.eclipse.help.toc">
+ <toc file="wsaxisant_toc.xml" />
+ <index path="index/"/>
+ </extension>
+
+</plugin>
diff --git a/docs/org.eclipse.wst.command.env.doc.user/topics/cwsaxisant.dita b/docs/org.eclipse.wst.command.env.doc.user/topics/cwsaxisant.dita
new file mode 100644
index 0000000..62cf826
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/topics/cwsaxisant.dita
@@ -0,0 +1,45 @@
+<?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="creatingawebservicefromajavabean" xml:lang="en-us">
+<title>Creating Axis runtime environment Web services and clients using Web
+services Ant tasks</title>
+<titlealts>
+<searchtitle>Creating Axis runtime environment Web services and clients using
+Ant tasks</searchtitle>
+</titlealts>
+<shortdesc>If you prefer not to use the Web service wizard, you can use Ant
+files to create Web services and clients using the Axis runtime environment.
+The Web services Ant tasks can be run in two ways: through the Eclipse workspace
+using <menucascade><uicontrol>Run As</uicontrol><uicontrol>Ant Build...</uicontrol>
+</menucascade>, or they can be run headless through the command line. Once
+you have created your Web service, you can then deploy it to a server, test
+it, and publish it as a business entity or business service.</shortdesc>
+<conbody>
+<section><title>Prerequisites</title><p>Before you create a Web service or
+client using the Ant tasks, you need to complete a few prerequisites.</p><ul>
+<li>Install Apache Tomcat, create a server, and create a dynamic Web project
+associated with that server as described in <xref href="../../org.eclipse.jst.ws.axis.ui.doc.user/tasks/ttomcatserv.dita">Creating
+an Apache Tomcat server and Web project</xref></li>
+<li>Import the required Ant files into your workspace:<ol>
+<li>Create a project.</li>
+<li>Import the required Ant files. Select <menucascade><uicontrol>File</uicontrol>
+<uicontrol>New</uicontrol><uicontrol>Other</uicontrol><uicontrol>Web Services</uicontrol>
+<uicontrol>Ant Files</uicontrol><uicontrol>Next</uicontrol></menucascade>.</li>
+<li>Select the project you created, and click <uicontrol>Finish</uicontrol>.</li>
+</ol>Three files will be imported into this project:<ul>
+<li>wsgen.xml - this is the Ant file.</li>
+<li>axisservice.properties - this is a sample Ant properties file referenced
+by the Ant file. You can modify the properties in this file to generate a
+Web service.</li>
+<li>axisclient.properties - this is a sample Ant properties file referenced
+by the Ant file. You can modify the properties in this file to generate a
+Web service client.</li>
+</ul></li>
+<li>Create a dynamic Web project for the Web service or client.</li>
+</ul></section>
+<section><title>Creating a Web service or client</title><p>Once you've completed
+the prerequisites you can do the following:</p></section>
+</conbody>
+</concept>
diff --git a/docs/org.eclipse.wst.command.env.doc.user/topics/cwsaxisant.html b/docs/org.eclipse.wst.command.env.doc.user/topics/cwsaxisant.html
new file mode 100644
index 0000000..7faac23
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/topics/cwsaxisant.html
@@ -0,0 +1,90 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" />
+<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 Axis runtime environment Web services and clients using Web services Ant tasks" />
+<meta name="abstract" content="If you prefer not to use the Web service wizard, you can use Ant files to create Web services and clients using the Axis runtime environment. The Web services Ant tasks can be run in two ways: through the Eclipse workspace using Run As > Ant Build..., or they can be run headless through the command line. Once you have created your Web service, you can then deploy it to a server, test it, and publish it as a business entity or business service." />
+<meta name="description" content="If you prefer not to use the Web service wizard, you can use Ant files to create Web services and clients using the Axis runtime environment. The Web services Ant tasks can be run in two ways: through the Eclipse workspace using Run As > Ant Build..., or they can be run headless through the command line. Once you have created your Web service, you can then deploy it to a server, test it, and publish it as a business entity or business service." />
+<meta scheme="URI" name="DC.Relation" content="../topics/twbwsa.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/twbwsclienta.html" />
+<meta content="XHTML" name="DC.Format" />
+<meta content="creatingawebservicefromajavabean" name="DC.Identifier" />
+<meta content="en-us" name="DC.Language" />
+<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
+<title>Creating Axis runtime environment Web services and clients using
+Ant tasks</title>
+</head>
+<body id="creatingawebservicefromajavabean"><a name="creatingawebservicefromajavabean"><!-- --></a>
+
+
+<h1 class="topictitle1">Creating Axis runtime environment Web services and clients using Web
+services Ant tasks</h1>
+
+
+
+<div><p>If you prefer not to use the Web service wizard, you can use Ant
+files to create Web services and clients using the Axis runtime environment.
+The Web services Ant tasks can be run in two ways: through the Eclipse workspace
+using <span class="menucascade"><span class="uicontrol">Run As</span> > <span class="uicontrol">Ant Build...</span>
+</span>, or they can be run headless through the command line. Once
+you have created your Web service, you can then deploy it to a server, test
+it, and publish it as a business entity or business service.</p>
+
+<div class="section"><h4 class="sectiontitle">Prerequisites</h4><p>Before you create a Web service or
+client using the Ant tasks, you need to complete a few prerequisites.</p>
+<ul>
+<li>Install Apache Tomcat, create a server, and create a dynamic Web project
+associated with that server as described in <a href="../../org.eclipse.jst.ws.axis.ui.doc.user/tasks/ttomcatserv.html">Creating an Apache Tomcat server and Web project</a></li>
+
+<li>Import the required Ant files into your workspace:<ol>
+<li>Create a project.</li>
+
+<li>Import the required Ant files. Select <span class="menucascade"><span class="uicontrol">File</span>
+ > <span class="uicontrol">New</span> > <span class="uicontrol">Other</span> > <span class="uicontrol">Web Services</span>
+ > <span class="uicontrol">Ant Files</span> > <span class="uicontrol">Next</span></span>.</li>
+
+<li>Select the project you created, and click <span class="uicontrol">Finish</span>.</li>
+
+</ol>
+Three files will be imported into this project:<ul>
+<li>wsgen.xml - this is the Ant file.</li>
+
+<li>axisservice.properties - this is a sample Ant properties file referenced
+by the Ant file. You can modify the properties in this file to generate a
+Web service.</li>
+
+<li>axisclient.properties - this is a sample Ant properties file referenced
+by the Ant file. You can modify the properties in this file to generate a
+Web service client.</li>
+
+</ul>
+</li>
+
+<li>Create a dynamic Web project for the Web service or client.</li>
+
+</ul>
+</div>
+
+<div class="section"><h4 class="sectiontitle">Creating a Web service or client</h4><p>Once you've completed
+the prerequisites you can do the following:</p>
+</div>
+
+</div>
+
+<div>
+<ul class="ullinks">
+<li class="ulchildlink"><strong><a href="../topics/twbwsa.html">Creating a Web service using Ant tasks in the Workbench</a></strong><br />
+You can use Ant through the Eclipse workspace to generate a Web service using the Axis run-time environment. Both top-down and bottom-up Web services development is supported with the Ant tasks.</li>
+<li class="ulchildlink"><strong><a href="../topics/twbwsclienta.html">Creating a Web service client using Ant tasks</a></strong><br />
+If you have a WSDL file you can use Ant through the Eclipse workspace to generate a Web service client using the Axis run-time environment.</li>
+</ul>
+</div>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.command.env.doc.user/topics/rbuwsa.dita b/docs/org.eclipse.wst.command.env.doc.user/topics/rbuwsa.dita
new file mode 100644
index 0000000..c04dafa
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/topics/rbuwsa.dita
@@ -0,0 +1,99 @@
+<?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="bottom-upaxiswebservicecommandlinereference" xml:lang="en-us">
+<title>Bottom-up Axis Web service Ant task properties file reference</title>
+<shortdesc>The <userinput>axisservice.properties</userinput> file is used
+to pass data to the Web services Ant tasks when creating an Axis Web service
+. This file shows the available options.</shortdesc>
+<refbody>
+<section><title>Parameters</title><parml><plentry>
+<pt>ScenarioType</pt>
+<pd><synph> Options: <codeph>service</codeph> </synph></pd>
+<pd>This is a required element that tells the Ant task if it is creating a
+Web service or a Web service client.</pd>
+</plentry><plentry>
+<pt>InitialSelection</pt>
+<pd>Enter the workspace relative URI to the WSDL file or Java bean within
+your workspace. For example <userinput>/dynamicWebProjectName/WebContent/myService.wsdl</userinput> or <userinput>/dynamicWebProjectName/src/myBean.java</userinput
+></pd>
+</plentry><plentry>
+<pt>ListRuntimes</pt>
+<pd><synph> Options: <codeph>true</codeph> <codeph>false</codeph></synph></pd>
+<pd>If <codeph>true</codeph> is selected, the list of valid runtime options
+will be provided when the Ant task is run.</pd>
+</plentry><plentry>
+<pt>ListServers</pt>
+<pd><synph> Options: <codeph>true</codeph> <codeph>false</codeph></synph></pd>
+<pd>If <codeph>true</codeph> is selected, the list of valid server options
+will be provided when the Ant task is run.</pd>
+</plentry><plentry>
+<pt>Service.RuntimeId</pt>
+<pd>This is the ID of the Web service's runtime. This parameter should not
+be modified.</pd>
+</plentry><plentry>
+<pt>Service.ServerId</pt>
+<pd>Options:<sl>
+<sli><codeph>org.eclipse.jst.server.tomcat.x</codeph> (where <codeph>x</codeph> is <codeph>32,
+40, 41, 50,</codeph> or <codeph>55</codeph>)</sli>
+<sli><codeph>org.eclipse.jst.server.generic.weblogicx</codeph> (where <codeph>x</codeph> is <codeph>81</codeph> or <codeph>90</codeph>) </sli>
+<sli><codeph>org.eclipse.jst.server.generic.jbossx</codeph> (where <codeph>x</codeph> is <codeph>323</codeph> or <codeph>4</codeph>)</sli>
+<sli><codeph>org.eclipse.jst.server.generic.jonas4</codeph></sli>
+<sli><codeph>org.eclipse.jst.server.generic.oracle1013</codeph></sli>
+<sli><codeph>org.eclipse.jst.servers.websphere.6</codeph></sli>
+</sl></pd>
+<pd>This is the ID of the target server. Delete or comment out this parameter
+to have the Ant task select the correct value based on the server settings
+of the dynamic Web project.</pd>
+</plentry><plentry>
+<pt>ServiceProjectName</pt>
+<pd>By default the service project is given the name of the WSDL file or Java
+bean from which it is created. Use this parameter to create the service project
+with a different name.</pd>
+</plentry><plentry>
+<pt>ServiceEarProjectName</pt>
+<pd>By default the service EAR project is given the name of the WSDL file
+or Java bean from which it is created. Use this parameter to create the service
+EAR project with a different name.</pd>
+</plentry><plentry>
+<pt>Mappings</pt>
+<pd>Enter the workspace relative URI to a property file containing mappings.</pd>
+<pd>Mappings are used to override the default namespace names in the generated
+WSDL. The content of the properties file must be of the format package = namespace </pd>
+</plentry><plentry>
+<pt>JavaOutput</pt>
+<pd>Enter the workspace relative URI to an existing Java source folder for
+the generated Java code.</pd>
+</plentry><plentry>
+<pt>Methods</pt>
+<pd>Use this parameter to limit which methods are exposed in the service.
+It must be in the form of a space delimited string of method signatures. For
+example, <userinput>method1(parmType1) method2(parmType2)</userinput>. If
+no list is provided, all methods are exposed. </pd>
+</plentry><plentry>
+<pt>Style</pt>
+<pd><synph> Options: <codeph>DOCUMENT</codeph> <codeph>RPC</codeph> <codeph>WRAPPED</codeph></synph></pd>
+<pd>Select the SOAP message style. The default is <codeph>DOCUMENT</codeph>.</pd>
+</plentry><plentry>
+<pt>Use</pt>
+<pd><synph> Options: <codeph>LITERAL</codeph> <codeph>ENCODED</codeph></synph></pd>
+<pd>Select if the SOAP message will be literal or encoded. The default is <codeph>LITERAL</codeph>.</pd>
+</plentry><plentry>
+<pt>OverwriteFilesEnabled</pt>
+<pd><synph> Options: <codeph>true</codeph> <codeph>false</codeph></synph></pd>
+<pd>Use this parameter to tell the Ant task to overwrite any file that it
+creates with the same name as an existing file. By default this is set to <codeph>true</codeph>.</pd>
+</plentry><plentry>
+<pt>CreateFoldersEnabled</pt>
+<pd><synph> Options: <codeph>true</codeph> <codeph>false</codeph></synph></pd>
+<pd>Use this parameter to tell the Ant task to create any neccessary folders.
+By default this is set to <codeph>true</codeph>.</pd>
+</plentry><plentry>
+<pt>CheckoutFilesEnabled</pt>
+<pd><synph> Options: <codeph>true</codeph> <codeph>false</codeph></synph></pd>
+<pd>Use this parameter to tell the Ant task to checkout files from CVS without
+prompting you. By default this is set to <codeph>true</codeph>.</pd>
+</plentry></parml></section>
+</refbody>
+</reference>
diff --git a/docs/org.eclipse.wst.command.env.doc.user/topics/rbuwsa.html b/docs/org.eclipse.wst.command.env.doc.user/topics/rbuwsa.html
new file mode 100644
index 0000000..75c4329
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/topics/rbuwsa.html
@@ -0,0 +1,177 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" />
+<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="Bottom-up Axis Web service Ant task properties file reference" />
+<meta name="abstract" content="The axisservice.properties file is used to pass data to the Web services Ant tasks when creating an Axis Web service . This file shows the available options." />
+<meta name="description" content="The axisservice.properties file is used to pass data to the Web services Ant tasks when creating an Axis Web service . This file shows the available options." />
+<meta scheme="URI" name="DC.Relation" content="../topics/twbwsa.html" />
+<meta content="XHTML" name="DC.Format" />
+<meta content="bottom-upaxiswebservicecommandlinereference" name="DC.Identifier" />
+<meta content="en-us" name="DC.Language" />
+<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
+<title>Bottom-up Axis Web service Ant task properties file reference</title>
+</head>
+<body id="bottom-upaxiswebservicecommandlinereference"><a name="bottom-upaxiswebservicecommandlinereference"><!-- --></a>
+
+
+<h1 class="topictitle1">Bottom-up Axis Web service Ant task properties file reference</h1>
+
+
+<div><p>The <kbd class="userinput">axisservice.properties</kbd> file is used
+to pass data to the Web services Ant tasks when creating an Axis Web service
+. This file shows the available options.</p>
+
+<div class="section"><h4 class="sectiontitle">Parameters</h4><dl>
+<dt class="dlterm">ScenarioType</dt>
+
+<dd><span class="synph"> Options: <samp class="codeph">service</samp> </span></dd>
+
+<dd class="ddexpand">This is a required element that tells the Ant task if it is creating a
+Web service or a Web service client.</dd>
+
+
+<dt class="dlterm">InitialSelection</dt>
+
+<dd>Enter the workspace relative URI to the WSDL file or Java bean within
+your workspace. For example <kbd class="userinput">/dynamicWebProjectName/WebContent/myService.wsdl</kbd> or <kbd class="userinput">/dynamicWebProjectName/src/myBean.java</kbd></dd>
+
+
+<dt class="dlterm">ListRuntimes</dt>
+
+<dd><span class="synph"> Options: <samp class="codeph">true</samp> <samp class="codeph">false</samp></span></dd>
+
+<dd class="ddexpand">If <samp class="codeph">true</samp> is selected, the list of valid runtime options
+will be provided when the Ant task is run.</dd>
+
+
+<dt class="dlterm">ListServers</dt>
+
+<dd><span class="synph"> Options: <samp class="codeph">true</samp> <samp class="codeph">false</samp></span></dd>
+
+<dd class="ddexpand">If <samp class="codeph">true</samp> is selected, the list of valid server options
+will be provided when the Ant task is run.</dd>
+
+
+<dt class="dlterm">Service.RuntimeId</dt>
+
+<dd>This is the ID of the Web service's runtime. This parameter should not
+be modified.</dd>
+
+
+<dt class="dlterm">Service.ServerId</dt>
+
+<dd>Options:<ul class="simple">
+<li><samp class="codeph">org.eclipse.jst.server.tomcat.x</samp> (where <samp class="codeph">x</samp> is <samp class="codeph">32,
+40, 41, 50,</samp> or <samp class="codeph">55</samp>)</li>
+
+<li><samp class="codeph">org.eclipse.jst.server.generic.weblogicx</samp> (where <samp class="codeph">x</samp> is <samp class="codeph">81</samp> or <samp class="codeph">90</samp>) </li>
+
+<li><samp class="codeph">org.eclipse.jst.server.generic.jbossx</samp> (where <samp class="codeph">x</samp> is <samp class="codeph">323</samp> or <samp class="codeph">4</samp>)</li>
+
+<li><samp class="codeph">org.eclipse.jst.server.generic.jonas4</samp></li>
+
+<li><samp class="codeph">org.eclipse.jst.server.generic.oracle1013</samp></li>
+
+<li><samp class="codeph">org.eclipse.jst.servers.websphere.6</samp></li>
+
+</ul>
+</dd>
+
+<dd class="ddexpand">This is the ID of the target server. Delete or comment out this parameter
+to have the Ant task select the correct value based on the server settings
+of the dynamic Web project.</dd>
+
+
+<dt class="dlterm">ServiceProjectName</dt>
+
+<dd>By default the service project is given the name of the WSDL file or Java
+bean from which it is created. Use this parameter to create the service project
+with a different name.</dd>
+
+
+<dt class="dlterm">ServiceEarProjectName</dt>
+
+<dd>By default the service EAR project is given the name of the WSDL file
+or Java bean from which it is created. Use this parameter to create the service
+EAR project with a different name.</dd>
+
+
+<dt class="dlterm">Mappings</dt>
+
+<dd>Enter the workspace relative URI to a property file containing mappings.</dd>
+
+<dd class="ddexpand">Mappings are used to override the default namespace names in the generated
+WSDL. The content of the properties file must be of the format package = namespace </dd>
+
+
+<dt class="dlterm">JavaOutput</dt>
+
+<dd>Enter the workspace relative URI to an existing Java source folder for
+the generated Java code.</dd>
+
+
+<dt class="dlterm">Methods</dt>
+
+<dd>Use this parameter to limit which methods are exposed in the service.
+It must be in the form of a space delimited string of method signatures. For
+example, <kbd class="userinput">method1(parmType1) method2(parmType2)</kbd>. If
+no list is provided, all methods are exposed. </dd>
+
+
+<dt class="dlterm">Style</dt>
+
+<dd><span class="synph"> Options: <samp class="codeph">DOCUMENT</samp> <samp class="codeph">RPC</samp> <samp class="codeph">WRAPPED</samp></span></dd>
+
+<dd class="ddexpand">Select the SOAP message style. The default is <samp class="codeph">DOCUMENT</samp>.</dd>
+
+
+<dt class="dlterm">Use</dt>
+
+<dd><span class="synph"> Options: <samp class="codeph">LITERAL</samp> <samp class="codeph">ENCODED</samp></span></dd>
+
+<dd class="ddexpand">Select if the SOAP message will be literal or encoded. The default is <samp class="codeph">LITERAL</samp>.</dd>
+
+
+<dt class="dlterm">OverwriteFilesEnabled</dt>
+
+<dd><span class="synph"> Options: <samp class="codeph">true</samp> <samp class="codeph">false</samp></span></dd>
+
+<dd class="ddexpand">Use this parameter to tell the Ant task to overwrite any file that it
+creates with the same name as an existing file. By default this is set to <samp class="codeph">true</samp>.</dd>
+
+
+<dt class="dlterm">CreateFoldersEnabled</dt>
+
+<dd><span class="synph"> Options: <samp class="codeph">true</samp> <samp class="codeph">false</samp></span></dd>
+
+<dd class="ddexpand">Use this parameter to tell the Ant task to create any neccessary folders.
+By default this is set to <samp class="codeph">true</samp>.</dd>
+
+
+<dt class="dlterm">CheckoutFilesEnabled</dt>
+
+<dd><span class="synph"> Options: <samp class="codeph">true</samp> <samp class="codeph">false</samp></span></dd>
+
+<dd class="ddexpand">Use this parameter to tell the Ant task to checkout files from CVS without
+prompting you. By default this is set to <samp class="codeph">true</samp>.</dd>
+
+</dl>
+</div>
+
+</div>
+
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/twbwsa.html" title="You can use Ant through the Eclipse workspace to generate a Web service using the Axis run-time environment. Both top-down and bottom-up Web services development is supported with the Ant tasks.">Creating a Web service using Ant tasks in the Workbench</a></div>
+</div>
+</div>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.command.env.doc.user/topics/rtdwsa.dita b/docs/org.eclipse.wst.command.env.doc.user/topics/rtdwsa.dita
new file mode 100644
index 0000000..1b4000a
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/topics/rtdwsa.dita
@@ -0,0 +1,100 @@
+<?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="top-downaxiswebservicecommandlinereference" xml:lang="en-us">
+<title>Top-down Axis Web service Ant task properties file reference</title>
+<shortdesc>The <userinput>axisservice.properties</userinput> file is used
+to pass data to the Web services Ant tasks when creating an Axis Web service
+. This file shows the available options.</shortdesc>
+<refbody>
+<section><title>Parameters</title><parml><plentry>
+<pt>ScenarioType</pt>
+<pd><synph> Options: <codeph>service</codeph> </synph></pd>
+<pd>This is a required element that tells the Ant task if it is creating a
+Web service or a Web service client.</pd>
+</plentry><plentry>
+<pt>InitialSelection</pt>
+<pd>Enter the workspace relative URI to the WSDL file or Java bean within
+your workspace. For example <userinput>/dynamicWebProjectName/WebContent/myService.wsdl</userinput> or <userinput>/dynamicWebProjectName/src/myBean.java</userinput
+></pd>
+</plentry><plentry>
+<pt>ListRuntimes</pt>
+<pd><synph> Options: <codeph>true</codeph> <codeph>false</codeph></synph></pd>
+<pd>If <codeph>true</codeph> is selected, the list of valid runtime options
+will be provided when the Ant task is run.</pd>
+</plentry><plentry>
+<pt>ListServers</pt>
+<pd><synph> Options: <codeph>true</codeph> <codeph>false</codeph></synph></pd>
+<pd>If <codeph>true</codeph> is selected, the list of valid server options
+will be provided when the Ant task is run.</pd>
+</plentry><plentry>
+<pt>Service.RuntimeId</pt>
+<pd>This is the ID of the Web service's runtime. This parameter should not
+be modified.</pd>
+</plentry><plentry>
+<pt>Service.ServerId</pt>
+<pd>Options:<sl>
+<sli><codeph>org.eclipse.jst.server.tomcat.x</codeph> (where <codeph>x</codeph> is <codeph>32,
+40, 41, 50,</codeph> or <codeph>55</codeph>)</sli>
+<sli><codeph>org.eclipse.jst.server.generic.weblogicx</codeph> (where <codeph>x</codeph> is <codeph>81</codeph> or <codeph>90</codeph>) </sli>
+<sli><codeph>org.eclipse.jst.server.generic.jbossx</codeph> (where <codeph>x</codeph> is <codeph>323</codeph> or <codeph>4</codeph>)</sli>
+<sli><codeph>org.eclipse.jst.server.generic.jonas4</codeph></sli>
+<sli><codeph>org.eclipse.jst.server.generic.oracle1013</codeph></sli>
+<sli><codeph>org.eclipse.jst.servers.websphere.6</codeph></sli>
+</sl></pd>
+<pd>This is the ID of the target server. Delete or comment out this parameter
+to have the Ant task select the correct value based on the server settings
+of the dynamic Web project.</pd>
+</plentry><plentry>
+<pt>ServiceProjectName</pt>
+<pd>By default the service project is given the name of the WSDL file or Java
+bean from which it is created. Use this parameter to create the service project
+with a different name.</pd>
+</plentry><plentry>
+<pt>ServiceEarProjectName</pt>
+<pd>By default the service EAR project is given the name of the WSDL file
+or Java bean from which it is created. Use this parameter to create the service
+EAR project with a different name.</pd>
+</plentry><plentry>
+<pt>Mappings</pt>
+<pd>Enter the workspace relative URI to a property file containing mappings.</pd>
+<pd>Mappings are used to override the default package names of the generated
+Java template classes. The content of the properties file must be of the format
+namespace=package </pd>
+</plentry><plentry>
+<pt>JavaOutput</pt>
+<pd>Enter the workspace relative URI to an existing Java source folder for
+the generated Java code.</pd>
+</plentry><plentry>
+<pt>Methods</pt>
+<pd>Use this parameter to limit which methods are exposed in the service.
+It must be in the form of a space delimited string of method signatures. For
+example, <userinput>method1(parmType1) method2(parmType2)</userinput>. If
+no list is provided, all methods are exposed. </pd>
+</plentry><plentry>
+<pt>Style</pt>
+<pd><synph> Options: <codeph>DOCUMENT</codeph> <codeph>RPC</codeph> <codeph>WRAPPED</codeph></synph></pd>
+<pd>Select the SOAP message style. The default is <codeph>DOCUMENT</codeph>.</pd>
+</plentry><plentry>
+<pt>Use</pt>
+<pd><synph> Options: <codeph>LITERAL</codeph> <codeph>ENCODED</codeph></synph></pd>
+<pd>Select if the SOAP message will be literal or encoded. The default is <codeph>LITERAL</codeph>.</pd>
+</plentry><plentry>
+<pt>OverwriteFilesEnabled</pt>
+<pd><synph> Options: <codeph>true</codeph> <codeph>false</codeph></synph></pd>
+<pd>Use this parameter to tell the Ant task to overwrite any file that it
+creates with the same name as an existing file. By default this is set to <codeph>true</codeph>.</pd>
+</plentry><plentry>
+<pt>CreateFoldersEnabled</pt>
+<pd><synph> Options: <codeph>true</codeph> <codeph>false</codeph></synph></pd>
+<pd>Use this parameter to tell the Ant task to create any neccessary folders.
+By default this is set to <codeph>true</codeph>.</pd>
+</plentry><plentry>
+<pt>CheckoutFilesEnabled</pt>
+<pd><synph> Options: <codeph>true</codeph> <codeph>false</codeph></synph></pd>
+<pd>Use this parameter to tell the Ant task to checkout files from CVS without
+prompting you. By default this is set to <codeph>true</codeph>.</pd>
+</plentry></parml></section>
+</refbody>
+</reference>
diff --git a/docs/org.eclipse.wst.command.env.doc.user/topics/rtdwsa.html b/docs/org.eclipse.wst.command.env.doc.user/topics/rtdwsa.html
new file mode 100644
index 0000000..823132f
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/topics/rtdwsa.html
@@ -0,0 +1,178 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" />
+<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="Top-down Axis Web service Ant task properties file reference" />
+<meta name="abstract" content="The axisservice.properties file is used to pass data to the Web services Ant tasks when creating an Axis Web service . This file shows the available options." />
+<meta name="description" content="The axisservice.properties file is used to pass data to the Web services Ant tasks when creating an Axis Web service . This file shows the available options." />
+<meta scheme="URI" name="DC.Relation" content="../topics/twbwsa.html" />
+<meta content="XHTML" name="DC.Format" />
+<meta content="top-downaxiswebservicecommandlinereference" name="DC.Identifier" />
+<meta content="en-us" name="DC.Language" />
+<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
+<title>Top-down Axis Web service Ant task properties file reference</title>
+</head>
+<body id="top-downaxiswebservicecommandlinereference"><a name="top-downaxiswebservicecommandlinereference"><!-- --></a>
+
+
+<h1 class="topictitle1">Top-down Axis Web service Ant task properties file reference</h1>
+
+
+<div><p>The <kbd class="userinput">axisservice.properties</kbd> file is used
+to pass data to the Web services Ant tasks when creating an Axis Web service
+. This file shows the available options.</p>
+
+<div class="section"><h4 class="sectiontitle">Parameters</h4><dl>
+<dt class="dlterm">ScenarioType</dt>
+
+<dd><span class="synph"> Options: <samp class="codeph">service</samp> </span></dd>
+
+<dd class="ddexpand">This is a required element that tells the Ant task if it is creating a
+Web service or a Web service client.</dd>
+
+
+<dt class="dlterm">InitialSelection</dt>
+
+<dd>Enter the workspace relative URI to the WSDL file or Java bean within
+your workspace. For example <kbd class="userinput">/dynamicWebProjectName/WebContent/myService.wsdl</kbd> or <kbd class="userinput">/dynamicWebProjectName/src/myBean.java</kbd></dd>
+
+
+<dt class="dlterm">ListRuntimes</dt>
+
+<dd><span class="synph"> Options: <samp class="codeph">true</samp> <samp class="codeph">false</samp></span></dd>
+
+<dd class="ddexpand">If <samp class="codeph">true</samp> is selected, the list of valid runtime options
+will be provided when the Ant task is run.</dd>
+
+
+<dt class="dlterm">ListServers</dt>
+
+<dd><span class="synph"> Options: <samp class="codeph">true</samp> <samp class="codeph">false</samp></span></dd>
+
+<dd class="ddexpand">If <samp class="codeph">true</samp> is selected, the list of valid server options
+will be provided when the Ant task is run.</dd>
+
+
+<dt class="dlterm">Service.RuntimeId</dt>
+
+<dd>This is the ID of the Web service's runtime. This parameter should not
+be modified.</dd>
+
+
+<dt class="dlterm">Service.ServerId</dt>
+
+<dd>Options:<ul class="simple">
+<li><samp class="codeph">org.eclipse.jst.server.tomcat.x</samp> (where <samp class="codeph">x</samp> is <samp class="codeph">32,
+40, 41, 50,</samp> or <samp class="codeph">55</samp>)</li>
+
+<li><samp class="codeph">org.eclipse.jst.server.generic.weblogicx</samp> (where <samp class="codeph">x</samp> is <samp class="codeph">81</samp> or <samp class="codeph">90</samp>) </li>
+
+<li><samp class="codeph">org.eclipse.jst.server.generic.jbossx</samp> (where <samp class="codeph">x</samp> is <samp class="codeph">323</samp> or <samp class="codeph">4</samp>)</li>
+
+<li><samp class="codeph">org.eclipse.jst.server.generic.jonas4</samp></li>
+
+<li><samp class="codeph">org.eclipse.jst.server.generic.oracle1013</samp></li>
+
+<li><samp class="codeph">org.eclipse.jst.servers.websphere.6</samp></li>
+
+</ul>
+</dd>
+
+<dd class="ddexpand">This is the ID of the target server. Delete or comment out this parameter
+to have the Ant task select the correct value based on the server settings
+of the dynamic Web project.</dd>
+
+
+<dt class="dlterm">ServiceProjectName</dt>
+
+<dd>By default the service project is given the name of the WSDL file or Java
+bean from which it is created. Use this parameter to create the service project
+with a different name.</dd>
+
+
+<dt class="dlterm">ServiceEarProjectName</dt>
+
+<dd>By default the service EAR project is given the name of the WSDL file
+or Java bean from which it is created. Use this parameter to create the service
+EAR project with a different name.</dd>
+
+
+<dt class="dlterm">Mappings</dt>
+
+<dd>Enter the workspace relative URI to a property file containing mappings.</dd>
+
+<dd class="ddexpand">Mappings are used to override the default package names of the generated
+Java template classes. The content of the properties file must be of the format
+namespace=package </dd>
+
+
+<dt class="dlterm">JavaOutput</dt>
+
+<dd>Enter the workspace relative URI to an existing Java source folder for
+the generated Java code.</dd>
+
+
+<dt class="dlterm">Methods</dt>
+
+<dd>Use this parameter to limit which methods are exposed in the service.
+It must be in the form of a space delimited string of method signatures. For
+example, <kbd class="userinput">method1(parmType1) method2(parmType2)</kbd>. If
+no list is provided, all methods are exposed. </dd>
+
+
+<dt class="dlterm">Style</dt>
+
+<dd><span class="synph"> Options: <samp class="codeph">DOCUMENT</samp> <samp class="codeph">RPC</samp> <samp class="codeph">WRAPPED</samp></span></dd>
+
+<dd class="ddexpand">Select the SOAP message style. The default is <samp class="codeph">DOCUMENT</samp>.</dd>
+
+
+<dt class="dlterm">Use</dt>
+
+<dd><span class="synph"> Options: <samp class="codeph">LITERAL</samp> <samp class="codeph">ENCODED</samp></span></dd>
+
+<dd class="ddexpand">Select if the SOAP message will be literal or encoded. The default is <samp class="codeph">LITERAL</samp>.</dd>
+
+
+<dt class="dlterm">OverwriteFilesEnabled</dt>
+
+<dd><span class="synph"> Options: <samp class="codeph">true</samp> <samp class="codeph">false</samp></span></dd>
+
+<dd class="ddexpand">Use this parameter to tell the Ant task to overwrite any file that it
+creates with the same name as an existing file. By default this is set to <samp class="codeph">true</samp>.</dd>
+
+
+<dt class="dlterm">CreateFoldersEnabled</dt>
+
+<dd><span class="synph"> Options: <samp class="codeph">true</samp> <samp class="codeph">false</samp></span></dd>
+
+<dd class="ddexpand">Use this parameter to tell the Ant task to create any neccessary folders.
+By default this is set to <samp class="codeph">true</samp>.</dd>
+
+
+<dt class="dlterm">CheckoutFilesEnabled</dt>
+
+<dd><span class="synph"> Options: <samp class="codeph">true</samp> <samp class="codeph">false</samp></span></dd>
+
+<dd class="ddexpand">Use this parameter to tell the Ant task to checkout files from CVS without
+prompting you. By default this is set to <samp class="codeph">true</samp>.</dd>
+
+</dl>
+</div>
+
+</div>
+
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/twbwsa.html" title="You can use Ant through the Eclipse workspace to generate a Web service using the Axis run-time environment. Both top-down and bottom-up Web services development is supported with the Ant tasks.">Creating a Web service using Ant tasks in the Workbench</a></div>
+</div>
+</div>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.command.env.doc.user/topics/rwsclienta.dita b/docs/org.eclipse.wst.command.env.doc.user/topics/rwsclienta.dita
new file mode 100644
index 0000000..c7346ca
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/topics/rwsclienta.dita
@@ -0,0 +1,89 @@
+<?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="axiswebserviceclientcommandlinereference" xml:lang="en-us">
+<title>Axis Web service client Ant task properties file reference</title>
+<shortdesc>The <userinput>axisclient.properties</userinput> file is used to
+pass data to the Web services Ant tasks when creating an Axis Web service
+client. This file shows the available options.</shortdesc>
+<refbody>
+<section><title>Parameters</title><parml><plentry>
+<pt>ScenarioType</pt>
+<pd><synph> Options: <codeph>client</codeph></synph></pd>
+<pd>This is a required element that tells the Ant task if it is creating a
+Web service or a Web service client.</pd>
+</plentry><plentry>
+<pt>InitialSelection</pt>
+<pd>Enter the workspace relative URI to the WSDL file or Java bean within
+your workspace. For example <userinput>/dynamicWebProjectName/WebContent/myService.wsdl</userinput> or <userinput>/dynamicWebProjectName/src/myBean.java</userinput
+></pd>
+</plentry><plentry>
+<pt>ListRuntimes</pt>
+<pd><synph> Options: <codeph>true</codeph> <codeph>false</codeph></synph></pd>
+<pd>If <codeph>true</codeph> is selected, the list of valid runtime options
+will be provided when the Ant task is run.</pd>
+</plentry><plentry>
+<pt>ListServers</pt>
+<pd><synph> Options: <codeph>true</codeph> <codeph>false</codeph></synph></pd>
+<pd>If <codeph>true</codeph> is selected, the list of valid server options
+will be provided when the Ant task is run.</pd>
+</plentry><plentry>
+<pt>Client.RuntimeId</pt>
+<pd>This is the ID of the Web service's runtime. This parameter should not
+be modified.</pd>
+</plentry><plentry>
+<pt>Client.ServerId</pt>
+<pd>Options:<sl>
+<sli><codeph>org.eclipse.jst.server.tomcat.x</codeph> (where <codeph>x</codeph> is <codeph>32,
+40, 41, 50,</codeph> or <codeph>55</codeph>)</sli>
+<sli><codeph>org.eclipse.jst.server.generic.weblogicx</codeph> (where <codeph>x</codeph> is <codeph>81</codeph> or <codeph>90</codeph>) </sli>
+<sli><codeph>org.eclipse.jst.server.generic.jbossx</codeph> (where <codeph>x</codeph> is <codeph>323</codeph> or <codeph>4</codeph>)</sli>
+<sli><codeph>org.eclipse.jst.server.generic.jonas4</codeph></sli>
+<sli><codeph>org.eclipse.jst.server.generic.oracle1013</codeph></sli>
+<sli><codeph>org.eclipse.jst.servers.websphere.6</codeph></sli>
+</sl></pd>
+<pd>This is the ID of the target server. Delete or comment out this parameter
+to have the Ant task select the correct value based on the server settings
+of the dynamic Web project.</pd>
+</plentry><plentry>
+<pt>ClientProjectName</pt>
+<pd>By default the client project is given the name of the WSDL file or Java
+bean from which it is created. Use this parameter to create the service project
+with a different name.</pd>
+</plentry><plentry>
+<pt>ClientEarProjectName</pt>
+<pd>By default the client EAR project is given the name of the WSDL file or
+Java bean from which it is created. Use this parameter to create the service
+EAR project with a different name.</pd>
+</plentry><plentry>
+<pt>ClientComponentType</pt>
+<pd><p>Options: <userinput>jst.web</userinput> <userinput>jst.java</userinput></p><p>Use
+this parameter to select the type of client project. The only valid client
+project type for Axis clients is <userinput>jst.web</userinput>.</p></pd>
+</plentry><plentry>
+<pt>CustomizeClientMappings</pt>
+<pd><p>Options: <userinput>true</userinput> <userinput>false</userinput></p><p>Mappings
+are used to override the default namespace names in the generated WSDL. The
+content of the properties file must be of the format package = namespace</p></pd>
+</plentry><plentry>
+<pt>Mappings</pt>
+<pd>Enter the workspace relative URI to a property file containing mappings. </pd>
+</plentry><plentry>
+<pt>OverwriteFilesEnabled</pt>
+<pd><synph> Options: <codeph>true</codeph> <codeph>false</codeph></synph></pd>
+<pd>Use this parameter to tell the Ant task to overwrite any file that it
+creates with the same name as an existing file. By default this is set to <codeph>true</codeph>.</pd>
+</plentry><plentry>
+<pt>CreateFoldersEnabled</pt>
+<pd><synph> Options: <codeph>true</codeph> <codeph>false</codeph></synph></pd>
+<pd>Use this parameter to tell the Ant task to create any neccessary folders.
+By default this is set to <codeph>true</codeph>.</pd>
+</plentry><plentry>
+<pt>CheckoutFilesEnabled</pt>
+<pd><synph> Options: <codeph>true</codeph> <codeph>false</codeph></synph></pd>
+<pd>Use this parameter to tell the Ant task to checkout files from CVS without
+prompting you. By default this is set to <codeph>true</codeph>.</pd>
+</plentry></parml></section>
+</refbody>
+</reference>
diff --git a/docs/org.eclipse.wst.command.env.doc.user/topics/rwsclienta.html b/docs/org.eclipse.wst.command.env.doc.user/topics/rwsclienta.html
new file mode 100644
index 0000000..cd2b343
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/topics/rwsclienta.html
@@ -0,0 +1,164 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" />
+<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="Axis Web service client Ant task properties file reference" />
+<meta name="abstract" content="The axisclient.properties file is used to pass data to the Web services Ant tasks when creating an Axis Web service client. This file shows the available options." />
+<meta name="description" content="The axisclient.properties file is used to pass data to the Web services Ant tasks when creating an Axis Web service client. This file shows the available options." />
+<meta scheme="URI" name="DC.Relation" content="../topics/twbwsclienta.html" />
+<meta content="XHTML" name="DC.Format" />
+<meta content="axiswebserviceclientcommandlinereference" name="DC.Identifier" />
+<meta content="en-us" name="DC.Language" />
+<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
+<title>Axis Web service client Ant task properties file reference</title>
+</head>
+<body id="axiswebserviceclientcommandlinereference"><a name="axiswebserviceclientcommandlinereference"><!-- --></a>
+
+
+<h1 class="topictitle1">Axis Web service client Ant task properties file reference</h1>
+
+
+<div><p>The <kbd class="userinput">axisclient.properties</kbd> file is used to
+pass data to the Web services Ant tasks when creating an Axis Web service
+client. This file shows the available options.</p>
+
+<div class="section"><h4 class="sectiontitle">Parameters</h4><dl>
+<dt class="dlterm">ScenarioType</dt>
+
+<dd><span class="synph"> Options: <samp class="codeph">client</samp></span></dd>
+
+<dd class="ddexpand">This is a required element that tells the Ant task if it is creating a
+Web service or a Web service client.</dd>
+
+
+<dt class="dlterm">InitialSelection</dt>
+
+<dd>Enter the workspace relative URI to the WSDL file or Java bean within
+your workspace. For example <kbd class="userinput">/dynamicWebProjectName/WebContent/myService.wsdl</kbd> or <kbd class="userinput">/dynamicWebProjectName/src/myBean.java</kbd></dd>
+
+
+<dt class="dlterm">ListRuntimes</dt>
+
+<dd><span class="synph"> Options: <samp class="codeph">true</samp> <samp class="codeph">false</samp></span></dd>
+
+<dd class="ddexpand">If <samp class="codeph">true</samp> is selected, the list of valid runtime options
+will be provided when the Ant task is run.</dd>
+
+
+<dt class="dlterm">ListServers</dt>
+
+<dd><span class="synph"> Options: <samp class="codeph">true</samp> <samp class="codeph">false</samp></span></dd>
+
+<dd class="ddexpand">If <samp class="codeph">true</samp> is selected, the list of valid server options
+will be provided when the Ant task is run.</dd>
+
+
+<dt class="dlterm">Client.RuntimeId</dt>
+
+<dd>This is the ID of the Web service's runtime. This parameter should not
+be modified.</dd>
+
+
+<dt class="dlterm">Client.ServerId</dt>
+
+<dd>Options:<ul class="simple">
+<li><samp class="codeph">org.eclipse.jst.server.tomcat.x</samp> (where <samp class="codeph">x</samp> is <samp class="codeph">32,
+40, 41, 50,</samp> or <samp class="codeph">55</samp>)</li>
+
+<li><samp class="codeph">org.eclipse.jst.server.generic.weblogicx</samp> (where <samp class="codeph">x</samp> is <samp class="codeph">81</samp> or <samp class="codeph">90</samp>) </li>
+
+<li><samp class="codeph">org.eclipse.jst.server.generic.jbossx</samp> (where <samp class="codeph">x</samp> is <samp class="codeph">323</samp> or <samp class="codeph">4</samp>)</li>
+
+<li><samp class="codeph">org.eclipse.jst.server.generic.jonas4</samp></li>
+
+<li><samp class="codeph">org.eclipse.jst.server.generic.oracle1013</samp></li>
+
+<li><samp class="codeph">org.eclipse.jst.servers.websphere.6</samp></li>
+
+</ul>
+</dd>
+
+<dd class="ddexpand">This is the ID of the target server. Delete or comment out this parameter
+to have the Ant task select the correct value based on the server settings
+of the dynamic Web project.</dd>
+
+
+<dt class="dlterm">ClientProjectName</dt>
+
+<dd>By default the client project is given the name of the WSDL file or Java
+bean from which it is created. Use this parameter to create the service project
+with a different name.</dd>
+
+
+<dt class="dlterm">ClientEarProjectName</dt>
+
+<dd>By default the client EAR project is given the name of the WSDL file or
+Java bean from which it is created. Use this parameter to create the service
+EAR project with a different name.</dd>
+
+
+<dt class="dlterm">ClientComponentType</dt>
+
+<dd><p>Options: <kbd class="userinput">jst.web</kbd> <kbd class="userinput">jst.java</kbd></p>
+<p>Use
+this parameter to select the type of client project. The only valid client
+project type for Axis clients is <kbd class="userinput">jst.web</kbd>.</p>
+</dd>
+
+
+<dt class="dlterm">CustomizeClientMappings</dt>
+
+<dd><p>Options: <kbd class="userinput">true</kbd> <kbd class="userinput">false</kbd></p>
+<p>Mappings
+are used to override the default namespace names in the generated WSDL. The
+content of the properties file must be of the format package = namespace</p>
+</dd>
+
+
+<dt class="dlterm">Mappings</dt>
+
+<dd>Enter the workspace relative URI to a property file containing mappings. </dd>
+
+
+<dt class="dlterm">OverwriteFilesEnabled</dt>
+
+<dd><span class="synph"> Options: <samp class="codeph">true</samp> <samp class="codeph">false</samp></span></dd>
+
+<dd class="ddexpand">Use this parameter to tell the Ant task to overwrite any file that it
+creates with the same name as an existing file. By default this is set to <samp class="codeph">true</samp>.</dd>
+
+
+<dt class="dlterm">CreateFoldersEnabled</dt>
+
+<dd><span class="synph"> Options: <samp class="codeph">true</samp> <samp class="codeph">false</samp></span></dd>
+
+<dd class="ddexpand">Use this parameter to tell the Ant task to create any neccessary folders.
+By default this is set to <samp class="codeph">true</samp>.</dd>
+
+
+<dt class="dlterm">CheckoutFilesEnabled</dt>
+
+<dd><span class="synph"> Options: <samp class="codeph">true</samp> <samp class="codeph">false</samp></span></dd>
+
+<dd class="ddexpand">Use this parameter to tell the Ant task to checkout files from CVS without
+prompting you. By default this is set to <samp class="codeph">true</samp>.</dd>
+
+</dl>
+</div>
+
+</div>
+
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/twbwsclienta.html" title="If you have a WSDL file you can use Ant through the Eclipse workspace to generate a Web service client using the Axis run-time environment.">Creating a Web service client using Ant tasks</a></div>
+</div>
+</div>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.command.env.doc.user/topics/twbwsa.dita b/docs/org.eclipse.wst.command.env.doc.user/topics/twbwsa.dita
new file mode 100644
index 0000000..45e9143
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/topics/twbwsa.dita
@@ -0,0 +1,75 @@
+<?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="ttdwsa" xml:lang="en-us">
+<title>Creating a Web service using Ant tasks in the Workbench</title>
+<titlealts>
+<searchtitle>Creating an Axis runtime Web service using Ant tasks in the Workbench</searchtitle>
+</titlealts>
+<shortdesc>You can use Ant through the Eclipse workspace to generate a Web
+service using the Axis run-time environment. Both top-down and bottom-up Web
+services development is supported with the Ant tasks.</shortdesc>
+<taskbody>
+<prereq>Before creating the Web service you must:<ul>
+<li>complete the prerequisites listed in: <xref href="cwsaxisant.dita"></xref></li>
+<li>if you are creating a top-down Web service, create or import a WSDL file
+into the <userinput>WebConent</userinput> folder of the dynamic Web project
+you created.</li>
+<li>If you are creating a bottom-up Web service, create or import a Java bean
+into the <userinput>src</userinput> folder of the dynamic Web project.</li>
+</ul></prereq>
+<context>In order to create the Web service you need to modify the Ant file
+and the service Ant properties file.</context>
+<steps>
+<step><cmd>Edit the Ant file (<userinput>wsgen.xml</userinput>) that you imported
+in the prerequisite steps. Ensure that it points to the service Ant properties
+file: it should contain a line stating <userinput><property file="axisservice.properties"/></userinput>.</cmd>
+<info>Save any changes that you have made.</info></step>
+<step><cmd>Edit the <userinput>axisservice.properties</userinput> file that
+you imported in the prerequisite steps.</cmd>
+<substeps>
+<substep><cmd>Ensure that the scenarioType parameter is set to service.</cmd>
+</substep>
+<substep><cmd>Set the workspace parameter so that it points to the location
+of your WSDL file or Java bean.</cmd></substep>
+<substep><cmd>All other parameters are optional and should be deleted if not
+explicitly set. The default values for the remaining parameters will be retrieved
+from the dynamic project settings and preferences. For additional information
+on how to set these parameters refer to: </cmd><info><ul>
+<li><xref href="rtdwsa.dita"></xref></li>
+<li><xref href="rbuwsa.dita"></xref></li>
+</ul></info></substep>
+</substeps>
+<info>Save the <userinput>axisservice.properties</userinput> file.</info>
+</step>
+<step><cmd>Right-click <userinput>wsgen.xml</userinput> and select <menucascade>
+<uicontrol>Run As</uicontrol><uicontrol>Ant Build...</uicontrol></menucascade></cmd>
+</step>
+<step><cmd>In the dialog that opens, select the <uicontrol>JRE</uicontrol> tab
+and select <uicontrol>Run in the same JRE as the workspace</uicontrol>.</cmd>
+<info>Click <uicontrol>Apply</uicontrol> and then click <uicontrol>Run</uicontrol>.</info>
+</step>
+<step><cmd>Once your Web service has been generated the console displays a <userinput>Build
+Successful</userinput> message.</cmd></step>
+</steps>
+<result>The WSDL file for the service will have been created and placed in
+the dynamic Web project's WebContent\wsdl folder. The following files will
+have been created and placed in a subdirectory of the dynamic Web project's
+WebContent\WEB-INF folder:<ul>
+<li>web.xml</li>
+<li>undeploy.wsdd</li>
+<li>deploy.wsdd </li>
+</ul>If you are creating a top-down Web service, Web service files similar
+to the following ones will be created and placed under the dynamic Web project's
+src folder. Depending on the WSDL file on which the Web service is based,
+the files for your Web service may be different:<ul>
+<li><i>Service_name</i>_PortType.java</li>
+<li><i>Service_name</i>_Service.java</li>
+<li><i>Service_name</i>_ServiceLocator.java</li>
+<li><i>Service_name</i>SOAPImpl.java</li>
+<li><i>Service_name</i>SOAPSkeleton.java</li>
+<li><i>Service_name</i>SOAPStub.java</li>
+</ul> </result>
+</taskbody>
+</task>
diff --git a/docs/org.eclipse.wst.command.env.doc.user/topics/twbwsa.html b/docs/org.eclipse.wst.command.env.doc.user/topics/twbwsa.html
new file mode 100644
index 0000000..d54efc0
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/topics/twbwsa.html
@@ -0,0 +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">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" />
+<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 using Ant tasks in the Workbench" />
+<meta name="abstract" content="You can use Ant through the Eclipse workspace to generate a Web service using the Axis run-time environment. Both top-down and bottom-up Web services development is supported with the Ant tasks." />
+<meta name="description" content="You can use Ant through the Eclipse workspace to generate a Web service using the Axis run-time environment. Both top-down and bottom-up Web services development is supported with the Ant tasks." />
+<meta scheme="URI" name="DC.Relation" content="../topics/cwsaxisant.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/rtdwsa.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/rbuwsa.html" />
+<meta content="XHTML" name="DC.Format" />
+<meta content="ttdwsa" name="DC.Identifier" />
+<meta content="en-us" name="DC.Language" />
+<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
+<title>Creating an Axis runtime Web service using Ant tasks in the Workbench</title>
+</head>
+<body id="ttdwsa"><a name="ttdwsa"><!-- --></a>
+
+
+<h1 class="topictitle1">Creating a Web service using Ant tasks in the Workbench</h1>
+
+
+
+<div><p>You can use Ant through the Eclipse workspace to generate a Web
+service using the Axis run-time environment. Both top-down and bottom-up Web
+services development is supported with the Ant tasks.</p>
+
+<div class="p">Before creating the Web service you must:<ul>
+<li>complete the prerequisites listed in: <a href="cwsaxisant.html" title="If you prefer not to use the Web service wizard, you can use Ant files to create Web services and clients using the Axis runtime environment. The Web services Ant tasks can be run in two ways: through the Eclipse workspace using Run As > Ant Build..., or they can be run headless through the command line. Once you have created your Web service, you can then deploy it to a server, test it, and publish it as a business entity or business service.">Creating Axis runtime environment Web services and clients using Web services Ant tasks</a></li>
+
+<li>if you are creating a top-down Web service, create or import a WSDL file
+into the <kbd class="userinput">WebConent</kbd> folder of the dynamic Web project
+you created.</li>
+
+<li>If you are creating a bottom-up Web service, create or import a Java bean
+into the <kbd class="userinput">src</kbd> folder of the dynamic Web project.</li>
+
+</ul>
+</div>
+
+<div class="section">In order to create the Web service you need to modify the Ant file
+and the service Ant properties file.</div>
+
+<ol>
+<li class="stepexpand"><span>Edit the Ant file (<kbd class="userinput">wsgen.xml</kbd>) that you imported
+in the prerequisite steps. Ensure that it points to the service Ant properties
+file: it should contain a line stating <kbd class="userinput"><property file="axisservice.properties"/></kbd>.</span>
+ Save any changes that you have made.</li>
+
+<li class="stepexpand"><span>Edit the <kbd class="userinput">axisservice.properties</kbd> file that
+you imported in the prerequisite steps.</span>
+<ol type="a">
+<li class="substepexpand"><span>Ensure that the scenarioType parameter is set to service.</span>
+</li>
+
+<li class="substepexpand"><span>Set the workspace parameter so that it points to the location
+of your WSDL file or Java bean.</span></li>
+
+<li class="substepexpand"><span>All other parameters are optional and should be deleted if not
+explicitly set. The default values for the remaining parameters will be retrieved
+from the dynamic project settings and preferences. For additional information
+on how to set these parameters refer to: </span> <ul>
+<li><a href="rtdwsa.html" title="The axisservice.properties file is used to pass data to the Web services Ant tasks when creating an Axis Web service . This file shows the available options.">Top-down Axis Web service Ant task properties file reference</a></li>
+
+<li><a href="rbuwsa.html" title="The axisservice.properties file is used to pass data to the Web services Ant tasks when creating an Axis Web service . This file shows the available options.">Bottom-up Axis Web service Ant task properties file reference</a></li>
+
+</ul>
+</li>
+
+</ol>
+
+ Save the <kbd class="userinput">axisservice.properties</kbd> file.
+</li>
+
+<li class="stepexpand"><span>Right-click <kbd class="userinput">wsgen.xml</kbd> and select <span class="menucascade">
+<span class="uicontrol">Run As</span> > <span class="uicontrol">Ant Build...</span></span></span>
+</li>
+
+<li class="stepexpand"><span>In the dialog that opens, select the <span class="uicontrol">JRE</span> tab
+and select <span class="uicontrol">Run in the same JRE as the workspace</span>.</span>
+ Click <span class="uicontrol">Apply</span> and then click <span class="uicontrol">Run</span>.
+</li>
+
+<li class="stepexpand"><span>Once your Web service has been generated the console displays a <kbd class="userinput">Build
+Successful</kbd> message.</span></li>
+
+</ol>
+
+<div class="section">The WSDL file for the service will have been created and placed in
+the dynamic Web project's WebContent\wsdl folder. The following files will
+have been created and placed in a subdirectory of the dynamic Web project's
+WebContent\WEB-INF folder:<ul>
+<li>web.xml</li>
+
+<li>undeploy.wsdd</li>
+
+<li>deploy.wsdd </li>
+
+</ul>
+If you are creating a top-down Web service, Web service files similar
+to the following ones will be created and placed under the dynamic Web project's
+src folder. Depending on the WSDL file on which the Web service is based,
+the files for your Web service may be different:<ul>
+<li><em>Service_name</em>_PortType.java</li>
+
+<li><em>Service_name</em>_Service.java</li>
+
+<li><em>Service_name</em>_ServiceLocator.java</li>
+
+<li><em>Service_name</em>SOAPImpl.java</li>
+
+<li><em>Service_name</em>SOAPSkeleton.java</li>
+
+<li><em>Service_name</em>SOAPStub.java</li>
+
+</ul>
+ </div>
+
+</div>
+
+<div>
+<ul class="ullinks">
+<li class="ulchildlink"><strong><a href="../topics/rtdwsa.html">Top-down Axis Web service Ant task properties file reference</a></strong><br />
+The axisservice.properties file is used to pass data to the Web services Ant tasks when creating an Axis Web service . This file shows the available options.</li>
+<li class="ulchildlink"><strong><a href="../topics/rbuwsa.html">Bottom-up Axis Web service Ant task properties file reference</a></strong><br />
+The axisservice.properties file is used to pass data to the Web services Ant tasks when creating an Axis Web service . This file shows the available options.</li>
+</ul>
+
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/cwsaxisant.html" title="If you prefer not to use the Web service wizard, you can use Ant files to create Web services and clients using the Axis runtime environment. The Web services Ant tasks can be run in two ways: through the Eclipse workspace using Run As > Ant Build..., or they can be run headless through the command line. Once you have created your Web service, you can then deploy it to a server, test it, and publish it as a business entity or business service.">Creating Axis runtime environment Web services and clients using Web services Ant tasks</a></div>
+</div>
+</div>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.command.env.doc.user/topics/twbwsclienta.dita b/docs/org.eclipse.wst.command.env.doc.user/topics/twbwsclienta.dita
new file mode 100644
index 0000000..4b7b5c7
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/topics/twbwsclienta.dita
@@ -0,0 +1,66 @@
+<?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="twsclienta" xml:lang="en-us">
+<title>Creating a Web service client using Ant tasks</title>
+<titlealts>
+<searchtitle>Creating an Axis runtime Web service client from a WSDL file
+using command line tools</searchtitle>
+</titlealts>
+<shortdesc>If you have a WSDL file you can use Ant through the Eclipse workspace
+to generate a Web service client using the Axis run-time environment.</shortdesc>
+<taskbody>
+<prereq>Before creating the Web service client you must:<ul>
+<li>complete the prerequisites listed in: <xref href="cwsaxisant.dita"></xref></li>
+<li>create or import a WSDL file into the dynamic Web project you created.</li>
+</ul></prereq>
+<context>In order to create the Web service client you need to modify the
+Ant file and the Ant properties file.</context>
+<steps>
+<step><cmd>Edit the Ant file (<userinput>wsgen.xml</userinput>) that you imported
+in the prerequisite steps. Ensure that it points to the client Ant properties
+file: it should contain a line stating <userinput><property file="axisclient.properties"/></userinput>.</cmd>
+<info>Save any changes that you have made.</info></step>
+<step><cmd>Edit the <userinput>axisclient.properties</userinput> file that
+you imported in the prerequisite steps.</cmd>
+<substeps>
+<substep><cmd>Ensure that the scenarioType parameter is set to client.</cmd>
+</substep>
+<substep><cmd>Set the workspace parameter so that it points to the location
+of your WSDL file.</cmd></substep>
+<substep><cmd>All other parameters are optional and should be deleted if not
+explicitly set. The default values for the remaining parameters will be retrieved
+from the dynamic project settings. For additional information on how to set
+these parameters refer to: <xref href="rwsclienta.dita"></xref></cmd></substep>
+</substeps>
+<info>Save the <userinput>axisclient.properties</userinput> file.</info></step>
+<step><cmd>Right-click <userinput>wsgen.xml</userinput> and select <menucascade>
+<uicontrol>Run As</uicontrol><uicontrol>Ant Build...</uicontrol></menucascade></cmd>
+</step>
+<step><cmd>In the dialog that opens, select the <uicontrol>JRE</uicontrol> tab
+and select <uicontrol>Run in the same JRE as the workspace</uicontrol>.</cmd>
+<info>Click <uicontrol>Apply</uicontrol> and then click <uicontrol>Run</uicontrol>.</info>
+</step>
+<step><cmd>Once your Web service has been generated the console displays a <userinput>Build
+Successful</userinput> message.</cmd></step>
+</steps>
+<result>The following files will have been created and placed in the dynamic
+Web project's WebContent\wsdl folder:<ul>
+<li><i>Service_name</i>SOAP.wsdl </li>
+</ul>The following files will have been created and placed in the dynamic
+Web project's WebContent\WEB-INF folder:<ul>
+<li>undeploy.wsdd</li>
+<li>deploy.wsdd </li>
+</ul>The following files will have been created and placed under the dynamic
+Web project's src folder. Depending on the WSDL file on which the Web service
+client is based, the files for your Web service client may be different:<ul>
+<li><i>Service_name</i>Proxy.java</li>
+<li>get<i>Service_name</i>.java</li>
+<li>get<i>Service_name</i>Locator.java</li>
+<li>get<i>Service_name</i>Soap.java</li>
+<li>get<i>Service_name</i>SoapProxy.java</li>
+<li>get<i>Service_name</i>SoapStub.java</li>
+</ul> </result>
+</taskbody>
+</task>
diff --git a/docs/org.eclipse.wst.command.env.doc.user/topics/twbwsclienta.html b/docs/org.eclipse.wst.command.env.doc.user/topics/twbwsclienta.html
new file mode 100644
index 0000000..3a076c3
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/topics/twbwsclienta.html
@@ -0,0 +1,126 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" />
+<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 client using Ant tasks" />
+<meta name="abstract" content="If you have a WSDL file you can use Ant through the Eclipse workspace to generate a Web service client using the Axis run-time environment." />
+<meta name="description" content="If you have a WSDL file you can use Ant through the Eclipse workspace to generate a Web service client using the Axis run-time environment." />
+<meta scheme="URI" name="DC.Relation" content="../topics/cwsaxisant.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/rwsclienta.html" />
+<meta content="XHTML" name="DC.Format" />
+<meta content="twsclienta" name="DC.Identifier" />
+<meta content="en-us" name="DC.Language" />
+<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
+<title>Creating an Axis runtime Web service client from a WSDL file
+using command line tools</title>
+</head>
+<body id="twsclienta"><a name="twsclienta"><!-- --></a>
+
+
+<h1 class="topictitle1">Creating a Web service client using Ant tasks</h1>
+
+
+
+<div><p>If you have a WSDL file you can use Ant through the Eclipse workspace
+to generate a Web service client using the Axis run-time environment.</p>
+
+<div class="p">Before creating the Web service client you must:<ul>
+<li>complete the prerequisites listed in: <a href="cwsaxisant.html" title="If you prefer not to use the Web service wizard, you can use Ant files to create Web services and clients using the Axis runtime environment. The Web services Ant tasks can be run in two ways: through the Eclipse workspace using Run As > Ant Build..., or they can be run headless through the command line. Once you have created your Web service, you can then deploy it to a server, test it, and publish it as a business entity or business service.">Creating Axis runtime environment Web services and clients using Web services Ant tasks</a></li>
+
+<li>create or import a WSDL file into the dynamic Web project you created.</li>
+
+</ul>
+</div>
+
+<div class="section">In order to create the Web service client you need to modify the
+Ant file and the Ant properties file.</div>
+
+<ol>
+<li class="stepexpand"><span>Edit the Ant file (<kbd class="userinput">wsgen.xml</kbd>) that you imported
+in the prerequisite steps. Ensure that it points to the client Ant properties
+file: it should contain a line stating <kbd class="userinput"><property file="axisclient.properties"/></kbd>.</span>
+ Save any changes that you have made.</li>
+
+<li class="stepexpand"><span>Edit the <kbd class="userinput">axisclient.properties</kbd> file that
+you imported in the prerequisite steps.</span>
+<ol type="a">
+<li><span>Ensure that the scenarioType parameter is set to client.</span>
+</li>
+
+<li><span>Set the workspace parameter so that it points to the location
+of your WSDL file.</span></li>
+
+<li><span>All other parameters are optional and should be deleted if not
+explicitly set. The default values for the remaining parameters will be retrieved
+from the dynamic project settings. For additional information on how to set
+these parameters refer to: <a href="rwsclienta.html" title="The axisclient.properties file is used to pass data to the Web services Ant tasks when creating an Axis Web service client. This file shows the available options.">Axis Web service client Ant task properties file reference</a></span></li>
+
+</ol>
+
+ Save the <kbd class="userinput">axisclient.properties</kbd> file.</li>
+
+<li class="stepexpand"><span>Right-click <kbd class="userinput">wsgen.xml</kbd> and select <span class="menucascade">
+<span class="uicontrol">Run As</span> > <span class="uicontrol">Ant Build...</span></span></span>
+</li>
+
+<li class="stepexpand"><span>In the dialog that opens, select the <span class="uicontrol">JRE</span> tab
+and select <span class="uicontrol">Run in the same JRE as the workspace</span>.</span>
+ Click <span class="uicontrol">Apply</span> and then click <span class="uicontrol">Run</span>.
+</li>
+
+<li class="stepexpand"><span>Once your Web service has been generated the console displays a <kbd class="userinput">Build
+Successful</kbd> message.</span></li>
+
+</ol>
+
+<div class="section">The following files will have been created and placed in the dynamic
+Web project's WebContent\wsdl folder:<ul>
+<li><em>Service_name</em>SOAP.wsdl </li>
+
+</ul>
+The following files will have been created and placed in the dynamic
+Web project's WebContent\WEB-INF folder:<ul>
+<li>undeploy.wsdd</li>
+
+<li>deploy.wsdd </li>
+
+</ul>
+The following files will have been created and placed under the dynamic
+Web project's src folder. Depending on the WSDL file on which the Web service
+client is based, the files for your Web service client may be different:<ul>
+<li><em>Service_name</em>Proxy.java</li>
+
+<li>get<em>Service_name</em>.java</li>
+
+<li>get<em>Service_name</em>Locator.java</li>
+
+<li>get<em>Service_name</em>Soap.java</li>
+
+<li>get<em>Service_name</em>SoapProxy.java</li>
+
+<li>get<em>Service_name</em>SoapStub.java</li>
+
+</ul>
+ </div>
+
+</div>
+
+<div>
+<ul class="ullinks">
+<li class="ulchildlink"><strong><a href="../topics/rwsclienta.html">Axis Web service client Ant task properties file reference</a></strong><br />
+The axisclient.properties file is used to pass data to the Web services Ant tasks when creating an Axis Web service client. This file shows the available options.</li>
+</ul>
+
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/cwsaxisant.html" title="If you prefer not to use the Web service wizard, you can use Ant files to create Web services and clients using the Axis runtime environment. The Web services Ant tasks can be run in two ways: through the Eclipse workspace using Run As > Ant Build..., or they can be run headless through the command line. Once you have created your Web service, you can then deploy it to a server, test it, and publish it as a business entity or business service.">Creating Axis runtime environment Web services and clients using Web services Ant tasks</a></div>
+</div>
+</div>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.command.env.doc.user/wsaxisant_toc.ditamap b/docs/org.eclipse.wst.command.env.doc.user/wsaxisant_toc.ditamap
new file mode 100644
index 0000000..256bfee
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/wsaxisant_toc.ditamap
@@ -0,0 +1,19 @@
+<?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#wsaxisant"
+id="wsaxisant" title="wsaxisant">
+<topicref href="topics/cwsaxisant.dita" navtitle="Creating Axis runtime Web services using Ant tasks">
+<topicref href="topics/twbwsa.dita" navtitle="Creating a Web service using Ant tasks in the Workbench">
+<topicref href="topics/rtdwsa.dita" navtitle="Top-down Axis Web service Ant file reference">
+</topicref>
+<topicref href="topics/rbuwsa.dita" navtitle="Bottom-up Axis Web service Ant file reference">
+</topicref>
+</topicref>
+<topicref href="topics/twbwsclienta.dita" navtitle="Creating a Web service client using Ant tasks in the Workbench">
+<topicref href="topics/rwsclienta.dita" navtitle="Axis Web service client Ant file reference">
+</topicref>
+</topicref>
+</topicref>
+</map>
diff --git a/docs/org.eclipse.wst.command.env.doc.user/wsaxisant_toc.xml b/docs/org.eclipse.wst.command.env.doc.user/wsaxisant_toc.xml
new file mode 100644
index 0000000..a3d8ac6
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.doc.user/wsaxisant_toc.xml
@@ -0,0 +1,15 @@
+<?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#wsaxisant" label="wsaxisant" topic="topics/cwsaxisant.html">
+<topic label="Creating Axis runtime environment Web services and clients using Web services Ant tasks" href="topics/cwsaxisant.html">
+<topic label="Creating a Web service using Ant tasks in the Workbench" href="topics/twbwsa.html">
+<topic label="Top-down Axis Web service Ant task properties file reference" href="topics/rtdwsa.html"/>
+<topic label="Bottom-up Axis Web service Ant task properties file reference" href="topics/rbuwsa.html"/>
+</topic>
+<topic label="Creating a Web service client using Ant tasks" href="topics/twbwsclienta.html">
+<topic label="Axis Web service client Ant task properties file reference" href="topics/rwsclienta.html"/>
+</topic>
+</topic>
+</toc>
diff --git a/docs/org.eclipse.wst.command.env.infopop/.cvsignore b/docs/org.eclipse.wst.command.env.infopop/.cvsignore
new file mode 100644
index 0000000..c14487c
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.infopop/.cvsignore
@@ -0,0 +1 @@
+build.xml
diff --git a/docs/org.eclipse.wst.command.env.infopop/.project b/docs/org.eclipse.wst.command.env.infopop/.project
new file mode 100644
index 0000000..71b83fe
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.infopop/.project
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.wst.command.env.infopop</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ <buildCommand>
+ <name>org.eclipse.pde.ManifestBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.pde.SchemaBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ </buildSpec>
+ <natures>
+ <nature>org.eclipse.pde.PluginNature</nature>
+ </natures>
+</projectDescription>
diff --git a/docs/org.eclipse.wst.command.env.infopop/META-INF/MANIFEST.MF b/docs/org.eclipse.wst.command.env.infopop/META-INF/MANIFEST.MF
new file mode 100644
index 0000000..1aa088e
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.infopop/META-INF/MANIFEST.MF
@@ -0,0 +1,8 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: %pluginName
+Bundle-SymbolicName: org.eclipse.wst.command.env.infopop; singleton:=true
+Bundle-Version: 1.0.3.qualifier
+Bundle-Vendor: %pluginProvider
+Bundle-Localization: plugin
+Eclipse-LazyStart: true
diff --git a/docs/org.eclipse.wst.command.env.infopop/about.html b/docs/org.eclipse.wst.command.env.infopop/about.html
new file mode 100644
index 0000000..73db36e
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.infopop/about.html
@@ -0,0 +1,34 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<HTML>
+
+<head>
+<title>About</title>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+</head>
+
+<BODY lang="EN-US">
+
+<H3>About This Content</H3>
+
+<P>June 06, 2007</P>
+
+<H3>License</H3>
+
+<P>The Eclipse Foundation makes available all content in this plug-in
+("Content"). Unless otherwise indicated below, the Content is provided to you
+under the terms and conditions of the Eclipse Public License Version 1.0
+("EPL"). A copy of the EPL is available at
+<A href="http://www.eclipse.org/org/documents/epl-v10.php">http://www.eclipse.org/org/documents/epl-v10.php</A>.
+For purposes of the EPL, "Program" will mean the Content.</P>
+
+<P>If you did not receive this Content directly from the Eclipse Foundation, the
+Content is being redistributed by another party ("Redistributor") and different
+terms and conditions may apply to your use of any object code in the Content.
+Check the Redistributors license that was provided with the Content. If no such
+license exists, contact the Redistributor. Unless otherwise indicated below, the
+terms and conditions of the EPL still apply to any source code in the Content
+and such source code may be obtained at
+<A href="http://www.eclipse.org/">http://www.eclipse.org/</A>.</P>
+
+</BODY>
+</HTML>
diff --git a/docs/org.eclipse.wst.command.env.infopop/build.properties b/docs/org.eclipse.wst.command.env.infopop/build.properties
new file mode 100644
index 0000000..b9f56eb
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.infopop/build.properties
@@ -0,0 +1,6 @@
+bin.includes = about.html,\
+ plugin.xml,\
+ wst-command-f1.xml,\
+ META-INF/,\
+ plugin.properties
+src.includes = build.properties
diff --git a/docs/org.eclipse.wst.command.env.infopop/plugin.properties b/docs/org.eclipse.wst.command.env.infopop/plugin.properties
new file mode 100644
index 0000000..14eef62
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.infopop/plugin.properties
@@ -0,0 +1,3 @@
+! plug-in properties
+pluginName = Web services UI
+pluginProvider = Eclipse.org
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.command.env.infopop/plugin.xml b/docs/org.eclipse.wst.command.env.infopop/plugin.xml
new file mode 100644
index 0000000..7870c05
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.infopop/plugin.xml
@@ -0,0 +1,18 @@
+<?xml version="1.0" ?>
+<?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.contexts">
+ <contexts file="wst-command-f1.xml" plugin="org.eclipse.wst.command.env.ui"/>
+ </extension>
+</plugin>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.command.env.infopop/wst-command-f1.xml b/docs/org.eclipse.wst.command.env.infopop/wst-command-f1.xml
new file mode 100644
index 0000000..0c63c64
--- /dev/null
+++ b/docs/org.eclipse.wst.command.env.infopop/wst-command-f1.xml
@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?NLS TYPE="org.eclipse.help.contexts"?>
+<contexts>
+
+<!--org.eclipse.wst.command.env.ui-->
+<context id="PPAD0001">
+<!--Action Dialogs Preference Page-->
+<description>You can use this page to choose which Web services popup actions are displayed or hidden. When using the Web services wizards launced from a popup menu you may see a check box that gives you the option of hiding the popup action that you have just performed. If you select that checkbox it will select the respective checkbox on this preference page. If you have chosen to hide a popup action that you want to display use this page to make the popup action visible.
+</description>
+</context>
+
+<context id="PPAD0002">
+<!--show all check box on the Action Dialogs Preference Page-->
+<description>By selecting this checkbox, all valid Web services popup actions will be displayed when you select a file in your workspace and right-click it. Alternately you can select to display or hide individual popup actions.
+</description>
+</context>
+
+<context id="PPAD0003">
+<!--hide all check box on the Action Dialogs Preference Page-->
+<description>By selecting this checkbox, all Web services popup actions will be hidden when you select a file in your workspace and right-click it. Alternately you can select to display or hide individual popup actions.
+</description>
+</context>
+
+<context id="TWP0001">
+<!--show/hide check box-->
+<description>When using the Web services wizards launced from a popup menu, this check box that gives you the option of hiding the popup action that you have just performed. If you select the checkbox it will select the respective checkbox on the Web services > Popup Dialog Selection preference page. If you have chosen to hide a popup action that you want to display, go to Window > Preferences > Web services > Popup Dialog Selection, and use this page to make the popup action visible.
+</description>
+</context>
+
+</contexts>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.ws.infopop/.cvsignore b/docs/org.eclipse.wst.ws.infopop/.cvsignore
new file mode 100644
index 0000000..c14487c
--- /dev/null
+++ b/docs/org.eclipse.wst.ws.infopop/.cvsignore
@@ -0,0 +1 @@
+build.xml
diff --git a/docs/org.eclipse.wst.ws.infopop/.project b/docs/org.eclipse.wst.ws.infopop/.project
new file mode 100644
index 0000000..527501f
--- /dev/null
+++ b/docs/org.eclipse.wst.ws.infopop/.project
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.wst.ws.infopop</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ <buildCommand>
+ <name>org.eclipse.pde.ManifestBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.pde.SchemaBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ </buildSpec>
+ <natures>
+ <nature>org.eclipse.pde.PluginNature</nature>
+ </natures>
+</projectDescription>
diff --git a/docs/org.eclipse.wst.ws.infopop/META-INF/MANIFEST.MF b/docs/org.eclipse.wst.ws.infopop/META-INF/MANIFEST.MF
new file mode 100644
index 0000000..04f84f3
--- /dev/null
+++ b/docs/org.eclipse.wst.ws.infopop/META-INF/MANIFEST.MF
@@ -0,0 +1,8 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: %pluginName
+Bundle-SymbolicName: org.eclipse.wst.ws.infopop; singleton:=true
+Bundle-Version: 1.0.203.qualifier
+Bundle-Localization: plugin
+Eclipse-LazyStart: true
+Bundle-Vendor: %providerName
diff --git a/docs/org.eclipse.wst.ws.infopop/about.html b/docs/org.eclipse.wst.ws.infopop/about.html
new file mode 100644
index 0000000..73db36e
--- /dev/null
+++ b/docs/org.eclipse.wst.ws.infopop/about.html
@@ -0,0 +1,34 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<HTML>
+
+<head>
+<title>About</title>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+</head>
+
+<BODY lang="EN-US">
+
+<H3>About This Content</H3>
+
+<P>June 06, 2007</P>
+
+<H3>License</H3>
+
+<P>The Eclipse Foundation makes available all content in this plug-in
+("Content"). Unless otherwise indicated below, the Content is provided to you
+under the terms and conditions of the Eclipse Public License Version 1.0
+("EPL"). A copy of the EPL is available at
+<A href="http://www.eclipse.org/org/documents/epl-v10.php">http://www.eclipse.org/org/documents/epl-v10.php</A>.
+For purposes of the EPL, "Program" will mean the Content.</P>
+
+<P>If you did not receive this Content directly from the Eclipse Foundation, the
+Content is being redistributed by another party ("Redistributor") and different
+terms and conditions may apply to your use of any object code in the Content.
+Check the Redistributors license that was provided with the Content. If no such
+license exists, contact the Redistributor. Unless otherwise indicated below, the
+terms and conditions of the EPL still apply to any source code in the Content
+and such source code may be obtained at
+<A href="http://www.eclipse.org/">http://www.eclipse.org/</A>.</P>
+
+</BODY>
+</HTML>
diff --git a/docs/org.eclipse.wst.ws.infopop/build.properties b/docs/org.eclipse.wst.ws.infopop/build.properties
new file mode 100644
index 0000000..31a159b
--- /dev/null
+++ b/docs/org.eclipse.wst.ws.infopop/build.properties
@@ -0,0 +1,6 @@
+bin.includes = about.html,\
+ plugin.xml,\
+ webserviceui-f1Contexts.xml,\
+ META-INF/,\
+ plugin.properties
+src.includes = build.properties
diff --git a/docs/org.eclipse.wst.ws.infopop/plugin.properties b/docs/org.eclipse.wst.ws.infopop/plugin.properties
new file mode 100644
index 0000000..df3b57f
--- /dev/null
+++ b/docs/org.eclipse.wst.ws.infopop/plugin.properties
@@ -0,0 +1,13 @@
+###############################################################################
+# Copyright (c) 2006 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
+###############################################################################
+
+pluginName = Web Services UI
+providerName = Eclipse.org
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.ws.infopop/plugin.xml b/docs/org.eclipse.wst.ws.infopop/plugin.xml
new file mode 100644
index 0000000..3fe3bfd
--- /dev/null
+++ b/docs/org.eclipse.wst.ws.infopop/plugin.xml
@@ -0,0 +1,18 @@
+<?xml version="1.0" ?>
+<?eclipse version="3.0"?>
+<?NLS TYPE="org.eclipse.help.toc"?>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2007 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * IBM Corporation - initial API and implementation
+ *******************************************************************************/ -->
+<plugin>
+ <extension point="org.eclipse.help.contexts">
+ <contexts file="webserviceui-f1Contexts.xml" plugin="org.eclipse.wst.ws.ui"/>
+ </extension>
+</plugin>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.ws.infopop/webserviceui-f1Contexts.xml b/docs/org.eclipse.wst.ws.infopop/webserviceui-f1Contexts.xml
new file mode 100644
index 0000000..bed6711
--- /dev/null
+++ b/docs/org.eclipse.wst.ws.infopop/webserviceui-f1Contexts.xml
@@ -0,0 +1,137 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?NLS TYPE="org.eclipse.help.contexts"?>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+
+<contexts>
+
+<!--WSIPage.java-->
+<context id="PWSI0001">
+<!--desc-->
+<description>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.
+
+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:
+- Require WS-I compliance - this level prevents you from creating a non-compliant Web service.
+- 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.
+- Ignore WS-I compliance - this level allows you to create a non-compliant Web service and does not notify you of non-compliance.
+
+You can also select which types of WSDL files to run validation on:
+- By selecting "No wizard WSDL validation" the wizards will not run validation on the WSDL file.
+- By selecting to run validation on remote files, the wizards will only validate WSDL files that exist outside of your workspace.
+- By selecting to run validation on all WSDL files the wizard will validate all WSDL files, regardless of where they reside.
+
+If you select to wait for WSDL validation to complete, the Web services wizards will prevent you from going forward and completing additional wizard pages once you have selected your WSDL file until that WSDL file has been validated. If the WSDL file is not valid, you will be given the option of exiting the wizard or continuing with the invalid WSDL file.
+</description>
+</context>
+
+<context id="PWSI0004">
+<description>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.
+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:
+- Require WS-I compliance - this level prevents you from creating a non-compliant Web service.
+- 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.
+- Ignore WS-I compliance - this level allows you to create a non-compliant Web service and does not notify you of non-compliance.
+</description>
+</context>
+
+<context id="PWSI0008">
+<description>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.
+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:
+- Require WS-I compliance - this level prevents you from creating a non-compliant Web service.
+- 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.
+- Ignore WS-I compliance - this level allows you to create a non-compliant Web service and does not notify you of non-compliance.
+</description>
+</context>
+
+<context id="PWSI0009">
+<!--desc-->
+<description>
+You can select which types of WSDL files to run validation on:
+- By selecting "No wizard WSDL validation" the wizards will not run validation on the WSDL file.
+- By selecting to run validation on remote files, the wizards will only validate WSDL files that exist outside of your workspace.
+- By selecting to run validation on all WSDL files the wizard will validate all WSDL files, regardless of where they reside.
+</description>
+</context>
+
+<context id="PWSI0010">
+<!--desc-->
+<description>
+You can select which types of WSDL files to run validation on:
+- By selecting "No wizard WSDL validation" the wizards will not run validation on the WSDL file.
+- By selecting to run validation on remote files, the wizards will only validate WSDL files that exist outside of your workspace.
+- By selecting to run validation on all WSDL files the wizard will validate all WSDL files, regardless of where they reside.
+</description>
+</context>
+
+<context id="PWSI00011">
+<!--desc-->
+<description>
+You can select which types of WSDL files to run validation on:
+- By selecting "No wizard WSDL validation" the wizards will not run validation on the WSDL file.
+- By selecting to run validation on remote files, the wizards will only validate WSDL files that exist outside of your workspace.
+- By selecting to run validation on all WSDL files the wizard will validate all WSDL files, regardless of where they reside.
+</description>
+</context>
+
+<context id="PWSI0012">
+<!--desc-->
+<description>
+If you select to wait for WSDL validation to complete, the Web services wizards will prevent you from going forward and completing additional wizard pages once you have selected your WSDL file until that WSDL file has been validated. If the WSDL file is not valid, you will be given the option of exiting the wizard or continuing with the invalid WSDL file.
+</description>
+</context>
+
+<context id="PWRS00009">
+<!--desc-->
+<description>
+You can select which types of WSDL files to run validation on:
+- By selecting "No wizard WSDL validation" the wizards will not run validation on the WSDL file.
+- By selecting to run validation on remote files, the wizards will only validate WSDL files that exist outside of your workspace.
+- By selecting to run validation on all WSDL files the wizard will validate all WSDL files, regardless of where they reside.
+</description>
+</context>
+
+<context id="PWRS00010">
+<!--desc-->
+<description>
+You can select which types of WSDL files to run validation on:
+- By selecting "No wizard WSDL validation" the wizards will not run validation on the WSDL file.
+- By selecting to run validation on remote files, the wizards will only validate WSDL files that exist outside of your workspace.
+- By selecting to run validation on all WSDL files the wizard will validate all WSDL files, regardless of where they reside.
+</description>
+</context>
+
+<context id="PWRS00011">
+<!--desc-->
+<description>
+You can select which types of WSDL files to run validation on:
+- By selecting "No wizard WSDL validation" the wizards will not run validation on the WSDL file.
+- By selecting to run validation on remote files, the wizards will only validate WSDL files that exist outside of your workspace.
+- By selecting to run validation on all WSDL files the wizard will validate all WSDL files, regardless of where they reside.
+</description>
+</context>
+
+<context id="PWRS00012">
+<!--desc-->
+<description>
+You can select which types of WSDL files to run validation on:
+- By selecting "No wizard WSDL validation" the wizards will not run validation on the WSDL file.
+- By selecting to run validation on remote files, the wizards will only validate WSDL files that exist outside of your workspace.
+- By selecting to run validation on all WSDL files the wizard will validate all WSDL files, regardless of where they reside.
+</description>
+</context>
+
+<context id="PWRS0013">
+<!--desc-->
+<description>
+If you select to wait for WSDL validation to complete, the Web services wizards will prevent you from going forward and completing additional wizard pages once you have selected your WSDL file until that WSDL file has been validated. If the WSDL file is not valid, you will be given the option of exiting the wizard or continuing with the invalid WSDL file.
+</description>
+</context>
+
+</contexts>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/.cvsignore b/docs/org.eclipse.wst.wsdl.ui.doc.user/.cvsignore
new file mode 100644
index 0000000..77adf97
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/.cvsignore
@@ -0,0 +1,4 @@
+org.eclipse.wst.wsdl.ui.doc.user_1.0.0.jar
+build.xml
+bak
+temp
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/.project b/docs/org.eclipse.wst.wsdl.ui.doc.user/.project
new file mode 100644
index 0000000..2785100
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/.project
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.wst.wsdl.ui.doc.user</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ <buildCommand>
+ <name>org.eclipse.pde.ManifestBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.pde.SchemaBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ </buildSpec>
+ <natures>
+ <nature>org.eclipse.pde.PluginNature</nature>
+ </natures>
+</projectDescription>
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/.settings/org.eclipse.core.resources.prefs b/docs/org.eclipse.wst.wsdl.ui.doc.user/.settings/org.eclipse.core.resources.prefs
new file mode 100644
index 0000000..c9c2647
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/.settings/org.eclipse.core.resources.prefs
@@ -0,0 +1,3 @@
+#Sun Apr 16 18:01:25 EDT 2006
+eclipse.preferences.version=1
+encoding/<project>=ISO-8859-1
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/.settings/org.eclipse.pde.prefs b/docs/org.eclipse.wst.wsdl.ui.doc.user/.settings/org.eclipse.pde.prefs
new file mode 100644
index 0000000..54ec5d8
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/.settings/org.eclipse.pde.prefs
@@ -0,0 +1,13 @@
+#Sun Apr 16 18:01:32 EDT 2006
+compilers.p.build=0
+compilers.p.deprecated=0
+compilers.p.no-required-att=0
+compilers.p.not-externalized-att=0
+compilers.p.unknown-attribute=0
+compilers.p.unknown-class=0
+compilers.p.unknown-element=0
+compilers.p.unknown-resource=0
+compilers.p.unresolved-ex-points=0
+compilers.p.unresolved-import=0
+compilers.use-project=true
+eclipse.preferences.version=1
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/DocBuild.xml b/docs/org.eclipse.wst.wsdl.ui.doc.user/DocBuild.xml
new file mode 100644
index 0000000..bd4b3fa
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/DocBuild.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.2" />
+
+ <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/META-INF/MANIFEST.MF b/docs/org.eclipse.wst.wsdl.ui.doc.user/META-INF/MANIFEST.MF
new file mode 100644
index 0000000..898e22f
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/META-INF/MANIFEST.MF
@@ -0,0 +1,8 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: %pluginName
+Bundle-SymbolicName: org.eclipse.wst.wsdl.ui.doc.user; singleton:=true
+Bundle-Version: 1.0.300.qualifier
+Bundle-Vendor: %pluginProvider
+Bundle-Localization: plugin
+Eclipse-LazyStart: true
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/about.html b/docs/org.eclipse.wst.wsdl.ui.doc.user/about.html
new file mode 100644
index 0000000..73db36e
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/about.html
@@ -0,0 +1,34 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<HTML>
+
+<head>
+<title>About</title>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+</head>
+
+<BODY lang="EN-US">
+
+<H3>About This Content</H3>
+
+<P>June 06, 2007</P>
+
+<H3>License</H3>
+
+<P>The Eclipse Foundation makes available all content in this plug-in
+("Content"). Unless otherwise indicated below, the Content is provided to you
+under the terms and conditions of the Eclipse Public License Version 1.0
+("EPL"). A copy of the EPL is available at
+<A href="http://www.eclipse.org/org/documents/epl-v10.php">http://www.eclipse.org/org/documents/epl-v10.php</A>.
+For purposes of the EPL, "Program" will mean the Content.</P>
+
+<P>If you did not receive this Content directly from the Eclipse Foundation, the
+Content is being redistributed by another party ("Redistributor") and different
+terms and conditions may apply to your use of any object code in the Content.
+Check the Redistributors license that was provided with the Content. If no such
+license exists, contact the Redistributor. Unless otherwise indicated below, the
+terms and conditions of the EPL still apply to any source code in the Content
+and such source code may be obtained at
+<A href="http://www.eclipse.org/">http://www.eclipse.org/</A>.</P>
+
+</BODY>
+</HTML>
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/build.properties b/docs/org.eclipse.wst.wsdl.ui.doc.user/build.properties
new file mode 100644
index 0000000..a701682
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/build.properties
@@ -0,0 +1,18 @@
+bin.includes = wswsdleditorc_toc.xml,\
+ wswsdleditort_toc.xml,\
+ about.html,\
+ org.eclipse.wst.wsdl.ui.doc.userindex.xml,\
+ images/,\
+ plugin.properties,\
+ plugin.xml,\
+ concepts/*.htm*,\
+ tasks/*.htm*,\
+ index/,\
+ META-INF/
+src.includes = build.properties,\
+ *.maplist,\
+ *.ditamap,\
+ concepts/*.dita,\
+ tasks/*.dita
+bin.excludes = DocBuild.xml,\
+ myPlugin*.xml
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 0000000..60bfda9
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/concepts/cwsdled.dita
@@ -0,0 +1,57 @@
+<?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">
+<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 *0000002617?>
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
new file mode 100644
index 0000000..55d7572
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/concepts/cwsdled.html
@@ -0,0 +1,95 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="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/common.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>
+
+<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 <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>
+<div class="linklist"><strong>Related concepts</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.html">WSDL</a></div></div>
+
+<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 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/images/httpskel.gif b/docs/org.eclipse.wst.wsdl.ui.doc.user/images/httpskel.gif
new file mode 100644
index 0000000..e2e6686
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/images/httpskel.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/images/show-hide-binding.gif b/docs/org.eclipse.wst.wsdl.ui.doc.user/images/show-hide-binding.gif
new file mode 100644
index 0000000..cda9b58
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/images/show-hide-binding.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/images/soapskel.gif b/docs/org.eclipse.wst.wsdl.ui.doc.user/images/soapskel.gif
new file mode 100644
index 0000000..8042735
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/images/soapskel.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/images/wsdleditor.gif b/docs/org.eclipse.wst.wsdl.ui.doc.user/images/wsdleditor.gif
new file mode 100644
index 0000000..ccbe3b9
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/images/wsdleditor.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/index/_f.cfs b/docs/org.eclipse.wst.wsdl.ui.doc.user/index/_f.cfs
new file mode 100644
index 0000000..1f8018a
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/index/_f.cfs
Binary files differ
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/index/deletable b/docs/org.eclipse.wst.wsdl.ui.doc.user/index/deletable
new file mode 100644
index 0000000..e423242
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/index/deletable
Binary files differ
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/index/indexed_contributions b/docs/org.eclipse.wst.wsdl.ui.doc.user/index/indexed_contributions
new file mode 100644
index 0000000..66de68d
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/index/indexed_contributions
@@ -0,0 +1,3 @@
+#This is a generated file; do not edit.
+#Wed May 09 14:15:38 EDT 2007
+org.eclipse.wst.wsdl.ui.doc.user=org.eclipse.wst.wsdl.ui.doc.user\n1.0.300.qualifier
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/index/indexed_dependencies b/docs/org.eclipse.wst.wsdl.ui.doc.user/index/indexed_dependencies
new file mode 100644
index 0000000..eb4868a
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/index/indexed_dependencies
@@ -0,0 +1,4 @@
+#This is a generated file; do not edit.
+#Wed May 09 14:15:38 EDT 2007
+lucene=1.4.103.v20060601
+analyzer=org.eclipse.help.base\#3.2.0.v20060601?locale\=en
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/index/indexed_docs b/docs/org.eclipse.wst.wsdl.ui.doc.user/index/indexed_docs
new file mode 100644
index 0000000..6612889
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/index/indexed_docs
@@ -0,0 +1,16 @@
+#This is a generated file; do not edit.
+#Wed May 09 14:15:38 EDT 2007
+/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetbind.html=0
+/org.eclipse.wst.wsdl.ui.doc.user/concepts/cwsdled.html=0
+/org.eclipse.wst.wsdl.ui.doc.user/tasks/tedtwsdl.html=0
+/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddpart.html=0
+/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddsrvc.html=0
+/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddoper.html=0
+/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetprtt.html=0
+/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddmess.html=0
+/org.eclipse.wst.wsdl.ui.doc.user/../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdlexp.html=0
+/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtwsdl.html=0
+/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtimpt.html=0
+/org.eclipse.wst.wsdl.ui.doc.user/tasks/timpwsdl.html=0
+/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddport.html=0
+/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrttype.html=0
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/index/segments b/docs/org.eclipse.wst.wsdl.ui.doc.user/index/segments
new file mode 100644
index 0000000..19b5d0c
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/index/segments
Binary files differ
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 0000000..17ece74
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/myplugin.xml
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?eclipse version="3.0"?>
+<?NLS TYPE="org.eclipse.help.toc"?>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2007 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * IBM Corporation - initial API and implementation
+ *******************************************************************************/ -->
+<!-- ================================================= -->
+<!-- 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"/>
+ <index path="index/"/>
+
+</extension>
+<extension point="org.eclipse.help.index">
+ <index file="org.eclipse.wst.wsdl.ui.doc.userindex.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 0000000..ddeb99f
--- /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/org.eclipse.wst.wsdl.ui.doc.userindex.html b/docs/org.eclipse.wst.wsdl.ui.doc.user/org.eclipse.wst.wsdl.ui.doc.userindex.html
new file mode 100644
index 0000000..210697f
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/org.eclipse.wst.wsdl.ui.doc.userindex.html
@@ -0,0 +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 lang="en-us" xml:lang="en-us">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<meta name="copyright" content="(C) Copyright IBM Corporation 2007" />
+<meta name="security" content="public" />
+<meta name="Robots" content="index,follow" />
+<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 name="DC.Format" content="XHTML" />
+<!-- All rights reserved. Licensed Materials Property of IBM -->
+<!-- US Government Users Restricted Rights -->
+<!-- Use, duplication or disclosure restricted by -->
+<!-- GSA ADP Schedule Contract with IBM Corp. -->
+<link rel="stylesheet" type="text/css" href="ibmdita.css" />
+<title>Index</title>
+</head>
+<body>
+<h1>Index</h1>
+<a name="IDX0_57" href="#IDX1_57">W</a>
+<hr></hr>
+<strong><a name="IDX1_57" href="#IDX0_57">W</a></strong>
+<ul class="indexlist">
+<li>Web services
+<ul class="indexlist">
+<li><a href="tasks/taddsrvc.html#taddsrvc">adding services to WSDL</a>
+</li>
+<li><a href="tasks/tcrtimpt.html#tcrtimpt">adding WSDL import statements</a>
+</li>
+<li><a href="tasks/taddpart.html#taddpart">adding WSDL message parts</a>
+</li>
+<li><a href="tasks/taddmess.html#taddmess">adding WSDL messages</a>
+</li>
+<li><a href="tasks/taddoper.html#taddoper">adding WSDL operations</a>
+</li>
+<li><a href="tasks/taddport.html#taddport">adding WSDL ports</a>
+</li>
+<li>bindings
+<ul class="indexlist">
+<li><a href="tasks/tsetbind.html#tsetbind">creating</a>
+</li>
+</ul>
+</li>
+<li><a href="tasks/tcrtwsdl.html#tcrtwsdl">creating WSDL</a>
+</li>
+<li><a href="tasks/tcrttype.html#tcrttype">creating WSDL types</a>
+</li>
+<li><a href="tasks/tedtwsdl.html#tedtwsdl">editing WSDL</a>
+</li>
+<li><a href="tasks/timpwsdl.html#timpwsdl">importing WSDL</a>
+</li>
+<li><a href="tasks/tsetprtt.html#tsetprtt">setting port types</a>
+</li>
+<li><a href="tasks/tsetbind.html#tsetbind">setting WSDL bindings</a>
+</li>
+</ul>
+</li>
+<li>WSDL
+<ul class="indexlist">
+<li><a href="tasks/tsetbind.html#tsetbind">bindings</a>
+</li>
+<li><a href="tasks/tcrtwsdl.html#tcrtwsdl">creating</a>
+</li>
+<li><a href="tasks/tedtwsdl.html#tedtwsdl">editing</a>
+</li>
+<li><a href="tasks/tcrtimpt.html#tcrtimpt">import statements</a>
+</li>
+<li><a href="tasks/timpwsdl.html#timpwsdl">importing</a>
+</li>
+<li><a href="tasks/taddpart.html#taddpart">message parts</a>
+</li>
+<li><a href="tasks/taddmess.html#taddmess">messages</a>
+</li>
+<li><a href="tasks/taddoper.html#taddoper">operations</a>
+</li>
+<li><a href="tasks/taddport.html#taddport">ports</a>
+</li>
+<li><a href="tasks/taddsrvc.html#taddsrvc">services</a>
+</li>
+<li><a href="tasks/tsetprtt.html#tsetprtt">setting port types</a>
+</li>
+<li><a href="tasks/tcrttype.html#tcrttype">types</a>
+</li>
+</ul>
+</li>
+</ul>
+</body></html>
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/org.eclipse.wst.wsdl.ui.doc.userindex.xml b/docs/org.eclipse.wst.wsdl.ui.doc.user/org.eclipse.wst.wsdl.ui.doc.userindex.xml
new file mode 100644
index 0000000..f9f2f5c
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/org.eclipse.wst.wsdl.ui.doc.userindex.xml
@@ -0,0 +1,84 @@
+<?xml version="1.0" encoding="utf-8"?>
+<index>
+ <entry keyword="WSDL">
+ <entry keyword="importing">
+ <topic href="tasks/timpwsdl.html#timpwsdl" title="Importing a WSDL file"/>
+ </entry>
+ <entry keyword="creating">
+ <topic href="tasks/tcrtwsdl.html#tcrtwsdl" title="Creating a new WSDL file"/>
+ </entry>
+ <entry keyword="editing">
+ <topic href="tasks/tedtwsdl.html#tedtwsdl" title="Editing WSDL files"/>
+ </entry>
+ <entry keyword="services">
+ <topic href="tasks/taddsrvc.html#taddsrvc" title="Adding a service"/>
+ </entry>
+ <entry keyword="ports">
+ <topic href="tasks/taddport.html#taddport" title="Adding a port to a service"/>
+ </entry>
+ <entry keyword="setting port types">
+ <topic href="tasks/tsetprtt.html#tsetprtt" title="Setting a port type"/>
+ </entry>
+ <entry keyword="bindings">
+ <topic href="tasks/tsetbind.html#tsetbind" title="Setting a binding"/>
+ </entry>
+ <entry keyword="operations">
+ <topic href="tasks/taddoper.html#taddoper" title="Adding an operation"/>
+ </entry>
+ <entry keyword="messages">
+ <topic href="tasks/taddmess.html#taddmess" title="Adding a message"/>
+ </entry>
+ <entry keyword="message parts">
+ <topic href="tasks/taddpart.html#taddpart" title="Adding a part to a message"/>
+ </entry>
+ <entry keyword="import statements">
+ <topic href="tasks/tcrtimpt.html#tcrtimpt" title="Creating an import statement"/>
+ </entry>
+ <entry keyword="types">
+ <topic href="tasks/tcrttype.html#tcrttype" title="Creating a new type for your WSDL file"/>
+ </entry>
+ </entry>
+ <entry keyword="Web services">
+ <entry keyword="importing WSDL">
+ <topic href="tasks/timpwsdl.html#timpwsdl" title="Importing a WSDL file"/>
+ </entry>
+ <entry keyword="creating WSDL">
+ <topic href="tasks/tcrtwsdl.html#tcrtwsdl" title="Creating a new WSDL file"/>
+ </entry>
+ <entry keyword="editing WSDL">
+ <topic href="tasks/tedtwsdl.html#tedtwsdl" title="Editing WSDL files"/>
+ </entry>
+ <entry keyword="adding services to WSDL">
+ <topic href="tasks/taddsrvc.html#taddsrvc" title="Adding a service"/>
+ </entry>
+ <entry keyword="adding WSDL ports">
+ <topic href="tasks/taddport.html#taddport" title="Adding a port to a service"/>
+ </entry>
+ <entry keyword="setting port types">
+ <topic href="tasks/tsetprtt.html#tsetprtt" title="Setting a port type"/>
+ </entry>
+ <entry keyword="bindings">
+ <entry keyword="creating">
+ <topic href="tasks/tsetbind.html#tsetbind" title="Setting a binding"/>
+ </entry>
+ </entry>
+ <entry keyword="setting WSDL bindings">
+ <topic href="tasks/tsetbind.html#tsetbind" title="Setting a binding"/>
+ </entry>
+ <entry keyword="adding WSDL operations">
+ <topic href="tasks/taddoper.html#taddoper" title="Adding an operation"/>
+ </entry>
+ <entry keyword="adding WSDL messages">
+ <topic href="tasks/taddmess.html#taddmess" title="Adding a message"/>
+ </entry>
+ <entry keyword="adding WSDL message parts">
+ <topic href="tasks/taddpart.html#taddpart" title="Adding a part to a message"/>
+ </entry>
+ <entry keyword="adding WSDL import statements">
+ <topic href="tasks/tcrtimpt.html#tcrtimpt" title="Creating an import statement"/>
+ </entry>
+ <entry keyword="creating WSDL types">
+ <topic href="tasks/tcrttype.html#tcrttype" title="Creating a new type for your WSDL file"/>
+ </entry>
+ </entry>
+</index>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/plugin.properties b/docs/org.eclipse.wst.wsdl.ui.doc.user/plugin.properties
new file mode 100644
index 0000000..a216421
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/plugin.properties
@@ -0,0 +1,15 @@
+###############################################################################
+# Copyright (c) 2001, 2005 IBM Corporation and others.
+# All rights reserved. This program and the accompanying materials
+# are made available under the terms of the Eclipse Public License v1.0
+# which accompanies this distribution, and is available at
+# http://www.eclipse.org/legal/epl-v10.html
+#
+# Contributors:
+# IBM Corporation - initial API and implementation
+###############################################################################
+# NLS_MESSAGEFORMAT_VAR
+# NLS_ENCODING=UTF-8
+
+pluginName = WSDL Editor Documentation
+pluginProvider = Eclipse.org
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/plugin.xml b/docs/org.eclipse.wst.wsdl.ui.doc.user/plugin.xml
new file mode 100644
index 0000000..17ece74
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/plugin.xml
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?eclipse version="3.0"?>
+<?NLS TYPE="org.eclipse.help.toc"?>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2007 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * IBM Corporation - initial API and implementation
+ *******************************************************************************/ -->
+<!-- ================================================= -->
+<!-- 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"/>
+ <index path="index/"/>
+
+</extension>
+<extension point="org.eclipse.help.index">
+ <index file="org.eclipse.wst.wsdl.ui.doc.userindex.xml"/>
+</extension>
+
+
+</plugin>
\ No newline at end of file
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 0000000..ef348a0
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddmess.dita
@@ -0,0 +1,87 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>Web services<indexterm>adding WSDL messages</indexterm></indexterm>
+<indexterm>WSDL<indexterm>messages</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<taskbody>
+<context><p>You can create a message using the Outline view by right-clicking
+the <b>Messages</b> folder and clicking <b>Add Message</b>.</p><p>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 Design view, right-click your input, output, or fault element
+and click <b>Set Message > New Message.</b></cmd></step>
+<step><cmd>Type the name of the message in 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 Design view within the port
+type.</cmd></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 > Add 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 Design view, right-click your input, output, or fault element and
+click <b>Set Message > Existing Message.</b></li>
+<li>In the <b>Name</b> field, type a search string to filter the list or leave
+the field blank to view all.</li>
+<li>You can change the scope of the list by selecting one of the following
+options:<ul>
+<li><b>Workspace</b>. Lists the messages available in your workspace.</li>
+<li><b>Enclosing Project</b>. Lists the messages available in the project
+that contains your file.</li>
+<li><b>Current Resource</b>. Lists the messages available in your current
+file.</li>
+<li><b>Working Sets</b>. Lists the messages available in a specified set of
+files. To specify a working set, click <b>Choose</b>. You can select files
+from an existing working set or create a new working set. Once you have selected
+the files, click <b>OK</b>.</li>
+</ul></li>
+<li>The existing messages will be listed. Select one and click <b>OK</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 Design view, right-click your input, output, or fault element and
+click <b>Set Message > Existing Message.</b></li>
+<li>In the <b>Name</b> field, type a search string to filter the list or leave
+the field blank to view all.</li>
+<li>You can import a message by selecting one of the following options:<ul>
+<li><b>Workspace</b>. Lists the messages available in your workspace.</li>
+<li><b>Enclosing Project</b>. Lists the messages available in the project
+that contains your file.</li>
+<li><b>Working Sets</b>. Lists the messages available in a specified set of
+files. To specify a working set, click <b>Choose</b>. You can select files
+from an existing working set or create a new working set. Once you have selected
+the files, click <b>OK</b>.</li>
+</ul></li>
+<li>The messages will be listed. Select one and click <b>OK</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>
+<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 *0000004676?>
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
new file mode 100644
index 0000000..f02e221
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddmess.html
@@ -0,0 +1,142 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="Adding a message" />
+<meta name="abstract" content="Messages represent an abstract definition of the data being transmitted. A message consists of logical parts, each of which is associated with a definition within some type system. WSDL messages are top level objects that can be referenced by an operation's input, output and fault elements (within a port type)." />
+<meta name="description" content="Messages represent an abstract definition of the data being transmitted. A message consists of logical parts, each of which is associated with a definition within some type system. WSDL messages are top level objects that can be referenced by an operation's input, output and fault elements (within a port type)." />
+<meta content="WSDL, adding messages, Web services, adding WSDL messages" name="DC.subject" />
+<meta content="WSDL, adding messages, Web services, adding WSDL messages" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../concepts/cwsdled.html" />
+<meta scheme="URI" name="DC.Relation" content="tcrtwsdl.html" />
+<meta scheme="URI" name="DC.Relation" content="tedtwsdl.html" />
+<meta content="XHTML" name="DC.Format" />
+<meta content="taddmess" name="DC.Identifier" />
+<meta content="en-us" name="DC.Language" />
+<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
+<title>Adding a message</title>
+</head>
+<body id="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>You can create a message using the Outline view by right-clicking
+the <strong>Messages</strong> folder and clicking <strong>Add Message</strong>.</p>
+<p>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 Design view, right-click your input, output, or fault element
+and click <strong>Set Message > New Message.</strong></span></li>
+
+<li class="stepexpand"><span>Type the name of the message in 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 Design view within the port
+type.</span></li>
+
+</ol>
+
+<div class="section"><p> <strong>Note</strong>: Messages are referenced within a port type (specifically
+by an operation's input, output and fault objects). The input, output and
+fault objects within a binding do not reference messages. Hence you cannot
+create a new message by right clicking on a input, output, or fault within
+a binding (these are also known as binding input, binding output and binding
+faults).</p>
+<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 > Add 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 Design view, right-click your input, output, or fault element and
+click <strong>Set Message > Existing Message.</strong></li>
+
+<li>In the <strong>Name</strong> field, type a search string to filter the list or leave
+the field blank to view all.</li>
+
+<li>You can change the scope of the list by selecting one of the following
+options:<ul>
+<li><strong>Workspace</strong>. Lists the messages available in your workspace.</li>
+
+<li><strong>Enclosing Project</strong>. Lists the messages available in the project
+that contains your file.</li>
+
+<li><strong>Current Resource</strong>. Lists the messages available in your current
+file.</li>
+
+<li><strong>Working Sets</strong>. Lists the messages available in a specified set of
+files. To specify a working set, click <strong>Choose</strong>. You can select files
+from an existing working set or create a new working set. Once you have selected
+the files, click <strong>OK</strong>.</li>
+
+</ul>
+</li>
+
+<li>The existing messages will be listed. Select one and click <strong>OK</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 Design view, right-click your input, output, or fault element and
+click <strong>Set Message > Existing Message.</strong></li>
+
+<li>In the <strong>Name</strong> field, type a search string to filter the list or leave
+the field blank to view all.</li>
+
+<li>You can import a message by selecting one of the following options:<ul>
+<li><strong>Workspace</strong>. Lists the messages available in your workspace.</li>
+
+<li><strong>Enclosing Project</strong>. Lists the messages available in the project
+that contains your file.</li>
+
+<li><strong>Working Sets</strong>. Lists the messages available in a specified set of
+files. To specify a working set, click <strong>Choose</strong>. You can select files
+from an existing working set or create a new working set. Once you have selected
+the files, click <strong>OK</strong>.</li>
+
+</ul>
+</li>
+
+<li>The messages will be listed. Select one and click <strong>OK</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="linklist"><strong>Related concepts</strong><br />
+
+<div><a href="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></div></div>
+
+<div class="linklist"><strong>Related tasks</strong><br />
+
+<div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div>
+<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div>
+</div>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddoper.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddoper.dita
new file mode 100644
index 0000000..ca691af
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddoper.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="taddoper" xml:lang="en-us">
+<title>Adding an operation</title>
+<shortdesc>An operation names the operation and lists the expected inputs
+and outputs. The operation element may also contain a fault sub-element that
+describes any error data the operation may return.</shortdesc>
+<prolog><metadata>
+<keywords><indexterm>Web services<indexterm>adding WSDL operations</indexterm></indexterm>
+<indexterm>WSDL<indexterm>operations</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<taskbody>
+<context>Using these, you can declare four transmission primitives that an
+endpoint can support:<ul>
+<li> <b>One-way</b>. The endpoint receives a message.</li>
+<li> <b>Request-response</b>. The endpoint receives a message, and sends a
+correlated message.</li>
+<li> <b>Solicit-response</b>. The endpoint sends a message, and receives a
+correlated message.</li>
+<li> <b>Notification</b>. The endpoint sends a message.</li>
+</ul><p>You can add an operation to a port type or a port binding.</p><p>To
+add an operation to a port type, follow these steps:</p></context>
+<steps>
+<step><cmd>In the Design view, right-click your port type.</cmd><info>Click <b>Add
+Operation</b>. To select the new operation, click the operation in the port
+type object.</info></step>
+<step><cmd>In the Properties view, click the <b>General</b> pane.</cmd></step>
+<step><cmd>In the <b>Name</b> field, type the name of the operation.</cmd>
+</step>
+<step><cmd>Right click on the operation to add input, output or fault objects.</cmd>
+<info>Depending on an operation's inputs and outputs it can be classified
+as follows:<ul>
+<li><b>One way operation</b>: input </li>
+<li><b>Request response operation</b>: input, output </li>
+<li><b> Solicit response operation</b>: output, input </li>
+<li><b>Notification operation</b>: output</li>
+</ul></info></step>
+<step><cmd>In the Properties view, type any information about the operation
+you wish the user to read in the <b>Documentation</b> pane.</cmd></step>
+</steps>
+<result><p> <b>Tip</b>: You can also create a new operation for your port
+type using the Outline view.</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 *0000002602?>
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
new file mode 100644
index 0000000..51d1d38
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddoper.html
@@ -0,0 +1,101 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="Adding an operation" />
+<meta name="abstract" content="An operation names the operation and lists the expected inputs and outputs. The operation element may also contain a fault sub-element that describes any error data the operation may return." />
+<meta name="description" content="An operation names the operation and lists the expected inputs and outputs. The operation element may also contain a fault sub-element that describes any error data the operation may return." />
+<meta content="WSDL, adding operations, Web services, adding WSDL operations" name="DC.subject" />
+<meta content="WSDL, adding operations, Web services, adding WSDL operations" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../concepts/cwsdled.html" />
+<meta scheme="URI" name="DC.Relation" content="tcrtwsdl.html" />
+<meta scheme="URI" name="DC.Relation" content="tedtwsdl.html" />
+<meta content="XHTML" name="DC.Format" />
+<meta content="taddoper" name="DC.Identifier" />
+<meta content="en-us" name="DC.Language" />
+<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
+<title>Adding an operation</title>
+</head>
+<body id="taddoper"><a name="taddoper"><!-- --></a>
+
+
+<h1 class="topictitle1">Adding an operation</h1>
+
+
+
+<div><p>An operation names the operation and lists the expected inputs
+and outputs. The operation element may also contain a fault sub-element that
+describes any error data the operation may return.</p>
+
+<div class="section">Using these, you can declare four transmission primitives that an
+endpoint can support:<ul>
+<li> <strong>One-way</strong>. The endpoint receives a message.</li>
+
+<li> <strong>Request-response</strong>. The endpoint receives a message, and sends a
+correlated message.</li>
+
+<li> <strong>Solicit-response</strong>. The endpoint sends a message, and receives a
+correlated message.</li>
+
+<li> <strong>Notification</strong>. The endpoint sends a message.</li>
+
+</ul>
+<p>You can add an operation to a port type or a port binding.</p>
+<p>To
+add an operation to a port type, follow these steps:</p>
+</div>
+
+<ol>
+<li class="stepexpand"><span>In the Design view, right-click your port type.</span> Click <strong>Add
+Operation</strong>. To select the new operation, click the operation in the port
+type object.</li>
+
+<li class="stepexpand"><span>In the Properties view, click the <strong>General</strong> pane.</span></li>
+
+<li class="stepexpand"><span>In the <strong>Name</strong> field, type the name of the operation.</span>
+</li>
+
+<li class="stepexpand"><span>Right click on the operation to add input, output or fault objects.</span>
+ Depending on an operation's inputs and outputs it can be classified
+as follows:<ul>
+<li><strong>One way operation</strong>: input </li>
+
+<li><strong>Request response operation</strong>: input, output </li>
+
+<li><strong> Solicit response operation</strong>: output, input </li>
+
+<li><strong>Notification operation</strong>: output</li>
+
+</ul>
+</li>
+
+<li class="stepexpand"><span>In the Properties view, type any information about the operation
+you wish the user to read in the <strong>Documentation</strong> pane.</span></li>
+
+</ol>
+
+<div class="section"><p> <strong>Tip</strong>: You can also create a new operation for your port
+type using the Outline view.</p>
+</div>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related concepts</strong><br />
+
+<div><a href="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></div></div>
+
+<div class="linklist"><strong>Related tasks</strong><br />
+
+<div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div>
+<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div>
+</div>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddpart.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddpart.dita
new file mode 100644
index 0000000..a8b9452
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddpart.dita
@@ -0,0 +1,53 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>Web services<indexterm>adding WSDL message parts</indexterm></indexterm>
+<indexterm>WSDL<indexterm>message parts</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<taskbody>
+<context><p>To add a part to a message, follow these steps:</p></context>
+<steps>
+<step><cmd>In Design view, right-click an input, output, or fault object and
+click <b>Add Part</b>. </cmd><stepresult> The part is added to the input,
+output, or fault's message reference.</stepresult></step>
+<step><cmd>To select the part, click the part in the port type
+object.</cmd></step>
+<step><cmd>In the Properties view, click the <b>General</b> pane.</cmd></step>
+<step><cmd>In the <b>Name</b> field, type the name of the part.</cmd></step>
+<step><cmd>Your part can refer to either a <b>type</b> or an <b>element</b>.</cmd>
+<info>Select the appropriate option 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.</cmd><info>The list of types comes from any available referenced
+XML schemas.</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 XML schema element from the <b>Element</b> drop
+down list.</cmd><info>The list of elements comes from any available referenced
+XML schemas.</info></step>
+</steps>
+<result><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 Part</b>. Your part will automatically appear in the Outline
+view (under the <b>Messages</b> folder), but it will only appear in the Design
+view if the message you added it to currently does.</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 *0000002672?>
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
new file mode 100644
index 0000000..5a9ce0f
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddpart.html
@@ -0,0 +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 lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="Adding a part to a message" />
+<meta name="abstract" content="All messages contain one or more parts. Parts are a flexible mechanism for describing the logical abstract content of a message. The message definition associates each part with a type using a message-typing attribute." />
+<meta name="description" content="All messages contain one or more parts. Parts are a flexible mechanism for describing the logical abstract content of a message. The message definition associates each part with a type using a message-typing attribute." />
+<meta content="WSDL, adding message parts, Web services, adding WSDL message parts" name="DC.subject" />
+<meta content="WSDL, adding message parts, Web services, adding WSDL message parts" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../concepts/cwsdled.html" />
+<meta scheme="URI" name="DC.Relation" content="tcrtwsdl.html" />
+<meta scheme="URI" name="DC.Relation" content="tedtwsdl.html" />
+<meta content="XHTML" name="DC.Format" />
+<meta content="taddpart" name="DC.Identifier" />
+<meta content="en-us" name="DC.Language" />
+<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
+<title>Adding a part to a message</title>
+</head>
+<body id="taddpart"><a name="taddpart"><!-- --></a>
+
+
+<h1 class="topictitle1">Adding a part to a message</h1>
+
+
+
+<div><p>All messages contain one or more parts. Parts are a flexible mechanism
+for describing the logical abstract content of a message. The message definition
+associates each part with a type using a message-typing attribute.</p>
+
+<div class="section"><p>To add a part to a message, follow these steps:</p>
+</div>
+
+<ol>
+<li class="stepexpand"><span>In Design view, right-click an input, output, or fault object and
+click <strong>Add Part</strong>. </span> The part is added to the input,
+output, or fault's message reference.</li>
+
+<li class="stepexpand"><span>To select the part, click the part in the port type
+object.</span></li>
+
+<li class="stepexpand"><span>In the Properties view, click the <strong>General</strong> pane.</span></li>
+
+<li class="stepexpand"><span>In the <strong>Name</strong> field, type the name of the part.</span></li>
+
+<li class="stepexpand"><span>Your part can refer to either a <strong>type</strong> or an <strong>element</strong>.</span>
+ Select the appropriate option 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.</span> The list of types comes from any available referenced
+XML schemas.</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.</span> The list of elements comes from any available referenced
+XML schemas.</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 Part</strong>. Your part will automatically appear in the Outline
+view (under the <strong>Messages</strong> folder), but it will only appear in the Design
+view if the message you added it to currently does.</p>
+</div>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related concepts</strong><br />
+
+<div><a href="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></div></div>
+
+<div class="linklist"><strong>Related tasks</strong><br />
+
+<div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div>
+<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div>
+</div>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddport.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddport.dita
new file mode 100644
index 0000000..729fc37
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddport.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="taddport" xml:lang="en-us">
+<title>Adding a port to a service</title>
+<shortdesc>A port defines an individual endpoint by specifying a single address
+for a binding. The port contains a 'binding' attribute that references a binding
+and an address element that provides a specification for the endpoint.</shortdesc>
+<prolog><metadata>
+<keywords><indexterm>Web services<indexterm>adding WSDL ports</indexterm></indexterm>
+<indexterm>WSDL<indexterm>ports</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<taskbody>
+<context><p>Services are used to group sets of related ports together. Ports
+within a service have the following relationship:</p><ul>
+<li>None of the ports communicate with each other (for example, the output
+of one port is not the input of another).</li>
+<li>If a service has several ports that share a port type, but employ different
+bindings or addresses, the ports are alternatives. Each port provides semantically
+equivalent behavior (within the transport and message format limitations imposed
+by each binding).</li>
+<li>You can determine a service's port types by examining its ports. Using
+this information a user can determine if a given machine supports all the
+operations needed to complete a given task.</li>
+</ul><p>To add a port to a service, follow these steps:</p></context>
+<steps>
+<step><cmd>In the Design view, right-click the service you want to add a port
+to, then click <b>Add Port.</b> To select the new port, click the port in
+the service object.</cmd></step>
+<step><cmd>In the Properties view, click the <b>General</b> pane. In the <b>Name</b> field,
+type the name of the port.</cmd><info>The name of the port should provide
+it with a unique name amongst all the ports defined within the service.</info>
+</step>
+<step><cmd>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 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>In the <b>Address</b> field, type the address of the port.</cmd>
+</step>
+<step><cmd>Type any information about the port you want the user to read in
+the <b>Documentation</b> pane.</cmd></step>
+<step><cmd>To manage extensions, click the <b>Extensibility</b> pane. You
+can either add, sort, or remove extensions. <draft-comment>Refer to the related
+tasks for more details. Add link to XSD Editor in related tasks section.</draft-comment></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
+Port</b>. Your port (regardless of which view you create it in) will appear
+in both the Design view and the Outline view.</p></result>
+</taskbody>
+<related-links>
+<linklist><title>Related concepts</title>
+<link href="../concepts/cwsdled.dita" scope="local"></link>
+</linklist>
+<linklist><title>Related tasks</title>
+<link href="tcrtwsdl.dita" scope="local"></link>
+<link href="tedtwsdl.dita" scope="local"></link>
+</linklist>
+</related-links>
+</task>
+<?Pub *0000003322?>
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
new file mode 100644
index 0000000..dbd031e
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddport.html
@@ -0,0 +1,102 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="Adding a port to a service" />
+<meta name="abstract" content="A port defines an individual endpoint by specifying a single address for a binding. The port contains a 'binding' attribute that references a binding and an address element that provides a specification for the endpoint." />
+<meta name="description" content="A port defines an individual endpoint by specifying a single address for a binding. The port contains a 'binding' attribute that references a binding and an address element that provides a specification for the endpoint." />
+<meta content="WSDL, adding ports, Web services, adding WSDL ports" name="DC.subject" />
+<meta content="WSDL, adding ports, Web services, adding WSDL ports" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../concepts/cwsdled.html" />
+<meta scheme="URI" name="DC.Relation" content="tcrtwsdl.html" />
+<meta scheme="URI" name="DC.Relation" content="tedtwsdl.html" />
+<meta content="XHTML" name="DC.Format" />
+<meta content="taddport" name="DC.Identifier" />
+<meta content="en-us" name="DC.Language" />
+<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
+<title>Adding a port to a service</title>
+</head>
+<body id="taddport"><a name="taddport"><!-- --></a>
+
+
+<h1 class="topictitle1">Adding a port to a service</h1>
+
+
+
+<div><p>A port defines an individual endpoint by specifying a single address
+for a binding. The port contains a 'binding' attribute that references a binding
+and an address element that provides a specification for the endpoint.</p>
+
+<div class="section"><p>Services are used to group sets of related ports together. Ports
+within a service have the following relationship:</p>
+<ul>
+<li>None of the ports communicate with each other (for example, the output
+of one port is not the input of another).</li>
+
+<li>If a service has several ports that share a port type, but employ different
+bindings or addresses, the ports are alternatives. Each port provides semantically
+equivalent behavior (within the transport and message format limitations imposed
+by each binding).</li>
+
+<li>You can determine a service's port types by examining its ports. Using
+this information a user can determine if a given machine supports all the
+operations needed to complete a given task.</li>
+
+</ul>
+<p>To add a port to a service, follow these steps:</p>
+</div>
+
+<ol>
+<li class="stepexpand"><span>In the Design view, right-click the service you want to add a port
+to, then click <strong>Add Port.</strong> To select the new port, click the port in
+the service object.</span></li>
+
+<li class="stepexpand"><span>In the Properties view, click the <strong>General</strong> pane. In the <strong>Name</strong> field,
+type the name of the port.</span> The name of the port should provide
+it with a unique name amongst all the ports defined within the service.
+</li>
+
+<li class="stepexpand"><span>A <strong>Binding</strong> defines the message format and protocol details
+for operations and messages defined by a particular port type.</span> You
+can 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>In the <strong>Address</strong> field, type the address of the port.</span>
+</li>
+
+<li class="stepexpand"><span>Type any information about the port you want the user to read in
+the <strong>Documentation</strong> pane.</span></li>
+
+<li class="stepexpand"><span>To manage extensions, click the <strong>Extensibility</strong> pane. You
+can either add, sort, or remove extensions. </span>
+</li>
+
+</ol>
+
+<div class="section"><p> <strong>Tip</strong>: You can also create a port using the Outline view
+by right-clicking your service under the <strong>Services</strong> folder and clicking <strong>Add
+Port</strong>. Your port (regardless of which view you create it in) will appear
+in both the Design view and the Outline view.</p>
+</div>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related concepts</strong><br />
+
+<div><a href="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></div></div>
+
+<div class="linklist"><strong>Related tasks</strong><br />
+
+<div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div>
+<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div>
+</div>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddsrvc.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddsrvc.dita
new file mode 100644
index 0000000..4752f4f
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddsrvc.dita
@@ -0,0 +1,45 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>Web services<indexterm>adding services to WSDL</indexterm></indexterm>
+<indexterm>WSDL<indexterm>services</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<taskbody>
+<context><p>To create a new service, follow these steps:</p></context>
+<steps>
+<step><cmd>In the Design view, right-click in any blank space and click <b>Add
+Service</b>. To select the new service, click the service object.</cmd></step>
+<step><cmd>In the Properties view, click the <b>General</b> pane. In the <b>Name</b> field,
+type the name of the service.</cmd><info>The name of the service provides
+it with a unique name amongst all the services defined within in the enclosing
+WSDL document.</info></step>
+<step><cmd>Type any information about the service you want the user to read
+in the <b>Documentation</b> pane.</cmd></step>
+<step><cmd>To manage extensions, click the <b>Extensibility</b> pane. You
+can either add, sort, or remove extensions.<draft-comment> Refer to the related
+tasks for more details. Add link to the XSD Editor plugin topic for "Adding
+extension components"</draft-comment></cmd></step>
+</steps>
+<result><p> <b>Tip</b>: You can also create a service using the Outline view
+by right-clicking the <b>Services</b> folder and clicking <b>Add Service</b>.</p><p>You
+can now add a port to your service. A port defines an individual endpoint
+by specifying a single address for a binding.</p></result>
+</taskbody>
+<related-links>
+<linklist><title>Related concepts</title>
+<link href="../concepts/cwsdled.dita" scope="local"></link>
+</linklist>
+<linklist><title>Related tasks</title>
+<link href="tcrtwsdl.dita" scope="local"></link>
+<link href="tedtwsdl.dita" scope="local"></link>
+</linklist>
+</related-links>
+</task>
+<?Pub *0000002157?>
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
new file mode 100644
index 0000000..7a8acb3
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/taddsrvc.html
@@ -0,0 +1,76 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="Adding a service" />
+<meta name="abstract" content="The service element is a collection of related ports and specifies the location of the service." />
+<meta name="description" content="The service element is a collection of related ports and specifies the location of the service." />
+<meta content="WSDL, adding services, Web services, adding services to WSDL" name="DC.subject" />
+<meta content="WSDL, adding services, Web services, adding services to WSDL" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../concepts/cwsdled.html" />
+<meta scheme="URI" name="DC.Relation" content="tcrtwsdl.html" />
+<meta scheme="URI" name="DC.Relation" content="tedtwsdl.html" />
+<meta content="XHTML" name="DC.Format" />
+<meta content="taddsrvc" name="DC.Identifier" />
+<meta content="en-us" name="DC.Language" />
+<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
+<title>Adding a service</title>
+</head>
+<body id="taddsrvc"><a name="taddsrvc"><!-- --></a>
+
+
+<h1 class="topictitle1">Adding a service</h1>
+
+
+
+<div><p>The <tt class="sysout">service</tt> element is a collection
+of related ports and specifies the location of the service.</p>
+
+<div class="section"><p>To create a new service, follow these steps:</p>
+</div>
+
+<ol>
+<li class="stepexpand"><span>In the Design view, right-click in any blank space and click <strong>Add
+Service</strong>. To select the new service, click the service object.</span></li>
+
+<li class="stepexpand"><span>In the Properties view, click the <strong>General</strong> pane. In the <strong>Name</strong> field,
+type the name of the service.</span> The name of the service provides
+it with a unique name amongst all the services defined within in the enclosing
+WSDL document.</li>
+
+<li class="stepexpand"><span>Type any information about the service you want the user to read
+in the <strong>Documentation</strong> pane.</span></li>
+
+<li class="stepexpand"><span>To manage extensions, click the <strong>Extensibility</strong> pane. You
+can either add, sort, or remove extensions.</span></li>
+
+</ol>
+
+<div class="section"><p> <strong>Tip</strong>: You can also create a service using the Outline view
+by right-clicking the <strong>Services</strong> folder and clicking <strong>Add Service</strong>.</p>
+<p>You
+can now add a port to your service. A port defines an individual endpoint
+by specifying a single address for a binding.</p>
+</div>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related concepts</strong><br />
+
+<div><a href="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></div></div>
+
+<div class="linklist"><strong>Related tasks</strong><br />
+
+<div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div>
+<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div>
+</div>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtimpt.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtimpt.dita
new file mode 100644
index 0000000..9b7adaa
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtimpt.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="tcrtimpt" xml:lang="en-us">
+<title>Creating an import statement</title>
+<shortdesc>The import statement is used to import other WSDL documents or
+XML schemas into your WSDL document. This enables you to have more modular
+WSDL documents. The use of the <b>import</b> statement allows the separation
+of the different elements of a service definition into independent documents,
+which can then be imported as needed. This technique helps in writing clearer
+service definitions, by separating the definitions according to their level
+of abstraction.</shortdesc>
+<prolog><metadata>
+<keywords><indexterm>Web services<indexterm>adding WSDL import statements</indexterm></indexterm>
+<indexterm>WSDL<indexterm>import statements</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<taskbody>
+<context><p>To create an import statement, follow these steps:</p></context>
+<steps>
+<step><cmd>In the Outline view, right-click the <b>Imports</b> folder and
+click <b>Add Import.</b> Select your new import statement.</cmd></step>
+<step><cmd>In the Properties view, click the <b>General</b> pane.</cmd></step>
+<step><cmd>Click the icon to the right of the <b>Location</b> field.</cmd>
+<stepresult>A "Select file" window opens.</stepresult></step>
+<step><cmd>Select the WSDL file or XML Schema file you wish to import. Click <b>OK</b>.<draft-comment>Send
+for final sign-off</draft-comment></cmd></step>
+<step><cmd>Type any information about the import statement you wish the user
+to read in the <b>Documentation</b> pane.</cmd></step>
+</steps>
+<result>Once you specify the location of the document you wish to import,
+the import object's label changes to reflect the specified location. Imported
+WSDL components may now be visible within the editor.</result>
+</taskbody>
+<related-links>
+<linklist><title>Related concepts</title>
+<link href="../concepts/cwsdled.dita" scope="local"></link>
+</linklist>
+<linklist><title>Related tasks</title>
+<link href="tcrtwsdl.dita" scope="local"></link>
+<link href="tedtwsdl.dita" scope="local"></link>
+</linklist>
+</related-links>
+</task>
+<?Pub *0000002258?>
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
new file mode 100644
index 0000000..8a49410
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtimpt.html
@@ -0,0 +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 lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="Creating an import statement" />
+<meta name="abstract" content="The import statement is used to import other WSDL documents or XML schemas into your WSDL document. This enables you to have more modular WSDL documents. The use of the import statement allows the separation of the different elements of a service definition into independent documents, which can then be imported as needed. This technique helps in writing clearer service definitions, by separating the definitions according to their level of abstraction." />
+<meta name="description" content="The import statement is used to import other WSDL documents or XML schemas into your WSDL document. This enables you to have more modular WSDL documents. The use of the import statement allows the separation of the different elements of a service definition into independent documents, which can then be imported as needed. This technique helps in writing clearer service definitions, by separating the definitions according to their level of abstraction." />
+<meta content="WSDL, adding import statements, Web services, adding WSDL import statements" name="DC.subject" />
+<meta content="WSDL, adding import statements, Web services, adding WSDL import statements" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../concepts/cwsdled.html" />
+<meta scheme="URI" name="DC.Relation" content="tcrtwsdl.html" />
+<meta scheme="URI" name="DC.Relation" content="tedtwsdl.html" />
+<meta content="XHTML" name="DC.Format" />
+<meta content="tcrtimpt" name="DC.Identifier" />
+<meta content="en-us" name="DC.Language" />
+<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
+<title>Creating an import statement</title>
+</head>
+<body id="tcrtimpt"><a name="tcrtimpt"><!-- --></a>
+
+
+<h1 class="topictitle1">Creating an import statement</h1>
+
+
+
+<div><p>The import statement is used to import other WSDL documents or
+XML schemas into your WSDL document. This enables you to have more modular
+WSDL documents. The use of the <strong>import</strong> statement allows the separation
+of the different elements of a service definition into independent documents,
+which can then be imported as needed. This technique helps in writing clearer
+service definitions, by separating the definitions according to their level
+of abstraction.</p>
+
+<div class="section"><p>To create an import statement, follow these steps:</p>
+</div>
+
+<ol>
+<li class="stepexpand"><span>In the Outline view, right-click the <strong>Imports</strong> folder and
+click <strong>Add Import.</strong> Select your new import statement.</span></li>
+
+<li class="stepexpand"><span>In the Properties view, click the <strong>General</strong> pane.</span></li>
+
+<li class="stepexpand"><span>Click the icon to the right of the <strong>Location</strong> field.</span>
+ A "Select file" window opens.</li>
+
+<li class="stepexpand"><span>Select the WSDL file or XML Schema file you wish to import. Click <strong>OK</strong>.</span></li>
+
+<li class="stepexpand"><span>Type any information about the import statement you wish the user
+to read in the <strong>Documentation</strong> pane.</span></li>
+
+</ol>
+
+<div class="section">Once you specify the location of the document you wish to import,
+the import object's label changes to reflect the specified location. Imported
+WSDL components may now be visible within the editor.</div>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related concepts</strong><br />
+
+<div><a href="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></div></div>
+
+<div class="linklist"><strong>Related tasks</strong><br />
+
+<div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div>
+<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div>
+</div>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrttype.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrttype.dita
new file mode 100644
index 0000000..b646f8e
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrttype.dita
@@ -0,0 +1,39 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>Web services<indexterm>creating WSDL types</indexterm></indexterm>
+<indexterm>WSDL<indexterm>types</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<taskbody>
+<context><p>WSDL allows type systems to be added via extensibility elements.
+An extensibility element may appear under the <b>types</b> element to identify
+the type definition system being used and to provide an XML container element
+for the type definitions.</p><p>To add an XSD type or element to your WSDL
+file:</p></context>
+<steps-unordered>
+<step><cmd>In the Design view, click the indicator icon to the right of the
+port type object to drill down into the schema. Now you can edit the schema
+in the XML schema editor.</cmd></step>
+</steps-unordered>
+<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>
+<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 *0000001697?>
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
new file mode 100644
index 0000000..7b2977c
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrttype.html
@@ -0,0 +1,68 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="Creating a new type for your WSDL file" />
+<meta name="abstract" content="Types describe all the data types used between the client and server. WSDL is not tied exclusively to a specific typing system, but it uses the W3C XML Schema specification as its default choice." />
+<meta name="description" content="Types describe all the data types used between the client and server. WSDL is not tied exclusively to a specific typing system, but it uses the W3C XML Schema specification as its default choice." />
+<meta content="WSDL, creating types, Web services, creating WSDL types" name="DC.subject" />
+<meta content="WSDL, creating types, Web services, creating WSDL types" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../concepts/cwsdled.html" />
+<meta scheme="URI" name="DC.Relation" content="tcrtwsdl.html" />
+<meta scheme="URI" name="DC.Relation" content="tedtwsdl.html" />
+<meta content="XHTML" name="DC.Format" />
+<meta content="tcrttype" name="DC.Identifier" />
+<meta content="en-us" name="DC.Language" />
+<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
+<title>Creating a new type for your WSDL file</title>
+</head>
+<body id="tcrttype"><a name="tcrttype"><!-- --></a>
+
+
+<h1 class="topictitle1">Creating a new type for your WSDL file</h1>
+
+
+
+<div><p>Types describe all the data types used between the client and server.
+WSDL is not tied exclusively to a specific typing system, but it uses the
+W3C XML Schema specification as its default choice.</p>
+
+<div class="section"><p>WSDL allows type systems to be added via extensibility elements.
+An extensibility element may appear under the <strong>types</strong> element to identify
+the type definition system being used and to provide an XML container element
+for the type definitions.</p>
+<p>To add an XSD type or element to your WSDL
+file:</p>
+</div>
+
+
+<div class="p"><span>In the Design view, click the indicator icon to the right of the
+port type object to drill down into the schema. Now you can edit the schema
+in the XML schema editor.</span></div>
+
+
+<div class="section"><p>For more information about XML schemas, refer to the XML schema
+editor online documentation.</p>
+</div>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related concepts</strong><br />
+
+<div><a href="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></div></div>
+
+<div class="linklist"><strong>Related tasks</strong><br />
+
+<div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div>
+<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div>
+</div>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtwsdl.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtwsdl.dita
new file mode 100644
index 0000000..ec6d4de
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtwsdl.dita
@@ -0,0 +1,91 @@
+<?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">
+<title>Creating a new WSDL file</title>
+<shortdesc>You can create a new, empty WSDL file, then edit it using the WSDL
+editor.</shortdesc>
+<prolog><metadata>
+<keywords><indexterm>WSDL<indexterm>creating</indexterm></indexterm><indexterm>Web
+services<indexterm>creating WSDL</indexterm></indexterm></keywords>
+</metadata></prolog>
+<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.
+Use the SOAP protocol when you want to exchange structured and typed information.
+Use the HTTP protocol when you want your application client to just request
+or update information.</cmd><info> If you select SOAP you can
+then select the encoding style you want to use.<ul>
+<li><b>Document literal</b>. Document style messages, literal encoding. Use
+this style of binding when you want to send SOAP messages that can be validated
+by an XML validator. All the data types in the SOAP message body are defined
+in a schema, so the WSDL parts must point to schema elements. </li>
+<li><b>RPC literal</b>. RPC style messages, literal encoding. Use this style
+of binding when you want to specify the operation method names in your SOAP
+messages so a server can dispatch the specified methods. Data types must
+be defined, so the WSDL parts must point to XSD types.</li>
+<li><b>RPC encoded</b>. RPC style messages and SOAP encoding. Use this style
+of binding when you want to encode data graphs in your SOAP messages so a
+server can deserialize the object data. Data types must be defined, so the
+WSDL parts must point to XSD types.</li>
+</ul> If you select HTTP you can select whether to create an HTTP getter or
+setter.<ul>
+<li><b>HTTP GET</b>. A GET request fetches data from a Web server based on
+an URL value and a set of HTTP headers. Use this method when you want to retrieve
+information specified in the request. </li>
+<li><b>HTTP POST</b>. A POST request sends additional data to the server,
+specified after the URL and the headers. Use this method when you want to
+send data enclosed in the body of the request.</li>
+</ul></info></substep>
+</substeps>
+</step>
+<step><cmd>Click <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:</p><p><image alt="Image of a WSDL skeleton using SOAP bindings"
+href="../images/soapskel.gif" placement="break"></image></p><p>If you created
+a WSDL file with a skeleton using HTTP bindings, it should look similar to
+the following:</p><p><image alt="Image of a WSDL skeleton using HTTP bindings"
+href="../images/httpskel.gif" placement="break"></image></p></result>
+</taskbody>
+<related-links>
+<linklist><title>Related concepts</title>
+<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.dita" scope="peer">
+<linktext>WSDL</linktext></link>
+<link href="../concepts/cwsdled.dita" scope="local"></link>
+</linklist>
+<linklist><title>Related tasks</title>
+<link href="timpwsdl.dita" scope="local"></link>
+<link href="tedtwsdl.dita" scope="local"></link>
+</linklist>
+</related-links>
+</task>
+<?Pub *0000004991?>
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
new file mode 100644
index 0000000..0e1e24a
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtwsdl.html
@@ -0,0 +1,139 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="Creating a new WSDL file" />
+<meta name="abstract" content="You can create a new, empty WSDL file, then edit it using the WSDL editor." />
+<meta name="description" content="You can create a new, empty WSDL file, then edit it using the WSDL editor." />
+<meta content="WSDL, creating, Web services, creating WSDL" name="DC.subject" />
+<meta content="WSDL, creating, Web services, creating WSDL" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.html" />
+<meta scheme="URI" name="DC.Relation" content="../concepts/cwsdled.html" />
+<meta scheme="URI" name="DC.Relation" content="timpwsdl.html" />
+<meta scheme="URI" name="DC.Relation" content="tedtwsdl.html" />
+<meta content="XHTML" name="DC.Format" />
+<meta content="tcrtwsdl" name="DC.Identifier" />
+<meta content="en-us" name="DC.Language" />
+<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
+<title>Creating a new WSDL file</title>
+</head>
+<body id="tcrtwsdl"><a name="tcrtwsdl"><!-- --></a>
+
+
+<h1 class="topictitle1">Creating a new WSDL file</h1>
+
+
+
+<div><p>You can create a new, empty WSDL file, then edit it using the WSDL
+editor.</p>
+
+<div class="section"><p>To create a WSDL file, follow these steps:</p>
+</div>
+
+<ol>
+<li class="stepexpand"><span>Create a project to contain the WSDL document.</span> It does
+not matter what kind of project you create.</li>
+
+<li class="stepexpand"><span>In the workbench, click <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
+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
+type, binding and service defined in the WSDL file. The value must take the
+form of a valid URI (for example, <samp class="codeph">http://www.mycompany.com/myservice/</samp>)
+</li>
+
+<li class="substepexpand"><span>The <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.
+Use the SOAP protocol when you want to exchange structured and typed information.
+Use the HTTP protocol when you want your application client to just request
+or update information.</span> If you select SOAP you can
+then select the encoding style you want to use.<ul>
+<li><strong>Document literal</strong>. Document style messages, literal encoding. Use
+this style of binding when you want to send SOAP messages that can be validated
+by an XML validator. All the data types in the SOAP message body are defined
+in a schema, so the WSDL parts must point to schema elements. </li>
+
+<li><strong>RPC literal</strong>. RPC style messages, literal encoding. Use this style
+of binding when you want to specify the operation method names in your SOAP
+messages so a server can dispatch the specified methods. Data types must
+be defined, so the WSDL parts must point to XSD types.</li>
+
+<li><strong>RPC encoded</strong>. RPC style messages and SOAP encoding. Use this style
+of binding when you want to encode data graphs in your SOAP messages so a
+server can deserialize the object data. Data types must be defined, so the
+WSDL parts must point to XSD types.</li>
+
+</ul>
+ If you select HTTP you can select whether to create an HTTP getter or
+setter.<ul>
+<li><strong>HTTP GET</strong>. A GET request fetches data from a Web server based on
+an URL value and a set of HTTP headers. Use this method when you want to retrieve
+information specified in the request. </li>
+
+<li><strong>HTTP POST</strong>. A POST request sends additional data to the server,
+specified after the URL and the headers. Use this method when you want to
+send data enclosed in the body of the request.</li>
+
+</ul>
+</li>
+
+</ol>
+
+</li>
+
+<li class="stepexpand"><span>Click <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:</p>
+<p><br /><img src="../images/soapskel.gif" alt="Image of a WSDL skeleton using SOAP bindings" /><br /></p>
+<p>If you created
+a WSDL file with a skeleton using HTTP bindings, it should look similar to
+the following:</p>
+<p><br /><img src="../images/httpskel.gif" alt="Image of a WSDL skeleton using HTTP bindings" /><br /></p>
+</div>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related concepts</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.html">WSDL</a></div>
+<div><a href="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></div></div>
+
+<div class="linklist"><strong>Related tasks</strong><br />
+
+<div><a href="timpwsdl.html" title="You can import WSDL files into the workbench and open them in the WSDL editor. Opening them in the WSDL editor provides you with an opportunity to have a structured viewing of the WSDL file.">Importing a WSDL file</a></div>
+<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div>
+</div>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tedtwsdl.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tedtwsdl.dita
new file mode 100644
index 0000000..31041e3
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tedtwsdl.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="tedtwsdl" xml:lang="en-us">
+<title>Editing WSDL files</title>
+<shortdesc>Once you have created a WSDL file, you can edit it in the WSDL
+editor. You can also import WSDL files you have created into the workbench
+and edit them in the WSDL editor.</shortdesc>
+<prolog><metadata>
+<keywords><indexterm>WSDL<indexterm>editing</indexterm></indexterm><indexterm>Web
+services<indexterm>editing WSDL</indexterm></indexterm></keywords>
+</metadata></prolog>
+<taskbody>
+<context><p>To open a WSDL file in the WSDL editor, double-click it in the
+Navigator view or right-click it and click <b>Open With > WSDL Editor.</b></p></context>
+</taskbody>
+<task id="editisourceview">
+<title>Editing in the Source view</title>
+<taskbody>
+<context>To edit a WSDL file in the Source view, 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
+code of the WSDL file. You can also edit your WSDL file directly in the Source
+view.</p></result>
+</taskbody>
+</task>
+<task id="editeditview">
+<title>Editing in the Design view</title>
+<taskbody>
+<context><p>The Design view provides a graphical way to browse and edit your
+WSDL file. Each type of top level wsdl object is shown within a tabular view
+(for example, service, binding, port type). Each tabular view contains one
+or more rows that represent the structure of the object. The service, binding,
+and port type objects are 'linked'. A line displays to denote a reference
+(or association) between these objects.</p><p> <image alt="Image of a WSDL file open in the WSDL editor"
+href="../images/wsdleditor.gif" placement="break"></image></p></context>
+</taskbody>
+</task>
+<task id="editpropertiesview">
+<title>Editing in the Properties view</title>
+<taskbody>
+<context><p>The Properties view displays a list of attributes and editable
+attribute values of a selected wsdl object.</p><p>The Properties view contains
+the following panes (by clicking and selecting the appropriate pane) to edit:</p><ul>
+<li> <b>General</b> pane, which displays a list of object attributes.</li>
+<li> <b>Documentation</b> pane, which specifies the information you want the
+user to read.</li>
+<li> <b>Extensibility</b> pane, which is used to add extension components.</li>
+</ul><draft-comment> [Legacy Title] Showing Bindings in the Design [Legacy
+Context]By default bindings are shown in the Design View. Select the show/hide
+binding button at the top left of the Design View to hide the bindings. With
+the bindings hidden a service can be browsed from a purely abstract level
+without showing binding information. When the need arises to understand the
+concrete details represented by the binding, select the show/hide binding
+button again to make them visible. view [Writer comments] Remove topic "Showing
+bindings..." because there is no show/hide binding function in the new GUI</draft-comment></context>
+</taskbody>
+</task>
+<task id="editoutlineview" xml:lang="en-us">
+<title>Editing in the Outline view</title>
+<taskbody>
+<context><p>The Outline view will show you all the items in your WSDL file
+as you add them. In this view, you can both create and delete WSDL components.</p><p>The
+Outline view contains the following folders you can use (by right-clicking
+and selecting the appropriate option) to edit your WSDL file:</p><ul>
+<li> <b>Imports</b> statements, which are used to associate a namespace
+with a document location.</li>
+<li> <b>Types</b>, which provide data type definitions used to describe the
+messages exchanged. You cannot edit any types directly using this folder.</li>
+<li> <b>Services</b>, which are used to aggregate a set of related ports.</li>
+<li> <b>Bindings</b>, which specify concrete protocol and data format specifications
+for the operations and messages defined by a particular port type.</li>
+<li> <b>Port Types</b>, which are a set of abstract operations. Each operation
+refers to an input message and output messages. </li>
+<li> <b>Messages</b>, which represent an abstract definition of the data being
+transmitted. A message consists of logical parts, each of which is associated
+with a definition within some type system.</li>
+</ul></context>
+</taskbody>
+<related-links>
+<linklist><title>Related concepts</title>
+<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.dita" scope="peer">
+<linktext>WSDL</linktext></link>
+<link href="../concepts/cwsdled.dita" scope="local"></link>
+</linklist>
+<linklist><title>Related tasks</title>
+<link href="tcrtwsdl.dita" scope="local"></link>
+<link href="timpwsdl.dita" scope="local"></link>
+</linklist>
+</related-links>
+</task>
+</task>
+<?Pub *0000004972?>
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
new file mode 100644
index 0000000..3a032db
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tedtwsdl.html
@@ -0,0 +1,151 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="Editing WSDL files" />
+<meta name="abstract" content="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor." />
+<meta name="description" content="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor." />
+<meta content="WSDL, editing, Web services, editing WSDL" name="DC.subject" />
+<meta content="WSDL, editing, Web services, editing WSDL" name="keywords" />
+<meta content="XHTML" name="DC.Format" />
+<meta content="tedtwsdl" name="DC.Identifier" />
+<meta content="en-us" name="DC.Language" />
+<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
+<title>Editing WSDL files</title>
+</head>
+<body id="tedtwsdl"><a name="tedtwsdl"><!-- --></a>
+
+
+<h1 class="topictitle1">Editing WSDL files</h1>
+
+
+
+<div><p>Once you have created a WSDL file, you can edit it in the WSDL
+editor. You can also import WSDL files you have created into the workbench
+and edit them in the WSDL editor.</p>
+
+<div class="section"><p>To open a WSDL file in the WSDL editor, double-click it in the
+Navigator view or right-click it and click <strong>Open With > WSDL Editor.</strong></p>
+</div>
+
+</div>
+
+<div class="nested1" id="editisourceview"><a name="editisourceview"><!-- --></a>
+<h2 class="topictitle2">Editing in the Source view</h2>
+
+<div>
+<div class="section">To edit a WSDL file in the Source view, 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
+code of 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 Design view</h2>
+
+<div>
+<div class="section"><p>The Design view provides a graphical way to browse and edit your
+WSDL file. Each type of top level wsdl object is shown within a tabular view
+(for example, service, binding, port type). Each tabular view contains one
+or more rows that represent the structure of the object. The service, binding,
+and port type objects are 'linked'. A line displays to denote a reference
+(or association) between these objects.</p>
+<p> <br /><img src="../images/wsdleditor.gif" alt="Image of a WSDL file open in the WSDL editor" /><br /></p>
+</div>
+
+</div>
+
+</div>
+
+<div class="nested1" id="editpropertiesview"><a name="editpropertiesview"><!-- --></a>
+<h2 class="topictitle2">Editing in the Properties view</h2>
+
+<div>
+<div class="section"><p>The Properties view displays a list of attributes and editable
+attribute values of a selected wsdl object.</p>
+<p>The Properties view contains
+the following panes (by clicking and selecting the appropriate pane) to edit:</p>
+<ul>
+<li> <strong>General</strong> pane, which displays a list of object attributes.</li>
+
+<li> <strong>Documentation</strong> pane, which specifies the information you want the
+user to read.</li>
+
+<li> <strong>Extensibility</strong> pane, which is used to add extension components.</li>
+
+</ul>
+</div>
+
+</div>
+
+</div>
+
+<div class="nested1" xml:lang="en-us" id="editoutlineview"><a name="editoutlineview"><!-- --></a>
+<h2 class="topictitle2">Editing in the Outline view</h2>
+
+<div>
+<div class="section"><p>The Outline view will show you all the items in your WSDL file
+as you add them. In this view, you can both create and delete WSDL components.</p>
+<p>The
+Outline view contains the following folders you can use (by right-clicking
+and selecting the appropriate option) to edit your WSDL file:</p>
+<ul>
+<li> <strong>Imports</strong> statements, which are used to associate a namespace
+with a document location.</li>
+
+<li> <strong>Types</strong>, which provide data type definitions used to describe the
+messages exchanged. You cannot edit any types directly using this folder.</li>
+
+<li> <strong>Services</strong>, which are used to aggregate a set of related ports.</li>
+
+<li> <strong>Bindings</strong>, which specify concrete protocol and data format specifications
+for the operations and messages defined by a particular port type.</li>
+
+<li> <strong>Port Types</strong>, which are a set of abstract operations. Each operation
+refers to an input message and output messages. </li>
+
+<li> <strong>Messages</strong>, which represent an abstract definition of the data being
+transmitted. A message consists of logical parts, each of which is associated
+with a definition within some type system.</li>
+
+</ul>
+</div>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related concepts</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.html">WSDL</a></div>
+<div><a href="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></div></div>
+
+<div class="linklist"><strong>Related tasks</strong><br />
+
+<div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div>
+<div><a href="timpwsdl.html" title="You can import WSDL files into the workbench and open them in the WSDL editor. Opening them in the WSDL editor provides you with an opportunity to have a structured viewing of the WSDL file.">Importing a WSDL file</a></div></div>
+</div>
+</div>
+
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/timpwsdl.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/timpwsdl.dita
new file mode 100644
index 0000000..8ff77da
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/timpwsdl.dita
@@ -0,0 +1,80 @@
+<?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>
+<shortdesc>You can import WSDL files into the workbench and open them in the
+WSDL editor. Opening them in the WSDL editor provides you with an opportunity
+to have a structured viewing of the WSDL file.</shortdesc>
+<prolog><metadata>
+<keywords><indexterm>WSDL<indexterm>importing</indexterm></indexterm><indexterm>Web
+services<indexterm>importing WSDL</indexterm></indexterm></keywords>
+</metadata></prolog>
+<taskbody>
+<context><p>The Web Service wizard assists you in creating a new Web service
+from a WSDL file. You must first create or import a WSDL file. A WSDL file
+can be created using the WSDL editor. This is described in: <xref href="../tasks/tcrtwsdl.dita"
+scope="peer">Creating a new WSDL file</xref>. To import a WSDL file follow
+the instructions below.</p><p> <uicontrol>Prerequisite:</uicontrol> Create
+a project. It is recommend that you create a Web project so that the WSDL
+can be easily used to generate additional artifacts and deployed.</p><p>For
+more information on creating a Web project, refer to the Web application development
+documentation.</p><p>To import a WSDL file to your Web project:</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 <uicontrol>Browse</uicontrol> on the next page
+of the wizard to select the directories from which you would like to add the
+WSDL.</cmd></step>
+<step><cmd>In the import selection panes, use the following methods to select
+exactly the resources you want to add: </cmd><info><ul>
+<li>Expand the hierarchies in the left pane and select or clear the checkboxes
+that represent the folders in the selected directory. Then in the right pane,
+select or clear 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>
+<?Pub *0000004517?>
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
new file mode 100644
index 0000000..30126e7
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/timpwsdl.html
@@ -0,0 +1,119 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="Importing a WSDL file" />
+<meta name="abstract" content="You can import WSDL files into the workbench and open them in the WSDL editor. Opening them in the WSDL editor provides you with an opportunity to have a structured viewing of the WSDL file." />
+<meta name="description" content="You can import WSDL files into the workbench and open them in the WSDL editor. Opening them in the WSDL editor provides you with an opportunity to have a structured viewing of the WSDL file." />
+<meta content="WSDL, importing, Web services, importing WSDL" name="DC.subject" />
+<meta content="WSDL, importing, Web services, importing WSDL" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.html" />
+<meta scheme="URI" name="DC.Relation" content="../concepts/cwsdled.html" />
+<meta scheme="URI" name="DC.Relation" content="tcrtwsdl.html" />
+<meta scheme="URI" name="DC.Relation" content="tedtwsdl.html" />
+<meta content="XHTML" name="DC.Format" />
+<meta content="timpwsdl" name="DC.Identifier" />
+<meta content="en-us" name="DC.Language" />
+<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
+<title>Importing WSDL files</title>
+</head>
+<body id="timpwsdl"><a name="timpwsdl"><!-- --></a>
+
+
+<h1 class="topictitle1">Importing a WSDL file</h1>
+
+
+
+
+<div><p>You can import WSDL files into the workbench and open them in the
+WSDL editor. Opening them in the WSDL editor provides you with an opportunity
+to have a structured viewing of the WSDL file.</p>
+
+<div class="section"><p>The Web Service wizard assists you in creating a new Web service
+from a WSDL file. You must first create or import a WSDL file. A WSDL file
+can be created using the WSDL editor. This is described in: <a href="../tasks/tcrtwsdl.html">Creating a new WSDL file</a>. To import a WSDL file follow
+the instructions below.</p>
+<p> <span class="uicontrol">Prerequisite:</span> Create
+a project. It is recommend that you create a Web project so that the WSDL
+can be easily used to generate additional artifacts and deployed.</p>
+<p>For
+more information on creating a Web project, refer to the Web application development
+documentation.</p>
+<p>To import a WSDL file to your Web project:</p>
+</div>
+
+<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>Click <span class="uicontrol">Browse</span> on the next page
+of the wizard to select the directories from which you would like to add the
+WSDL.</span></li>
+
+<li class="stepexpand"><span>In the import selection panes, use the following methods to select
+exactly the resources you want to add: </span> <ul>
+<li>Expand the hierarchies in the left pane and select or clear the checkboxes
+that represent the folders in the selected directory. Then in the right pane,
+select or clear 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>
+
+</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>
+</div>
+
+<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
+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 />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.html">WSDL</a></div>
+<div><a href="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></div></div>
+
+<div class="linklist"><strong>Related tasks</strong><br />
+
+<div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div>
+<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div>
+</div>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetbind.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetbind.dita
new file mode 100644
index 0000000..64f306c
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetbind.dita
@@ -0,0 +1,108 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>Web services<indexterm>bindings<indexterm>creating</indexterm></indexterm><indexterm>setting WSDL bindings</indexterm></indexterm>
+<indexterm>WSDL<indexterm>bindings</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<taskbody>
+<context><p>You can create a binding by right clicking in any blank space
+in the Design view and selecting <uicontrol>Add Binding</uicontrol>. You can
+create a new binding, reuse an existing one, or import one. </p></context>
+</taskbody>
+<task id="createnewbind">
+<title>Creating a new binding</title>
+<taskbody>
+<context><p>To create a new binding for your port, follow these steps:</p></context>
+<steps>
+<step><cmd>In the Design view, right-click your port and click <b>Set Binding
+> New Binding</b>.</cmd></step>
+<step><cmd>In the <b>Name</b> field, type the name of the binding.</cmd><info>The
+name should be unique among all bindings defined within the enclosing WSDL
+document. Click <b>OK.</b> To select the new binding, click the binding object.</info>
+</step>
+<step><cmd>A <b>Port Type</b> is a named set of abstract operations and the
+abstract messages involved. You can either create a new port type for your
+binding, reuse an existing one, or import one. Refer to the related tasks
+for more details.</cmd></step>
+<step><cmd>Type any information about the binding you want the user to read
+in the <b>Documentation</b> pane.</cmd></step>
+</steps>
+<result><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 Design view, select your port.</cmd></step>
+<step><cmd>In the Properties view, click the <b>General</b> pane.</cmd></step>
+<step><cmd>From the <b>Binding</b> drop down list, select the binding you
+want to use.</cmd></step>
+</steps>
+</taskbody>
+</task>
+<task id="regeneratingabinding">
+<title>Regenerating a binding</title>
+<taskbody>
+<context>To regenerate a binding:</context>
+<steps>
+<step><cmd>Right-click the binding you want to regenerate.</cmd></step>
+<step><cmd>Select <uicontrol>Generate Binding Content</uicontrol>.<draft-comment>RATLC00975711
+provide more info about SOAP binding options</draft-comment></cmd></step>
+<step><cmd>Specify an required binding information. If you are modifying an
+existing binding, ensure that you select the <uicontrol>Overwrite existing
+binding information</uicontrol> check box.</cmd></step>
+</steps>
+</taskbody>
+</task>
+<task id="impbinding">
+<title>Import an existing binding</title>
+<taskbody>
+<context>To import an existing binding for your port, follow these steps:</context>
+<steps>
+<step><cmd>In the Design view, right-click your port and click <b>Set Binding
+> Existing Binding.</b></cmd></step>
+<step><cmd>In the <b>Name</b> field, type a search string to filter the list
+or leave the field blank to view all.</cmd></step>
+<step><cmd>You can import a binding by selecting one of the following options:</cmd>
+<choices>
+<choice><b>Workspace</b>. Lists the bindings available in your workspace.</choice>
+<choice><b>Enclosing Project</b>. Lists the bindings available in the project
+that contains your file.</choice>
+<choice><b>Working Sets</b>. Lists the bindings available in a specified set
+of files. To specify a working set, click <b>Choose</b>. You can select files
+from an existing working set or create a new working set. Once you have selected
+the files, click <b>OK</b>.</choice>
+</choices>
+</step>
+<step><cmd>The bindings will be listed. Select one and click <b>OK</b>. In
+the Design view, click the binding object.</cmd></step>
+<step><cmd>In the Properties view, type any information about the binding
+you wish the user to read in the <b>Documentation</b> pane.</cmd></step>
+</steps>
+</taskbody>
+<related-links>
+<linklist><title>Related concepts</title>
+<link href="../concepts/cwsdled.dita" scope="local"></link>
+</linklist>
+<linklist><title>Related tasks</title>
+<link href="tcrtwsdl.dita" scope="local"></link>
+<link href="tedtwsdl.dita" scope="local"></link>
+</linklist>
+</related-links>
+</task>
+</task>
+<?Pub *0000004937?>
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
new file mode 100644
index 0000000..8118345
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetbind.html
@@ -0,0 +1,172 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" />
+<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="WSDL, setting bindings, Web services, setting WSDL bindings, bindings, creating" name="DC.subject" />
+<meta content="WSDL, setting bindings, Web services, setting WSDL bindings, bindings, creating" name="keywords" />
+<meta content="XHTML" name="DC.Format" />
+<meta content="tsetbind" name="DC.Identifier" />
+<meta content="en-us" name="DC.Language" />
+<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
+<title>Setting a binding</title>
+</head>
+<body id="tsetbind"><a name="tsetbind"><!-- --></a>
+
+
+<h1 class="topictitle1">Setting a binding</h1>
+
+
+
+<div><p>A binding is a top level WSDL object that provides a concrete specification
+regarding the transmission of messages to and from a web service. A binding
+references exactly one port type. The structure of a binding corresponds very
+closely to that of the port type. The binding contains extensibility elements
+(for example, soap, http, and mime) that specify protocol specific details.
+Each port within a service references exactly one binding.</p>
+
+<div class="section"><p>You can create a binding by right clicking in any blank space
+in the Design view and selecting <span class="uicontrol">Add Binding</span>. You can
+create a new binding, reuse an existing one, or import one. </p>
+</div>
+
+</div>
+
+<div class="nested1" id="createnewbind"><a name="createnewbind"><!-- --></a>
+<h2 class="topictitle2">Creating a new binding</h2>
+
+<div>
+<div class="section"><p>To create a new binding for your port, follow these steps:</p>
+</div>
+
+<ol>
+<li class="stepexpand"><span>In the Design view, right-click your port and click <strong>Set Binding
+> New Binding</strong>.</span></li>
+
+<li class="stepexpand"><span>In the <strong>Name</strong> field, type the name of the binding.</span> The
+name should be unique among all bindings defined within the enclosing WSDL
+document. Click <strong>OK.</strong> To select the new binding, click the binding object.
+</li>
+
+<li class="stepexpand"><span>A <strong>Port Type</strong> is a named set of abstract operations and the
+abstract messages involved. You can either create a new port type for your
+binding, reuse an existing one, or import one. Refer to the related tasks
+for more details.</span></li>
+
+<li class="stepexpand"><span>Type any information about the binding you want the user to read
+in the <strong>Documentation</strong> pane.</span></li>
+
+</ol>
+
+<div class="section"><p> <strong>Tip</strong>: You can also create a new binding for your port using
+the Outline view.</p>
+</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>
+
+<ol>
+<li><span>In the Design view, select your port.</span></li>
+
+<li><span>In the Properties view, click the <strong>General</strong> pane.</span></li>
+
+<li><span>From the <strong>Binding</strong> drop down list, select the binding you
+want to use.</span></li>
+
+</ol>
+
+</div>
+
+</div>
+
+<div class="nested1" id="regeneratingabinding"><a name="regeneratingabinding"><!-- --></a>
+<h2 class="topictitle2">Regenerating a binding</h2>
+
+<div>
+<div class="section">To regenerate a binding:</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 the <span class="uicontrol">Overwrite existing
+binding information</span> check box.</span></li>
+
+</ol>
+
+</div>
+
+</div>
+
+<div class="nested1" id="impbinding"><a name="impbinding"><!-- --></a>
+<h2 class="topictitle2">Import an existing binding</h2>
+
+<div>
+<div class="section">To import an existing binding for your port, follow these steps:</div>
+
+<ol>
+<li><span>In the Design view, right-click your port and click <strong>Set Binding
+> Existing Binding.</strong></span></li>
+
+<li><span>In the <strong>Name</strong> field, type a search string to filter the list
+or leave the field blank to view all.</span></li>
+
+<li><span>You can import a binding by selecting one of the following options:</span>
+<ul>
+<li><strong>Workspace</strong>. Lists the bindings available in your workspace.</li>
+
+<li><strong>Enclosing Project</strong>. Lists the bindings available in the project
+that contains your file.</li>
+
+<li><strong>Working Sets</strong>. Lists the bindings available in a specified set
+of files. To specify a working set, click <strong>Choose</strong>. You can select files
+from an existing working set or create a new working set. Once you have selected
+the files, click <strong>OK</strong>.</li>
+
+</ul>
+
+</li>
+
+<li><span>The bindings will be listed. Select one and click <strong>OK</strong>. In
+the Design view, click the binding object.</span></li>
+
+<li><span>In the Properties view, type any information about the binding
+you wish the user to read in the <strong>Documentation</strong> pane.</span></li>
+
+</ol>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related concepts</strong><br />
+
+<div><a href="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></div></div>
+
+<div class="linklist"><strong>Related tasks</strong><br />
+
+<div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div>
+<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div>
+</div>
+</div>
+
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetprtt.dita b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetprtt.dita
new file mode 100644
index 0000000..829aa09
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetprtt.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="tsetprtt" xml:lang="en-us">
+<title>Setting a port type</title>
+<shortdesc>A port type is a named set of abstract operations and the abstract
+messages involved. Each operation refers to an input message and output messages.
+A port type is referenced by a binding object. Each binding references exactly
+one port type. Since each port refers to exactly one binding, each port has
+exactly one port type.</shortdesc>
+<prolog><metadata>
+<keywords><indexterm>WSDL<indexterm>setting port types</indexterm></indexterm>
+<indexterm>Web services<indexterm>setting port types</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<taskbody>
+<context><p>You can create a port type by right clicking in any blank space
+in the Design view and selecting <uicontrol>Add PortType</uicontrol>. As a
+convenience you can also add a port type via a binding. This allows you to
+create a port type and modify the binding to reference the new port type in
+one action. You can either create a new port type for your binding, re-use
+an existing one, or import one.</p></context>
+</taskbody>
+<task id="createporttype">
+<title>Create a new port type for a binding</title>
+<taskbody>
+<context><p>If you want to create a new port type for your binding, follow
+these steps:</p></context>
+<steps>
+<step><cmd>In the Design view, right-click on a binding object (note that
+port must reference a binding) and click <b>Set Port Type > New PortType</b>.</cmd>
+</step>
+<step><cmd>Type the name of the port type in the <b>Name</b> field.</cmd>
+<info>The name should be unique name among all port types defined within in
+the enclosing WSDL document. Click <b>OK</b>. To select the new port type,
+click the port type object.</info></step>
+<step><cmd>In the Properties view, type any information about the port type
+you wish the user to read in the <b>Documentation</b> pane.</cmd></step>
+</steps>
+<result><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 Design view, right-click on a binding object (note that
+port must reference a binding) and click <b>Set Port Type > Existing PortType</b>.</cmd>
+</step>
+<step><cmd>In the <b>Name</b> field, type a search string to filter the list
+or leave the field blank to view all.</cmd></step>
+<step><cmd>You can change the scope of the list by selecting one of the following
+options:</cmd>
+<choices>
+<choice><b>Workspace</b>. Lists the port types available in your workspace.</choice>
+<choice><b>Enclosing Project</b>. Lists the port types available in the project
+that contains your file.</choice>
+<choice><b>Current Resource</b>. Lists the port types available in your current
+file.</choice>
+<choice><b>Working Sets</b>. Lists the port types available in a specified
+set of files. To specify a working set, click <b>Choose</b>. You can select
+files from an existing working set or create a new working set. Once you have
+selected the files, click <b>OK</b>.</choice>
+</choices>
+</step>
+<step><cmd>The existing port types will be listed. Select one and click <b>OK</b>.</cmd>
+</step>
+</steps>
+</taskbody>
+</task>
+<task id="importporttype">
+<title>Import a port type for a binding</title>
+<taskbody>
+<context><p>If you want to import an existing port type for your binding,
+follow these steps:</p></context>
+<steps>
+<step><cmd>In the Design view, right-click on a binding object (note that
+port must reference a binding) and click <b>Set Port Type > Existing PortType.</b></cmd>
+</step>
+<step><cmd>In the <b>Name</b> field, type a search string to filter the list
+or leave the field blank to view all.</cmd></step>
+<step><cmd>You can import a port type by selecting one of the following options:</cmd>
+<choices>
+<choice><b>Workspace</b>. Lists the port types available in your workspace.</choice>
+<choice><b>Enclosing Project</b>. Lists the port types available in the project
+that contains your file.</choice>
+<choice><b>Working Sets</b>. Lists the port types available in a specified
+set of files. To specify a working set, click <b>Choose</b>. You can select
+files from an existing working set or create a new working set. Once you have
+selected the files, click <b>OK</b>.</choice>
+</choices>
+</step>
+<step><cmd>The port types will be listed. Select one and click <b>OK</b>.
+In the Design view, click the port type object.</cmd></step>
+<step><cmd>In the Properties view, type any information about the port type
+you wish the user to read in the <b>Documentation</b> pane.</cmd></step>
+</steps>
+</taskbody>
+<related-links>
+<linklist><title>Related concepts</title>
+<link href="../concepts/cwsdled.dita" scope="local"></link>
+</linklist>
+<linklist><title>Related tasks</title>
+<link href="tcrtwsdl.dita" scope="local"></link>
+<link href="tedtwsdl.dita" scope="local"></link>
+</linklist>
+</related-links>
+</task>
+</task>
+<?Pub *0000005308?>
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
new file mode 100644
index 0000000..d3c0d52
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/tasks/tsetprtt.html
@@ -0,0 +1,179 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="Setting a port type" />
+<meta name="abstract" content="A port type is a named set of abstract operations and the abstract messages involved. Each operation refers to an input message and output messages. A port type is referenced by a binding object. Each binding references exactly one port type. Since each port refers to exactly one binding, each port has exactly one port type." />
+<meta name="description" content="A port type is a named set of abstract operations and the abstract messages involved. Each operation refers to an input message and output messages. A port type is referenced by a binding object. Each binding references exactly one port type. Since each port refers to exactly one binding, each port has exactly one port type." />
+<meta content="WSDL, setting port types, Web services" name="DC.subject" />
+<meta content="WSDL, setting port types, Web services" name="keywords" />
+<meta content="XHTML" name="DC.Format" />
+<meta content="tsetprtt" name="DC.Identifier" />
+<meta content="en-us" name="DC.Language" />
+<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
+<title>Setting a port type</title>
+</head>
+<body id="tsetprtt"><a name="tsetprtt"><!-- --></a>
+
+
+<h1 class="topictitle1">Setting a port type</h1>
+
+
+
+<div><p>A port type is a named set of abstract operations and the abstract
+messages involved. Each operation refers to an input message and output messages.
+A port type is referenced by a binding object. Each binding references exactly
+one port type. Since each port refers to exactly one binding, each port has
+exactly one port type.</p>
+
+<div class="section"><p>You can create a port type by right clicking in any blank space
+in the Design view and selecting <span class="uicontrol">Add PortType</span>. As a
+convenience you can also add a port type via a binding. This allows you to
+create a port type and modify the binding to reference the new port type in
+one action. You can either create a new port type for your binding, re-use
+an existing one, or import one.</p>
+</div>
+
+</div>
+
+<div class="nested1" id="createporttype"><a name="createporttype"><!-- --></a>
+<h2 class="topictitle2">Create a new port type for a binding</h2>
+
+<div>
+<div class="section"><p>If you want to create a new port type for your binding, follow
+these steps:</p>
+</div>
+
+<ol>
+<li class="stepexpand"><span>In the Design view, right-click on a binding object (note that
+port must reference a binding) and click <strong>Set Port Type > New PortType</strong>.</span>
+</li>
+
+<li class="stepexpand"><span>Type the name of the port type in the <strong>Name</strong> field.</span>
+ The name should be unique name among all port types defined within in
+the enclosing WSDL document. Click <strong>OK</strong>. To select the new port type,
+click the port type object.</li>
+
+<li class="stepexpand"><span>In the Properties view, type any information about the port type
+you wish the user to read in the <strong>Documentation</strong> pane.</span></li>
+
+</ol>
+
+<div class="section"><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="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 Design view, right-click on a binding object (note that
+port must reference a binding) and click <strong>Set Port Type > Existing PortType</strong>.</span>
+</li>
+
+<li><span>In the <strong>Name</strong> field, type a search string to filter the list
+or leave the field blank to view all.</span></li>
+
+<li><span>You can change the scope of the list by selecting one of the following
+options:</span>
+<ul>
+<li><strong>Workspace</strong>. Lists the port types available in your workspace.</li>
+
+<li><strong>Enclosing Project</strong>. Lists the port types available in the project
+that contains your file.</li>
+
+<li><strong>Current Resource</strong>. Lists the port types available in your current
+file.</li>
+
+<li><strong>Working Sets</strong>. Lists the port types available in a specified
+set of files. To specify a working set, click <strong>Choose</strong>. You can select
+files from an existing working set or create a new working set. Once you have
+selected the files, click <strong>OK</strong>.</li>
+
+</ul>
+
+</li>
+
+<li><span>The existing port types will be listed. Select one and click <strong>OK</strong>.</span>
+</li>
+
+</ol>
+
+</div>
+
+</div>
+
+<div class="nested1" id="importporttype"><a name="importporttype"><!-- --></a>
+<h2 class="topictitle2">Import a port type for a binding</h2>
+
+<div>
+<div class="section"><p>If you want to import an existing port type for your binding,
+follow these steps:</p>
+</div>
+
+<ol>
+<li><span>In the Design view, right-click on a binding object (note that
+port must reference a binding) and click <strong>Set Port Type > Existing PortType.</strong></span>
+</li>
+
+<li><span>In the <strong>Name</strong> field, type a search string to filter the list
+or leave the field blank to view all.</span></li>
+
+<li><span>You can import a port type by selecting one of the following options:</span>
+<ul>
+<li><strong>Workspace</strong>. Lists the port types available in your workspace.</li>
+
+<li><strong>Enclosing Project</strong>. Lists the port types available in the project
+that contains your file.</li>
+
+<li><strong>Working Sets</strong>. Lists the port types available in a specified
+set of files. To specify a working set, click <strong>Choose</strong>. You can select
+files from an existing working set or create a new working set. Once you have
+selected the files, click <strong>OK</strong>.</li>
+
+</ul>
+
+</li>
+
+<li><span>The port types will be listed. Select one and click <strong>OK</strong>.
+In the Design view, click the port type object.</span></li>
+
+<li><span>In the Properties view, type any information about the port type
+you wish the user to read in the <strong>Documentation</strong> pane.</span></li>
+
+</ol>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related concepts</strong><br />
+
+<div><a href="../concepts/cwsdled.html" title="The WSDL editor allows you to easily and graphically create, modify, view, and validate WSDL files.">Editing WSDL files with the WSDL Editor</a></div></div>
+
+<div class="linklist"><strong>Related tasks</strong><br />
+
+<div><a href="tcrtwsdl.html" title="You can create a new, empty WSDL file, then edit it using the WSDL editor.">Creating a new WSDL file</a></div>
+<div><a href="tedtwsdl.html" title="Once you have created a WSDL file, you can edit it in the WSDL editor. You can also import WSDL files you have created into the workbench and edit them in the WSDL editor.">Editing WSDL files</a></div></div>
+</div>
+</div>
+
+
+</body>
+</html>
\ No newline at end of file
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 0000000..7de60ab
--- /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/wswsdleditorc_toc.xml b/docs/org.eclipse.wst.wsdl.ui.doc.user/wswsdleditorc_toc.xml
new file mode 100644
index 0000000..4a826b1
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/wswsdleditorc_toc.xml
@@ -0,0 +1,7 @@
+<?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#wswsdleditorc" label="wswsdleditorc" topic="concepts/cwsdled.html">
+<topic label="Editing WSDL files with the WSDL Editor" href="concepts/cwsdled.html"/>
+</toc>
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 0000000..4970a52
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/wswsdleditort_toc.ditamap
@@ -0,0 +1,34 @@
+<?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" linking="none" navtitle="Adding a service">
+</topicref>
+<topicref href="tasks/taddport.dita" linking="none" navtitle="Adding a port to a service">
+</topicref>
+<topicref href="tasks/tsetprtt.dita" linking="none" navtitle="Setting a port type">
+</topicref>
+<topicref href="tasks/tsetbind.dita" linking="none" navtitle="Setting a binding">
+</topicref>
+<topicref href="tasks/taddoper.dita" linking="none" navtitle="Adding an operation">
+</topicref>
+<topicref href="tasks/taddmess.dita" linking="none" navtitle="Adding a message">
+</topicref>
+<topicref href="tasks/taddpart.dita" linking="none" navtitle="Adding a part to a message">
+</topicref>
+<topicref href="tasks/tcrtimpt.dita" linking="none" navtitle="Creating an import statement">
+</topicref>
+<topicref href="tasks/tcrttype.dita" linking="none" 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>
+<?Pub *0000001713?>
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
new file mode 100644
index 0000000..d984e08
--- /dev/null
+++ b/docs/org.eclipse.wst.wsdl.ui.doc.user/wswsdleditort_toc.xml
@@ -0,0 +1,22 @@
+<?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>
diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/.cvsignore b/docs/org.eclipse.wst.wsi.ui.doc.user/.cvsignore
new file mode 100644
index 0000000..385a69c
--- /dev/null
+++ b/docs/org.eclipse.wst.wsi.ui.doc.user/.cvsignore
@@ -0,0 +1,3 @@
+org.eclipse.wst.wsi.ui.doc.user_1.0.0.jar
+bak
+temp
diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/.project b/docs/org.eclipse.wst.wsi.ui.doc.user/.project
new file mode 100644
index 0000000..0d7c46e
--- /dev/null
+++ b/docs/org.eclipse.wst.wsi.ui.doc.user/.project
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.wst.wsi.ui.doc.user</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ <buildCommand>
+ <name>org.eclipse.pde.ManifestBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.pde.SchemaBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ </buildSpec>
+ <natures>
+ <nature>org.eclipse.pde.PluginNature</nature>
+ </natures>
+</projectDescription>
diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/.settings/org.eclipse.core.resources.prefs b/docs/org.eclipse.wst.wsi.ui.doc.user/.settings/org.eclipse.core.resources.prefs
new file mode 100644
index 0000000..1737c9a
--- /dev/null
+++ b/docs/org.eclipse.wst.wsi.ui.doc.user/.settings/org.eclipse.core.resources.prefs
@@ -0,0 +1,3 @@
+#Sun May 07 23:09:10 EDT 2006
+eclipse.preferences.version=1
+encoding/<project>=ISO-8859-1
diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/DocBuild.xml b/docs/org.eclipse.wst.wsi.ui.doc.user/DocBuild.xml
new file mode 100644
index 0000000..36bb7b2
--- /dev/null
+++ b/docs/org.eclipse.wst.wsi.ui.doc.user/DocBuild.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.2" />
+
+ <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/META-INF/MANIFEST.MF b/docs/org.eclipse.wst.wsi.ui.doc.user/META-INF/MANIFEST.MF
new file mode 100644
index 0000000..63fe02f
--- /dev/null
+++ b/docs/org.eclipse.wst.wsi.ui.doc.user/META-INF/MANIFEST.MF
@@ -0,0 +1,7 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: %pluginName
+Bundle-SymbolicName: org.eclipse.wst.wsi.ui.doc.user; singleton:=true
+Bundle-Version: 1.0.203.qualifier
+Bundle-Vendor: %pluginProvider
+Bundle-Localization: plugin
diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/about.html b/docs/org.eclipse.wst.wsi.ui.doc.user/about.html
new file mode 100644
index 0000000..73db36e
--- /dev/null
+++ b/docs/org.eclipse.wst.wsi.ui.doc.user/about.html
@@ -0,0 +1,34 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<HTML>
+
+<head>
+<title>About</title>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+</head>
+
+<BODY lang="EN-US">
+
+<H3>About This Content</H3>
+
+<P>June 06, 2007</P>
+
+<H3>License</H3>
+
+<P>The Eclipse Foundation makes available all content in this plug-in
+("Content"). Unless otherwise indicated below, the Content is provided to you
+under the terms and conditions of the Eclipse Public License Version 1.0
+("EPL"). A copy of the EPL is available at
+<A href="http://www.eclipse.org/org/documents/epl-v10.php">http://www.eclipse.org/org/documents/epl-v10.php</A>.
+For purposes of the EPL, "Program" will mean the Content.</P>
+
+<P>If you did not receive this Content directly from the Eclipse Foundation, the
+Content is being redistributed by another party ("Redistributor") and different
+terms and conditions may apply to your use of any object code in the Content.
+Check the Redistributors license that was provided with the Content. If no such
+license exists, contact the Redistributor. Unless otherwise indicated below, the
+terms and conditions of the EPL still apply to any source code in the Content
+and such source code may be obtained at
+<A href="http://www.eclipse.org/">http://www.eclipse.org/</A>.</P>
+
+</BODY>
+</HTML>
diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/build.properties b/docs/org.eclipse.wst.wsi.ui.doc.user/build.properties
new file mode 100644
index 0000000..b2eb17c
--- /dev/null
+++ b/docs/org.eclipse.wst.wsi.ui.doc.user/build.properties
@@ -0,0 +1,15 @@
+bin.includes = about.html,\
+ images/,\
+ plugin.xml,\
+ tasks/*.htm*,\
+ wswsitest_toc.xml,\
+ org.eclipse.wst.wsi.ui.doc.userindex.xml,\
+ META-INF/,\
+ index/,\
+ plugin.properties
+src.includes = build.properties,\
+ *.maplist,\
+ *.ditamap,\
+ tasks/*.dita
+bin.excludes = DocBuild.xml,\
+ myPlugin*.xml
diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/images/traffic.gif b/docs/org.eclipse.wst.wsi.ui.doc.user/images/traffic.gif
new file mode 100644
index 0000000..231ea4a
--- /dev/null
+++ b/docs/org.eclipse.wst.wsi.ui.doc.user/images/traffic.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/images/wsivalico.gif b/docs/org.eclipse.wst.wsi.ui.doc.user/images/wsivalico.gif
new file mode 100644
index 0000000..1bcad84
--- /dev/null
+++ b/docs/org.eclipse.wst.wsi.ui.doc.user/images/wsivalico.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/index/_3.cfs b/docs/org.eclipse.wst.wsi.ui.doc.user/index/_3.cfs
new file mode 100644
index 0000000..6a786b7
--- /dev/null
+++ b/docs/org.eclipse.wst.wsi.ui.doc.user/index/_3.cfs
Binary files differ
diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/index/deletable b/docs/org.eclipse.wst.wsi.ui.doc.user/index/deletable
new file mode 100644
index 0000000..e423242
--- /dev/null
+++ b/docs/org.eclipse.wst.wsi.ui.doc.user/index/deletable
Binary files differ
diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/index/indexed_contributions b/docs/org.eclipse.wst.wsi.ui.doc.user/index/indexed_contributions
new file mode 100644
index 0000000..7385b26
--- /dev/null
+++ b/docs/org.eclipse.wst.wsi.ui.doc.user/index/indexed_contributions
@@ -0,0 +1,3 @@
+#This is a generated file; do not edit.
+#Wed May 09 14:15:52 EDT 2007
+org.eclipse.wst.wsi.ui.doc.user=org.eclipse.wst.wsi.ui.doc.user\n1.0.202.qualifier
diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/index/indexed_dependencies b/docs/org.eclipse.wst.wsi.ui.doc.user/index/indexed_dependencies
new file mode 100644
index 0000000..9079150
--- /dev/null
+++ b/docs/org.eclipse.wst.wsi.ui.doc.user/index/indexed_dependencies
@@ -0,0 +1,4 @@
+#This is a generated file; do not edit.
+#Wed May 09 14:15:52 EDT 2007
+lucene=1.4.103.v20060601
+analyzer=org.eclipse.help.base\#3.2.0.v20060601?locale\=en
diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/index/indexed_docs b/docs/org.eclipse.wst.wsi.ui.doc.user/index/indexed_docs
new file mode 100644
index 0000000..68fc6a9
--- /dev/null
+++ b/docs/org.eclipse.wst.wsi.ui.doc.user/index/indexed_docs
@@ -0,0 +1,5 @@
+#This is a generated file; do not edit.
+#Wed May 09 14:15:52 EDT 2007
+/org.eclipse.wst.wsi.ui.doc.user/tasks/twsival.html=0
+/org.eclipse.wst.wsi.ui.doc.user/tasks/twsdlval.html=0
+/org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.html=0
diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/index/segments b/docs/org.eclipse.wst.wsi.ui.doc.user/index/segments
new file mode 100644
index 0000000..19b5d0c
--- /dev/null
+++ b/docs/org.eclipse.wst.wsi.ui.doc.user/index/segments
Binary files differ
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 0000000..62cf3bd
--- /dev/null
+++ b/docs/org.eclipse.wst.wsi.ui.doc.user/myplugin.xml
@@ -0,0 +1,28 @@
+<?xml version="1.0"?>
+<?eclipse version="3.0"?>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2007 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * IBM Corporation - initial API and implementation
+ *******************************************************************************/ -->
+<!-- ================================================= -->
+<!-- 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"/>
+ <index path="index/"/>
+</extension>
+
+ <extension point="org.eclipse.help.index">
+ <index file="org.eclipse.wst.wsi.ui.doc.userindex.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 0000000..3d58a26
--- /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/org.eclipse.wst.wsi.ui.doc.userindex.html b/docs/org.eclipse.wst.wsi.ui.doc.user/org.eclipse.wst.wsi.ui.doc.userindex.html
new file mode 100644
index 0000000..c9efd46
--- /dev/null
+++ b/docs/org.eclipse.wst.wsi.ui.doc.user/org.eclipse.wst.wsi.ui.doc.userindex.html
@@ -0,0 +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">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="security" content="public" />
+<meta name="Robots" content="index,follow" />
+<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 name="DC.Format" content="XHTML" />
+<link rel="stylesheet" type="text/css" href="../org.eclipse.wst.doc.user/ibmdita.css" />
+<link rel="stylesheet" type="text/css" href="../org.eclipse.wst.doc.user/common.css" />
+<title>Index</title>
+</head>
+<body>
+<h1>Index</h1>
+<strong>T</strong>
+<ul class="indexlist">
+<li>TCP/IP Monitor
+<ul class="indexlist">
+<li><a href="tasks/tmonitor.html#tmonitor">testing Web services</a>
+</li>
+</ul>
+</li>
+</ul>
+<strong>W</strong>
+<ul class="indexlist">
+<li>Web services
+<ul class="indexlist">
+<li><a href="tasks/tmonitor.html#tmonitor">monitoring TCP/IP traffic</a>
+</li>
+<li><a href="tasks/tmonitor.html#tmonitor">testing traffic</a>
+</li>
+<li>validating WS-I compliance
+<ul class="indexlist">
+<li><a href="tasks/twsival.html#twsival">interoperability</a>
+</li>
+<li><a href="tasks/twsival.html#twsival">validating</a>
+</li>
+</ul>
+</li>
+<li><a href="tasks/twsdlval.html#twsdlval">validating WSDL</a>
+</li>
+</ul>
+</li>
+<li>WS-I
+<ul class="indexlist">
+<li><a href="tasks/twsival.html#twsival">validating</a>
+</li>
+</ul>
+</li>
+<li>WSDL
+<ul class="indexlist">
+<li><a href="tasks/twsdlval.html#twsdlval">validating</a>
+</li>
+</ul>
+</li>
+</ul>
+</body></html>
diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/org.eclipse.wst.wsi.ui.doc.userindex.xml b/docs/org.eclipse.wst.wsi.ui.doc.user/org.eclipse.wst.wsi.ui.doc.userindex.xml
new file mode 100644
index 0000000..54547b4
--- /dev/null
+++ b/docs/org.eclipse.wst.wsi.ui.doc.user/org.eclipse.wst.wsi.ui.doc.userindex.xml
@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="utf-8"?>
+<index>
+ <entry keyword="WSDL">
+ <entry keyword="validating">
+ <topic href="tasks/twsdlval.html#twsdlval" title="Validating WSDL files"/>
+ </entry>
+ </entry>
+ <entry keyword="Web services">
+ <entry keyword="validating WSDL">
+ <topic href="tasks/twsdlval.html#twsdlval" title="Validating WSDL files"/>
+ </entry>
+ <entry keyword="testing traffic">
+ <topic href="tasks/tmonitor.html#tmonitor" title="Using the TCP/IP Monitor to test Web services"/>
+ </entry>
+ <entry keyword="monitoring TCP/IP traffic">
+ <topic href="tasks/tmonitor.html#tmonitor" title="Using the TCP/IP Monitor to test Web services"/>
+ </entry>
+ <entry keyword="validating WS-I compliance">
+ <entry keyword="validating">
+ <topic href="tasks/twsival.html#twsival" title="Validating WS-I Web service traffic compliance"/>
+ </entry>
+ <entry keyword="interoperability">
+ <topic href="tasks/twsival.html#twsival" title="Validating WS-I Web service traffic compliance"/>
+ </entry>
+ </entry>
+ </entry>
+ <entry keyword="TCP/IP Monitor">
+ <entry keyword="testing Web services">
+ <topic href="tasks/tmonitor.html#tmonitor" title="Using the TCP/IP Monitor to test Web services"/>
+ </entry>
+ </entry>
+ <entry keyword="WS-I">
+ <entry keyword="validating">
+ <topic href="tasks/twsival.html#twsival" title="Validating WS-I Web service traffic compliance"/>
+ </entry>
+ </entry>
+</index>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/plugin.properties b/docs/org.eclipse.wst.wsi.ui.doc.user/plugin.properties
new file mode 100644
index 0000000..d936fec
--- /dev/null
+++ b/docs/org.eclipse.wst.wsi.ui.doc.user/plugin.properties
@@ -0,0 +1,15 @@
+###############################################################################
+# Copyright (c) 2001, 2005 IBM Corporation and others.
+# All rights reserved. This program and the accompanying materials
+# are made available under the terms of the Eclipse Public License v1.0
+# which accompanies this distribution, and is available at
+# http://www.eclipse.org/legal/epl-v10.html
+#
+# Contributors:
+# IBM Corporation - initial API and implementation
+###############################################################################
+# NLS_MESSAGEFORMAT_VAR
+# NLS_ENCODING=UTF-8
+
+pluginName = WS-I Validation Documentation
+pluginProvider = Eclipse.org
diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/plugin.xml b/docs/org.eclipse.wst.wsi.ui.doc.user/plugin.xml
new file mode 100644
index 0000000..4219daa
--- /dev/null
+++ b/docs/org.eclipse.wst.wsi.ui.doc.user/plugin.xml
@@ -0,0 +1,28 @@
+<?xml version="1.0"?>
+<?eclipse version="3.0"?>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2007 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * IBM Corporation - initial API and implementation
+ *******************************************************************************/ -->
+<!-- ================================================= -->
+<!-- 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"/>
+ <index path="index/"/>
+</extension>
+
+ <extension point="org.eclipse.help.index">
+ <index file="org.eclipse.wst.wsi.ui.doc.userindex.xml"/>
+</extension>
+</plugin>
\ No newline at end of file
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 0000000..e395b27
--- /dev/null
+++ b/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.dita
@@ -0,0 +1,93 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>TCP/IP Monitor<indexterm>testing Web services</indexterm></indexterm>
+<indexterm>Web services<indexterm>testing traffic</indexterm><indexterm>monitoring
+TCP/IP traffic</indexterm></indexterm></keywords>
+</metadata></prolog>
+<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>
+<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 <uicontrol>Run/Debug</uicontrol>,
+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>
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
new file mode 100644
index 0000000..167ea8e
--- /dev/null
+++ b/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.html
@@ -0,0 +1,148 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="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 content="TCP/IP Monitor, testing Web services, Web services, testing traffic, monitoring TCP/IP traffic" name="DC.subject" />
+<meta content="TCP/IP Monitor, testing Web services, Web services, testing traffic, monitoring TCP/IP traffic" name="keywords" />
+<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/common.css" type="text/css" rel="stylesheet" />
+<title>Using the TCP/IP or SOAP monitor to test Web services</title>
+</head>
+<body id="tmonitor"><a name="tmonitor"><!-- --></a>
+
+
+<h1 class="topictitle1">Using the TCP/IP Monitor to test Web services</h1>
+
+
+
+
+<div><p>Once you have created your Web service and Web service client,
+you can monitor the Web service's SOAP traffic using the TCP/IP Monitor.</p>
+
+<div class="p"><p> Prerequisites: </p>
+<ul>
+<li>Generate a Web service</li>
+
+<li>Generate a Proxy and a sample application</li>
+
+</ul>
+</div>
+
+<div class="section"><p>When creating a Web service using the Web service or Web service
+client wizards, you can select to set up and run the TCP/IP Monitor automatically.
+Alternately, you can set up the TCP/IP Monitor manually by completing the
+following steps:</p>
+</div>
+
+<ol>
+<li><span>In the sample application, invoke the getEndPoint method. Record
+this endpoint. The default endpoint for a Web service is: http://localhost:<port>/<web
+module context root>/services/<port></span></li>
+
+<li><span>Create a server to act as the TCP/IP Monitor:</span>
+<ol type="a">
+<li><span>From the Window menu, select <span class="uicontrol">Preferences</span>. </span>
+</li>
+
+<li><span>In the Preferences window, expand <span class="uicontrol">Run/Debug</span>,
+and then select <span class="uicontrol">TCP/IP Monitor</span>. </span></li>
+
+<li><span>Select the <span class="uicontrol">Show TCP/IP Monitor View when there is
+activity</span> check box. </span></li>
+
+<li><span>Under the TCP/IP Monitors lists, click <span class="uicontrol">Add</span>.
+A New Monitor dialog opens.</span></li>
+
+<li><span>Specify the following settings: </span></li>
+
+</ol>
+
+
+<table class="choicetableborder" summary="" cellspacing="0" cellpadding="4" rules="rows" frame="hsides" border="1">
+<thead><tr><th valign="bottom" id="N100E9-option">Option</th>
+<th valign="bottom" id="N100E9-desc">Description</th></tr></thead>
+<tbody>
+
+<tr><td valign="top" headers="N100E9-option" id="N10102"><strong>Local monitoring port</strong></td>
+<td valign="top" headers="N100E9-desc N10102">Specify a unique
+port number on your local machine.</td>
+</tr>
+
+<tr><td valign="top" headers="N100E9-option" id="N10111"><strong>Host name</strong></td>
+<td valign="top" headers="N100E9-desc N10111">Specify the host name or IP address
+of the machine where the server is running.</td>
+</tr>
+
+<tr><td valign="top" headers="N100E9-option" id="N10120"><strong>Port</strong></td>
+<td valign="top" headers="N100E9-desc N10120">Specify the port number of the remote
+server.</td>
+</tr>
+
+<tr><td valign="top" headers="N100E9-option" id="N1012F"><strong>Type</strong></td>
+<td valign="top" headers="N100E9-desc N1012F">Specify whether the request type from
+the Web browser are sent by HTTP or TCP/IP. If the HTTP option is selected
+the requests from the Web browser are modified so that the HTTP header points
+to the remote machine and separated if multiple HTTP requests are received
+in the same connection. If the TCP/IP option is selected, all the requests
+are sent byte for byte. </td>
+</tr>
+
+</tbody></table>
+
+</li>
+
+<li><span>In order to route the Web service through the monitor, the endpoint
+of the Web service client needs to be changed. The TCP/IP Monitor listens
+on port 9081. In the Web browser window used in step 1, invoke the setEndPoint
+method, and change the endpoint so that it directs to port 9081. For example,
+the default would be: <samp class="codeph">http://localhost:9081/web_module_context_root/servlet/rpcrouter</samp> Invoke
+the getEndPoint method again to ensure that your change has been implemented.</span>
+</li>
+
+<li><span>Select a Web service method in the Methods pane. Invoke this method.</span>
+</li>
+
+<li><span>Change to the TCP/IP Monitor view by selecting the TCP/IP Monitor
+tab in the Servers view. This will display request and response pairs that
+are being routed through the TCP/IP Monitor. It will look similar to the following
+picture: <br /><img src="../images/traffic.gif" alt="Screen capture of request and response traffic" /><br /></span></li>
+
+<li><span>To ensure that your Web service SOAP traffic is WS-I compliant,
+you can generate a log file by clicking the <img src="../images/wsivalico.gif" alt="WS-I validation icon" /> icon. In the dialog box that opens,
+select a name for the log file and specify where you want it to be stored. </span>
+</li>
+
+</ol>
+
+<div class="section">This log file will be validated for WS-I compliance. You can open
+the log file in an XML editor to examine its contents.</div>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related Concepts</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/csoap.html">SOAP</a></div>
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsiover.html">WS-I</a></div></div>
+
+<div class="linklist"><strong>Related Tasks</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.html">Setting the level of WS-I compliance</a></div></div>
+</div>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsdlval.dita b/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsdlval.dita
new file mode 100644
index 0000000..c39dc7a
--- /dev/null
+++ b/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsdlval.dita
@@ -0,0 +1,53 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>WSDL<indexterm>validating</indexterm></indexterm><indexterm>Web
+services<indexterm>validating WSDL</indexterm></indexterm></keywords>
+</metadata></prolog>
+<taskbody>
+<context><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</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 WSDL
+Validator check box in the Build column 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>
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
new file mode 100644
index 0000000..fcd483c
--- /dev/null
+++ b/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsdlval.html
@@ -0,0 +1,79 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" />
+<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 content="WSDL, validating, Web services, validating WSDL" name="DC.subject" />
+<meta content="WSDL, validating, Web services, validating WSDL" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.html" />
+<meta scheme="URI" name="DC.Relation" content="../../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/common.css" type="text/css" rel="stylesheet" />
+<title>Validating WSDL files</title>
+</head>
+<body id="twsdlval"><a name="twsdlval"><!-- --></a>
+
+
+<h1 class="topictitle1">Validating WSDL files</h1>
+
+
+
+
+<div><p>If you have created a WSDL file through the Web services wizard
+the WSDL that is generated should be valid. However, if you have imported
+a WSDL file, or if you are creating a WSDL file, you should validate the WSDL
+to ensure it is valid.</p>
+
+<div class="section"><p>If you have selected Require or Suggest WS-I Compliance on the
+WS-I Compliance preference page, the validation also checks WS-I compliance.
+If you have selected Ignore WS-I Compliance the validator will only check
+the validity of the WSDL. For more information on setting WS-I compliance
+levels, refer to: <a href="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.html">Setting the level of WS-I compliance</a>.</p>
+<p>The WSDL
+Validator compares the WSDL file in your project to the W3C <a href="http://www.w3.org/TR/wsdl" target="_blank">Web Services Description Language (WSDL) 1.1</a> specifications, and the WS-I compliance settings
+that you have selected.</p>
+<p>To validate your WSDL, complete the following
+steps:</p>
+</div>
+
+<ol>
+<li><span>Select a WSDL file in the <strong>Project Navigator</strong> view.</span>
+</li>
+
+<li><span>Right-click the WSDL file, and select <strong>Validate</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 WSDL
+Validator check box in the Build column is selected.</p>
+</div>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related Concepts</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.html">WSDL</a></div>
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsiover.html">WS-I</a></div></div>
+
+<div class="linklist"><strong>Related Tasks</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.html">Setting WS-I compliance</a></div></div>
+</div>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsival.dita b/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsival.dita
new file mode 100644
index 0000000..d39b18c
--- /dev/null
+++ b/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsival.dita
@@ -0,0 +1,53 @@
+<?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>
+<prolog><metadata>
+<keywords><indexterm>WS-I<indexterm>validating</indexterm></indexterm><indexterm>Web
+services<indexterm>validating WS-I compliance<indexterm>interoperability<indexterm>validating</indexterm></indexterm></indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<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
new file mode 100644
index 0000000..4e71cb2
--- /dev/null
+++ b/docs/org.eclipse.wst.wsi.ui.doc.user/tasks/twsival.html
@@ -0,0 +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 lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" />
+<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 content="WS-I, validating, Web services, validating WS-I compliance, interoperability" name="DC.subject" />
+<meta content="WS-I, validating, Web services, validating WS-I compliance, interoperability" name="keywords" />
+<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/common.css" type="text/css" rel="stylesheet" />
+<title>Validating WS-I Web service traffic compliance</title>
+</head>
+<body id="twsival"><a name="twsival"><!-- --></a>
+
+
+<h1 class="topictitle1">Validating WS-I Web service traffic compliance</h1>
+
+
+
+
+<div><p>As well as setting the level of WS-I compliance during Web services
+creation, you can validate WS-I compliance of the SOAP traffic a Web service
+produces through the TCP/IP Monitor.</p>
+
+<div class="p"> Prerequisites: Before you can use the validation tool to ensure that
+your Web service SOAP traffic is WS-I compliant, you must have completed the
+following steps:<ul>
+<li>Generate a Web service.</li>
+
+<li> <a href="twsdlval.html">Validate the WSDL that is produced.</a> </li>
+
+<li>Generate a Proxy and a sample application. </li>
+
+<li> <a href="tmonitor.html">Set up the TCP/IP Monitor.</a> Ensure that
+your Web service sample application traffic is directed through the TCP/IP
+Monitor.</li>
+
+</ul>
+</div>
+
+<div class="section"><p>To validate your Web service, complete the following steps:</p>
+</div>
+
+<ol>
+<li><span>Invoke a method in your Web service sample application to generate
+traffic through the TCP/IP Monitor.</span></li>
+
+<li><span>To ensure that your Web service SOAP traffic is WS-I compliant,
+you can generate a log file by clicking the <img src="../images/wsivalico.gif" alt="Validate icon" /> icon.</span></li>
+
+<li><span>In the dialog box that opens, select a name for the log file and
+specify where you want it to be stored.</span></li>
+
+</ol>
+
+<div class="section"> This log file will show whether or not messages sent to and from
+your Web service are WS-I compliant, and list any non-compliant elements.
+You can open the log file in an XML editor to examine its contents.</div>
+
+</div>
+
+<div>
+<div class="linklist"><strong>Related Concepts</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsiover.html">WS-I</a></div></div>
+
+<div class="linklist"><strong>Related Tasks</strong><br />
+
+<div><a href="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.html">Setting the level of WS-I compliance</a></div></div>
+</div>
+
+</body>
+</html>
\ No newline at end of file
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 0000000..fd982c9
--- /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
new file mode 100644
index 0000000..a1020ae
--- /dev/null
+++ b/docs/org.eclipse.wst.wsi.ui.doc.user/wswsitest_toc.xml
@@ -0,0 +1,9 @@
+<?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#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>
diff --git a/features/org.eclipse.wst.ws_userdoc.feature/.cvsignore b/features/org.eclipse.wst.ws_userdoc.feature/.cvsignore
new file mode 100644
index 0000000..ceeff56
--- /dev/null
+++ b/features/org.eclipse.wst.ws_userdoc.feature/.cvsignore
@@ -0,0 +1,3 @@
+build.xml
+org.eclipse.wst.ws_userdoc.feature_1.0.0.jar
+org.eclipse.wst.xml_userdoc.feature_1.0.0.jar
diff --git a/features/org.eclipse.wst.ws_userdoc.feature/.project b/features/org.eclipse.wst.ws_userdoc.feature/.project
new file mode 100644
index 0000000..fd5675e
--- /dev/null
+++ b/features/org.eclipse.wst.ws_userdoc.feature/.project
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.wst.ws_userdoc.feature</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ <buildCommand>
+ <name>org.eclipse.pde.FeatureBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ </buildSpec>
+ <natures>
+ <nature>org.eclipse.pde.FeatureNature</nature>
+ </natures>
+</projectDescription>
diff --git a/features/org.eclipse.wst.ws_userdoc.feature/build.properties b/features/org.eclipse.wst.ws_userdoc.feature/build.properties
new file mode 100644
index 0000000..7f47694
--- /dev/null
+++ b/features/org.eclipse.wst.ws_userdoc.feature/build.properties
@@ -0,0 +1,5 @@
+bin.includes = feature.xml,\
+ eclipse_update_120.jpg,\
+ epl-v10.html,\
+ license.html,\
+ feature.properties
diff --git a/features/org.eclipse.wst.ws_userdoc.feature/eclipse_update_120.jpg b/features/org.eclipse.wst.ws_userdoc.feature/eclipse_update_120.jpg
new file mode 100644
index 0000000..bfdf708
--- /dev/null
+++ b/features/org.eclipse.wst.ws_userdoc.feature/eclipse_update_120.jpg
Binary files differ
diff --git a/features/org.eclipse.wst.ws_userdoc.feature/epl-v10.html b/features/org.eclipse.wst.ws_userdoc.feature/epl-v10.html
new file mode 100644
index 0000000..ed4b196
--- /dev/null
+++ b/features/org.eclipse.wst.ws_userdoc.feature/epl-v10.html
@@ -0,0 +1,328 @@
+<html xmlns:o="urn:schemas-microsoft-com:office:office"
+xmlns:w="urn:schemas-microsoft-com:office:word"
+xmlns="http://www.w3.org/TR/REC-html40">
+
+<head>
+<meta http-equiv=Content-Type content="text/html; charset=windows-1252">
+<meta name=ProgId content=Word.Document>
+<meta name=Generator content="Microsoft Word 9">
+<meta name=Originator content="Microsoft Word 9">
+<link rel=File-List
+href="./Eclipse%20EPL%202003_11_10%20Final_files/filelist.xml">
+<title>Eclipse Public License - Version 1.0</title>
+<!--[if gte mso 9]><xml>
+ <o:DocumentProperties>
+ <o:Revision>2</o:Revision>
+ <o:TotalTime>3</o:TotalTime>
+ <o:Created>2004-03-05T23:03:00Z</o:Created>
+ <o:LastSaved>2004-03-05T23:03:00Z</o:LastSaved>
+ <o:Pages>4</o:Pages>
+ <o:Words>1626</o:Words>
+ <o:Characters>9270</o:Characters>
+ <o:Lines>77</o:Lines>
+ <o:Paragraphs>18</o:Paragraphs>
+ <o:CharactersWithSpaces>11384</o:CharactersWithSpaces>
+ <o:Version>9.4402</o:Version>
+ </o:DocumentProperties>
+</xml><![endif]--><!--[if gte mso 9]><xml>
+ <w:WordDocument>
+ <w:TrackRevisions/>
+ </w:WordDocument>
+</xml><![endif]-->
+<style>
+<!--
+ /* Font Definitions */
+@font-face
+ {font-family:Tahoma;
+ panose-1:2 11 6 4 3 5 4 4 2 4;
+ mso-font-charset:0;
+ mso-generic-font-family:swiss;
+ mso-font-pitch:variable;
+ mso-font-signature:553679495 -2147483648 8 0 66047 0;}
+ /* Style Definitions */
+p.MsoNormal, li.MsoNormal, div.MsoNormal
+ {mso-style-parent:"";
+ margin:0in;
+ margin-bottom:.0001pt;
+ mso-pagination:widow-orphan;
+ font-size:12.0pt;
+ font-family:"Times New Roman";
+ mso-fareast-font-family:"Times New Roman";}
+p
+ {margin-right:0in;
+ mso-margin-top-alt:auto;
+ mso-margin-bottom-alt:auto;
+ margin-left:0in;
+ mso-pagination:widow-orphan;
+ font-size:12.0pt;
+ font-family:"Times New Roman";
+ mso-fareast-font-family:"Times New Roman";}
+p.BalloonText, li.BalloonText, div.BalloonText
+ {mso-style-name:"Balloon Text";
+ margin:0in;
+ margin-bottom:.0001pt;
+ mso-pagination:widow-orphan;
+ font-size:8.0pt;
+ font-family:Tahoma;
+ mso-fareast-font-family:"Times New Roman";}
+@page Section1
+ {size:8.5in 11.0in;
+ margin:1.0in 1.25in 1.0in 1.25in;
+ mso-header-margin:.5in;
+ mso-footer-margin:.5in;
+ mso-paper-source:0;}
+div.Section1
+ {page:Section1;}
+-->
+</style>
+</head>
+
+<body lang=EN-US style='tab-interval:.5in'>
+
+<div class=Section1>
+
+<p align=center style='text-align:center'><b>Eclipse Public License - v 1.0</b>
+</p>
+
+<p><span style='font-size:10.0pt'>THE ACCOMPANYING PROGRAM IS PROVIDED UNDER
+THE TERMS OF THIS ECLIPSE PUBLIC LICENSE ("AGREEMENT"). ANY USE,
+REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE
+OF THIS AGREEMENT.</span> </p>
+
+<p><b><span style='font-size:10.0pt'>1. DEFINITIONS</span></b> </p>
+
+<p><span style='font-size:10.0pt'>"Contribution" means:</span> </p>
+
+<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>a)
+in the case of the initial Contributor, the initial code and documentation
+distributed under this Agreement, and<br clear=left>
+b) in the case of each subsequent Contributor:</span></p>
+
+<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>i)
+changes to the Program, and</span></p>
+
+<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>ii)
+additions to the Program;</span></p>
+
+<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>where
+such changes and/or additions to the Program originate from and are distributed
+by that particular Contributor. A Contribution 'originates' from a Contributor
+if it was added to the Program by such Contributor itself or anyone acting on
+such Contributor's behalf. Contributions do not include additions to the
+Program which: (i) are separate modules of software distributed in conjunction
+with the Program under their own license agreement, and (ii) are not derivative
+works of the Program. </span></p>
+
+<p><span style='font-size:10.0pt'>"Contributor" means any person or
+entity that distributes the Program.</span> </p>
+
+<p><span style='font-size:10.0pt'>"Licensed Patents " mean patent
+claims licensable by a Contributor which are necessarily infringed by the use
+or sale of its Contribution alone or when combined with the Program. </span></p>
+
+<p><span style='font-size:10.0pt'>"Program" means the Contributions
+distributed in accordance with this Agreement.</span> </p>
+
+<p><span style='font-size:10.0pt'>"Recipient" means anyone who
+receives the Program under this Agreement, including all Contributors.</span> </p>
+
+<p><b><span style='font-size:10.0pt'>2. GRANT OF RIGHTS</span></b> </p>
+
+<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>a)
+Subject to the terms of this Agreement, each Contributor hereby grants Recipient
+a non-exclusive, worldwide, royalty-free copyright license to<span
+style='color:red'> </span>reproduce, prepare derivative works of, publicly
+display, publicly perform, distribute and sublicense the Contribution of such
+Contributor, if any, and such derivative works, in source code and object code
+form.</span></p>
+
+<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>b)
+Subject to the terms of this Agreement, each Contributor hereby grants
+Recipient a non-exclusive, worldwide,<span style='color:green'> </span>royalty-free
+patent license under Licensed Patents to make, use, sell, offer to sell, import
+and otherwise transfer the Contribution of such Contributor, if any, in source
+code and object code form. This patent license shall apply to the combination
+of the Contribution and the Program if, at the time the Contribution is added
+by the Contributor, such addition of the Contribution causes such combination
+to be covered by the Licensed Patents. The patent license shall not apply to
+any other combinations which include the Contribution. No hardware per se is
+licensed hereunder. </span></p>
+
+<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>c)
+Recipient understands that although each Contributor grants the licenses to its
+Contributions set forth herein, no assurances are provided by any Contributor
+that the Program does not infringe the patent or other intellectual property
+rights of any other entity. Each Contributor disclaims any liability to Recipient
+for claims brought by any other entity based on infringement of intellectual
+property rights or otherwise. As a condition to exercising the rights and
+licenses granted hereunder, each Recipient hereby assumes sole responsibility
+to secure any other intellectual property rights needed, if any. For example,
+if a third party patent license is required to allow Recipient to distribute
+the Program, it is Recipient's responsibility to acquire that license before
+distributing the Program.</span></p>
+
+<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>d)
+Each Contributor represents that to its knowledge it has sufficient copyright
+rights in its Contribution, if any, to grant the copyright license set forth in
+this Agreement. </span></p>
+
+<p><b><span style='font-size:10.0pt'>3. REQUIREMENTS</span></b> </p>
+
+<p><span style='font-size:10.0pt'>A Contributor may choose to distribute the
+Program in object code form under its own license agreement, provided that:</span>
+</p>
+
+<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>a)
+it complies with the terms and conditions of this Agreement; and</span></p>
+
+<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>b)
+its license agreement:</span></p>
+
+<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>i)
+effectively disclaims on behalf of all Contributors all warranties and
+conditions, express and implied, including warranties or conditions of title
+and non-infringement, and implied warranties or conditions of merchantability
+and fitness for a particular purpose; </span></p>
+
+<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>ii)
+effectively excludes on behalf of all Contributors all liability for damages,
+including direct, indirect, special, incidental and consequential damages, such
+as lost profits; </span></p>
+
+<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>iii)
+states that any provisions which differ from this Agreement are offered by that
+Contributor alone and not by any other party; and</span></p>
+
+<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>iv)
+states that source code for the Program is available from such Contributor, and
+informs licensees how to obtain it in a reasonable manner on or through a
+medium customarily used for software exchange.<span style='color:blue'> </span></span></p>
+
+<p><span style='font-size:10.0pt'>When the Program is made available in source
+code form:</span> </p>
+
+<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>a)
+it must be made available under this Agreement; and </span></p>
+
+<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>b) a
+copy of this Agreement must be included with each copy of the Program. </span></p>
+
+<p><span style='font-size:10.0pt'>Contributors may not remove or alter any
+copyright notices contained within the Program. </span></p>
+
+<p><span style='font-size:10.0pt'>Each Contributor must identify itself as the
+originator of its Contribution, if any, in a manner that reasonably allows
+subsequent Recipients to identify the originator of the Contribution. </span></p>
+
+<p><b><span style='font-size:10.0pt'>4. COMMERCIAL DISTRIBUTION</span></b> </p>
+
+<p><span style='font-size:10.0pt'>Commercial distributors of software may
+accept certain responsibilities with respect to end users, business partners
+and the like. While this license is intended to facilitate the commercial use
+of the Program, the Contributor who includes the Program in a commercial
+product offering should do so in a manner which does not create potential
+liability for other Contributors. Therefore, if a Contributor includes the
+Program in a commercial product offering, such Contributor ("Commercial
+Contributor") hereby agrees to defend and indemnify every other
+Contributor ("Indemnified Contributor") against any losses, damages and
+costs (collectively "Losses") arising from claims, lawsuits and other
+legal actions brought by a third party against the Indemnified Contributor to
+the extent caused by the acts or omissions of such Commercial Contributor in
+connection with its distribution of the Program in a commercial product
+offering. The obligations in this section do not apply to any claims or Losses
+relating to any actual or alleged intellectual property infringement. In order
+to qualify, an Indemnified Contributor must: a) promptly notify the Commercial
+Contributor in writing of such claim, and b) allow the Commercial Contributor
+to control, and cooperate with the Commercial Contributor in, the defense and
+any related settlement negotiations. The Indemnified Contributor may participate
+in any such claim at its own expense.</span> </p>
+
+<p><span style='font-size:10.0pt'>For example, a Contributor might include the
+Program in a commercial product offering, Product X. That Contributor is then a
+Commercial Contributor. If that Commercial Contributor then makes performance
+claims, or offers warranties related to Product X, those performance claims and
+warranties are such Commercial Contributor's responsibility alone. Under this
+section, the Commercial Contributor would have to defend claims against the
+other Contributors related to those performance claims and warranties, and if a
+court requires any other Contributor to pay any damages as a result, the
+Commercial Contributor must pay those damages.</span> </p>
+
+<p><b><span style='font-size:10.0pt'>5. NO WARRANTY</span></b> </p>
+
+<p><span style='font-size:10.0pt'>EXCEPT AS EXPRESSLY SET FORTH IN THIS
+AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS" BASIS, WITHOUT
+WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING,
+WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT,
+MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely
+responsible for determining the appropriateness of using and distributing the
+Program and assumes all risks associated with its exercise of rights under this
+Agreement , including but not limited to the risks and costs of program errors,
+compliance with applicable laws, damage to or loss of data, programs or
+equipment, and unavailability or interruption of operations. </span></p>
+
+<p><b><span style='font-size:10.0pt'>6. DISCLAIMER OF LIABILITY</span></b> </p>
+
+<p><span style='font-size:10.0pt'>EXCEPT AS EXPRESSLY SET FORTH IN THIS
+AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY
+OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
+NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF
+THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF
+THE POSSIBILITY OF SUCH DAMAGES.</span> </p>
+
+<p><b><span style='font-size:10.0pt'>7. GENERAL</span></b> </p>
+
+<p><span style='font-size:10.0pt'>If any provision of this Agreement is invalid
+or unenforceable under applicable law, it shall not affect the validity or
+enforceability of the remainder of the terms of this Agreement, and without
+further action by the parties hereto, such provision shall be reformed to the
+minimum extent necessary to make such provision valid and enforceable.</span> </p>
+
+<p><span style='font-size:10.0pt'>If Recipient institutes patent litigation
+against any entity (including a cross-claim or counterclaim in a lawsuit)
+alleging that the Program itself (excluding combinations of the Program with
+other software or hardware) infringes such Recipient's patent(s), then such
+Recipient's rights granted under Section 2(b) shall terminate as of the date
+such litigation is filed. </span></p>
+
+<p><span style='font-size:10.0pt'>All Recipient's rights under this Agreement
+shall terminate if it fails to comply with any of the material terms or
+conditions of this Agreement and does not cure such failure in a reasonable
+period of time after becoming aware of such noncompliance. If all Recipient's
+rights under this Agreement terminate, Recipient agrees to cease use and
+distribution of the Program as soon as reasonably practicable. However,
+Recipient's obligations under this Agreement and any licenses granted by
+Recipient relating to the Program shall continue and survive. </span></p>
+
+<p><span style='font-size:10.0pt'>Everyone is permitted to copy and distribute
+copies of this Agreement, but in order to avoid inconsistency the Agreement is
+copyrighted and may only be modified in the following manner. The Agreement
+Steward reserves the right to publish new versions (including revisions) of
+this Agreement from time to time. No one other than the Agreement Steward has
+the right to modify this Agreement. The Eclipse Foundation is the initial
+Agreement Steward. The Eclipse Foundation may assign the responsibility to
+serve as the Agreement Steward to a suitable separate entity. Each new version
+of the Agreement will be given a distinguishing version number. The Program
+(including Contributions) may always be distributed subject to the version of
+the Agreement under which it was received. In addition, after a new version of
+the Agreement is published, Contributor may elect to distribute the Program
+(including its Contributions) under the new version. Except as expressly stated
+in Sections 2(a) and 2(b) above, Recipient receives no rights or licenses to
+the intellectual property of any Contributor under this Agreement, whether
+expressly, by implication, estoppel or otherwise. All rights in the Program not
+expressly granted under this Agreement are reserved.</span> </p>
+
+<p><span style='font-size:10.0pt'>This Agreement is governed by the laws of the
+State of New York and the intellectual property laws of the United States of
+America. No party to this Agreement will bring a legal action under this
+Agreement more than one year after the cause of action arose. Each party waives
+its rights to a jury trial in any resulting litigation.</span> </p>
+
+<p class=MsoNormal><![if !supportEmptyParas]> <![endif]><o:p></o:p></p>
+
+</div>
+
+</body>
+
+</html>
\ No newline at end of file
diff --git a/features/org.eclipse.wst.ws_userdoc.feature/feature.properties b/features/org.eclipse.wst.ws_userdoc.feature/feature.properties
new file mode 100644
index 0000000..bca585c
--- /dev/null
+++ b/features/org.eclipse.wst.ws_userdoc.feature/feature.properties
@@ -0,0 +1,145 @@
+###############################################################################
+# Copyright (c) 2006 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
+###############################################################################
+# feature.properties
+# contains externalized strings for feature.xml
+# "%foo" in feature.xml corresponds to the key "foo" in this file
+# java.io.Properties file (ISO 8859-1 with "\" escapes)
+# This file should be translated.
+
+# "featureName" property - name of the feature
+featureName=WST Web Services User Documentation
+
+# "providerName" property - name of the company that provides the feature
+providerName=Eclipse.org
+
+# "updateSiteName" property - label for the update site
+updateSiteName=The Eclipse Web Tools Platform (WTP) Project update site
+
+# "description" property - description of the feature
+description=WST Web services user documentation
+
+# "copyright" property - text of the "Feature Update Copyright"
+copyright=\
+Copyright (c) 2006 IBM Corporation and others.\n\
+All rights reserved. This program and the accompanying materials\n\
+are made available under the terms of the Eclipse Public License v1.0\n\
+which accompanies this distribution, and is available at\n\
+http://www.eclipse.org/legal/epl-v10.html\n\
+\n\
+Contributors:\n\
+ IBM Corporation - initial API and implementation\n
+################ end of copyright property ####################################
+
+# "licenseURL" property - URL of the "Feature License"
+# do not translate value - just change to point to a locale-specific HTML page
+licenseURL=license.html
+
+# "license" property - text of the "Feature Update License"
+# should be plain text version of license agreement pointed to be "licenseURL"
+license=\
+ECLIPSE FOUNDATION SOFTWARE USER AGREEMENT\n\
+June 06, 2007\n\
+\n\
+Usage Of Content\n\
+\n\
+THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR\n\
+OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY "CONTENT").\n\
+USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS\n\
+AGREEMENT AND/OR THE TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR\n\
+NOTICES INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU\n\
+AGREE THAT YOUR USE OF THE CONTENT IS GOVERNED BY THIS AGREEMENT\n\
+AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS\n\
+OR NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE\n\
+TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND CONDITIONS\n\
+OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED\n\
+BELOW, THEN YOU MAY NOT USE THE CONTENT.\n\
+\n\
+Applicable Licenses\n\
+\n\
+Unless otherwise indicated, all Content made available by the Eclipse Foundation\n\
+is provided to you under the terms and conditions of the Eclipse Public\n\
+License Version 1.0 ("EPL"). A copy of the EPL is provided with this\n\
+Content and is also available at http://www.eclipse.org/legal/epl-v10.html.\n\
+For purposes of the EPL, "Program" will mean the Content.\n\
+\n\
+Content includes, but is not limited to, source code, object code,\n\
+documentation and other files maintained in the Eclipse.org CVS\n\
+repository ("Repository") in CVS modules ("Modules") and made available\n\
+as downloadable archives ("Downloads").\n\
+\n\
+ - Content may be structured and packaged into modules to facilitate delivering,\n\
+ extending, and upgrading the Content. Typical modules may include plug-ins ("Plug-ins"),\n\
+ plug-in fragments ("Fragments"), and features ("Features").\n\
+ - Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java? ARchive)\n\
+ in a directory named "plugins".\n\
+ - A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material.\n\
+ Each Feature may be packaged as a sub-directory in a directory named "features".\n\
+ Within a Feature, files named "feature.xml" may contain a list of the names and version\n\
+ numbers of the Plug-ins and/or Fragments associated with that Feature.\n\
+ - Features may also include other Features ("Included Features"). Within a Feature, files\n\
+ named "feature.xml" may contain a list of the names and version numbers of Included Features.\n\
+\n\
+Features may also include other Features ("Included Features"). Files named\n\
+"feature.xml" may contain a list of the names and version numbers of\n\
+Included Features.\n\
+\n\
+The terms and conditions governing Plug-ins and Fragments should be\n\
+contained in files named "about.html" ("Abouts"). The terms and\n\
+conditions governing Features and Included Features should be contained\n\
+in files named "license.html" ("Feature Licenses"). Abouts and Feature\n\
+Licenses may be located in any directory of a Download or Module\n\
+including, but not limited to the following locations:\n\
+\n\
+ - The top-level (root) directory\n\
+ - Plug-in and Fragment directories\n\
+ - Inside Plug-ins and Fragments packaged as JARs\n\
+ - Sub-directories of the directory named "src" of certain Plug-ins\n\
+ - Feature directories\n\
+\n\
+Note: if a Feature made available by the Eclipse Foundation is installed using the\n\
+Eclipse Update Manager, you must agree to a license ("Feature Update\n\
+License") during the installation process. If the Feature contains\n\
+Included Features, the Feature Update License should either provide you\n\
+with the terms and conditions governing the Included Features or inform\n\
+you where you can locate them. Feature Update Licenses may be found in\n\
+the "license" property of files named "feature.properties". Such Abouts,\n\
+Feature Licenses and Feature Update Licenses contain the terms and\n\
+conditions (or references to such terms and conditions) that govern your\n\
+use of the associated Content in that directory.\n\
+\n\
+THE ABOUTS, FEATURE LICENSES AND FEATURE UPDATE LICENSES MAY REFER\n\
+TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS.\n\
+SOME OF THESE OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):\n\
+\n\
+ - Common Public License Version 1.0 (available at http://www.eclipse.org/legal/cpl-v10.html)\n\
+ - Apache Software License 1.1 (available at http://www.apache.org/licenses/LICENSE)\n\
+ - Apache Software License 2.0 (available at http://www.apache.org/licenses/LICENSE-2.0)\n\
+ - IBM Public License 1.0 (available at http://oss.software.ibm.com/developerworks/opensource/license10.html)\n\
+ - Metro Link Public License 1.00 (available at http://www.opengroup.org/openmotif/supporters/metrolink/license.html)\n\
+ - Mozilla Public License Version 1.1 (available at http://www.mozilla.org/MPL/MPL-1.1.html)\n\
+ - Common Development and Distribution License (CDDL) Version 1.0 (available at http://www.sun.com/cddl/cddl.html)\n\
+\n\
+IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR\n\
+TO USE OF THE CONTENT. If no About, Feature License or Feature Update License\n\
+is provided, please contact the Eclipse Foundation to determine what terms and conditions\n\
+govern that particular Content.\n\
+\n\
+Cryptography\n\
+\n\
+Content may contain encryption software. The country in which you are\n\
+currently may have restrictions on the import, possession, and use,\n\
+and/or re-export to another country, of encryption software. BEFORE\n\
+using any encryption software, please check the country's laws,\n\
+regulations and policies concerning the import, possession, or use,\n\
+and re-export of encryption software, to see if this is permitted.\n\
+\n\
+Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.\n
+########### end of license property ##########################################
diff --git a/features/org.eclipse.wst.ws_userdoc.feature/feature.xml b/features/org.eclipse.wst.ws_userdoc.feature/feature.xml
new file mode 100644
index 0000000..0b9ab89
--- /dev/null
+++ b/features/org.eclipse.wst.ws_userdoc.feature/feature.xml
@@ -0,0 +1,45 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<feature
+ id="org.eclipse.wst.ws_userdoc.feature"
+ label="%featureName"
+ version="2.0.0.qualifier"
+ provider-name="%providerName">
+
+ <description>
+ %description
+ </description>
+
+ <copyright>
+ %copyright
+ </copyright>
+
+ <license url="license.html">
+ %license
+ </license>
+
+ <url>
+ <update label="%updateSiteName" url="http://download.eclipse.org/webtools/updates/"/>
+ </url>
+
+ <plugin
+ id="org.eclipse.wst.wsdl.ui.doc.user"
+ download-size="0"
+ install-size="0"
+ version="0.0.0"
+ unpack="false"/>
+
+ <plugin
+ id="org.eclipse.wst.wsi.ui.doc.user"
+ download-size="0"
+ install-size="0"
+ version="0.0.0"
+ unpack="false"/>
+
+ <plugin
+ id="org.eclipse.wst.command.env.doc.user"
+ download-size="0"
+ install-size="0"
+ version="0.0.0"
+ unpack="false"/>
+
+</feature>
diff --git a/features/org.eclipse.wst.ws_userdoc.feature/license.html b/features/org.eclipse.wst.ws_userdoc.feature/license.html
new file mode 100644
index 0000000..5644598
--- /dev/null
+++ b/features/org.eclipse.wst.ws_userdoc.feature/license.html
@@ -0,0 +1,98 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3c.org/TR/1999/REC-html401-19991224/loose.dtd">
+<!-- saved from url=(0044)http://www.eclipse.org/legal/epl/notice.html -->
+<HTML><HEAD><TITLE>Eclipse.org Software User Agreement</TITLE>
+<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
+<META content="MSHTML 6.00.2800.1479" name=GENERATOR></HEAD>
+<BODY lang=EN-US vLink=purple link=blue>
+<H2>Eclipse Foundation Software User Agreement</H2>
+<P>June 06, 2007</P>
+<H3>Usage Of Content</H3>
+<P>THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION
+AND/OR OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY "CONTENT"). USE OF
+THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS AGREEMENT AND/OR THE
+TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED
+BELOW. BY USING THE CONTENT, YOU AGREE THAT YOUR USE OF THE CONTENT IS GOVERNED
+BY THIS AGREEMENT AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE
+AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE
+TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND CONDITIONS OF ANY
+APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW, THEN YOU
+MAY NOT USE THE CONTENT.</P>
+<H3>Applicable Licenses</H3>
+<P>Unless otherwise indicated, all Content made available by the Eclipse
+Foundation is provided to you under the terms and conditions of the Eclipse
+Public License Version 1.0 ("EPL"). A copy of the EPL is provided with this
+Content and is also available at <A
+href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</A>.
+For purposes of the EPL, "Program" will mean the Content.</P>
+<P>Content includes, but is not limited to, source code, object code,
+documentation and other files maintained in the Eclipse.org CVS repository
+("Repository") in CVS modules ("Modules") and made available as downloadable
+archives ("Downloads").</P>
+<P>Content may be apportioned into plug-ins ("Plug-ins"), plug-in fragments
+("Fragments"), and features ("Features"). A Feature is a bundle of one or more
+Plug-ins and/or Fragments and associated material. Files named "feature.xml" may
+contain a list of the names and version numbers of the Plug-ins and/or Fragments
+associated with a Feature. Plug-ins and Fragments are located in directories
+named "plugins" and Features are located in directories named "features".</P>
+<P>Features may also include other Features ("Included Features"). Files named
+"feature.xml" may contain a list of the names and version numbers of Included
+Features.</P>
+<P>The terms and conditions governing Plug-ins and Fragments should be contained
+in files named "about.html" ("Abouts"). The terms and conditions governing
+Features and Included Features should be contained in files named "license.html"
+("Feature Licenses"). Abouts and Feature Licenses may be located in any
+directory of a Download or Module including, but not limited to the following
+locations:</P>
+<UL>
+ <LI>The top-level (root) directory
+ <LI>Plug-in and Fragment directories
+ <LI>Subdirectories of the directory named "src" of certain Plug-ins
+ <LI>Feature directories </LI></UL>
+<P>Note: if a Feature made available by the Eclipse Foundation is installed
+using the Eclipse Update Manager, you must agree to a license ("Feature Update
+License") during the installation process. If the Feature contains Included
+Features, the Feature Update License should either provide you with the terms
+and conditions governing the Included Features or inform you where you can
+locate them. Feature Update Licenses may be found in the "license" property of
+files named "feature.properties". Such Abouts, Feature Licenses and Feature
+Update Licenses contain the terms and conditions (or references to such terms
+and conditions) that govern your use of the associated Content in that
+directory.</P>
+<P>THE ABOUTS, FEATURE LICENSES AND FEATURE UPDATE LICENSES MAY REFER TO THE EPL
+OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS. SOME OF THESE
+OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):</P>
+<UL>
+ <LI>Common Public License Version 1.0 (available at <A
+ href="http://www.eclipse.org/legal/cpl-v10.html">http://www.eclipse.org/legal/cpl-v10.html</A>)
+
+ <LI>Apache Software License 1.1 (available at <A
+ href="http://www.apache.org/licenses/LICENSE">http://www.apache.org/licenses/LICENSE</A>)
+
+ <LI>Apache Software License 2.0 (available at <A
+ href="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</A>)
+
+ <LI>IBM Public License 1.0 (available at <A
+ href="http://oss.software.ibm.com/developerworks/opensource/license10.html">http://oss.software.ibm.com/developerworks/opensource/license10.html</A>)
+
+ <LI>Metro Link Public License 1.00 (available at <A
+ href="http://www.opengroup.org/openmotif/supporters/metrolink/license.html">http://www.opengroup.org/openmotif/supporters/metrolink/license.html</A>)
+
+ <LI>Mozilla Public License Version 1.1 (available at <A
+ href="http://www.mozilla.org/MPL/MPL-1.1.html">http://www.mozilla.org/MPL/MPL-1.1.html</A>)
+ </LI>
+
+ <LI>Common Development and Distribution License (CDDL) Version 1.0 (available at <A
+ href="http://www.sun.com/cddl/cddl.html">http://www.sun.com/cddl/cddl.html)</A>
+ </LI>
+</UL>
+<P>IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR
+TO USE OF THE CONTENT. If no About, Feature License or Feature Update License is
+provided, please contact the Eclipse Foundation to determine what terms and
+conditions govern that particular Content.</P>
+<H3>Cryptography</H3>
+<P>Content may contain encryption software. The country in which you are
+currently may have restrictions on the import, possession, and use, and/or
+re-export to another country, of encryption software. BEFORE using any
+encryption software, please check the country's laws, regulations and policies
+concerning the import, possession, or use, and re-export of encryption software,
+to see if this is permitted.</P></BODY></HTML>
