1 files changed, 0 insertions, 9 deletions
diff --git a/tests/org.eclipse.wst.wsdl.validation.tests/testresources/samples/WSDL/Import/WSDLOnlyTypes.wsdl b/tests/org.eclipse.wst.wsdl.validation.tests/testresources/samples/WSDL/Import/WSDLOnlyTypes.wsdl
deleted file mode 100644
index faf4f64bc..000000000
--- a/tests/org.eclipse.wst.wsdl.validation.tests/testresources/samples/WSDL/Import/WSDLOnlyTypes.wsdl
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<wsdl:definitions xmlns:tns="http://tempuri.org/WSDLOnlyTypes/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="WSDLOnlyTypes" targetNamespace="http://tempuri.org/WSDLOnlyTypes/">
-	<wsdl:types>
-		<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
-			elementFormDefault="qualified"
-			targetNamespace="http://tempuri.org/WSDLOnlyTypes/">
-		<xsd:element name="NewGlobalElement" type="xsd:string"></xsd:element></xsd:schema>
-	</wsdl:types>
-</wsdl:definitions>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/.cvsignore b/docs/org.eclipse.jst.j2ee.doc.user/.cvsignore
deleted file mode 100644
index 0598c5482..000000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/.cvsignore
+++ /dev/null
@@ -1,2 +0,0 @@
-build.xml
-org.eclipse.jst.j2ee.doc.user_1.0.0.jar
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/.project b/docs/org.eclipse.jst.j2ee.doc.user/.project
deleted file mode 100644
index 86d94083c..000000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/.project
+++ /dev/null
@@ -1,22 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
-	<name>Copy of org.eclipse.jst.j2ee.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.j2ee.doc.user/META-INF/MANIFEST.MF b/docs/org.eclipse.jst.j2ee.doc.user/META-INF/MANIFEST.MF
deleted file mode 100644
index f13fb0841..000000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/META-INF/MANIFEST.MF
+++ /dev/null
@@ -1,8 +0,0 @@
-Manifest-Version: 1.0
-Bundle-ManifestVersion: 2
-Bundle-Name: %pluginName
-Bundle-SymbolicName: org.eclipse.jst.j2ee.doc.user; singleton:=true
-Bundle-Version: 1.0.1.qualifier
-Bundle-Vendor: %pluginProvider
-Bundle-Localization: plugin
-Eclipse-LazyStart: true
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/about.html b/docs/org.eclipse.jst.j2ee.doc.user/about.html
deleted file mode 100644
index 4c99086f8..000000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/about.html
+++ /dev/null
@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
-<title>About</title>
-</head>
-<body lang="EN-US">
-<h2>About This Content</h2>
- 
-<p>February 24, 2005</p>	
-<h3>License</h3>
-
-<p>The Eclipse Foundation makes available all content in this plug-in (&quot;Content&quot;).  Unless otherwise indicated below, the Content is provided to you under the terms and conditions of the
-Eclipse Public License Version 1.0 (&quot;EPL&quot;).  A copy of the EPL is available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
-For purposes of the EPL, &quot;Program&quot; 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 (&quot;Redistributor&quot;) and different terms and conditions may
-apply to your use of any object code in the Content.  Check the Redistributor's license that was provided with the Content.  If no such license exists, contact the Redistributor.  Unless otherwise
-indicated below, the terms and conditions of the EPL still apply to any source code in the Content.</p>
-
-</body>
-</html>
-\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/build.properties b/docs/org.eclipse.jst.j2ee.doc.user/build.properties
deleted file mode 100644
index 5c4701193..000000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/build.properties
+++ /dev/null
@@ -1,11 +0,0 @@
-bin.includes = images/,\
-               jst_j2ee_toc.xml,\
-               jst_j2ee_ant.xml,\
-               topics/,\
-               plugin.xml,\
-               plugin.properties,\
-               META-INF/,\
-               about.html/,\
-               about.html,\
-               org.eclipse.jst.j2ee.doc.userindex.html
-src.includes = build.properties,\
-\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/images/ProjectExplorer.gif b/docs/org.eclipse.jst.j2ee.doc.user/images/ProjectExplorer.gif
deleted file mode 100644
index c51d9d96f..000000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/images/ProjectExplorer.gif
+++ /dev/null
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/jst_j2ee_toc.xml b/docs/org.eclipse.jst.j2ee.doc.user/jst_j2ee_toc.xml
deleted file mode 100644
index e3cde96c9..000000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/jst_j2ee_toc.xml
+++ /dev/null
@@ -1,39 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<?NLS  TYPE="org.eclipse.help.toc"?>
-<toc label="J2EE applications - WTP" topic="topics/ph-j2eeapp.html">
-   <topic label="J2EE Applications" href="topics/ph-j2eeapp.html">
-      <topic label="J2EE architecture" href="topics/cjarch.html"/>
-      <topic label="J2EE perspective" href="topics/cjpers.html"/>
-      <topic label="Project Explorer view in the J2EE perspective" href="topics/cjview.html"/>
-      <topic label="Working with projects" href="topics/ph-projects.html">
-         <topic label="Enterprise application projects" href="topics/cjearproj.html"/>
-         <topic label="Application client projects" href="topics/cjappcliproj.html"/>
-         <topic label="Specifying target servers for J2EE projects" href="topics/tjtargetserver.html"/>
-         <topic label="Importing and exporting projects and files" href="topics/ph-importexport.html">
-            <topic label="Exporting an application client project" href="topics/tjexpapp.html"/>
-            <topic label="Exporting an enterprise application into an EAR file" href="topics/tjexpear.html"/>
-            <topic label="Exporting connector projects to RAR files" href="topics/tjexprar.html"/>
-            <topic label="Importing an enterprise application EAR file" href="topics/tjimpear.html"/>
-            <topic label="Importing an application client JAR file" href="topics/tjimpapp.html"/>
-            <topic label="Importing a connector project RAR file" href="topics/tjimprar.html"/>
-            <topic label="Cyclical dependencies between J2EE modules" href="topics/cjcircle.html"/>
-            <topic label="Correcting cyclical dependencies after an EAR is imported" href="topics/tjcircleb.html"/>
-         </topic>
-      </topic>
-      <topic label="Validating code in enterprise applications" href="topics/tjval.html">
-         <topic label="Common validation errors and solutions" href="topics/rvalerr.html"/>
-         <topic label="J2EE Validators" href="topics/rvalidators.html"/>
-         <topic label="Enabling automatic code validation" href="topics/tjvalauto.html"/>
-         <topic label="Enabling build validation" href="topics/tjvalbuild.html"/>
-         <topic label="Disabling a validator" href="topics/tjvaldisable.html"/>
-         <topic label="Overriding global validation preferences" href="topics/tjvalglobalpref.html"/>
-         <topic label="Manually validating code" href="topics/tjvalmanual.html"/>
-         <topic label="Selecting code validators" href="topics/tjvalselect.html"/>
-      </topic>
-      <topic label="Reference" href="topics/ph-ref.html">
-         <topic label="J2EE Validators" href="topics/rvalidators.html"/>
-         <topic label="Common validation errors and solutions" href="topics/rvalerr.html"/>
-         <topic label="Limitations of J2EE development tools" href="topics/rjlimitcurrent.html"/>
-      </topic>
-   </topic>
-</toc>
-\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/org.eclipse.jst.j2ee.doc.userindex.html b/docs/org.eclipse.jst.j2ee.doc.user/org.eclipse.jst.j2ee.doc.userindex.html
deleted file mode 100644
index 6be89b65c..000000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/org.eclipse.jst.j2ee.doc.userindex.html
+++ /dev/null
@@ -1,175 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
-  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright IBM Corporation 2005" />
-<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_41" href="#IDX1_41">A</a>
-<a name="IDX0_42" href="#IDX1_42">B</a>
-<a name="IDX0_43" href="#IDX1_43">C</a>
-<a name="IDX0_45" href="#IDX1_45">E</a>
-<a name="IDX0_4A" href="#IDX1_4A">J</a>
-<a name="IDX0_50" href="#IDX1_50">P</a>
-<a name="IDX0_52" href="#IDX1_52">R</a>
-<a name="IDX0_56" href="#IDX1_56">V</a>
-<hr></hr>
-<strong><a name="IDX1_41" href="#IDX0_41">A</a></strong>
-<ul class="indexlist">
-<li>Ant
-<ul class="indexlist">
-<li><a href="topics/cjant.html#cjant">additional information</a>
-</li>
-<li><a href="topics/cjant.html#cjant">overview</a>
-</li>
-</ul>
-</li>
-<li>application client projects
-<ul class="indexlist">
-<li><a href="topics/cjappcliproj.html#cjappcliproj">overview</a>
-</li>
-</ul>
-</li>
-</ul>
-<strong><a name="IDX1_42" href="#IDX0_42">B</a></strong>
-<ul class="indexlist">
-<li>build validation
-<ul class="indexlist">
-<li><a href="topics/tjvalbuild.html#tjvalbuild">enabling</a>
-</li>
-</ul>
-</li>
-</ul>
-<strong><a name="IDX1_43" href="#IDX0_43">C</a></strong>
-<ul class="indexlist">
-<li>code validation
-<ul class="indexlist">
-<li><a href="topics/tjvalauto.html#tjvalauto">automatic</a>
-</li>
-<li><a href="topics/tjvaldisable.html#tjvaldisable">disabling validators</a>
-</li>
-<li><a href="topics/rvalerr.html#rvalerr">errors</a>
-</li>
-<li><a href="topics/rvalidators.html#rvalidators">J2EE validators</a>
-</li>
-<li><a href="topics/tjvalmanual.html#tjvalmanual">manual</a>
-</li>
-<li><a href="topics/tjvalglobalpref.html#tjvalglobalpref">overriding global preferences</a>
-</li>
-<li><a href="topics/tjval.html#tjval">overview</a>
-</li>
-<li><a href="topics/tjvalselect.html#tjvalselect">selecting validators</a>
-</li>
-<li><a href="topics/rvalerr.html#rvalerr">solutions to errors</a>
-</li>
-</ul>
-</li>
-<li>connector projects
-<ul class="indexlist">
-<li><a href="topics/tjexprar.html#tjexprar">exporting</a>
-</li>
-<li><a href="topics/tjimprar.html#tjimprar">importing</a>
-</li>
-</ul>
-</li>
-<li>cyclical dependencies
-<ul class="indexlist">
-<li><a href="topics/tjcircleb.html#tjcircleb">correcting</a>
-</li>
-<li><a href="topics/cjcircle.html#cjcircle">overview</a>
-</li>
-</ul>
-</li>
-</ul>
-<strong><a name="IDX1_45" href="#IDX0_45">E</a></strong>
-<ul class="indexlist">
-<li>enterprise application projects
-<ul class="indexlist">
-<li><a href="topics/cjearproj.html#cjearproj">overview</a>
-</li>
-</ul>
-</li>
-</ul>
-<strong><a name="IDX1_4A" href="#IDX0_4A">J</a></strong>
-<ul class="indexlist">
-<li>J2EE development
-<ul class="indexlist">
-<li><a href="topics/rjlimitcurrent.html#rjlimitcurrent">limitations</a>
-</li>
-</ul>
-</li>
-</ul>
-<strong><a name="IDX1_50" href="#IDX0_50">P</a></strong>
-<ul class="indexlist">
-<li>perspectives
-<ul class="indexlist">
-<li><a href="topics/cjpers.html#cjpers">J2EE</a>
-</li>
-</ul>
-</li>
-<li>projects
-<ul class="indexlist">
-<li><a href="topics/cjappcliproj.html#cjappcliproj">application client</a>
-</li>
-<li><a href="topics/tjcircleb.html#tjcircleb">correcting cyclical dependencies</a>
-</li>
-<li><a href="topics/cjcircle.html#cjcircle">cyclical dependencies</a>
-</li>
-</ul>
-</li>
-</ul>
-<strong><a name="IDX1_52" href="#IDX0_52">R</a></strong>
-<ul class="indexlist">
-<li>RAR files
-<ul class="indexlist">
-<li><a href="topics/tjexprar.html#tjexprar">exporting</a>
-</li>
-<li><a href="topics/tjimprar.html#tjimprar">importing</a>
-</li>
-</ul>
-</li>
-</ul>
-<strong><a name="IDX1_56" href="#IDX0_56">V</a></strong>
-<ul class="indexlist">
-<li>validation
-<ul class="indexlist">
-<li><a href="topics/tjvalauto.html#tjvalauto">automatic</a>
-</li>
-<li><a href="topics/tjvalbuild.html#tjvalbuild">build validation</a>
-</li>
-<li><a href="topics/tjvaldisable.html#tjvaldisable">disabling validators</a>
-</li>
-<li><a href="topics/rvalerr.html#rvalerr">errors</a>
-</li>
-<li><a href="topics/rvalidators.html#rvalidators">J2EE validators</a>
-</li>
-<li><a href="topics/tjvalmanual.html#tjvalmanual">manual</a>
-</li>
-<li><a href="topics/tjvalglobalpref.html#tjvalglobalpref">overriding global preferences</a>
-</li>
-<li><a href="topics/tjval.html#tjval">overview</a>
-</li>
-<li><a href="topics/tjvalselect.html#tjvalselect">selecting validators</a>
-</li>
-<li><a href="topics/rvalerr.html#rvalerr">solutions to errors</a>
-</li>
-</ul>
-</li>
-<li>views
-<ul class="indexlist">
-<li><a href="topics/cjview.html#cjview">Project Explorer</a>
-</li>
-</ul>
-</li>
-</ul>
-</body></html>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/plugin.properties b/docs/org.eclipse.jst.j2ee.doc.user/plugin.properties
deleted file mode 100644
index 2ca2bd40a..000000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/plugin.properties
+++ /dev/null
@@ -1,13 +0,0 @@
-###############################################################################
-# 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
-###############################################################################
-
-pluginName = J2EE tools documentation
-pluginProvider = Eclipse.org
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/plugin.xml b/docs/org.eclipse.jst.j2ee.doc.user/plugin.xml
deleted file mode 100644
index 1354079bf..000000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/plugin.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?eclipse version="3.0"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- /*******************************************************************************
- * Copyright (c) 2000, 2005 IBM Corporation and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- * 
- * Contributors:
- *     IBM Corporation - initial API and implementation
- *******************************************************************************/ -->
- <plugin>
-<extension point="org.eclipse.help.toc">
-       <toc file="jst_j2ee_toc.xml"/>
-       </extension>
-</plugin>
-\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjappcliproj.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjappcliproj.html
deleted file mode 100644
index 16a37f8e5..000000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjappcliproj.html
+++ /dev/null
@@ -1,84 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
-  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<!-- /*******************************************************************************
- * Copyright (c) 2000, 2005 IBM Corporation and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- * 
- * Contributors:
- *     IBM Corporation - initial API and implementation
- *******************************************************************************/ -->
-<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
-
-<title>Application client projects</title>
-</head>
-<body id="cjappcliproj"><a name="cjappcliproj"><!-- --></a>
-<h1 class="topictitle1">Application client projects</h1>
-<div><p> Application client projects contain the resources needed for application
-client modules. An application client module is used to contain a full-function
-client Java™ application (non Web-based) that connects to and
-uses the J2EE resources defined in your server. When you place the client
-code in an application client module instead of a simple JAR file, the application
-client benefits from the server's resources (it does not need to re-specify
-the class path to J2EE and server JAR files) as well as from easier JNDI lookup
-(the client container fills in the initial context and other parameters).
-The application client project allows you to work as if you are creating a
-standalone Java application in a Java project.</p>
-<p>An application client project enables you to do the following things:</p>
-<ul><li>Develop the Java classes that implement the client module</li>
-<li>Set the application client deployment descriptor</li>
-<li>Test the application client</li>
-</ul>
-<p>Like Java projects, application client projects contain the
-resources needed for application clients, including Java class
-files. When you create a new application client project, the environment is
-set up for Java development. A Java <em>builder</em> is associated with the
-project so the Java source can be incrementally compiled as it is updated.
-The application client project contains information about the type hierarchy
-and Java elements.
-This information is kept current as changes are made, and the Java builder
-will incrementally compile the resources within these projects as the resources
-are updated.</p>
-<p>In the workbench, application client projects are always referenced by
-enterprise application (EAR) projects. When you create an application client
-project, you specify the enterprise application project to which the application
-client project belongs. A module element is automatically added to the <samp class="codeph">application.xml</samp> deployment
-descriptor for the EAR project.</p>
-<p>An application client project is deployed as a JAR file. This application
-client JAR file contains the necessary resources for the application, including Java class
-files, and deployment descriptor information and any meta-data extensions
-and bindings files.</p>
-<p>Application client projects are typically run on networked client systems
-connected to J2EE (EJB) servers. The point of entry for the application client
-is a Java main-class,
-which is simply a Java class that contains a static main method. The class
-is declared in the manifest file of the client module. </p>
-<p>A J2EE application client container provides access to the J2EE service
-(JNDI naming services, deployment services, transaction services, and security
-services) and communications APIs (internet protocols, Remote Method Invocation
-protocols, Object Management Group protocols, Messaging protocols, and data
-formats).</p>
-<p>By default, application client projects contain one folder named <span class="uicontrol">appClientModule</span>,
-which contains both Java source code and compiled <samp class="codeph">.class</samp> files,
-along with all the meta-data files in the <span class="uicontrol">META-INF</span> subfolder.</p>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/ph-projects.html" title="The workbench can work with many different types of projects. The following topics cover creating and managing some of the types of projects related to J2EE development.">Working with projects</a></div>
-</div>
-<div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="../topics/cjarch.html" title="The Java 2 Platform, Enterprise Edition (J2EE) provides a standard for developing multitier, enterprise services.">J2EE architecture</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="../topics/tjappproj.html" title="You can use a wizard to create a new application client project and add it to a new or existing enterprise application project.">Creating an application client project</a></div>
-<div><a href="../topics/tjexpapp.html" title="You can export an application client project as a JAR file.">Exporting an application client project</a></div>
-<div><a href="../topics/tjimpapp.html" title="Application client projects are deployed as JAR files. You can import an application client project that has been deployed into a JAR file by using the Import wizard.">Importing an application client JAR file</a></div>
-</div>
-</div></body>
-</html>
-\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjarch.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjarch.html
deleted file mode 100644
index 68eea0044..000000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjarch.html
+++ /dev/null
@@ -1,68 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
-  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<!-- /*******************************************************************************
- * Copyright (c) 2000, 2005 IBM Corporation and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- * 
- * Contributors:
- *     IBM Corporation - initial API and implementation
- *******************************************************************************/ -->
-<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
-
-<title>J2EE architecture</title>
-</head>
-<body id="cjarch"><a name="cjarch"><!-- --></a>
-<h1 class="topictitle1">J2EE architecture</h1>
-<div><p>The Java™ 2 Platform, Enterprise Edition (J2EE) provides
-a standard for developing multitier, enterprise services.</p>
-<p>The economy and technology of today have intensified the need for faster,
-more efficient, and larger-scale information management solutions. The J2EE
-specification satisfies these challenges by providing a programming model
-that improves development productivity, standardizes the platform for hosting
-enterprise applications, and ensures portability of developed applications
-with an extensive test suite.</p>
-<p>J2EE architecture supports component-based development of multi-tier enterprise
-applications. A J2EE application system typically includes the following tiers:</p>
-<ul><li><strong>Client tier</strong>: In the client tier, Web components, such as Servlets
-and JavaServer Pages (JSPs), or standalone Java applications provide a dynamic
-interface to the middle tier.</li>
-<li><strong>Middle tier</strong>: In the server tier, or middle tier, enterprise beans
-and Web Services encapsulate reusable, distributable business logic for the
-application. These server-tier components are contained on a J2EE Application
-Server, which provides the platform for these components to perform actions
-and store data.</li>
-<li><strong>Enterprise data tier</strong>: In the data tier, the enterprise's data is
-stored and persisted, typically in a relational database.</li>
-</ul>
-<p>J2EE applications are comprised of components, containers, and services.
-Components are application-level components. Web components, such as Servlets
-and JSPs, provide dynamic responses to requests from a Web page. EJB components
-contain server-side business logic for enterprise applications. Web and EJB
-component containers host services that support Web and EJB modules.</p>
-<p>For more information on J2EE architecture and its implicit technologies,
-download and read the <a href="http://java.sun.com/j2ee/download.html#platformspec" target="_blank">J2EE 1.4 Specification</a>.</p>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/ph-j2eeapp.html" title="These topics deal with the Java 2 Platform, Enterprise Edition (J2EE).">J2EE Applications</a></div>
-</div>
-<div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="../topics/cjearproj.html" title="An enterprise application project contains the hierarchy of resources that are required to deploy a J2EE enterprise application, often referred to as an EAR file.">Enterprise application projects</a></div>
-<div><a href="../topics/cjappcliproj.html">Application client projects</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="../topics/tjimpear.html" title="Enterprise application projects are deployed into EAR files. You can import an enterprise application project by importing it from a deployed EAR file.">Importing an enterprise application EAR file</a></div>
-<div><a href="../topics/tjexpear.html" title="Enterprise applications are deployed in the form of an EAR file. Use the Export wizard to export an enterprise application project into an EAR file for deployment.">Exporting an enterprise application into an EAR file</a></div>
-<div><a href="../topics/tjappproj.html" title="You can use a wizard to create a new application client project and add it to a new or existing enterprise application project.">Creating an application client project</a></div>
-<div><a href="../topics/tjexpapp.html" title="You can export an application client project as a JAR file.">Exporting an application client project</a></div>
-<div><a href="../topics/tjimpapp.html" title="Application client projects are deployed as JAR files. You can import an application client project that has been deployed into a JAR file by using the Import wizard.">Importing an application client JAR file</a></div>
-</div>
-</div></body>
-</html>
-\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjcircle.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjcircle.html
deleted file mode 100644
index 93e8f4a48..000000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjcircle.html
+++ /dev/null
@@ -1,43 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
-  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<!-- /*******************************************************************************
- * Copyright (c) 2000, 2005 IBM Corporation and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- * 
- * Contributors:
- *     IBM Corporation - initial API and implementation
- *******************************************************************************/ -->
-<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
-
-<title>Cyclical dependencies between J2EE modules</title>
-</head>
-<body id="cjcircle"><a name="cjcircle"><!-- --></a>
-<h1 class="topictitle1">Cyclical dependencies between J2EE modules</h1>
-<div><p>A cyclical dependency between two or more modules in an enterprise application
-most commonly occurs when projects are imported from outside WebSphere<sup>®</sup> Studio.
-When a cycle exists between two or more modules in an enterprise application,
-the Java™ builder
-cannot accurately compute the build order of the projects. Full builds fail
-under these conditions, or require several invocations.</p>
-<p>Therefore, the best practice is to componentize your projects or modules.
-This allows you to have your module dependencies function as a tree instead
-of a cycle diagram. This practice has the added benefit of producing a better
-factored and layered application.</p>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/ph-importexport.html" title="These topics cover how to import files and projects into the workbench and export files and projects to disk.">Importing and exporting projects and files</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="../topics/tjimpear.html" title="Enterprise application projects are deployed into EAR files. You can import an enterprise application project by importing it from a deployed EAR file.">Importing an enterprise application EAR file</a></div>
-<div><a href="../topics/tjcircleb.html" title="You can resolve cyclical dependencies after an EAR is imported.">Correcting cyclical dependencies after an EAR is imported</a></div>
-</div>
-</div></body>
-</html>
-\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjearproj.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjearproj.html
deleted file mode 100644
index 756454cc4..000000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjearproj.html
+++ /dev/null
@@ -1,87 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
-  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<!-- /*******************************************************************************
- * Copyright (c) 2000, 2005 IBM Corporation and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- * 
- * Contributors:
- *     IBM Corporation - initial API and implementation
- *******************************************************************************/ -->
-<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
-
-<title>Enterprise application projects</title>
-</head>
-<body id="cjearproj"><a name="cjearproj"><!-- --></a>
-<h1 class="topictitle1">Enterprise application projects</h1>
-<div><p>An enterprise application project contains the hierarchy of resources
-that are required to deploy a J2EE enterprise application, often referred
-to as an EAR file.</p>
-<p>An enterprise application project also contains a set of references to
-other J2EE modules and Java™ projects that are combined to compose
-an EAR file. These projects can be Web modules, EJB modules, application client
-modules, connector modules, general utility Java JAR files, and EJB client JAR files.
-Enterprise application projects created in the workbench include a deployment
-descriptor, as well as files that are common to all J2EE modules
-that are defined in the deployment descriptor.</p>
-<p>When a J2EE module project is created, it can be associated with an enterprise
-application project. The project wizards aid this by allowing you to specify
-a new or existing enterprise application project. Enterprise application projects
-are exported as EAR (enterprise archive) files that include all files defined
-in the Enterprise Application project as well as the appropriate archive file
-for each J2EE module or utility JAR project defined in the deployment descriptor,
-such as Web archive (WAR) files and EJB JAR files.</p>
-<p>An enterprise application can contain utility JAR files that are to be
-used by the contained modules. This allows sharing of code at the application
-level by multiple Web, EJB, or application client modules. These JAR files
-are commonly referred to as <em>utility JAR files.</em> The utility JAR files
-defined for an enterprise application project can be actual JAR files in the
-project, or you can include utility Java projects that are designated to become
-the utility JAR files during assembly and deployment.</p>
-<p>To start developing J2EE applications, you typically first create an enterprise
-application project to contain your Web, EJB, and application client modules.
-The enterprise application project is used to compose an entire application
-from the various modules. Since no source code is built directly into an enterprise
-application, these projects are not Java projects, and they are not compiled
-by the Java builder.</p>
-<div class="p">When you create an enterprise application project using the workbench,
-the following key files are automatically created:<dl><dt class="dlterm">META-INF/application.xml</dt>
-<dd>This file is the deployment descriptor for the enterprise application,
-as defined in the J2EE specification, that is responsible for associating
-J2EE modules to a specific EAR file. It is created in the <span class="uicontrol">META-INF</span> folder.</dd>
-<dt class="dlterm">META-INF/.modulemaps</dt>
-<dd>This file contains the mappings to the contained modules and utility JAR
-projects.</dd>
-</dl>
-</div>
-<div class="p">The following workbench artifacts are also created in an enterprise application
-project but will not become part of the EAR file, and you should not edit
-them manually:<dl><dt class="dlterm">.j2ee</dt>
-<dd>This is a workbench artifact that includes the product version and J2EE
-specification level for the project.</dd>
-<dt class="dlterm">.project</dt>
-<dd>This is a workbench artifact, the standard project description file.</dd>
-<dt class="dlterm">.runtime</dt>
-<dd>This is a workbench artifact that contains the target server definition.</dd>
-</dl>
-</div>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/ph-projects.html" title="The workbench can work with many different types of projects. The following topics cover creating and managing some of the types of projects related to J2EE development.">Working with projects</a></div>
-</div>
-<div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="../topics/cjarch.html" title="The Java 2 Platform, Enterprise Edition (J2EE) provides a standard for developing multitier, enterprise services.">J2EE architecture</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="../topics/tjimpear.html" title="Enterprise application projects are deployed into EAR files. You can import an enterprise application project by importing it from a deployed EAR file.">Importing an enterprise application EAR file</a></div>
-<div><a href="../topics/tjexpear.html" title="Enterprise applications are deployed in the form of an EAR file. Use the Export wizard to export an enterprise application project into an EAR file for deployment.">Exporting an enterprise application into an EAR file</a></div>
-</div>
-</div></body>
-</html>
-\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjpers.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjpers.html
deleted file mode 100644
index 2d5d772c6..000000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjpers.html
+++ /dev/null
@@ -1,78 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
-  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<!-- /*******************************************************************************
- * Copyright (c) 2000, 2005 IBM Corporation and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- * 
- * Contributors:
- *     IBM Corporation - initial API and implementation
- *******************************************************************************/ -->
-<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
-
-<title>J2EE perspective</title>
-</head>
-<body id="cjpers"><a name="cjpers"><!-- --></a>
-<h1 class="topictitle1">J2EE perspective</h1>
-<div><p>The J2EE perspective includes workbench views that you can use
-when developing resources for enterprise applications, EJB modules, Web modules,
-application client modules, and connector projects or modules.</p>
-<p>You can rearrange the location, tiling, and size of the views within the
-perspective. You can also add other views to the J2EE perspective by clicking <span class="menucascade"><span class="uicontrol">Window</span> &gt; <span class="uicontrol">Show View</span></span> and
-selecting the view.</p>
-<p>The workbench provides synchronization between different views and editors.
-This is also true in the J2EE perspective.</p>
-<p>By default, the J2EE perspective includes the following workbench views:</p>
-<dl><dt class="dlterm"><span class="uicontrol">Project Explorer</span></dt>
-<dd>The Project Explorer provides an integrated view of your projects, grouped
-by type, and their artifacts related to J2EE development. It displays navigable
-models of J2EE deployment descriptors, Java™ artifacts (source folders, packages,
-and classes), navigable models of the available Web services, and specialized
-views of Web modules to simplify the development of dynamic Web applications.
-In addition, EJB database mapping and the configuration of projects for a
-J2EE application server are made readily available.</dd>
-<dt class="dlterm"><span class="uicontrol"> Outline</span></dt>
-<dd>The Outline view in the J2EE perspective shows the outline of the file
-that you are editing. For example, if you are using a tabbed deployment descriptor
-editor, the Outline view shows the outline for the selected page's elements,
-and if you are editing on the Source tab, the outline for the XML source is
-displayed. If you are editing an enterprise bean in the Java editor,
-the Outline view shows the outline for the Java class.</dd>
-<dt class="dlterm"><span class="uicontrol">Tasks</span></dt>
-<dd>The Tasks view lists the to-do items that you have entered.</dd>
-<dt class="dlterm"><span class="uicontrol">Problems</span></dt>
-<dd>The Problems view displays problems, warnings, or errors associated with
-the selected project. You can double-click on an item to address the specific
-problem in the appropriate resource.</dd>
-<dt class="dlterm"><span class="uicontrol">Properties</span></dt>
-<dd>The Properties view provides a tabular view of the properties and associated
-values of objects in files you have open in an editor. For example, you can
-specify converters in the Properties view of the Mapping editor.</dd>
-<dt class="dlterm"><span class="uicontrol">Status bar</span></dt>
-<dd>The Status bar provides a description of the location of selected objects
-in the Project Explorer views in the left side. When file and deployment descriptors
-are open, the status bar shows the read-only state of the files and the line
-and column numbers when applicable. Sometimes when long operations run, a
-status monitor will appear in the status bar, along with a button with a stop
-sign icon. Clicking the stop sign stops the operation when the operation can
-be cancelled.</dd>
-<dt class="dlterm"><span class="uicontrol">Servers</span></dt>
-<dd>The Servers view shows all the created server instances. You can start
-and stop each server from this view, and you can launch the test client.</dd>
-<dt class="dlterm"><span class="uicontrol">Snippets</span></dt>
-<dd>The Snippets view provides categorized pieces of code that
-you can insert into appropriate places in your source code.</dd>
-</dl>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/ph-j2eeapp.html" title="These topics deal with the Java 2 Platform, Enterprise Edition (J2EE).">J2EE Applications</a></div>
-</div>
-</div></body>
-</html>
-\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjview.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjview.html
deleted file mode 100644
index a90a6b761..000000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjview.html
+++ /dev/null
@@ -1,62 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
-  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<!-- /*******************************************************************************
- * Copyright (c) 2000, 2005 IBM Corporation and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- * 
- * Contributors:
- *     IBM Corporation - initial API and implementation
- *******************************************************************************/ -->
-<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
-
-<title>Project Explorer view in the J2EE perspective</title>
-</head>
-<body id="cjview"><a name="cjview"><!-- --></a>
-<h1 class="topictitle1">Project Explorer view in the J2EE perspective</h1>
-<div><p>While developing J2EE applications in the J2EE perspective, the
-Project Explorer view is your main view of your J2EE projects and resources.</p>
-<div class="section"><h4 class="sectiontitle">Project Explorer view</h4>The Project Explorer view provides
-an integrated view of all project resources, including models of J2EE deployment
-descriptors, Java™ artifacts, resources, Web services, databases,
-and dynamic Web project artifacts.<p>You should use this view to work with
-your J2EE deployment descriptors and their content. You can easily view an
-enterprise application project and see all of the modules associated with
-it. </p>
-<p>The following image shows the Project Explorer view with the <span class="uicontrol">Group
-projects by type</span> option selected in the toolbar:<br /><img src="../images/ProjectExplorer.gif" alt="Screen capture of the Project Explorer view" /><br /></p>
-<dl><dt class="dlterm">Enterprise Applications</dt>
-<dd>Shows a hierarchical model of all enterprise application projects.</dd>
-<dt class="dlterm">Application Client Projects</dt>
-<dd>Shows a hierarchical model of all application client modules.</dd>
-<dt class="dlterm">Connector Projects</dt>
-<dd>Shows a hierarchical model of all connector modules.</dd>
-<dt class="dlterm">Dynamic Web Projects</dt>
-<dd>Shows a hierarchical model of all dynamic Web modules.</dd>
-<dt class="dlterm">EJB Projects</dt>
-<dd>Shows a hierarchical model of all EJB projects.</dd>
-<dt class="dlterm">Other Projects</dt>
-<dd>Shows any non-J2EE module projects, such as Java projects. These Java projects
-can be any of the following types: <ul><li>Utility projects for existing Enterprise Application projects in your
-workspace</li>
-<li>EJB Client JAR Projects, which include the client interface classes (remote,
-home, local, or local home interfaces) for beans in EJB projects</li>
-<li>Java projects
-that are in your workspace but unrelated to your J2EE development</li>
-</ul>
-</dd>
-</dl>
-</div>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/ph-j2eeapp.html" title="These topics deal with the Java 2 Platform, Enterprise Edition (J2EE).">J2EE Applications</a></div>
-</div>
-</div></body>
-</html>
-\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-importexport.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-importexport.html
deleted file mode 100644
index 1456e930e..000000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-importexport.html
+++ /dev/null
@@ -1,58 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
-  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<!-- /*******************************************************************************
- * Copyright (c) 2000, 2005 IBM Corporation and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- * 
- * Contributors:
- *     IBM Corporation - initial API and implementation
- *******************************************************************************/ -->
-<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
-
-<title>Importing and exporting projects and files</title>
-</head>
-<body id="ph-importexport"><a name="ph-importexport"><!-- --></a>
-<h1 class="topictitle1">Importing and exporting projects and files</h1>
-<div><p>These topics cover how to import files and projects into the workbench
-and export files and projects to disk.</p>
-</div>
-<div>
-<ul class="ullinks">
-<li class="ulchildlink"><strong><a href="../topics/tjexpapp.html">Exporting an application client project</a></strong><br />
-You can export an application client project as a JAR file.</li>
-<li class="ulchildlink"><strong><a href="../topics/tjexpear.html">Exporting an enterprise application into an EAR file</a></strong><br />
-Enterprise applications are deployed in the form of an EAR file.
-Use the Export wizard to export an enterprise application project into an
-EAR file for deployment.</li>
-<li class="ulchildlink"><strong><a href="../topics/tjexprar.html">Exporting connector projects to RAR files</a></strong><br />
-You can export a connector project to a RAR file in preparation
-for deploying it to a server.</li>
-<li class="ulchildlink"><strong><a href="../topics/tjimpear.html">Importing an enterprise application EAR file</a></strong><br />
-Enterprise application projects are deployed into EAR files. You
-can import an enterprise application project by importing it from a deployed
-EAR file.</li>
-<li class="ulchildlink"><strong><a href="../topics/tjimpapp.html">Importing an application client JAR file</a></strong><br />
-Application client projects are deployed as JAR files. You can
-import an application client project that has been deployed into a JAR file
-by using the Import wizard.</li>
-<li class="ulchildlink"><strong><a href="../topics/tjimprar.html">Importing a connector project RAR file</a></strong><br />
-Connector projects are deployed into RAR files. You can import
-a connector project by importing a deployed RAR file.</li>
-<li class="ulchildlink"><strong><a href="../topics/cjcircle.html">Cyclical dependencies between J2EE modules</a></strong><br />
-</li>
-<li class="ulchildlink"><strong><a href="../topics/tjcircleb.html">Correcting cyclical dependencies after an EAR is imported</a></strong><br />
-You can resolve cyclical dependencies after an EAR is imported.</li>
-</ul>
-
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/ph-projects.html" title="The workbench can work with many different types of projects. The following topics cover creating and managing some of the types of projects related to J2EE development.">Working with projects</a></div>
-</div>
-</div></body>
-</html>
-\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-j2eeapp.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-j2eeapp.html
deleted file mode 100644
index 9b6143c96..000000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-j2eeapp.html
+++ /dev/null
@@ -1,47 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
-  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<!-- /*******************************************************************************
- * Copyright (c) 2000, 2005 IBM Corporation and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- * 
- * Contributors:
- *     IBM Corporation - initial API and implementation
- *******************************************************************************/ -->
-<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
-
-<title>J2EE Applications</title>
-</head>
-<body id="ph-j2eeapp"><a name="ph-j2eeapp"><!-- --></a>
-<h1 class="topictitle1">J2EE Applications</h1>
-<div><p>These topics deal with the Java™ 2 Platform, Enterprise Edition (J2EE).</p>
-</div>
-<div>
-<ul class="ullinks">
-<li class="ulchildlink"><strong><a href="../topics/cjarch.html">J2EE architecture</a></strong><br />
-The Java 2 Platform, Enterprise Edition (J2EE) provides
-a standard for developing multitier, enterprise services.</li>
-<li class="ulchildlink"><strong><a href="../topics/cjpers.html">J2EE perspective</a></strong><br />
-The J2EE perspective includes workbench views that you can use
-when developing resources for enterprise applications, EJB modules, Web modules,
-application client modules, and connector projects or modules.</li>
-<li class="ulchildlink"><strong><a href="../topics/cjview.html">Project Explorer view in the J2EE perspective</a></strong><br />
-While developing J2EE applications in the J2EE perspective, the
-Project Explorer view is your main view of your J2EE projects and resources.</li>
-<li class="ulchildlink"><strong><a href="../topics/ph-projects.html">Working with projects</a></strong><br />
-The workbench can work with many different types of projects. The
-following topics cover creating and managing some of the types of projects
-related to J2EE development.</li>
-<li class="ulchildlink"><strong><a href="../topics/tjval.html">Validating code in enterprise applications</a></strong><br />
-</li>
-<li class="ulchildlink"><strong><a href="../topics/ph-ref.html">Reference</a></strong><br />
-The following reference material on J2EE is available:</li>
-</ul>
-</div></body>
-</html>
-\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-projects.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-projects.html
deleted file mode 100644
index 876ce021f..000000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-projects.html
+++ /dev/null
@@ -1,50 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
-  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<!-- /*******************************************************************************
- * Copyright (c) 2000, 2005 IBM Corporation and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- * 
- * Contributors:
- *     IBM Corporation - initial API and implementation
- *******************************************************************************/ -->
-<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
-
-<title>Working with projects</title>
-</head>
-<body id="phprojects"><a name="phprojects"><!-- --></a>
-<h1 class="topictitle1">Working with projects</h1>
-<div><p>The workbench can work with many different types of projects. The
-following topics cover creating and managing some of the types of projects
-related to J2EE development.</p>
-</div>
-<div>
-<ul class="ullinks">
-<li class="ulchildlink"><strong><a href="../topics/cjearproj.html">Enterprise application projects</a></strong><br />
-An enterprise application project contains the hierarchy of resources
-that are required to deploy a J2EE enterprise application, often referred
-to as an EAR file.</li>
-<li class="ulchildlink"><strong><a href="../topics/cjappcliproj.html">Application client projects</a></strong><br />
-</li>
-<li class="ulchildlink"><strong><a href="../topics/tjtargetserver.html">Specifying target servers for J2EE projects</a></strong><br />
-When you develop J2EE applications, the workbench requires that
-you specify the server runtime environments for your J2EE projects. The target
-server is specified during project creation and import, and it can be changed
-in the project properties. The target server setting is the default mechanism
-for setting the class path for J2EE projects.</li>
-<li class="ulchildlink"><strong><a href="../topics/ph-importexport.html">Importing and exporting projects and files</a></strong><br />
-These topics cover how to import files and projects into the workbench
-and export files and projects to disk.</li>
-</ul>
-
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/ph-j2eeapp.html" title="These topics deal with the Java 2 Platform, Enterprise Edition (J2EE).">J2EE Applications</a></div>
-</div>
-</div></body>
-</html>
-\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-ref.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-ref.html
deleted file mode 100644
index c24a9c16f..000000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-ref.html
+++ /dev/null
@@ -1,42 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
-  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<!-- /*******************************************************************************
- * Copyright (c) 2000, 2005 IBM Corporation and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- * 
- * Contributors:
- *     IBM Corporation - initial API and implementation
- *******************************************************************************/ -->
-<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
-
-<title>Reference</title>
-</head>
-<body id="ph-ref"><a name="ph-ref"><!-- --></a>
-<h1 class="topictitle1">Reference</h1>
-<div><p>The following reference material on J2EE is available:</p>
-</div>
-<div>
-<ul class="ullinks">
-<li class="ulchildlink"><strong><a href="../topics/rvalidators.html">J2EE Validators</a></strong><br />
-This table lists the validators that are available for the different
-project types and gives a brief description of each validator.</li>
-<li class="ulchildlink"><strong><a href="../topics/rvalerr.html">Common validation errors and solutions</a></strong><br />
-You may encounter these common error messages when you validate
-your projects.</li>
-<li class="ulchildlink"><strong><a href="../topics/rjlimitcurrent.html">Limitations of J2EE development tools</a></strong><br />
-This topic outlines current known limitations and restrictions
-for J2EE tooling.</li>
-</ul>
-
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/ph-j2eeapp.html" title="These topics deal with the Java 2 Platform, Enterprise Edition (J2EE).">J2EE Applications</a></div>
-</div>
-</div></body>
-</html>
-\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/rjlimitcurrent.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/rjlimitcurrent.html
deleted file mode 100644
index 72209406b..000000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/rjlimitcurrent.html
+++ /dev/null
@@ -1,80 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
-  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<!-- /*******************************************************************************
- * Copyright (c) 2000, 2005 IBM Corporation and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- * 
- * Contributors:
- *     IBM Corporation - initial API and implementation
- *******************************************************************************/ -->
-<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
-
-<title>Limitations of J2EE development tools</title>
-</head>
-<body id="rjlimitcurrent"><a name="rjlimitcurrent"><!-- --></a>
-<h1 class="topictitle1">Limitations of J2EE development tools</h1>
-<div><p>This topic outlines current known limitations and restrictions
-for J2EE tooling.</p>
-<div class="section"><h4 class="sectiontitle">Alternate deployment descriptor (alt-dd) elements in enterprise
-applications</h4>The use of alt-dd elements is currently not supported
-in the workbench. The workaround is to edit the deployment descriptors of
-the contained modules.</div>
-<div class="section"><h4 class="sectiontitle">Spaces not supported in JAR URIs within an enterprise application</h4>Spaces
-are not supported in the URI for modules or utility JAR files in an enterprise
-application. The "Class-Path:" attribute of a MANIFEST.MF file in a JAR file
-or module is a space-delimited list of relative paths within an enterprise
-application. A JAR file would not be able to reference another JAR file in
-the EAR if the URI of the referenced JAR file contained spaces.</div>
-<div class="section"><h4 class="sectiontitle">Enterprise application project names should not contain DBCS
-characters</h4><p id="rjlimitcurrent__limitation_ear_dbcs"><a name="rjlimitcurrent__limitation_ear_dbcs"><!-- --></a>When you create an enterprise
-application project, it is recommended that you do not give it a name that
-contains double-byte character set (DBCS) characters.</p>
-</div>
-<div class="section"><h4 class="sectiontitle">Java™ build path updates when removing the dependency
-on a Utility JAR file</h4>When removing the dependency on a Utility JAR,
-the corresponding Java project will be removed from the Java build
-path only if the dependent JAR is still referenced by the EAR project. For
-example, suppose you create a J2EE 1.3 Web project and EAR along with the
-JUnit Java Example
-project. Next, add the JUnit project as a Utility JAR in the EAR, then add
-JUnit as a Java JAR Dependency of the Web project. If you then
-wanted to remove the dependency between JUnit and the Web project, remove
-the Java JAR
-Dependency from the Web project first, then remove the Utility JAR from the
-EAR. Follow this order to ensure that this works correctly.</div>
-<div class="section"><h4 class="sectiontitle">Java JAR Dependencies page fails to update Java build
-path</h4>The Java JAR Dependencies page is not synchronized with
-the Java build
-path page in the project properties dialog. Therefore, a change applied in
-one may not be reflected in the other within the same dialog session. There
-are also some instances where flipping back and forth between the pages will
-cause the update from one to cancel out the update from another when the <span class="uicontrol">OK</span> button
-is clicked or if the <span class="uicontrol">Apply</span> button is clicked prior
-to the <span class="uicontrol">OK</span> button. Typically this will appear as if
-a JAR dependency was added, but the project did not get added to the Java build
-path. The workaround is to reopen the properties dialogs, switch to the JAR
-dependency page, clear and re-select the dependent JAR files, then click <span class="uicontrol">OK</span>.</div>
-<div class="section"><h4 class="sectiontitle">'Invalid project description' error when using a non-default
-project location for a new J2EE project</h4>When you create a new J2EE
-project (including Java, enterprise application, Dynamic Web,
-EJB, application client, and connector projects), you cannot use a project
-location that is already used by another project in the workbench. If you
-choose a project location that is used by another project, the wizard displays
-an "Invalid project description" error dialog or message. If after you receive
-this message you then select a valid project location by clicking the Browse
-button, the project creation will still not finish. The workaround is to click
-Cancel and reopen the project creation wizard.</div>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/ph-ref.html" title="The following reference material on J2EE is available:">Reference</a></div>
-</div>
-</div></body>
-</html>
-\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/rvalerr.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/rvalerr.html
deleted file mode 100644
index 54090d30e..000000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/rvalerr.html
+++ /dev/null
@@ -1,190 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
-  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<!-- /*******************************************************************************
- * Copyright (c) 2000, 2005 IBM Corporation and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- * 
- * Contributors:
- *     IBM Corporation - initial API and implementation
- *******************************************************************************/ -->
-<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
-
-<title>Common validation errors and solutions</title>
-</head>
-<body id="rvalerr"><a name="rvalerr"><!-- --></a>
-<h1 class="topictitle1">Common validation errors and solutions</h1>
-<div><p>You may encounter these common error messages when you validate
-your projects.</p>
-
-<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="20.27027027027027%" id="d0e33">Message prefix</th>
-<th valign="top" width="24.324324324324326%" id="d0e35">Message</th>
-<th valign="top" width="55.4054054054054%" id="d0e37">Explanation</th>
-</tr>
-</thead>
-<tbody><tr><td colspan="3" valign="top" headers="d0e33 d0e35 d0e37 "><span class="uicontrol">Application Client validator</span></td>
-</tr>
-<tr><td valign="top" width="20.27027027027027%" headers="d0e33 ">CHKJ1000</td>
-<td valign="top" width="24.324324324324326%" headers="d0e35 ">Validation failed because the application client file
-is not valid. Ensure that the deployment descriptor is valid.</td>
-<td valign="top" width="55.4054054054054%" headers="d0e37 ">The application-client.xml file cannot be loaded. The
-project metadata cannot be initialized from the application-client.xml file.
-  <ol><li>Ensure the following:  <ul><li>that the META-INF folder exists in the application client project</li>
-<li>that META-INF contains the application-client.xml file</li>
-<li>that META-INF is in the project's classpath.</li>
-</ul>
-  </li>
-<li>Validate the syntax of the application-client.xml file: in the Navigator
-view, highlight the application-client.xml file, right-click, and select <span class="uicontrol">Validate
-XML file</span>.</li>
-<li>If both 1) and 2) are okay, close the project, reopen the project, and
-rebuild the project. The project metadata will refresh.</li>
-</ol>
- </td>
-</tr>
-<tr><td colspan="3" valign="top" headers="d0e33 d0e35 d0e37 "><span class="uicontrol">EAR validator</span></td>
-</tr>
-<tr><td valign="top" width="20.27027027027027%" headers="d0e33 ">CHKJ1001</td>
-<td valign="top" width="24.324324324324326%" headers="d0e35 ">The EAR project {0} is invalid.</td>
-<td valign="top" width="55.4054054054054%" headers="d0e37 ">The application.xml file cannot be loaded. The project
-metadata cannot be initialized from the application.xml file.  <ol><li>Ensure the following:  <ul><li>that the META-INF folder exists in the EAR project</li>
-<li>that META-INF contains <samp class="codeph">application.xml</samp></li>
-<li>that META-INF is in the project's classpath.</li>
-</ul>
-  </li>
-<li>Validate the syntax of the application.xml file: in the Navigator view,
-highlight the application.xml file, right-click, and select <span class="uicontrol">Validate
-XML file</span>.</li>
-<li>If both 1) and 2) are okay, close the project, reopen the project, and
-rebuild the project. The project metadata will refresh.</li>
-</ol>
-</td>
-</tr>
-<tr><td colspan="3" valign="top" headers="d0e33 d0e35 d0e37 "><span class="uicontrol">EJB validator</span></td>
-</tr>
-<tr><td valign="top" width="20.27027027027027%" headers="d0e33 ">CHKJ2019</td>
-<td valign="top" width="24.324324324324326%" headers="d0e35 ">The {0} key class must be serializable at runtime. </td>
-<td rowspan="3" valign="top" width="55.4054054054054%" headers="d0e37 ">The EJB is compliant with the EJB specification. This
-message is a warning that problems may occur. The warning appears when a type
-needs to be serializable at runtime and when serializability cannot be verified
-at compile-time. A type is serializable if, at runtime, it is a primitive
-type, a primitive array, a remote object, or if it implements java.io.Serializable.
-This message flags java.lang.Object and it cannot be disabled. You can either
-make the object serializable at compile-time or ignore the warning. </td>
-</tr>
-<tr><td valign="top" width="20.27027027027027%" headers="d0e33 ">CHKJ2412</td>
-<td valign="top" width="24.324324324324326%" headers="d0e35 ">The return type must be serializable at runtime. </td>
-</tr>
-<tr><td valign="top" width="20.27027027027027%" headers="d0e33 ">CHKJ2413</td>
-<td valign="top" width="24.324324324324326%" headers="d0e35 ">Argument {1} of {0} must be serializable at runtime.</td>
-</tr>
-<tr><td valign="top" width="20.27027027027027%" headers="d0e33 ">CHKJ2102</td>
-<td valign="top" width="24.324324324324326%" headers="d0e35 ">Either a finder descriptor, or a matching custom finder method on the
-{0} class, must be defined.</td>
-<td valign="top" width="55.4054054054054%" headers="d0e37 ">A finder descriptor must exist for every finder method. </td>
-</tr>
-<tr><td valign="top" width="20.27027027027027%" headers="d0e33 ">CHKJ2873</td>
-<td valign="top" width="24.324324324324326%" headers="d0e35 ">Migrate this bean's datasource binding to a CMP Connection Factory
-binding.</td>
-<td valign="top" width="55.4054054054054%" headers="d0e37 ">&nbsp;</td>
-</tr>
-<tr><td valign="top" width="20.27027027027027%" headers="d0e33 ">CHKJ2874</td>
-<td valign="top" width="24.324324324324326%" headers="d0e35 ">Migrate this EJB module's default datasource binding to a default CMP
-Connection Factory binding.</td>
-<td valign="top" width="55.4054054054054%" headers="d0e37 ">&nbsp;</td>
-</tr>
-<tr><td valign="top" width="20.27027027027027%" headers="d0e33 ">CHKJ2875E       </td>
-<td valign="top" width="24.324324324324326%" headers="d0e35 ">&lt;ejb-client-jar&gt; {0} must exist in every EAR file
-that contains this EJB module.</td>
-<td valign="top" width="55.4054054054054%" headers="d0e37 ">If <samp class="codeph">&lt;ejb-client-jar&gt;</samp> is specified
-in <span class="filepath">ejb-jar.xml</span>, a corresponding EJB client project must
-contain the home and remote interfaces and any other types that a client will
-need. If these types are all contained in a single EJB project, delete the <samp class="codeph">&lt;ejb-client-jar&gt;</samp> line
-in the deployment descriptor. Otherwise, ensure that the EJB client project
-exists, is open, and is a project utility JAR in every EAR that uses this
-EJB project as a module.</td>
-</tr>
-<tr><td valign="top" width="20.27027027027027%" headers="d0e33 ">CHKJ2905</td>
-<td valign="top" width="24.324324324324326%" headers="d0e35 ">The EJB validator did not run because ejb-jar.xml could not be loaded.
-Run the XML validator for more information.</td>
-<td valign="top" width="55.4054054054054%" headers="d0e37 ">CHKJ2905 means that the project's metadata could not be initialized
-from ejb-jar.xml. <ol><li>Ensure the following:  <ul><li>that the META-INF folder exists in the EJB project</li>
-<li>that META-INF contains ejb-jar.xml</li>
-<li>that META-INF is in the project's classpath.</li>
-</ul>
-  </li>
-<li>Validate the syntax of the ejb-jar.xml file: in the Navigator view, highlight
-the ejb-jar.xml file, right-click, and select <span class="uicontrol">Validate XML file</span>.</li>
-<li>If both 1) and 2) are okay, close the project, reopen the project, and
-rebuild the project. The project metadata will refresh.</li>
-</ol>
-</td>
-</tr>
-<tr><td colspan="3" valign="top" headers="d0e33 d0e35 d0e37 "><span class="uicontrol">JSP validator</span></td>
-</tr>
-<tr><td valign="top" width="20.27027027027027%" headers="d0e33 ">IWAW0482</td>
-<td valign="top" width="24.324324324324326%" headers="d0e35 ">No valid JspTranslator</td>
-<td valign="top" width="55.4054054054054%" headers="d0e37 ">There is a path problem with the project; the JSP Validator
-needs access to the WAS runtime code. If IWAW0482E appears on all web projects,
-check the Variable or JRE path:   <ol><li>Check the global preferences (<span class="uicontrol">Window &gt; Preferences &gt; Java &gt;Installed
-JREs</span>) and make sure that the location for the JRE is pointing
-to a valid JRE directory.  </li>
-<li>Ensure that the classpath variables (<span class="uicontrol">Window &gt; Preferences &gt;
-Java &gt; Classpath Variables</span>) are set correctly.</li>
-</ol>
- </td>
-</tr>
-<tr><td colspan="3" valign="top" headers="d0e33 d0e35 d0e37 "><span class="uicontrol">WAR validator</span></td>
-</tr>
-<tr><td valign="top" width="20.27027027027027%" headers="d0e33 ">CHKJ3008</td>
-<td valign="top" width="24.324324324324326%" headers="d0e35 ">Missing or invalid WAR file.</td>
-<td valign="top" width="55.4054054054054%" headers="d0e37 ">The web.xml file cannot be loaded. The project metadata
-cannot be initialized from the web.xml file.   <ol><li>Ensure the following:  <ul><li>that the WEB-INF folder exists in the web project</li>
-<li>that WEB-INF contains the web.xml file</li>
-<li>that WEB-INF is in the project's classpath.</li>
-</ul>
-  </li>
-<li>Validate the syntax of the web.xml file: in the Navigator view, highlight
-the web.xml file, right-click, and select <span class="uicontrol">Validate XML file</span>.</li>
-<li>If both 1) and 2) are okay, close the project, reopen the project, and
-rebuild the project. The project metadata will refresh.</li>
-</ol>
-</td>
-</tr>
-<tr><td colspan="3" valign="top" headers="d0e33 d0e35 d0e37 "><span class="uicontrol">XML validator</span></td>
-</tr>
-<tr><td valign="top" width="20.27027027027027%" headers="d0e33 "> </td>
-<td valign="top" width="24.324324324324326%" headers="d0e35 ">The content of element type "ejb-jar" is incomplete, it must match
-"(description?,display-name?,small-icon?,large-icon?,enterprise-beans,assembly-descriptor?,ejb-client-jar?)".</td>
-<td valign="top" width="55.4054054054054%" headers="d0e37 ">The EJB 1.1 and 2.0 specifications mandate that at least one enterprise
-bean must exist in an EJB .jar file. This error message is normal during development
-of EJB .jar files and can be ignored until you perform a production action,
-such as exporting or deploying code. Define at least one enterprise bean in
-the project.</td>
-</tr>
-</tbody>
-</table>
-</div>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/tjval.html">Validating code in enterprise applications</a></div>
-</div>
-
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/ph-ref.html" title="The following reference material on J2EE is available:">Reference</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="../topics/tjval.html">Validating code in enterprise applications</a></div>
-</div>
-<div class="relref"><strong>Related reference</strong><br />
-<div><a href="../topics/rvalidators.html" title="This table lists the validators that are available for the different project types and gives a brief description of each validator.">J2EE Validators</a></div>
-</div>
-</div></body>
-</html>
-\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/rvalidators.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/rvalidators.html
deleted file mode 100644
index 2a7b973a2..000000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/rvalidators.html
+++ /dev/null
@@ -1,151 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
-  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<!-- /*******************************************************************************
- * Copyright (c) 2000, 2005 IBM Corporation and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- * 
- * Contributors:
- *     IBM Corporation - initial API and implementation
- *******************************************************************************/ -->
-<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
-
-<title>J2EE Validators</title>
-</head>
-<body id="rvalidators"><a name="rvalidators"><!-- --></a>
-<h1 class="topictitle1">J2EE Validators</h1>
-<div><p>This table lists the validators that are available for the different
-project types and gives a brief description of each validator.</p>
-
-<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="50%" id="d0e24">Validator name</th>
-<th valign="top" width="50%" id="d0e26">Description</th>
-</tr>
-</thead>
-<tbody><tr><td align="left" valign="top" width="50%" headers="d0e24 ">Application Client Validator</td>
-<td align="left" valign="top" width="50%" headers="d0e26 ">The Application Client Validator validates
-the following Application Client project resources:   <ul><li>Deployment descriptor (application-client.xml)</li>
-<li>EJB references</li>
-<li>Resource references</li>
-</ul>
-</td>
-</tr>
-<tr><td valign="top" width="50%" headers="d0e24 ">Connector Validator</td>
-<td valign="top" width="50%" headers="d0e26 ">The Connector validator checks for invalid J2EE specification
-levels in connector projects.</td>
-</tr>
-<tr><td align="left" valign="top" width="50%" headers="d0e24 ">DTD Validator</td>
-<td align="left" valign="top" width="50%" headers="d0e26 ">The DTD validator determines whether the
-current state of a DTD is semantically valid. XML files are validated according
-to the XML specification <a href="http://www.w3.org/TR/2000/REC-xml-20001006" target="_blank"> Extensible Markup Language (XML) 1.0</a> from the W3C
-Web site. As well, the DTD validator checks for errors such as references
-to entities and elements that do not exist.</td>
-</tr>
-<tr><td align="left" valign="top" width="50%" headers="d0e24 ">EAR Validator</td>
-<td align="left" valign="top" width="50%" headers="d0e26 ">The EAR Validator validates the following:
- <ul><li>EAR deployment descriptor (application.xml)</li>
-<li>EJB references of all module projects in the enterprise application project</li>
-<li>Security roles</li>
-<li>Resource references</li>
-<li>Manifest files for all contained or referenced modules and utility JAR
-files</li>
-<li>Target server consistency between the enterprise application project and
-any utility and module projects</li>
-<li>Existence of projects for each module defined in enterprise application</li>
-</ul>
-  <p>Note that the EAR Validator only ensures the validity and dependency
-of the module projects with respect to the enterprise application project.</p>
-</td>
-</tr>
-<tr><td align="left" valign="top" width="50%" headers="d0e24 ">EJB Validator</td>
-<td align="left" valign="top" width="50%" headers="d0e26 ">The EJB Validator verifies that enterprise
-beans contained in an EJB project comply with the Sun Enterprise JavaBeans™ Specifications
-(1.1, 2.0, and 2.1), depending on the level of the bean. Code validation for
-the EJB 1.0 specification is not supported.   <p>Specifically, the EJB Validator
-validates the following resources: </p>
-  <ul><li>Java™ .class
-files that are members of an enterprise bean (home interface, remote interface,
-enterprise bean class, and, if the bean is an entity bean, the key class)</li>
-<li>ejb-jar.xml</li>
-</ul>
-</td>
-</tr>
-<tr><td valign="top" width="50%" headers="d0e24 ">EL Syntax Validator</td>
-<td valign="top" width="50%" headers="d0e26 ">&nbsp;</td>
-</tr>
-<tr><td align="left" valign="top" width="50%" headers="d0e24 ">HTML Syntax Validator</td>
-<td align="left" valign="top" width="50%" headers="d0e26 ">The HTML Syntax Validator validates HTML
-basic syntax and HTML DTD compliance in the following Web project resources:
- <ul><li>HTML files</li>
-<li>JSP files</li>
-</ul>
-</td>
-</tr>
-<tr><td align="left" valign="top" width="50%" headers="d0e24 ">JSP Syntax Validator</td>
-<td align="left" valign="top" width="50%" headers="d0e26 ">The JSP Syntax Validator validates JSP files
-in a project by translating them into the corresponding Java code
-and then checking the Java code for compile errors.</td>
-</tr>
-<tr><td align="left" valign="top" width="50%" headers="d0e24 ">War Validator</td>
-<td align="left" valign="top" width="50%" headers="d0e26 ">The War Validator validates the following
-web project resources:   <ul><li>Deployment descriptor (web.xml)</li>
-<li>Servlets</li>
-<li>Security roles</li>
-<li>Servlet &amp; servlet mappings</li>
-<li>EJB references</li>
-</ul>
-</td>
-</tr>
-<tr><td valign="top" width="50%" headers="d0e24 ">WSDL Validator</td>
-<td valign="top" width="50%" headers="d0e26 ">The WSDL validator checks the following in WSDL files: <ul><li>XML syntax</li>
-<li>XML Schema types in the &lt;types&gt; section</li>
-<li>Referential integrity of the various constructs in WSDL </li>
-</ul>
-The validator also includes an extension point to allow other validators
-to be plugged into the WSDL validation to provide additional verification
-of the WSDL file. Through this mechanism, interoperability is checked by validating
-a WSDL file against WS-I Profiles. </td>
-</tr>
-<tr><td valign="top" width="50%" headers="d0e24 ">WS-I Message Validator</td>
-<td valign="top" width="50%" headers="d0e26 ">WS-I Message validator checks SOAP messages against
-WS-I Profiles. A user can capture and verify SOAP messages using the TCP/IP
-Monitor. The validator checks a message log that is saved as a project resource
-(.wsimsg). The log conforms to a format as specified by WS-I.</td>
-</tr>
-<tr><td align="left" valign="top" width="50%" headers="d0e24 ">XML Schema Validator</td>
-<td align="left" valign="top" width="50%" headers="d0e26 ">The XML schema validator determines whether
-the current state of an XML schema file is semantically valid. XML schemas
-are validated according to the XML Schema specification <a href="http://www.w3.org/TR/xmlschema-1/"> XML Schema Part 1:
-Structures</a> from the W3C Web site.</td>
-</tr>
-<tr><td align="left" valign="top" width="50%" headers="d0e24 ">XML Validator</td>
-<td align="left" valign="top" width="50%" headers="d0e26 ">The XML validator ensures that an XML file
-is well-formed. It also verifies if an XML file is valid - that is, it follows
-the constraints established in the DTD or XML schema the XML file is associated
-with.</td>
-</tr>
-</tbody>
-</table>
-</div>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/tjval.html">Validating code in enterprise applications</a></div>
-</div>
-
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/ph-ref.html" title="The following reference material on J2EE is available:">Reference</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="../topics/tjval.html">Validating code in enterprise applications</a></div>
-</div>
-<div class="relref"><strong>Related reference</strong><br />
-<div><a href="../topics/rvalerr.html" title="You may encounter these common error messages when you validate your projects.">Common validation errors and solutions</a></div>
-</div>
-</div></body>
-</html>
-\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjappproj.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjappproj.html
deleted file mode 100644
index 72dd0b9c5..000000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjappproj.html
+++ /dev/null
@@ -1,69 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
-  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<!-- /*******************************************************************************
- * Copyright (c) 2000, 2005 IBM Corporation and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- * 
- * Contributors:
- *     IBM Corporation - initial API and implementation
- *******************************************************************************/ -->
-<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
-
-<title>Creating an application client project</title>
-</head>
-<body id="tjappproj"><a name="tjappproj"><!-- --></a>
-<h1 class="topictitle1">Creating an application client project</h1>
-<div><p>You can use a wizard to create a new application client project
-and add it to a new or existing enterprise application project.</p>
-<div class="section"> <p>Application client projects contain the resources needed for
-application client modules. Application client projects contain programs that
-run on networked client systems. An application client project is deployed
-as a JAR file.</p>
-<p>To create a J2EE application client project:</p>
-</div>
-<ol><li class="stepexpand"><span>In the J2EE perspective, click <span class="menucascade"><span class="uicontrol">File</span> &gt; <span class="uicontrol">New</span> &gt; <span class="uicontrol">Application Client Project</span></span>. The New Application Client Project window opens.</span></li>
-<li class="stepexpand"><span>In the <span class="uicontrol">Name</span> field, type a name for the application
-client project. </span></li>
-<li class="stepexpand"><span>To change the default <span class="uicontrol">Project location</span>,
-click the <span class="uicontrol">Browse</span> button to select a new location. If
-you specify a non-default project location that is already being used by another
-project, the project creation will fail.</span></li>
-<li class="stepexpand"><span>Click <span class="uicontrol">Show Advanced</span>.</span></li>
-<li class="stepexpand"><span>In the <span class="uicontrol">Target runtime</span> drop-down list, select
-the application server that you want to target for your development. This
-selection affects the run time settings by modifying the class path entries
-for the project.</span></li>
-<li class="stepexpand"><span>In the <span class="uicontrol">Module version</span> drop-down list, select
-the module version to which you want your application client project to adhere.</span></li>
-<li class="stepexpand"><span>Specify whether you want to add the new module to an enterprise
-application (EAR) project.</span></li>
-<li class="stepexpand"><span>In the <span class="uicontrol">EAR application</span> combination box,
-type a new project name or select an existing enterprise application project
-from the drop-down list. Or, click the <span class="uicontrol">New</span> button to
-launch the New Enterprise Application Project wizard.</span> <div class="note"><span class="notetitle">Note:</span> If
-you type a new EAR project name, the EAR project will be created in the default
-location with the lowest compatible J2EE version based on the version of the
-project being created. If you want to specify a different version or a different
-location for the enterprise application, you must use the New Enterprise Application
-Project wizard.</div>
-</li>
-<li class="stepexpand"><span>Click <span class="uicontrol">Finish</span>.</span></li>
-</ol>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="../topics/cjarch.html" title="The Java 2 Platform, Enterprise Edition (J2EE) provides a standard for developing multitier, enterprise services.">J2EE architecture</a></div>
-<div><a href="../topics/cjappcliproj.html">Application client projects</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="../topics/tjexpapp.html" title="You can export an application client project as a JAR file.">Exporting an application client project</a></div>
-<div><a href="../topics/tjimpapp.html" title="Application client projects are deployed as JAR files. You can import an application client project that has been deployed into a JAR file by using the Import wizard.">Importing an application client JAR file</a></div>
-</div>
-</div></body>
-</html>
-\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjcircleb.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjcircleb.html
deleted file mode 100644
index 05a1cf6b6..000000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjcircleb.html
+++ /dev/null
@@ -1,55 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
-  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<!-- /*******************************************************************************
- * Copyright (c) 2000, 2005 IBM Corporation and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- * 
- * Contributors:
- *     IBM Corporation - initial API and implementation
- *******************************************************************************/ -->
-<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
-
-<title>Correcting cyclical dependencies after an EAR is imported</title>
-</head>
-<body id="tjcircleb"><a name="tjcircleb"><!-- --></a>
-<h1 class="topictitle1">Correcting cyclical dependencies after an EAR is imported</h1>
-<div><p>You can resolve cyclical dependencies after an EAR is imported.</p>
-<div class="section">A cyclical dependency between two or more modules in an enterprise
-application most commonly occurs when projects are imported from outside the
-workbench. When a cycle exists between two or more modules in an enterprise
-application, the Java™ builder cannot accurately compute the build order
-of the projects. Full builds fail under these conditions, or require several
-invocations.<p>Therefore, the best practice is to organize your projects or
-modules into components. This allows your module dependencies to function
-as a tree instead of a cycle diagram. This practice has the added benefit
-of producing a better factored and layered application.</p>
-</div>
-<ol><li><span>Identify all the classes within the JAR files that have cyclical
-dependencies, then move those classes into a common Java project
-or JAR file.</span></li>
-<li><span>Use the enterprise application editor to map utility JAR files
-to the common projects.</span></li>
-<li><span>Use the JAR dependency editor or properties page, for each module
-of the JAR in the application, to set dependencies only to the JAR files that
-are truly required.</span></li>
-</ol>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/ph-importexport.html" title="These topics cover how to import files and projects into the workbench and export files and projects to disk.">Importing and exporting projects and files</a></div>
-</div>
-<div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="../topics/cjcircle.html">Cyclical dependencies between J2EE modules</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="../topics/tjimpear.html" title="Enterprise application projects are deployed into EAR files. You can import an enterprise application project by importing it from a deployed EAR file.">Importing an enterprise application EAR file</a></div>
-</div>
-</div></body>
-</html>
-\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjear.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjear.html
deleted file mode 100644
index 79d015428..000000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjear.html
+++ /dev/null
@@ -1,86 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
-  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<!-- /*******************************************************************************
- * Copyright (c) 2000, 2005 IBM Corporation and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- * 
- * Contributors:
- *     IBM Corporation - initial API and implementation
- *******************************************************************************/ -->
-<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
-
-<title>Creating an enterprise application project</title>
-</head>
-<body id="tjear"><a name="tjear"><!-- --></a>
-<h1 class="topictitle1">Creating an enterprise application project</h1>
-<div><div class="section"><p>Enterprise application projects contain references to the resources
-needed for enterprise applications and can contain a combination of Web modules,
-JAR files, connector modules, EJB modules, and application client modules.
-An enterprise application project is deployed in the form of an EAR file,
-and is therefore sometimes referred to as an EAR project. The modules in an
-enterprise application project are mapped to other J2EE projects. The mapping
-information is stored in metadata files within the enterprise application
-project. The metadata files are used for exporting the project to an EAR file
-and for running the project on the server.</p>
-<p>When you create an enterprise
-application project, it is recommended that you do not give it a name that
-contains double-byte character set (DBCS) characters.</p>
-<p>To
-create a J2EE enterprise application project:</p>
-</div>
-<ol><li class="stepexpand"><span>In the J2EE perspective, select <span class="menucascade"><span class="uicontrol">File</span> &gt; <span class="uicontrol">New</span> &gt; <span class="uicontrol">Enterprise Application Project</span></span>.</span></li>
-<li class="stepexpand"><span>In the <span class="uicontrol">Name</span> field, type a name for the new
-enterprise application project. To change the default <span class="uicontrol">Project location</span>,
-click the <span class="uicontrol">Browse</span> button to select a new location.</span></li>
-<li class="stepexpand"><span>Click <span class="uicontrol">Show Advanced</span>.</span></li>
-<li class="stepexpand"><span>In the <span class="uicontrol">Target runtime</span> drop-down list, select
-the application server that you want to target for your development. </span></li>
-<li class="stepexpand"><span>In the <span class="uicontrol">Module Version</span> list, specify the
-J2EE specification level that you want to use for this enterprise application.</span></li>
-<li class="stepexpand"><span>Click <span class="uicontrol">Next</span>.</span></li>
-<li class="stepexpand"><span>On the EAR Modules page of the wizard, select the existing modules
-that you want to add to the new enterprise application project. Click the <span class="uicontrol">New
-Module</span> button to open another wizard where you can create new
-modules for this enterprise application. In the New Module wizard, if you
-select the <span class="uicontrol">Create default module projects</span> check box,
-you can choose to create default versions of the following modules which will
-be compatible with the enterprise application J2EE version:</span><ul><li>Application client project</li>
-<li>EJB project</li>
-<li>Web project</li>
-<li>Connector project</li>
-</ul>
- The wizard provides default project names for the modules, but you can
-specify different project names. The default modules that are created will
-have the same server target as the new enterprise application.<p>If you clear
-the <span class="uicontrol">Create default module projects</span> check box, you can
-select a single module type and proceed with the proper wizard for that project
-type.</p>
-<p>If you create new modules at this time, they are added to the
-list of available modules in the New Enterprise Application Project wizard,
-if the module versions are compatible with the new enterprise application
-you are creating.</p>
-</li>
-<li class="stepexpand"><span>Click <span class="uicontrol">Finish</span>.</span></li>
-</ol>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/ph-projects.html" title="The workbench can work with many different types of projects. The following topics cover creating and managing some of the types of projects related to J2EE development.">Working with projects</a></div>
-</div>
-<div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="../topics/cjarch.html" title="The Java 2 Platform, Enterprise Edition (J2EE) provides a standard for developing multitier, enterprise services.">J2EE architecture</a></div>
-<div><a href="../topics/cjearproj.html" title="An enterprise application project contains the hierarchy of resources that are required to deploy a J2EE enterprise application, often referred to as an EAR file.">Enterprise application projects</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="../topics/tjimpear.html" title="Enterprise application projects are deployed into EAR files. You can import an enterprise application project by importing it from a deployed EAR file.">Importing an enterprise application EAR file</a></div>
-<div><a href="../topics/tjexpear.html" title="Enterprise applications are deployed in the form of an EAR file. Use the Export wizard to export an enterprise application project into an EAR file for deployment.">Exporting an enterprise application into an EAR file</a></div>
-</div>
-</div></body>
-</html>
-\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexpapp.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexpapp.html
deleted file mode 100644
index c49cbaf87..000000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexpapp.html
+++ /dev/null
@@ -1,55 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
-  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<!-- /*******************************************************************************
- * Copyright (c) 2000, 2005 IBM Corporation and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- * 
- * Contributors:
- *     IBM Corporation - initial API and implementation
- *******************************************************************************/ -->
-<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
-
-<title>Exporting an application client project</title>
-</head>
-<body id="tjexpapp"><a name="tjexpapp"><!-- --></a>
-<h1 class="topictitle1">Exporting an application client project</h1>
-<div><p>You can export an application client project as a JAR file.</p>
-<div class="section"><p>To export an application client project from the workbench:</p>
-</div>
-<ol><li><span>In the Project Explorer view of the J2EE perspective, right-click
-the application client project that you want to export.</span></li>
-<li><span>Select <span class="menucascade"><span class="uicontrol">Export</span> &gt; <span class="uicontrol">App
-Client JAR file</span></span> from the pop-up menu. The Export
-wizard opens.</span></li>
-<li><span>In the <span class="uicontrol">Destination</span> field, enter the full
-path and JAR file name where you want to export the application client project
-that is selected in the <span class="uicontrol">Application Client project</span> field.</span></li>
-<li><strong>Optional: </strong><span>To export source files, select the <span class="uicontrol">Export
-source files</span> check box.</span></li>
-<li><strong>Optional: </strong><span>If you are exporting to an existing JAR file
-and you do not want to be warned about overwriting it, select <span class="uicontrol">Overwrite
-existing files without warning</span>.</span></li>
-<li><span>Click <span class="uicontrol">Finish</span>.</span></li>
-</ol>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/ph-importexport.html" title="These topics cover how to import files and projects into the workbench and export files and projects to disk.">Importing and exporting projects and files</a></div>
-</div>
-<div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="../topics/cjarch.html" title="The Java 2 Platform, Enterprise Edition (J2EE) provides a standard for developing multitier, enterprise services.">J2EE architecture</a></div>
-<div><a href="../topics/cjappcliproj.html">Application client projects</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="../topics/tjappproj.html" title="You can use a wizard to create a new application client project and add it to a new or existing enterprise application project.">Creating an application client project</a></div>
-<div><a href="../topics/tjimpapp.html" title="Application client projects are deployed as JAR files. You can import an application client project that has been deployed into a JAR file by using the Import wizard.">Importing an application client JAR file</a></div>
-</div>
-</div></body>
-</html>
-\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexpear.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexpear.html
deleted file mode 100644
index d5ed8d908..000000000
--- a/