This commit was manufactured by cvs2svn to create tag 'R3_0_3'.
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 6e60185..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/.cvsignore
+++ /dev/null
@@ -1,4 +0,0 @@
-build.xml
-org.eclipse.jst.j2ee.doc.user_1.0.0.jar
-temp
-DitaLink.cat
\ No newline at end of file
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 86d9408..0000000
--- 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/DocBuild.xml b/docs/org.eclipse.jst.j2ee.doc.user/DocBuild.xml
deleted file mode 100644
index 6ecb379..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/DocBuild.xml
+++ /dev/null
@@ -1,66 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" ?>
-<!--
-
- This script build the Help plug-in by transforming the DITA source files into HTML.
-
- To use this script, you must install DITA-OT on your machine in the directory
- defined by the dita.ot.dir property.
-
- Run the default target after you edit the DITA source files to regenerate the HTML.
-
- To customize this script for other Help plug-ins, modify the value of the args.input property
- to be the DITA map file for the plug-in.
-
- NOTE: This script assumes that links to sibling Help plug-ins have scope="peer", otherwise the
- output directory structure will be shifted incorrectly.
-
- NOTE: This script assumes that you hand code your plugin.xml file in myplugin.xml. This file
- will be copied over the generated plugin.xml which is currently not being generated correctly
- by DITA-OT.
-
- ChangeLog:
- 2006-04-05 Arthur Ryman <ryman@ca.ibm.com>
- - Created.
- 2008-01-09 Kate Price <katep@ca.ibm.com>
- - modified for new DITA-OT version
- 2008-05-05 Kate Price <katep@ca.ibm.com>
- - modified to add generation of pre-built help index.
- - Must delete /index folder before running build
--->
-<project name="eclipsehelp" default="all">
-
- <property name="dita.ot.dir" location="C:/DITA-OT1.2.2" />
-
- <path id="dost.class.path">
- <pathelement location="${dita.ot.dir}${file.separator}lib${file.separator}dost.jar" />
- </path>
-
- <taskdef name="integrate" classname="org.dita.dost.platform.IntegratorTask">
- <classpath refid="dost.class.path" />
- </taskdef>
- <target name="all" depends="integrate, eclipsehelp">
- </target>
- <target name="integrate">
- <integrate ditadir="${dita.ot.dir}" />
- </target>
-
- <!-- revise below here -->
- <target name="eclipsehelp">
- <ant antfile="${dita.ot.dir}${file.separator}conductor.xml" target="init" dir="${dita.ot.dir}">
- <property name="args.copycss" value="no" />
- <property name="args.csspath" value="../org.eclipse.wst.doc.user" />
- <property name="args.eclipse.provider" value="Eclipse.org" />
- <property name="args.eclipse.version" value="3.3.0" />
- <property name="args.input" location="jst_j2ee_toc.ditamap" />
- <property name="clean.temp" value="true" />
- <property name="dita.extname" value=".dita" />
- <property name="dita.temp.dir" location="temp" />
- <property name="output.dir" location="" />
- <property name="transtype" value="eclipsehelp" />
- </ant>
- <copy file="myplugin.xml" tofile="plugin.xml" overwrite="yes" />
- </target>
- <target name="build.index" description="Builds search index for the plug-in" if="eclipse.running">
- <help.buildHelpIndex manifest="plugin.xml" destination="."/>
- </target>
-</project>
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 8dba9e6..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/META-INF/MANIFEST.MF
+++ /dev/null
@@ -1,7 +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.1.1.qualifier
-Bundle-Vendor: %pluginProvider
-Bundle-Localization: plugin
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 2199df3..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/about.html
+++ /dev/null
@@ -1,34 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<HTML>
-
-<head>
-<title>About</title>
-<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
-</head>
-
-<BODY lang="EN-US">
-
-<H3>About This Content</H3>
-
-<P>June, 2008</P>
-
-<H3>License</H3>
-
-<P>The Eclipse Foundation makes available all content in this plug-in
-("Content"). Unless otherwise indicated below, the Content is provided to you
-under the terms and conditions of the Eclipse Public License Version 1.0
-("EPL"). A copy of the EPL is available at
-<A href="http://www.eclipse.org/org/documents/epl-v10.php">http://www.eclipse.org/org/documents/epl-v10.php</A>.
-For purposes of the EPL, "Program" will mean the Content.</P>
-
-<P>If you did not receive this Content directly from the Eclipse Foundation, the
-Content is being redistributed by another party ("Redistributor") and different
-terms and conditions may apply to your use of any object code in the Content.
-Check the Redistributors license that was provided with the Content. If no such
-license exists, contact the Redistributor. Unless otherwise indicated below, the
-terms and conditions of the EPL still apply to any source code in the Content
-and such source code may be obtained at
-<A href="http://www.eclipse.org/">http://www.eclipse.org/</A>.</P>
-
-</BODY>
-</HTML>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/build.properties b/docs/org.eclipse.jst.j2ee.doc.user/build.properties
deleted file mode 100644
index 10f19b1..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/build.properties
+++ /dev/null
@@ -1,16 +0,0 @@
-bin.includes = images/,\
- jst_j2ee_toc.xml,\
- jst_j2ee_relsmap.xml,\
- topics/*.htm*,\
- plugin.xml,\
- plugin.properties,\
- index/,\
- META-INF/,\
- about.html,\
- org.eclipse.jst.j2ee.doc.userindex.xml
-src.includes = build.properties,\
- *.maplist,\
- *.ditamap,\
- topics/*.dita
-bin.excludes = DocBuild.xml,\
- myPlugin*.xml
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/images/AddRelationship.gif b/docs/org.eclipse.jst.j2ee.doc.user/images/AddRelationship.gif
deleted file mode 100644
index a56a758..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/images/AddRelationship.gif
+++ /dev/null
Binary files differ
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 d5c7290..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/images/ProjectExplorer.gif
+++ /dev/null
Binary files differ
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/images/Relationships.gif b/docs/org.eclipse.jst.j2ee.doc.user/images/Relationships.gif
deleted file mode 100644
index a9f52eb..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/images/Relationships.gif
+++ /dev/null
Binary files differ
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/images/n5rpdcst.gif b/docs/org.eclipse.jst.j2ee.doc.user/images/n5rpdcst.gif
deleted file mode 100644
index 68be18c..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/images/n5rpdcst.gif
+++ /dev/null
Binary files differ
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/images/validatefilters.jpg b/docs/org.eclipse.jst.j2ee.doc.user/images/validatefilters.jpg
deleted file mode 100644
index 6481091..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/images/validatefilters.jpg
+++ /dev/null
Binary files differ
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/images/ycwin.gif b/docs/org.eclipse.jst.j2ee.doc.user/images/ycwin.gif
deleted file mode 100644
index 895f9ca..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/images/ycwin.gif
+++ /dev/null
Binary files differ
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/index/_18.cfs b/docs/org.eclipse.jst.j2ee.doc.user/index/_18.cfs
deleted file mode 100644
index 3402414..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/index/_18.cfs
+++ /dev/null
Binary files differ
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/index/deletable b/docs/org.eclipse.jst.j2ee.doc.user/index/deletable
deleted file mode 100644
index 593f470..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/index/deletable
+++ /dev/null
Binary files differ
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/index/indexed_contributions b/docs/org.eclipse.jst.j2ee.doc.user/index/indexed_contributions
deleted file mode 100644
index 4b6436b..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/index/indexed_contributions
+++ /dev/null
@@ -1,3 +0,0 @@
-#This is a generated file; do not edit.
-#Tue May 27 10:47:44 EDT 2008
-org.eclipse.jst.j2ee.doc.user=org.eclipse.jst.j2ee.doc.user\n1.1.0.qualifier
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/index/indexed_dependencies b/docs/org.eclipse.jst.j2ee.doc.user/index/indexed_dependencies
deleted file mode 100644
index 943e5fe..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/index/indexed_dependencies
+++ /dev/null
@@ -1,4 +0,0 @@
-#This is a generated file; do not edit.
-#Tue May 27 10:47:44 EDT 2008
-lucene=1.9.1.v200706111724
-analyzer=org.eclipse.help.base\#3.3.1.v20070813_33x?locale\=en
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/index/indexed_docs b/docs/org.eclipse.jst.j2ee.doc.user/index/indexed_docs
deleted file mode 100644
index 8289a25..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/index/indexed_docs
+++ /dev/null
@@ -1,42 +0,0 @@
-#This is a generated file; do not edit.
-#Tue May 27 10:47:44 EDT 2008
-/org.eclipse.jst.j2ee.doc.user/topics/cjcircle.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/tjvalselect.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/taddingfacet.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/tjimpapp.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/cfacets.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/tchangefacet.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/ph-j2eeapp.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/tjappproj.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/ph-projects.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/ctypesofanno.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/rjlimitcurrent.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/cjee5overview.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/cjview.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/cjarch.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/ph-importexport.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/tjimprar.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/tjear.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/tjimpear.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/ph-ref.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/tjcircleb.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/tjrar.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/cjpers.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/cjappcliproj.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/rvalerr.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/tdefiningannotations.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/tchangejavalevel.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/tjvalmanual.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/rvalidators.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/tjexpapp.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/tjval.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/cannotations.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/cjearproj.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/tjviewfilters.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/tjexpear.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/tjexprar.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/cjavaee5.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/tjtargetserver.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/tjvaldisable.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/rtunevalidat.html=0
-/org.eclipse.jst.j2ee.doc.user/topics/tjvalglobalpref.html=0
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/index/segments b/docs/org.eclipse.jst.j2ee.doc.user/index/segments
deleted file mode 100644
index cbc649a..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/index/segments
+++ /dev/null
Binary files differ
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/jst_j2ee_relsmap.ditamap b/docs/org.eclipse.jst.j2ee.doc.user/jst_j2ee_relsmap.ditamap
deleted file mode 100644
index d07f946..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/jst_j2ee_relsmap.ditamap
+++ /dev/null
@@ -1,158 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN"
- "map.dtd">
-<map title="J2EE WTP relational table">
-<reltable>
-<relheader>
-<relcolspec type="concept"></relcolspec>
-<relcolspec type="task"></relcolspec>
-<relcolspec type="reference"></relcolspec>
-</relheader>
-<relrow>
-<relcell linking="targetonly">
-<topicref href="topics/cjarch.dita" navtitle="J2EE architecture"></topicref>
-</relcell>
-<relcell collection-type="family">
-<topicref href="topics/tjtargetserver.dita" navtitle="Specifying target servers for J2EE projects">
-</topicref>
-</relcell>
-<relcell></relcell>
-<relcell>
-<topicref format="html" href="../org.eclipse.wst.server.ui.doc.user/topics/twinstprf.html"
-linking="targetonly" locktitle="yes" navtitle="Defining the installed server runtime environments"
-scope="peer"></topicref>
-</relcell>
-</relrow>
-<relrow>
-<relcell></relcell>
-<relcell>
-<topicref href="topics/tjval.dita" navtitle="Validating code in enterprise applications">
-</topicref>
-</relcell>
-<relcell collection-type="family">
-<topicref href="topics/rvalerr.dita" navtitle="Common validation errors and solutions">
-</topicref>
-<topicref href="topics/rvalidators.dita" navtitle="J2EE Validators"></topicref>
-</relcell>
-</relrow>
-<relrow>
-<relcell></relcell>
-<relcell collection-type="family">
-<topicref href="topics/tjvaldisable.dita" navtitle="Disabling validation">
-</topicref>
-<topicref href="topics/tjvalglobalpref.dita" navtitle="Overriding global validation preferences">
-</topicref>
-<topicref href="topics/tjvalmanual.dita" navtitle="Manually validating code">
-</topicref>
-<topicref href="topics/tjvalselect.dita" navtitle="Selecting code validators">
-</topicref>
-</relcell>
-<relcell>
-<topicref href="topics/rtunevalidat.dita" navtitle="Tuning validators"></topicref>
-</relcell>
-</relrow>
-<relrow>
-<relcell collection-type="family">
-<topicref href="topics/cjarch.dita" navtitle="J2EE architecture"></topicref>
-<topicref href="topics/cjearproj.dita" navtitle="Enterprise application projects">
-</topicref>
-</relcell>
-<relcell collection-type="family">
-<topicref href="topics/tjear.dita" navtitle="Creating an enterprise application project">
-</topicref>
-<topicref href="topics/tjimpear.dita" navtitle="Importing an enterprise application EAR file">
-</topicref>
-<topicref href="topics/tjexpear.dita" navtitle="Exporting an enterprise application into an EAR file">
-</topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell collection-type="family">
-<topicref href="topics/cjarch.dita" navtitle="J2EE architecture"></topicref>
-<topicref href="topics/cjappcliproj.dita" navtitle="Application client projects">
-</topicref>
-</relcell>
-<relcell collection-type="family">
-<topicref href="topics/tjappproj.dita" navtitle="Creating an application client project">
-</topicref>
-<topicref href="topics/tjexpapp.dita" navtitle="Exporting an application client project">
-</topicref>
-<topicref href="topics/tjimpapp.dita" navtitle="Importing an application client JAR file">
-</topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell>
-<topicref href="topics/cjcircle.dita" navtitle="Cyclical dependencies between J2EE modules">
-</topicref>
-</relcell>
-<relcell collection-type="family">
-<topicref href="topics/tjimpear.dita" navtitle="Importing an enterprise application EAR file">
-</topicref>
-<topicref href="topics/tjcircleb.dita" navtitle="Correcting cyclical dependencies after an EAR is imported">
-</topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell collection-type="family">
-<topicref href="topics/cjview.dita" navtitle="Project Explorer view in the J2EE perspective">
-</topicref>
-</relcell>
-<relcell>
-<topicref href="topics/tjviewfilters.dita" navtitle="Filtering in the Project Explorer view">
-</topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell>
-<topicref href="topics/cjearproj.dita" navtitle="Enterprise application projects">
-</topicref>
-</relcell>
-<relcell>
-<topicref href="topics/tjear.dita" navtitle="Creating an enterprise application project">
-</topicref>
-<topicref href="topics/tjappproj.dita" navtitle="Creating an application client project">
-</topicref>
-<topicref href="topics/tjrar.dita" navtitle="Creating a connector project">
-</topicref>
-</relcell>
-<relcell></relcell>
-<relcell>
-<topicref href="topics/cfacets.dita" navtitle="Project facets"></topicref>
-</relcell>
-</relrow>
-<relrow>
-<relcell>
-<topicref href="topics/cjpers.dita" navtitle="J2EE perspective"></topicref>
-<topicref href="topics/cjview.dita" navtitle="Project Explorer view in the J2EE perspective">
-</topicref>
-</relcell>
-<relcell></relcell>
-<relcell></relcell>
-<relcell>
-<topicref format="html" href="../org.eclipse.platform.doc.user/concepts/cworkset.htm"
-locktitle="yes" navtitle="Working sets" scope="peer"></topicref>
-</relcell>
-</relrow>
-<relrow>
-<relcell>
-<topicref href="topics/cfacets.dita" navtitle="Project facets"></topicref>
-</relcell>
-<relcell collection-type="family">
-<topicref href="topics/taddingfacet.dita" navtitle="Adding a facet to a J2EE project">
-</topicref>
-<topicref href="topics/tchangejavalevel.dita" navtitle="Changing the Java compiler version for a J2EE
-project"></topicref>
-<topicref href="topics/tchangefacet.dita" navtitle="Changing the version of a facet">
-</topicref>
-</relcell>
-<relcell></relcell>
-<relcell></relcell>
-</relrow>
-</reltable>
-</map>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/jst_j2ee_relsmap.xml b/docs/org.eclipse.jst.j2ee.doc.user/jst_j2ee_relsmap.xml
deleted file mode 100644
index a0c990b..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/jst_j2ee_relsmap.xml
+++ /dev/null
@@ -1,5 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<?NLS TYPE="org.eclipse.help.toc"?>
-
-<toc label="J2EE WTP relational table"/>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/jst_j2ee_toc.ditamap b/docs/org.eclipse.jst.j2ee.doc.user/jst_j2ee_toc.ditamap
deleted file mode 100644
index 3f2dad8..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/jst_j2ee_toc.ditamap
+++ /dev/null
@@ -1,120 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN"
- "map.dtd">
-<map id="jstj2eetoc" title="J2EE applications - WTP">
-<anchor id="map_top"/>
-<topicref href="topics/ph-j2eeapp.dita" navtitle="Java EE applications">
-<anchor id="before_intro_topics"/>
-<topicref href="topics/cjavaee5.dita" navtitle="Developing Java EE 5 Applications">
-<topicref href="topics/cjee5overview.dita" navtitle="Java EE 5: Overview">
-</topicref>
-<topicref href="topics/cannotations.dita" navtitle="Java EE 5 support for annotations">
-<topicref href="topics/tdefiningannotations.dita" navtitle="Defining and using Annotations">
-<topicref href="topics/ctypesofanno.dita" navtitle="Types of annotations">
-</topicref>
-</topicref>
-</topicref>
-</topicref>
-<topicref href="topics/cjarch.dita" navtitle="J2EE architecture"></topicref>
-<topicref href="topics/cjpers.dita" navtitle="Java EE perspective"></topicref>
-<topicref href="topics/cjview.dita" navtitle="Project Explorer view in the Java EE perspective">
-</topicref>
-<anchor id="after_intro_topics"/>
-<anchor id="before_filters"/>
-<topicref href="topics/tjviewfilters.dita" navtitle="Filtering in the Project Explorer view">
-</topicref>
-<anchor id="after_filters"/>
-<anchor id="before_projects"/>
-<topicref href="topics/ph-projects.dita" navtitle="Working with projects">
-<topicref href="topics/cjearproj.dita" navtitle="Enterprise application projects">
-</topicref>
-<topicref href="topics/cjappcliproj.dita" navtitle="Application client projects">
-</topicref>
-<anchor id="project_types"/>
-<topicref href="topics/tjear.dita" navtitle="Creating an enterprise application project">
-</topicref>
-<topicref href="topics/tjappproj.dita" navtitle="Creating an application client project">
-</topicref>
-<topicref href="topics/tjrar.dita" navtitle="Creating a connector project">
-</topicref>
-<anchor id="creating_projects"/>
-<topicref href="topics/tjtargetserver.dita" navtitle="Specifying target servers for J2EE projects">
-</topicref>
-<anchor id="target_servers"/>
-<topicref href="topics/cfacets.dita" navtitle="Project facets">
-<topicref href="topics/taddingfacet.dita" navtitle="Adding a facet to a Java EE project">
-</topicref>
-<topicref href="topics/tchangefacet.dita" navtitle="Changing the version of a facet">
-</topicref>
-<topicref href="topics/tchangejavalevel.dita" navtitle="Changing the Java compiler version for a Java EE project">
-</topicref>
-<anchor id="childof_J2EEProjectFacets"/></topicref>
-<anchor id="J2EEProjectFacets"/>
-<anchor id="before_importexport"/>
-<topicref href="topics/ph-importexport.dita" navtitle="Importing and exporting projects and files">
-<anchor id="importexport_top"/>
-<topicref href="topics/tjexpapp.dita" navtitle="Exporting an application client project">
-</topicref>
-<topicref href="topics/tjexpear.dita" navtitle="Exporting an enterprise application into an EAR file">
-</topicref>
-<topicref href="topics/tjexprar.dita" navtitle="Exporting connector projects to RAR files">
-</topicref>
-<anchor id="export_types"/>
-<topicref href="topics/tjimpear.dita" navtitle="Importing an enterprise application EAR file">
-</topicref>
-<topicref href="topics/tjimpapp.dita" navtitle="Importing an application client JAR file">
-</topicref>
-<topicref href="topics/tjimprar.dita" navtitle="Importing a connector project RAR file">
-</topicref>
-<topicref format="html" href="../org.eclipse.wst.webtools.doc.user/topics/twimpwar.html"
-linking="targetonly" locktitle="yes" navtitle="Importing Web archive (WAR) files"
-scope="peer" toc="no"></topicref>
-<topicref format="html" href="../org.eclipse.wst.webtools.doc.user/topics/twcrewar.html"
-linking="targetonly" locktitle="yes" navtitle="Exporting Web Archive (WAR) files"
-scope="peer" toc="no"></topicref>
-<topicref format="html" href="../org.eclipse.jst.ejb.doc.user/topics/teimp.html"
-linking="targetonly" locktitle="yes" navtitle="Importing EJB JAR files" scope="peer"
-toc="no"></topicref>
-<topicref format="html" href="../org.eclipse.jst.ejb.doc.user/topics/teexp.html"
-linking="targetonly" locktitle="yes" navtitle="Exporting EJB projects to EJB JAR files"
-scope="peer" toc="no"></topicref>
-<anchor id="import_types"/>
-<anchor id="before_dependencies"/>
-<topicref href="topics/cjcircle.dita" navtitle="Cyclical dependencies between Java EE modules">
-</topicref>
-<topicref href="topics/tjcircleb.dita" navtitle="Correcting cyclical dependencies after an EAR
-is imported"></topicref>
-<anchor id="after_dependencies"/>
-<anchor id="importexport_bottom"/></topicref>
-<anchor id="after_importexport"/></topicref>
-<anchor id="after_projects"/>
-<anchor id="before_validation"/>
-<topicref href="topics/tjval.dita" navtitle="Validating code in enterprise applications">
-<anchor id="validation_top"/>
-<topicref href="topics/rtunevalidat.dita" navtitle="Tuning validators"></topicref>
-<topicref href="topics/rvalerr.dita" navtitle="Common validation errors and solutions">
-</topicref>
-<topicref href="topics/rvalidators.dita" navtitle="J2EE Validators">
-<anchor id="childof_validators"/></topicref>
-<topicref href="topics/tjvaldisable.dita" navtitle="Disabling validation">
-</topicref>
-<topicref href="topics/tjvalselect.dita" navtitle="Selecting code validators">
-</topicref>
-<topicref href="topics/tjvalglobalpref.dita" navtitle="Overriding global validation preferences">
-</topicref>
-<topicref href="topics/tjvalmanual.dita" navtitle="Manually validating code">
-</topicref>
-<anchor id="validation_bottom"/></topicref>
-<anchor id="after_validation"/>
-<anchor id="before_reference"/>
-<topicref href="topics/ph-ref.dita" navtitle="Reference">
-<anchor id="reference_top"/>
-<topicref href="topics/rvalidators.dita" navtitle="J2EE Validators"></topicref>
-<topicref href="topics/rvalerr.dita" navtitle="Common validation errors and solutions">
-<anchor id="validation_errors"/></topicref>
-<topicref href="topics/rjlimitcurrent.dita" navtitle="Limitations of J2EE development tools">
-<anchor id="limitations"/></topicref>
-<anchor id="reference_bottom"/></topicref>
-<anchor id="after_reference"/></topicref>
-<anchor id="map_bottom"/></map>
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 b8a1c37..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/jst_j2ee_toc.xml
+++ /dev/null
@@ -1,92 +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">
-<anchor id="map_top"/>
-<topic label="Java EE applications" href="topics/ph-j2eeapp.html">
-<anchor id="before_intro_topics"/>
-<topic label="Developing Java EE 5 Applications" href="topics/cjavaee5.html">
-<topic label="Java EE 5: Overview" href="topics/cjee5overview.html"/>
-<topic label="Java EE 5 support for annotations" href="topics/cannotations.html">
-<topic label="Defining and using annotations" href="topics/tdefiningannotations.html">
-<topic label="Types of annotations" href="topics/ctypesofanno.html"/>
-</topic>
-</topic>
-</topic>
-<topic label="J2EE architecture" href="topics/cjarch.html"/>
-<topic label="Java EE perspective" href="topics/cjpers.html"/>
-<topic label="Project Explorer view in the Java EE perspective" href="topics/cjview.html"/>
-<anchor id="after_intro_topics"/>
-<anchor id="before_filters"/>
-<topic label="Filtering in the Project Explorer view" href="topics/tjviewfilters.html"/>
-<anchor id="after_filters"/>
-<anchor id="before_projects"/>
-<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"/>
-<anchor id="project_types"/>
-<topic label="Creating an enterprise application project" href="topics/tjear.html"/>
-<topic label="Creating an application client project" href="topics/tjappproj.html"/>
-<topic label="Creating a connector project" href="topics/tjrar.html"/>
-<anchor id="creating_projects"/>
-<topic label="Specifying target servers for J2EE projects" href="topics/tjtargetserver.html"/>
-<anchor id="target_servers"/>
-<topic label="Project facets" href="topics/cfacets.html">
-<topic label="Adding a facet to a Java EE project" href="topics/taddingfacet.html"/>
-<topic label="Changing the version of a facet" href="topics/tchangefacet.html"/>
-<topic label="Changing the Java compiler version for a Java EE project" href="topics/tchangejavalevel.html"/>
-<anchor id="childof_J2EEProjectFacets"/>
-</topic>
-<anchor id="J2EEProjectFacets"/>
-<anchor id="before_importexport"/>
-<topic label="Importing and exporting projects and files" href="topics/ph-importexport.html">
-<anchor id="importexport_top"/>
-<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"/>
-<anchor id="export_types"/>
-<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"/>
-<anchor id="import_types"/>
-<anchor id="before_dependencies"/>
-<topic label="Cyclical dependencies between Java EE modules" href="topics/cjcircle.html"/>
-<topic label="Correcting cyclical dependencies after an EAR is imported" href="topics/tjcircleb.html"/>
-<anchor id="after_dependencies"/>
-<anchor id="importexport_bottom"/>
-</topic>
-<anchor id="after_importexport"/>
-</topic>
-<anchor id="after_projects"/>
-<anchor id="before_validation"/>
-<topic label="Validating code in enterprise applications" href="topics/tjval.html">
-<anchor id="validation_top"/>
-<topic label="Tuning validators" href="topics/rtunevalidat.html"/>
-<topic label="Common validation errors and solutions" href="topics/rvalerr.html"/>
-<topic label="J2EE Validators" href="topics/rvalidators.html">
-<anchor id="childof_validators"/>
-</topic>
-<topic label="Disabling validation" href="topics/tjvaldisable.html"/>
-<topic label="Selecting code validators" href="topics/tjvalselect.html"/>
-<topic label="Overriding global validation preferences" href="topics/tjvalglobalpref.html"/>
-<topic label="Manually validating code" href="topics/tjvalmanual.html"/>
-<anchor id="validation_bottom"/>
-</topic>
-<anchor id="after_validation"/>
-<anchor id="before_reference"/>
-<topic label="Reference" href="topics/ph-ref.html">
-<anchor id="reference_top"/>
-<topic label="J2EE Validators" href="topics/rvalidators.html"/>
-<topic label="Common validation errors and solutions" href="topics/rvalerr.html">
-<anchor id="validation_errors"/>
-</topic>
-<topic label="Limitations of J2EE development tools" href="topics/rjlimitcurrent.html">
-<anchor id="limitations"/>
-</topic>
-<anchor id="reference_bottom"/>
-</topic>
-<anchor id="after_reference"/>
-</topic>
-<anchor id="map_bottom"/>
-</toc>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/myplugin.xml b/docs/org.eclipse.jst.j2ee.doc.user/myplugin.xml
deleted file mode 100644
index d718056..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/myplugin.xml
+++ /dev/null
@@ -1,26 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?eclipse version="3.3"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- /*******************************************************************************
- * Copyright (c) 2000, 2008 IBM Corporation and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * IBM Corporation - initial API and implementation
- *******************************************************************************/ -->
-<plugin>
-
- <extension point="org.eclipse.help.toc">
- <toc file="jst_j2ee_toc.xml" />
- <index path="index/"/>
- </extension>
- <extension point="org.eclipse.help.index">
- <index file="org.eclipse.jst.j2ee.doc.userindex.xml"/>
- </extension>
- <extension point="org.eclipse.help.base.luceneSearchParticipants">
- <binding participantId="org.eclipse.help.base.xhtml"/>
- </extension>
-</plugin>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/org.eclipse.jst.j2ee.doc.user.maplist b/docs/org.eclipse.jst.j2ee.doc.user/org.eclipse.jst.j2ee.doc.user.maplist
deleted file mode 100644
index ab8c2ad..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/org.eclipse.jst.j2ee.doc.user.maplist
+++ /dev/null
@@ -1,9 +0,0 @@
-<maplist version="3.6.2">
- <nav>
- <map file="jst_j2ee_toc.ditamap"/>
- </nav>
- <link>
- <map file="jst_j2ee_toc.ditamap"/>
- <map file="jst_j2ee_relsmap.ditamap"/>
- </link>
-</maplist>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/org.eclipse.jst.j2ee.doc.userindex.xml b/docs/org.eclipse.jst.j2ee.doc.user/org.eclipse.jst.j2ee.doc.userindex.xml
deleted file mode 100644
index 3755b16..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/org.eclipse.jst.j2ee.doc.userindex.xml
+++ /dev/null
@@ -1,252 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<index>
- <entry keyword="Java Enterprise Edition 5">
- <entry keyword="Overview">
- <topic href="topics/cjavaee5.html#cjavaee5" title="Developing Java EE 5 Applications"/>
- </entry>
- </entry>
- <entry keyword="Java EE 5">
- <topic href="topics/cjee5overview.html#cjavaee5" title="Java EE 5: Overview"/>
- <entry keyword="annotations">
- <topic href="topics/cannotations.html#cjavaee5" title="Java EE 5 support for annotations"/>
- <topic href="topics/tdefiningannotations.html#tjimpear" title="Defining and using annotations"/>
- <entry keyword="types">
- <topic href="topics/ctypesofanno.html#cjavaee5" title="Types of annotations"/>
- </entry>
- </entry>
- <entry keyword="defining">
- <topic href="topics/tdefiningannotations.html#tjimpear" title="Defining and using annotations"/>
- </entry>
- </entry>
- <entry keyword="Oerview">
- <topic href="topics/cjee5overview.html#cjavaee5" title="Java EE 5: Overview"/>
- </entry>
- <entry keyword="J2EE">
- <entry keyword="architecture">
- <topic href="topics/cjarch.html#cjarch" title="J2EE architecture"/>
- </entry>
- <entry keyword="enterprise application projects">
- <entry keyword="overview">
- <topic href="topics/cjearproj.html#cjearproj" title="Enterprise application projects"/>
- </entry>
- <entry keyword="creating">
- <topic href="topics/tjear.html#tjear" title="Creating an enterprise application project"/>
- </entry>
- </entry>
- <entry keyword="target servers">
- <topic href="topics/tjtargetserver.html#tjtargetserver" title="Specifying target servers for J2EE projects"/>
- </entry>
- <entry keyword="tool limitations">
- <topic href="topics/rjlimitcurrent.html#rjlimitcurrent" title="Limitations of J2EE development tools"/>
- </entry>
- </entry>
- <entry keyword="Java EE">
- <topic href="topics/cjarch.html#cjarch" title="J2EE architecture"/>
- <entry keyword="workbench perspectives">
- <topic href="topics/cjpers.html#cjpers" title="Java EE perspective"/>
- </entry>
- <entry keyword="application client projects">
- <topic href="topics/cjappcliproj.html#cjappcliproj" title="Application client projects"/>
- </entry>
- <entry keyword="project facets">
- <topic href="topics/cfacets.html#cfacets" title="Project facets"/>
- </entry>
- <entry keyword="adding project facets">
- <topic href="topics/taddingfacet.html#taddingfacet" title="Adding a facet to a Java EE project"/>
- </entry>
- <entry keyword="changing facet versions">
- <topic href="topics/tchangefacet.html#tchangefacet" title="Changing the version of a facet"/>
- </entry>
- <entry keyword="project compiler level">
- <topic href="topics/tchangejavalevel.html#tchangejavalevel" title="Changing the Java compiler version for a Java EE project"/>
- </entry>
- <entry keyword="cyclical dependencies between modules">
- <topic href="topics/cjcircle.html#cjcircle" title="Cyclical dependencies between Java EE modules"/>
- </entry>
- </entry>
- <entry keyword="enterprise applications">
- <entry keyword="Java EE perspective">
- <topic href="topics/cjpers.html#cjpers" title="Java EE perspective"/>
- </entry>
- <entry keyword="projects">
- <entry keyword="artifacts">
- <topic href="topics/cjearproj.html#cjearproj" title="Enterprise application projects"/>
- </entry>
- <entry keyword="creating">
- <topic href="topics/tjear.html#tjear" title="Creating an enterprise application project"/>
- </entry>
- <entry keyword="exporting">
- <topic href="topics/tjexpear.html#tjexpear" title="Exporting an enterprise application into an EAR file"/>
- </entry>
- <entry keyword="importing">
- <topic href="topics/tjimpear.html#tjimpear" title="Importing an enterprise application EAR file"/>
- </entry>
- </entry>
- </entry>
- <entry keyword="views">
- <entry keyword="Project Explorer">
- <topic href="topics/cjview.html#cjview" title="Project Explorer view in the Java EE perspective"/>
- </entry>
- <entry keyword="Project Explorer filters">
- <topic href="topics/tjviewfilters.html#cjviewfiltersCait" title="Filtering in the Project Explorer view"/>
- </entry>
- </entry>
- <entry keyword="filters">
- <entry keyword="Project Explorer view">
- <topic href="topics/tjviewfilters.html#cjviewfiltersCait" title="Filtering in the Project Explorer view"/>
- </entry>
- </entry>
- <entry keyword="projects">
- <entry keyword="filtering">
- <topic href="topics/tjviewfilters.html#cjviewfiltersCait" title="Filtering in the Project Explorer view"/>
- </entry>
- <entry keyword="enterprise applications">
- <topic href="topics/cjearproj.html#cjearproj" title="Enterprise application projects"/>
- </entry>
- <entry keyword="target servers">
- <topic href="topics/tjtargetserver.html#tjtargetserver" title="Specifying target servers for J2EE projects"/>
- </entry>
- <entry keyword="facets">
- <entry keyword="overview">
- <topic href="topics/cfacets.html#cfacets" title="Project facets"/>
- </entry>
- <entry keyword="adding">
- <topic href="topics/taddingfacet.html#taddingfacet" title="Adding a facet to a Java EE project"/>
- </entry>
- </entry>
- <entry keyword="changing facet versions">
- <topic href="topics/tchangefacet.html#tchangefacet" title="Changing the version of a facet"/>
- </entry>
- <entry keyword="Java compiler level">
- <topic href="topics/tchangejavalevel.html#tchangejavalevel" title="Changing the Java compiler version for a Java EE project"/>
- </entry>
- <entry keyword="cyclical dependencies">
- <topic href="topics/cjcircle.html#cjcircle" title="Cyclical dependencies between Java EE modules"/>
- </entry>
- <entry keyword="correcting cyclical dependencies">
- <topic href="topics/tjcircleb.html#tjcircleb" title="Correcting cyclical dependencies after an EAR is imported"/>
- </entry>
- </entry>
- <entry keyword="application client projects">
- <entry keyword="overview">
- <topic href="topics/cjappcliproj.html#cjappcliproj" title="Application client projects"/>
- </entry>
- <entry keyword="creating">
- <topic href="topics/tjappproj.html#tjappproj" title="Creating an application client project"/>
- </entry>
- <entry keyword="exporting">
- <topic href="topics/tjexpapp.html#tjexpapp" title="Exporting an application client project"/>
- </entry>
- <entry keyword="importing">
- <topic href="topics/tjimpapp.html#tjimpapp" title="Importing an application client JAR file"/>
- </entry>
- </entry>
- <entry keyword="connector projects">
- <entry keyword="creating">
- <topic href="topics/tjrar.html#tjrar" title="Creating a connector project"/>
- </entry>
- <entry keyword="exporting">
- <topic href="topics/tjexprar.html#tjexprar" title="Exporting connector projects to RAR files"/>
- </entry>
- <entry keyword="importing">
- <topic href="topics/tjimprar.html#tjimprar" title="Importing a connector project RAR file"/>
- </entry>
- </entry>
- <entry keyword="target servers">
- <entry keyword="J2EE applications">
- <topic href="topics/tjtargetserver.html#tjtargetserver" title="Specifying target servers for J2EE projects"/>
- </entry>
- </entry>
- <entry keyword="JavaServer Faces (JSF)">
- <entry keyword="project facets">
- <topic href="topics/cfacets.html#cfacets" title="Project facets"/>
- </entry>
- </entry>
- <entry keyword="facets">
- <entry keyword="changing versions">
- <topic href="topics/tchangefacet.html#tchangefacet" title="Changing the version of a facet"/>
- </entry>
- </entry>
- <entry keyword="EAR">
- <entry keyword="files">
- <entry keyword="exporting">
- <topic href="topics/tjexpear.html#tjexpear" title="Exporting an enterprise application into an EAR file"/>
- </entry>
- <entry keyword="importing">
- <topic href="topics/tjimpear.html#tjimpear" title="Importing an enterprise application EAR file"/>
- </entry>
- </entry>
- </entry>
- <entry keyword="RAR files">
- <entry keyword="exporting">
- <topic href="topics/tjexprar.html#tjexprar" title="Exporting connector projects to RAR files"/>
- </entry>
- <entry keyword="importing">
- <topic href="topics/tjimprar.html#tjimprar" title="Importing a connector project RAR file"/>
- </entry>
- </entry>
- <entry keyword="dependencies">
- <entry keyword="cycles between modules">
- <topic href="topics/cjcircle.html#cjcircle" title="Cyclical dependencies between Java EE modules"/>
- </entry>
- <entry keyword="correcting cyclical">
- <topic href="topics/tjcircleb.html#tjcircleb" title="Correcting cyclical dependencies after an EAR is imported"/>
- </entry>
- </entry>
- <entry keyword="EAR files">
- <entry keyword="correcting cyclical dependencies">
- <topic href="topics/tjcircleb.html#tjcircleb" title="Correcting cyclical dependencies after an EAR is imported"/>
- </entry>
- </entry>
- <entry keyword="build validation">
- <entry keyword="enabling">
- <topic href="topics/tjval.html#tjval" title="Validating code in enterprise applications"/>
- </entry>
- </entry>
- <entry keyword="code validation">
- <entry keyword="overview">
- <topic href="topics/tjval.html#tjval" title="Validating code in enterprise applications"/>
- </entry>
- <entry keyword="error solutions">
- <topic href="topics/rvalerr.html#rvalerr" title="Common validation errors and solutions"/>
- </entry>
- <entry keyword="J2EE validators">
- <topic href="topics/rvalidators.html#rvalidators" title="J2EE Validators"/>
- </entry>
- <entry keyword="disabling">
- <topic href="topics/tjvaldisable.html#tjvaldisable" title="Disabling validation"/>
- </entry>
- <entry keyword="selecting validators">
- <topic href="topics/tjvalselect.html#tjvalselect" title="Selecting code validators"/>
- </entry>
- <entry keyword="overriding global preferences">
- <topic href="topics/tjvalglobalpref.html#tjvalglobalpref" title="Overriding global validation preferences"/>
- </entry>
- <entry keyword="manual">
- <topic href="topics/tjvalmanual.html#tjvalmanual" title="Manually validating code"/>
- </entry>
- </entry>
- <entry keyword="validation">
- <entry keyword="overview">
- <topic href="topics/tjval.html#tjval" title="Validating code in enterprise applications"/>
- </entry>
- <entry keyword="error solutions">
- <topic href="topics/rvalerr.html#rvalerr" title="Common validation errors and solutions"/>
- </entry>
- <entry keyword="J2EE validators">
- <topic href="topics/rvalidators.html#rvalidators" title="J2EE Validators"/>
- </entry>
- <entry keyword="disabling">
- <topic href="topics/tjvaldisable.html#tjvaldisable" title="Disabling validation"/>
- </entry>
- <entry keyword="selecting validators">
- <topic href="topics/tjvalselect.html#tjvalselect" title="Selecting code validators"/>
- </entry>
- <entry keyword="overriding global preferences">
- <topic href="topics/tjvalglobalpref.html#tjvalglobalpref" title="Overriding global validation preferences"/>
- </entry>
- <entry keyword="manual">
- <topic href="topics/tjvalmanual.html#tjvalmanual" title="Manually validating code"/>
- </entry>
- </entry>
-</index>
\ No newline at end of file
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 15a4950..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/plugin.properties
+++ /dev/null
@@ -1,14 +0,0 @@
-###############################################################################
-# Copyright (c) 2001, 2008 IBM Corporation and others.
-# All rights reserved. This program and the accompanying materials
-# are made available under the terms of the Eclipse Public License v1.0
-# which accompanies this distribution, and is available at
-# http://www.eclipse.org/legal/epl-v10.html
-#
-# Contributors:
-# IBM Corporation - initial API and implementation
-###############################################################################
-# NLS_MESSAGEFORMAT_VAR
-# NLS_ENCODING=UTF-8
-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 d718056..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/plugin.xml
+++ /dev/null
@@ -1,26 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?eclipse version="3.3"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- /*******************************************************************************
- * Copyright (c) 2000, 2008 IBM Corporation and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * IBM Corporation - initial API and implementation
- *******************************************************************************/ -->
-<plugin>
-
- <extension point="org.eclipse.help.toc">
- <toc file="jst_j2ee_toc.xml" />
- <index path="index/"/>
- </extension>
- <extension point="org.eclipse.help.index">
- <index file="org.eclipse.jst.j2ee.doc.userindex.xml"/>
- </extension>
- <extension point="org.eclipse.help.base.luceneSearchParticipants">
- <binding participantId="org.eclipse.help.base.xhtml"/>
- </extension>
-</plugin>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/cannotations.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/cannotations.dita
deleted file mode 100644
index 196f729..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cannotations.dita
+++ /dev/null
@@ -1,62 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<concept id="cjavaee5" xml:lang="en-us">
-<title outputclass="id_title"><tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> EE 5 support for annotations</title>
-<shortdesc outputclass="id_shortdesc">The goal of <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> EE 5 platform development is to minimize
-the number of artifacts that you have to create and maintain, thereby simplifying
-the development process. <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> EE 5 supports the injection of annotations
-into your source code, so that you can embed resources, dependencies, services,
-and life-cycle notifications in your source code, without having to maintain
-these artifacts elsewhere.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>Java EE 5<indexterm>annotations</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p>An annotation is a modifier or Metadata tag that provides additional data
-to <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> classes,
-interfaces, constructors, methods, fields, parameters, and local variables.
-Annotations replace boilerplate code, common code that is required by certain
-applications. For example, an annotation can replace the paired interface
-and implementation required for a Web service. Annotations can also replace
-additional files that programs require, which are maintained separately. By
-using an annotation, this separate file is no longer required. For example,
-annotations can replace the need for a separately maintained deployment descriptor
-for <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="JavaBeans">JavaBeans</tm>. </p>
-<p>Annotations<ul>
-<li>Replace descriptors for most purposes</li>
-<li>Remove the need for marker interfaces (like java.rmi.Remote)</li>
-<li>Allow application settings to be visible in the component they affect</li>
-</ul></p>
-<p>Java EE 5 provides annotations for the following tasks, among others:<ul>
-<li>Developing Enterprise JavaBean applications</li>
-<li>Defining and using Web services</li>
-<li>Mapping Java technology classes to XML</li>
-<li>Mapping Java technology classes to databases</li>
-<li>Mapping methods to operations</li>
-<li>Specifying external dependencies</li>
-<li>Specirying deployment information, including security attributes</li>
-</ul></p>
-<p><tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> EE
-5 defines a number of annotations that can be injected into your source code.
-To declare an annotation, you simply precede the keyword with an "at" sign
-(@). <codeblock>
-package com.ibm.counter;
-
-import javax.ejb.Stateless;
-
-@Stateless
-
-public class CounterBean {
-
-}</codeblock></p>
-<p>For more information about the categories of annotations that <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> EE
-5 supports, see <xref href="ctypesofanno.dita">Types of annotations</xref>.</p>
-</conbody>
-</concept>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/cannotations.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/cannotations.html
deleted file mode 100644
index 029ce1a..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cannotations.html
+++ /dev/null
@@ -1,109 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="concept" name="DC.Type" />
-<meta name="DC.Title" content="Java EE 5 support for annotations" />
-<meta name="abstract" content="The goal of Java EE 5 platform development is to minimize the number of artifacts that you have to create and maintain, thereby simplifying the development process. Java EE 5 supports the injection of annotations into your source code, so that you can embed resources, dependencies, services, and life-cycle notifications in your source code, without having to maintain these artifacts elsewhere." />
-<meta name="description" content="The goal of Java EE 5 platform development is to minimize the number of artifacts that you have to create and maintain, thereby simplifying the development process. Java EE 5 supports the injection of annotations into your source code, so that you can embed resources, dependencies, services, and life-cycle notifications in your source code, without having to maintain these artifacts elsewhere." />
-<meta content="Java EE 5, annotations" name="DC.subject" />
-<meta content="Java EE 5, annotations" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjavaee5.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tdefiningannotations.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="cjavaee5" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Java EE 5 support for annotations</title>
-</head>
-<body id="cjavaee5"><a name="cjavaee5"><!-- --></a>
-
-
-<h1 class="id_title">Java EE 5 support for annotations</h1>
-
-
-
-<div><p class="id_shortdesc">The goal of Java™ EE 5 platform development is to minimize
-the number of artifacts that you have to create and maintain, thereby simplifying
-the development process. Java EE 5 supports the injection of annotations
-into your source code, so that you can embed resources, dependencies, services,
-and life-cycle notifications in your source code, without having to maintain
-these artifacts elsewhere.</p>
-
-<p>An annotation is a modifier or Metadata tag that provides additional data
-to Java classes,
-interfaces, constructors, methods, fields, parameters, and local variables.
-Annotations replace boilerplate code, common code that is required by certain
-applications. For example, an annotation can replace the paired interface
-and implementation required for a Web service. Annotations can also replace
-additional files that programs require, which are maintained separately. By
-using an annotation, this separate file is no longer required. For example,
-annotations can replace the need for a separately maintained deployment descriptor
-for JavaBeans™. </p>
-
-<div class="p">Annotations<ul>
-<li>Replace descriptors for most purposes</li>
-
-<li>Remove the need for marker interfaces (like java.rmi.Remote)</li>
-
-<li>Allow application settings to be visible in the component they affect</li>
-
-</ul>
-</div>
-
-<div class="p">Java EE 5 provides annotations for the following tasks, among others:<ul>
-<li>Developing Enterprise JavaBean applications</li>
-
-<li>Defining and using Web services</li>
-
-<li>Mapping Java technology classes to XML</li>
-
-<li>Mapping Java technology classes to databases</li>
-
-<li>Mapping methods to operations</li>
-
-<li>Specifying external dependencies</li>
-
-<li>Specirying deployment information, including security attributes</li>
-
-</ul>
-</div>
-
-<div class="p">Java EE
-5 defines a number of annotations that can be injected into your source code.
-To declare an annotation, you simply precede the keyword with an "at" sign
-(@). <pre>
-package com.ibm.counter;
-
-import javax.ejb.Stateless;
-
-@Stateless
-
-public class CounterBean {
-
-}</pre>
-</div>
-
-<p>For more information about the categories of annotations that Java EE
-5 supports, see <a href="ctypesofanno.html">Types of annotations</a>.</p>
-
-</div>
-
-<div>
-<ul class="ullinks">
-<li class="ulchildlink"><strong><a href="../topics/tdefiningannotations.html">Defining and using annotations</a></strong><br />
-You can use the @Interface annotation to define your own annotation definition.</li>
-</ul>
-
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/cjavaee5.html" title="The Java EE 5 programming model simplifies the process of creating Java applications.">Developing Java EE 5 Applications</a></div>
-</div>
-</div>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/cfacets.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/cfacets.dita
deleted file mode 100644
index 11b0578..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cfacets.dita
+++ /dev/null
@@ -1,40 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<concept id="cfacets" xml:lang="en-us">
-<title outputclass="id_title">Project facets</title>
-<shortdesc outputclass="id_shortdesc">Facets define characteristics and requirements
-for Java EE projects and are used as part of the runtime configuration. </shortdesc>
-<prolog><metadata>
-<keywords><indexterm>Java EE<indexterm>project facets</indexterm></indexterm>
-<indexterm>JavaServer Faces (JSF)<indexterm>project facets</indexterm></indexterm>
-<indexterm>projects<indexterm>facets<indexterm>overview</indexterm></indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody outputclass="id_conbody">
-<p outputclass="anchor_topictop"></p>
-<p id="aboutfacet">When you add a facet to a project, that project is configured
-to perform a certain task, fulfill certain requirements, or have certain characteristics.
-For example, the EAR facet sets up a project to function as an enterprise
-application by adding a deployment descriptor and setting up the project's
-classpath.</p>
-<p>You can add facets only to Java EE projects and other types of projects
-that are based on J2EE projects, such as enterprise application projects,
-dynamic Web projects, and EJB projects. You cannot add facets to a <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> project
-or plug-in project, for example. Typically, a facet-enabled project has at
-least one facet when it is created, allowing you to add more facets if necessary.
-For example, a new EJB project has the EJB Module facet. You can then add
-other facets to this project like the EJBDoclet (XDoclet) facet. To add a
-facet to a project, see <xref href="taddingfacet.dita"></xref>.</p>
-<p>Some facets require other facets as prerequisites. Other facets cannot
-be in the same project together. For example, you cannot add the Dynamic Web
-Module facet to an EJB project because the EJB project already has the EJB
-Module facet. Some facets can be removed from a project and others cannot.</p>
-<p>Facets also have version numbers. You can change the version numbers of
-facets as long as you stay within the requirements for the facets. To change
-the version number of a facet, see <xref href="tchangefacet.dita"></xref>.</p>
-<p outputclass="anchor_topicbottom"></p>
-</conbody>
-</concept>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/cfacets.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/cfacets.html
deleted file mode 100644
index ae958e4..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cfacets.html
+++ /dev/null
@@ -1,83 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="concept" name="DC.Type" />
-<meta name="DC.Title" content="Project facets" />
-<meta name="abstract" content="Facets define characteristics and requirements for Java EE projects and are used as part of the runtime configuration." />
-<meta name="description" content="Facets define characteristics and requirements for Java EE projects and are used as part of the runtime configuration." />
-<meta content="Java EE, project facets, JavaServer Faces (JSF), projects, facets, overview" name="DC.subject" />
-<meta content="Java EE, project facets, JavaServer Faces (JSF), projects, facets, overview" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjearproj.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjear.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjappproj.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjrar.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/taddingfacet.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tchangejavalevel.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tchangefacet.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="cfacets" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Project facets</title>
-</head>
-<body id="cfacets"><a name="cfacets"><!-- --></a>
-
-
-<h1 class="id_title">Project facets</h1>
-
-
-
-<div class="id_conbody"><p class="id_shortdesc">Facets define characteristics and requirements
-for Java EE projects and are used as part of the runtime configuration. </p>
-
-<p class="anchor_topictop" />
-
-<p id="cfacets__aboutfacet"><a name="cfacets__aboutfacet"><!-- --></a>When you add a facet to a project, that project is configured
-to perform a certain task, fulfill certain requirements, or have certain characteristics.
-For example, the EAR facet sets up a project to function as an enterprise
-application by adding a deployment descriptor and setting up the project's
-classpath.</p>
-
-<p>You can add facets only to Java EE projects and other types of projects
-that are based on J2EE projects, such as enterprise application projects,
-dynamic Web projects, and EJB projects. You cannot add facets to a Java™ project
-or plug-in project, for example. Typically, a facet-enabled project has at
-least one facet when it is created, allowing you to add more facets if necessary.
-For example, a new EJB project has the EJB Module facet. You can then add
-other facets to this project like the EJBDoclet (XDoclet) facet. To add a
-facet to a project, see <a href="taddingfacet.html" title="This topic explains how to add a facet to an existing project in your workspace.">Adding a facet to a Java EE project</a>.</p>
-
-<p>Some facets require other facets as prerequisites. Other facets cannot
-be in the same project together. For example, you cannot add the Dynamic Web
-Module facet to an EJB project because the EJB project already has the EJB
-Module facet. Some facets can be removed from a project and others cannot.</p>
-
-<p>Facets also have version numbers. You can change the version numbers of
-facets as long as you stay within the requirements for the facets. To change
-the version number of a facet, see <a href="tchangefacet.html" title="You can change the version of a facet in a Java EE project by editing the facets for the project.">Changing the version of a facet</a>.</p>
-
-<p class="anchor_topicbottom" />
-
-</div>
-
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="../topics/cjearproj.html" title="An enterprise application project ties together the resources that are required to deploy a J2EE enterprise application.">Enterprise application projects</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="../topics/tjear.html" title="Using the wizard to create an enterprise application project allows you to package many web applications and modules in a project and deploy these modules as a J2EE enterprise application.">Creating an enterprise application project</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/tjrar.html" title="A connector is a J2EE standard extension mechanism for containers to provide connectivity to enterprise information systems (EISs).">Creating a connector project</a></div>
-<div><a href="../topics/taddingfacet.html" title="This topic explains how to add a facet to an existing project in your workspace.">Adding a facet to a Java EE project</a></div>
-<div><a href="../topics/tchangejavalevel.html" title="You can change the version of Java used in a Java EE project by changing the value of the Java facet.">Changing the Java compiler version for a Java EE project</a></div>
-<div><a href="../topics/tchangefacet.html" title="You can change the version of a facet in a Java EE project by editing the facets for the project.">Changing the version of a facet</a></div>
-</div>
-</div>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjappcliproj.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjappcliproj.dita
deleted file mode 100644
index 92d44a0..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjappcliproj.dita
+++ /dev/null
@@ -1,81 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<concept id="cjappcliproj" xml:lang="en-us">
-<title outputclass="id_title">Application client projects</title>
-<shortdesc outputclass="id_shortdesc">Application client projects contain
-programs that run on networked client systems so the project can benefit from
-a server's tools.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>application client projects<indexterm>overview</indexterm></indexterm>
-<indexterm>Java EE<indexterm>application client projects</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody outputclass="id_conbody">
-<p outputclass="anchor_topictop"></p>
-<p> Application client projects contain the resources needed for application
-client modules. An application client module is used to contain a full-function
-client <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="Java">Java</tm> application (non Web-based) that connects to and
-uses the Java EE 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 Java EE 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 <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="Java">Java</tm> application in a <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> project.</p>
-<p>An application client project enables you to do the following things:</p>
-<ul>
-<li>Develop the <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="Java">Java</tm> classes that implement the client module</li>
-<li>Set the application client deployment descriptor</li>
-<li>Test the application client</li>
-</ul>
-<p>Like <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="Java">Java</tm> projects, application client projects contain the
-resources needed for application clients, including <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> class
-files. When you create a new application client project, the environment is
-set up for <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="Java">Java</tm> development. A <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> builder is associated with the project
-so the <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="Java">Java</tm> source can be incrementally compiled as it is updated.
-The application client project contains information about the type hierarchy
-and <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> elements.
-This information is kept current as changes are made, and the <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> 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 <codeph>application.xml</codeph> 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 <tm
-tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> 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 Java EE (EJB) servers. The point of entry for the application
-client is a <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="Java">Java</tm> main-class, which is simply a <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> class
-that contains a static main method. The class is declared in the manifest
-file of the client module. </p>
-<p>A Java EE application client container provides access to the Java EE 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 <uicontrol>appClientModule</uicontrol>,
-which contains both <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> source code and compiled <codeph>.class</codeph> files,
-along with all the meta-data files in the <uicontrol>META-INF</uicontrol> subfolder.</p>
-<p outputclass="anchor_topicbottom"></p>
-</conbody>
-</concept>
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 9848770..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjappcliproj.html
+++ /dev/null
@@ -1,114 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="concept" name="DC.Type" />
-<meta name="DC.Title" content="Application client projects" />
-<meta name="abstract" content="Application client projects contain programs that run on networked client systems so the project can benefit from a server's tools." />
-<meta name="description" content="Application client projects contain programs that run on networked client systems so the project can benefit from a server's tools." />
-<meta content="application client projects, overview, Java EE" name="DC.subject" />
-<meta content="application client projects, overview, Java EE" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjarch.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjappproj.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjexpapp.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjimpapp.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="cjappcliproj" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Application client projects</title>
-</head>
-<body id="cjappcliproj"><a name="cjappcliproj"><!-- --></a>
-
-
-<h1 class="id_title">Application client projects</h1>
-
-
-
-<div class="id_conbody"><p class="id_shortdesc">Application client projects contain
-programs that run on networked client systems so the project can benefit from
-a server's tools.</p>
-
-<p class="anchor_topictop" />
-
-<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 Java EE 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 Java EE 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 builder 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 Java EE (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 Java EE application client container provides access to the Java EE 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>
-
-<p class="anchor_topicbottom" />
-
-</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 applications.">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.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjarch.dita
deleted file mode 100644
index f715cd4..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjarch.dita
+++ /dev/null
@@ -1,51 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<concept id="cjarch" xml:lang="en-us">
-<title outputclass="id_title">J2EE architecture</title>
-<shortdesc outputclass="id_shortdesc">The <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> 2 Platform, Enterprise Edition (J2EE)
-provides a standard for developing multitier, enterprise applications.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>J2EE<indexterm>architecture</indexterm></indexterm><indexterm>Java
-EE</indexterm></keywords>
-</metadata></prolog>
-<conbody outputclass="id_conbody">
-<p outputclass="anchor_topictop"></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>
-<dl><dlentry outputclass="id_projectfiles_top">
-<dt>Client tier</dt>
-<dd>In the client tier, Web components, such as Servlets and JavaServer Pages
-(JSPs), or standalone <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> applications provide a dynamic interface
-to the middle tier.</dd>
-</dlentry><dlentry>
-<dt>Middle tier</dt>
-<dd>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.</dd>
-</dlentry><dlentry>
-<dt>Enterprise data tier</dt>
-<dd>In the data tier, the enterprise's data is stored and persisted, typically
-in a relational database.</dd>
-</dlentry></dl>
-<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 <xref format="html" href="http://java.sun.com/j2ee/download.html#platformspec"
-scope="external">J2EE 1.4 Specification<desc></desc></xref>.</p>
-<p outputclass="anchor_topicbottom"></p>
-</conbody>
-</concept>
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 c321ffc..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjarch.html
+++ /dev/null
@@ -1,103 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="concept" name="DC.Type" />
-<meta name="DC.Title" content="J2EE architecture" />
-<meta name="abstract" content="The Java 2 Platform, Enterprise Edition (J2EE) provides a standard for developing multitier, enterprise applications." />
-<meta name="description" content="The Java 2 Platform, Enterprise Edition (J2EE) provides a standard for developing multitier, enterprise applications." />
-<meta content="J2EE, architecture, Java EE" name="DC.subject" />
-<meta content="J2EE, architecture, Java EE" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjearproj.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjear.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjimpear.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjexpear.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjappcliproj.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjappproj.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjexpapp.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjimpapp.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="cjarch" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>J2EE architecture</title>
-</head>
-<body id="cjarch"><a name="cjarch"><!-- --></a>
-
-
-<h1 class="id_title">J2EE architecture</h1>
-
-
-
-<div class="id_conbody"><p class="id_shortdesc">The Java™ 2 Platform, Enterprise Edition (J2EE)
-provides a standard for developing multitier, enterprise applications.</p>
-
-<p class="anchor_topictop" />
-
-<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>
-
-<dl>
-<dt class="dlterm">Client tier</dt>
-
-<dd>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.</dd>
-
-
-<dt class="dlterm">Middle tier</dt>
-
-<dd>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.</dd>
-
-
-<dt class="dlterm">Enterprise data tier</dt>
-
-<dd>In the data tier, the enterprise's data is stored and persisted, typically
-in a relational database.</dd>
-
-</dl>
-
-<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" title="">J2EE 1.4 Specification</a>.</p>
-
-<p class="anchor_topicbottom" />
-
-</div>
-
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="../topics/cjearproj.html" title="An enterprise application project ties together the resources that are required to deploy a J2EE enterprise application.">Enterprise application projects</a></div>
-<div><a href="../topics/cjappcliproj.html" title="Application client projects contain programs that run on networked client systems so the project can benefit from a server's tools.">Application client projects</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="../topics/tjear.html" title="Using the wizard to create an enterprise application project allows you to package many web applications and modules in a project and deploy these modules as a J2EE enterprise application.">Creating an enterprise application project</a></div>
-<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/cjavaee5.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjavaee5.dita
deleted file mode 100644
index 1e5e146..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjavaee5.dita
+++ /dev/null
@@ -1,40 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<concept id="cjavaee5" xml:lang="en-us">
-<title outputclass="id_title">Developing <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> EE 5 Applications</title>
-<shortdesc outputclass="id_shortdesc">The <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> EE 5 programming model simplifies the
-process of creating <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> applications.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>Java Enterprise Edition 5<indexterm>Overview</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody outputclass="id_conbody">
-<p outputclass="anchor_topictop"></p>
-<p id="aboutfacet">In the Java EE 5 specifications, programming requirements
-have been streamlined, and XML deployment descriptors are optional. Instead,
-you can specify many details of assembly and deployment with Java annotations.
-Java EE 5 will provide default values in many situations so explicitly specification
-of these values are not required.</p>
-<p>Code validation, content assistance, Quick Fixes, and refactoring simplify
-working with your code. Code validators check your projects for errors. When
-an error is found, you can double-click on it in the Problems view in the
-product workbench to go to the error location. For some error types, you can
-use a Quick Fix to correct the error automatically. For both <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> source
-and <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> annotations,
-you can rely on content assistance to simplify your programming task. When
-you refactor source code, the tools automatically update the associated metadata.</p>
-<p>For additional information on <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> EE 5.0, see the official specification: <xref
-href="http://jcp.org/en/jsr/detail?id=244" scope="external">JSR 244: <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> Platform,
-Enterprise Edition 5 (<tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> EE 5) Specification</xref></p>
-<p outputclass="anchor_topicbottom"></p>
-</conbody>
-</concept>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjavaee5.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjavaee5.html
deleted file mode 100644
index d70c2c6..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjavaee5.html
+++ /dev/null
@@ -1,72 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="concept" name="DC.Type" />
-<meta name="DC.Title" content="Developing Java EE 5 Applications" />
-<meta name="abstract" content="The Java EE 5 programming model simplifies the process of creating Java applications." />
-<meta name="description" content="The Java EE 5 programming model simplifies the process of creating Java applications." />
-<meta content="Java Enterprise Edition 5, Overview" name="DC.subject" />
-<meta content="Java Enterprise Edition 5, Overview" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/ph-j2eeapp.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjee5overview.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cannotations.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="cjavaee5" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Developing Java EE 5 Applications</title>
-</head>
-<body id="cjavaee5"><a name="cjavaee5"><!-- --></a>
-
-
-<h1 class="id_title">Developing Java EE 5 Applications</h1>
-
-
-
-<div class="id_conbody"><p class="id_shortdesc">The Java™ EE 5 programming model simplifies the
-process of creating Java applications.</p>
-
-<p class="anchor_topictop" />
-
-<p id="cjavaee5__aboutfacet"><a name="cjavaee5__aboutfacet"><!-- --></a>In the Java EE 5 specifications, programming requirements
-have been streamlined, and XML deployment descriptors are optional. Instead,
-you can specify many details of assembly and deployment with Java annotations.
-Java EE 5 will provide default values in many situations so explicitly specification
-of these values are not required.</p>
-
-<p>Code validation, content assistance, Quick Fixes, and refactoring simplify
-working with your code. Code validators check your projects for errors. When
-an error is found, you can double-click on it in the Problems view in the
-product workbench to go to the error location. For some error types, you can
-use a Quick Fix to correct the error automatically. For both Java source
-and Java annotations,
-you can rely on content assistance to simplify your programming task. When
-you refactor source code, the tools automatically update the associated metadata.</p>
-
-<p>For additional information on Java EE 5.0, see the official specification: <a href="http://jcp.org/en/jsr/detail?id=244" target="_blank">JSR 244: Java Platform, Enterprise Edition 5 (Java EE 5) Specification</a></p>
-
-<p class="anchor_topicbottom" />
-
-</div>
-
-<div>
-<ul class="ullinks">
-<li class="ulchildlink"><strong><a href="../topics/cjee5overview.html">Java EE 5: Overview</a></strong><br />
-Using the Java Platform, Enterprise Edition (Java EE) architecture, you can build distributed Web and enterprise applications. This architecture helps you focus on presentation and application issues, rather than on systems issues.</li>
-<li class="ulchildlink"><strong><a href="../topics/cannotations.html">Java EE 5 support for annotations</a></strong><br />
-The goal of Java EE 5 platform development is to minimize the number of artifacts that you have to create and maintain, thereby simplifying the development process. Java EE 5 supports the injection of annotations into your source code, so that you can embed resources, dependencies, services, and life-cycle notifications in your source code, without having to maintain these artifacts elsewhere.</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 Enterprise Edition (Java EE).">Java EE applications</a></div>
-</div>
-</div>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjcircle.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjcircle.dita
deleted file mode 100644
index 3f4ab56..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjcircle.dita
+++ /dev/null
@@ -1,28 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<concept id="cjcircle" xml:lang="en-us">
-<title outputclass="id_title">Cyclical dependencies between Java EE modules</title>
-<shortdesc outputclass="id_shortdesc">A cyclical dependency between two or
-more modules in an enterprise application most commonly occurs when projects
-are imported from outside the Workbench.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>dependencies<indexterm>cycles between modules</indexterm></indexterm>
-<indexterm>Java EE<indexterm>cyclical dependencies between modules</indexterm></indexterm>
-<indexterm>projects<indexterm>cyclical dependencies</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody outputclass="id_conbody">
-<p outputclass="anchor_topictop"></p>
-<p>When a cycle exists between two or more modules in an enterprise application,
-the <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> 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>
-<p outputclass="anchor_topicbottom"></p>
-</conbody>
-</concept>
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 6ba2fe2..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjcircle.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 content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="concept" name="DC.Type" />
-<meta name="DC.Title" content="Cyclical dependencies between Java EE modules" />
-<meta name="abstract" content="A cyclical dependency between two or more modules in an enterprise application most commonly occurs when projects are imported from outside the Workbench." />
-<meta name="description" content="A cyclical dependency between two or more modules in an enterprise application most commonly occurs when projects are imported from outside the Workbench." />
-<meta content="dependencies, cycles between modules, Java EE, cyclical dependencies between modules, projects, cyclical dependencies" name="DC.subject" />
-<meta content="dependencies, cycles between modules, Java EE, cyclical dependencies between modules, projects, cyclical dependencies" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjimpear.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjcircleb.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="cjcircle" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Cyclical dependencies between Java EE modules</title>
-</head>
-<body id="cjcircle"><a name="cjcircle"><!-- --></a>
-
-
-<h1 class="id_title">Cyclical dependencies between Java EE modules</h1>
-
-
-
-<div class="id_conbody"><p class="id_shortdesc">A cyclical dependency between two or
-more modules in an enterprise application most commonly occurs when projects
-are imported from outside the Workbench.</p>
-
-<p class="anchor_topictop" />
-
-<p>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>
-
-<p class="anchor_topicbottom" />
-
-</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.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjearproj.dita
deleted file mode 100644
index aca0056..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjearproj.dita
+++ /dev/null
@@ -1,71 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<concept id="cjearproj" xml:lang="en-us">
-<title outputclass="id_title">Enterprise application projects</title>
-<shortdesc outputclass="id_shortdesc">An enterprise application project ties
-together the resources that are required to deploy a J2EE enterprise application.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>enterprise applications<indexterm>projects<indexterm>artifacts</indexterm></indexterm></indexterm>
-<indexterm>J2EE<indexterm>enterprise application projects<indexterm>overview</indexterm></indexterm></indexterm>
-<indexterm>projects<indexterm>enterprise applications</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody outputclass="id_conbody">
-<p outputclass="anchor_topictop"></p>
-<p>An enterprise application project contains a set of references to other
-J2EE modules and <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="Java">Java</tm> projects that are combined to compose an EAR file.
-These projects can be Web modules, EJB modules, application client modules,
-connector modules, general utility <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> 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 utility JAR files. The utility JAR files defined
-for an enterprise application project can be actual JAR files in the project,
-or you can include utility <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> 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 tie together 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 <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> projects, and they are not compiled
-by the <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="Java">Java</tm> builder.</p>
-<p>When you create an enterprise application project using the workbench,
-the following key files are automatically created:<dl><dlentry outputclass="id_projectfiles_top">
-<dt>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. This file is created in the <uicontrol>META-INF</uicontrol> folder.</dd>
-</dlentry><dlentry>
-<dt>.settings/.component</dt>
-<dd>This file matches the location of each module's source code to the location
-of the module at deployment. For each module included for deployment with
-the EAR file, the .component file lists its source path and deployment path.
-This file is created in the <uicontrol>.settings</uicontrol> folder.</dd>
-</dlentry><dlentry>
-<dt>.settings/org.eclipse.wst.common.project.facet.core.xml</dt>
-<dd>This file lists the facets of the enterprise application project. See <xref
-href="cfacets.dita"></xref>. This file is created in the <uicontrol>.settings</uicontrol> folder.</dd>
-</dlentry><dlentry outputclass="id_projectfiles_bottom">
-<dt>.project</dt>
-<dd>This is a workbench artifact, the standard project description file.</dd>
-</dlentry></dl></p>
-<p outputclass="anchor_topicbottom"></p>
-</conbody>
-</concept>
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 3766138..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjearproj.html
+++ /dev/null
@@ -1,120 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="concept" name="DC.Type" />
-<meta name="DC.Title" content="Enterprise application projects" />
-<meta name="abstract" content="An enterprise application project ties together the resources that are required to deploy a J2EE enterprise application." />
-<meta name="description" content="An enterprise application project ties together the resources that are required to deploy a J2EE enterprise application." />
-<meta content="enterprise applications, projects, artifacts, J2EE, enterprise application projects, overview" name="DC.subject" />
-<meta content="enterprise applications, projects, artifacts, J2EE, enterprise application projects, overview" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjarch.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjear.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjimpear.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjexpear.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjear.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjappproj.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjrar.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cfacets.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="cjearproj" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Enterprise application projects</title>
-</head>
-<body id="cjearproj"><a name="cjearproj"><!-- --></a>
-
-
-<h1 class="id_title">Enterprise application projects</h1>
-
-
-
-<div class="id_conbody"><p class="id_shortdesc">An enterprise application project ties
-together the resources that are required to deploy a J2EE enterprise application.</p>
-
-<p class="anchor_topictop" />
-
-<p>An enterprise application project 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 utility JAR files. 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 tie together 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. This file is created in the <span class="uicontrol">META-INF</span> folder.</dd>
-
-
-<dt class="dlterm">.settings/.component</dt>
-
-<dd>This file matches the location of each module's source code to the location
-of the module at deployment. For each module included for deployment with
-the EAR file, the .component file lists its source path and deployment path.
-This file is created in the <span class="uicontrol">.settings</span> folder.</dd>
-
-
-<dt class="dlterm">.settings/org.eclipse.wst.common.project.facet.core.xml</dt>
-
-<dd>This file lists the facets of the enterprise application project. See <a href="cfacets.html" title="Facets define characteristics and requirements for Java EE projects and are used as part of the runtime configuration. ">Project facets</a>. This file is created in the <span class="uicontrol">.settings</span> folder.</dd>
-
-
-<dt class="dlterm">.project</dt>
-
-<dd>This is a workbench artifact, the standard project description file.</dd>
-
-</dl>
-</div>
-
-<p class="anchor_topicbottom" />
-
-</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 applications.">J2EE architecture</a></div>
-<div><a href="../topics/cfacets.html" title="Facets define characteristics and requirements for Java EE projects and are used as part of the runtime configuration.">Project facets</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="../topics/tjear.html" title="Using the wizard to create an enterprise application project allows you to package many web applications and modules in a project and deploy these modules as a J2EE enterprise application.">Creating an enterprise application project</a></div>
-<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/tjrar.html" title="A connector is a J2EE standard extension mechanism for containers to provide connectivity to enterprise information systems (EISs).">Creating a connector project</a></div>
-</div>
-</div>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjee5overview.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjee5overview.dita
deleted file mode 100644
index 0d62b19..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjee5overview.dita
+++ /dev/null
@@ -1,84 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<concept id="cjavaee5" xml:lang="en-us">
-<title outputclass="id_title"><tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> EE 5: Overview</title>
-<shortdesc outputclass="id_shortdesc">Using the <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> Platform, Enterprise Edition (<tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> EE)
-architecture, you can build distributed Web and enterprise applications. This
-architecture helps you focus on presentation and application issues, rather
-than on systems issues.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>Java EE 5</indexterm><indexterm>Oerview</indexterm></keywords>
-</metadata></prolog>
-<conbody>
-<p>You can use the <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> EE 5 tools and features to create applications
-that are structured around modules with different purposes, such as Web sites
-and Enterprise <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="JavaBeans">JavaBeans</tm> (EJB) applications. When you use EJB
-3.0 components, you can create a distributed, secure application with transactional
-support. When you develop applications that access persistent data, you can
-use the new <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="Java">Java</tm> Persistence API (JPA). This standard simplifies
-the creation and use of persistent entities, as well as adding new features.
-For developing presentation logic, you can use technologies such as JavaServer
-Pages (JSP) or JavaServer Faces (JSF).</p>
-<p>Using the <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="Java">Java</tm> EE 5 Platform Enterprise Edition (Java EE) , you
-can develop applications more quickly and conveniently than in previous versions.
-The <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> EE
-5 platform replaces <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> 2 Enterprise Edition (J2EE), version
-1.4. The product tools support for both versions. Java EE 5 significantly
-enhances ease of use providing<ul>
-<li>Reduced development time</li>
-<li>Reduced application complexity</li>
-<li>Improved application performance</li>
-</ul></p>
-<p>Java EE 5 provides a simplified programming model, including the following
-tools:<ul>
-<li>Inline configuration with annotations, making deployment descriptors now
-optional</li>
-<li>Dependency injection, hiding resource creation and lookup from application
-code</li>
-<li>Java persistence API (JPA) allows data management without explicit SQL
-or JDBC</li>
-<li>Use of plain old Java objects (POJOs) for Enterprise JavaBeans and Web
-services</li>
-</ul></p>
-<p>Java EE 5 provides simplified packaging rules for enterprise applications:<ul>
-<li>Web applications us .WAR files</li>
-<li>Resource adapters use .RAR files</li>
-<li>Enterprise applications use .EAR files</li>
-<li>The <codeph>lib</codeph> directory contains shared .JAR files</li>
-<li>A .JAR file with <codeph>Main-Class</codeph> implies an application client</li>
-<li>A .JAR file with @Stateless annotation implies an EJB application</li>
-<li>Many simple applications no longer require deployment descriptors, including<ul>
-<li>EJB applications (.JAR files)</li>
-<li>Web applications that use JSP technology only</li>
-<li>Application clients</li>
-<li>Enterprise applications (.EAR files)</li>
-</ul></li>
-</ul></p>
-<p>Java EE 5 provides simplified resource access using dependency injection:<ul>
-<li>In the Dependency Injection pattern, an external entity automatically
-supplies an object's dependencies.<ul>
-<li>The object need not request these resources explicitly</li>
-</ul></li>
-<li>In Java EE 5, dependency injection can be applied to all resources that
-a component needs<ul>
-<li>Creation and lookup of resources are hidden from application code</li>
-</ul></li>
-<li>Dependency injection can be applied throughout Java EE 5 technology:<ul>
-<li>EJB containers</li>
-<li>Web containers</li>
-<li>Clients</li>
-<li>Web services</li>
-</ul></li>
-</ul></p>
-</conbody>
-</concept>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjee5overview.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjee5overview.html
deleted file mode 100644
index 3cb28f3..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjee5overview.html
+++ /dev/null
@@ -1,144 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="concept" name="DC.Type" />
-<meta name="DC.Title" content="Java EE 5: Overview" />
-<meta name="abstract" content="Using the Java Platform, Enterprise Edition (Java EE) architecture, you can build distributed Web and enterprise applications. This architecture helps you focus on presentation and application issues, rather than on systems issues." />
-<meta name="description" content="Using the Java Platform, Enterprise Edition (Java EE) architecture, you can build distributed Web and enterprise applications. This architecture helps you focus on presentation and application issues, rather than on systems issues." />
-<meta content="Java EE 5, Oerview" name="DC.subject" />
-<meta content="Java EE 5, Oerview" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjavaee5.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="cjavaee5" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Java EE 5: Overview</title>
-</head>
-<body id="cjavaee5"><a name="cjavaee5"><!-- --></a>
-
-
-<h1 class="id_title">Java EE 5: Overview</h1>
-
-
-
-<div><p class="id_shortdesc">Using the Java™ Platform, Enterprise Edition (Java EE)
-architecture, you can build distributed Web and enterprise applications. This
-architecture helps you focus on presentation and application issues, rather
-than on systems issues.</p>
-
-<p>You can use the Java EE 5 tools and features to create applications
-that are structured around modules with different purposes, such as Web sites
-and Enterprise JavaBeans™ (EJB) applications. When you use EJB
-3.0 components, you can create a distributed, secure application with transactional
-support. When you develop applications that access persistent data, you can
-use the new Java Persistence API (JPA). This standard simplifies
-the creation and use of persistent entities, as well as adding new features.
-For developing presentation logic, you can use technologies such as JavaServer
-Pages (JSP) or JavaServer Faces (JSF).</p>
-
-<div class="p">Using the Java EE 5 Platform Enterprise Edition (Java EE) , you
-can develop applications more quickly and conveniently than in previous versions.
-The Java EE
-5 platform replaces Java 2 Enterprise Edition (J2EE), version
-1.4. The product tools support for both versions. Java EE 5 significantly
-enhances ease of use providing<ul>
-<li>Reduced development time</li>
-
-<li>Reduced application complexity</li>
-
-<li>Improved application performance</li>
-
-</ul>
-</div>
-
-<div class="p">Java EE 5 provides a simplified programming model, including the following
-tools:<ul>
-<li>Inline configuration with annotations, making deployment descriptors now
-optional</li>
-
-<li>Dependency injection, hiding resource creation and lookup from application
-code</li>
-
-<li>Java persistence API (JPA) allows data management without explicit SQL
-or JDBC</li>
-
-<li>Use of plain old Java objects (POJOs) for Enterprise JavaBeans and Web
-services</li>
-
-</ul>
-</div>
-
-<div class="p">Java EE 5 provides simplified packaging rules for enterprise applications:<ul>
-<li>Web applications us .WAR files</li>
-
-<li>Resource adapters use .RAR files</li>
-
-<li>Enterprise applications use .EAR files</li>
-
-<li>The <samp class="codeph">lib</samp> directory contains shared .JAR files</li>
-
-<li>A .JAR file with <samp class="codeph">Main-Class</samp> implies an application client</li>
-
-<li>A .JAR file with @Stateless annotation implies an EJB application</li>
-
-<li>Many simple applications no longer require deployment descriptors, including<ul>
-<li>EJB applications (.JAR files)</li>
-
-<li>Web applications that use JSP technology only</li>
-
-<li>Application clients</li>
-
-<li>Enterprise applications (.EAR files)</li>
-
-</ul>
-</li>
-
-</ul>
-</div>
-
-<div class="p">Java EE 5 provides simplified resource access using dependency injection:<ul>
-<li>In the Dependency Injection pattern, an external entity automatically
-supplies an object's dependencies.<ul>
-<li>The object need not request these resources explicitly</li>
-
-</ul>
-</li>
-
-<li>In Java EE 5, dependency injection can be applied to all resources that
-a component needs<ul>
-<li>Creation and lookup of resources are hidden from application code</li>
-
-</ul>
-</li>
-
-<li>Dependency injection can be applied throughout Java EE 5 technology:<ul>
-<li>EJB containers</li>
-
-<li>Web containers</li>
-
-<li>Clients</li>
-
-<li>Web services</li>
-
-</ul>
-</li>
-
-</ul>
-</div>
-
-</div>
-
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/cjavaee5.html" title="The Java EE 5 programming model simplifies the process of creating Java applications.">Developing Java EE 5 Applications</a></div>
-</div>
-</div>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjpers.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjpers.dita
deleted file mode 100644
index 408bd00..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjpers.dita
+++ /dev/null
@@ -1,92 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<concept id="cjpers" xml:lang="en-us">
-<title outputclass="id_title"><tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> EE perspective</title>
-<shortdesc outputclass="id_shortdesc">The <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> EE 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.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>Java EE<indexterm>workbench perspectives</indexterm></indexterm>
-<indexterm>enterprise applications<indexterm>Java EE perspective</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody outputclass="id_conbody">
-<p outputclass="anchor_topictop"></p>
-<p>You can rearrange the location, tiling, and size of the views within the
-perspective. You can also add other views to the <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> EE perspective by clicking <menucascade>
-<uicontrol>Window</uicontrol><uicontrol>Show View</uicontrol></menucascade> 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 <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> EE perspective includes the following
-workbench views:</p>
-<dl><dlentry outputclass="id_perspectiveviews_top">
-<dt><uicontrol>Project Explorer</uicontrol></dt>
-<dd>The Project Explorer view provides an integrated view of your projects
-and their artifacts related to J2EE development. You can show or hide your
-projects based on working sets. This view displays navigable models of J2EE
-deployment descriptors, <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> 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>
-</dlentry><dlentry>
-<dt><uicontrol> Outline</uicontrol></dt>
-<dd>The Outline view in the <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> EE 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 <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> editor,
-the Outline view shows the outline for the <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> class.</dd>
-</dlentry><dlentry>
-<dt><uicontrol>Tasks</uicontrol></dt>
-<dd>The Tasks view lists the to-do items that you have entered.</dd>
-</dlentry><dlentry>
-<dt><uicontrol>Problems</uicontrol></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>
-</dlentry><dlentry>
-<dt><uicontrol>Properties</uicontrol></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.</dd>
-</dlentry><dlentry>
-<dt><uicontrol>Servers</uicontrol></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>
-</dlentry><dlentry outputclass="id_perspectiveviews_bottom">
-<dt><uicontrol>Snippets</uicontrol></dt>
-<dd>The Snippets view provides categorized pieces of code that you can insert
-into appropriate places in your source code.</dd>
-</dlentry><dlentry>
-<dt><uicontrol>Data Source Explorer</uicontrol></dt>
-<dd>The Data Source Explorer provides a list of configured connection profiles.
-If categories are enabled, you can see the list grouped into categories. Use
-the Data Source Explorer to connect to, navigate, and interact with resources
-associated with the selected connection profile. It also provides import and
-export capabilities to share connection profile definitions with other Eclipse
-Workbenches. </dd>
-</dlentry><dlentry>
-<dt><uicontrol>Status bar</uicontrol></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>
-</dlentry></dl>
-<p outputclass="anchor_topicbottom"></p>
-</conbody>
-</concept>
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 f44fe0c..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjpers.html
+++ /dev/null
@@ -1,133 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="concept" name="DC.Type" />
-<meta name="DC.Title" content="Java EE perspective" />
-<meta name="abstract" content="The Java EE 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." />
-<meta name="description" content="The Java EE 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." />
-<meta content="Java EE, workbench perspectives, enterprise applications, Java EE perspective" name="DC.subject" />
-<meta content="Java EE, workbench perspectives, enterprise applications, Java EE perspective" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.platform.doc.user/concepts/cworkset.htm" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="cjpers" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Java EE perspective</title>
-</head>
-<body id="cjpers"><a name="cjpers"><!-- --></a>
-
-
-<h1 class="id_title">Java EE perspective</h1>
-
-
-
-<div class="id_conbody"><p class="id_shortdesc">The Java™ EE 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 class="anchor_topictop" />
-
-<p>You can rearrange the location, tiling, and size of the views within the
-perspective. You can also add other views to the Java EE perspective by clicking <span class="menucascade">
-<span class="uicontrol">Window</span> > <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 Java EE perspective includes the following
-workbench views:</p>
-
-<dl>
-<dt class="dlterm"><span class="uicontrol">Project Explorer</span></dt>
-
-<dd>The Project Explorer view provides an integrated view of your projects
-and their artifacts related to J2EE development. You can show or hide your
-projects based on working sets. This view 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 Java EE 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.</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>
-
-
-<dt class="dlterm"><span class="uicontrol">Data Source Explorer</span></dt>
-
-<dd>The Data Source Explorer provides a list of configured connection profiles.
-If categories are enabled, you can see the list grouped into categories. Use
-the Data Source Explorer to connect to, navigate, and interact with resources
-associated with the selected connection profile. It also provides import and
-export capabilities to share connection profile definitions with other Eclipse
-Workbenches. </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>
-
-</dl>
-
-<p class="anchor_topicbottom" />
-
-</div>
-
-<div><div class="relinfo"><strong>Related information</strong><br />
-<div><a href="../../org.eclipse.platform.doc.user/concepts/cworkset.htm">Working sets</a></div>
-</div>
-</div>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjview.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjview.dita
deleted file mode 100644
index 8ca49e1..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjview.dita
+++ /dev/null
@@ -1,37 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<concept id="cjview" xml:lang="en-us">
-<title outputclass="id_title">Project Explorer view in the <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> EE
-perspective</title>
-<shortdesc outputclass="id_shortdesc">While developing J2EE applications in
-the <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> EE
-perspective, the Project Explorer view is your main view of your J2EE projects
-and resources.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>views<indexterm>Project Explorer</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody outputclass="id_conbody">
-<p outputclass="anchor_topictop"></p>
-<p>The Project Explorer view provides an integrated view of all project resources,
-including models of J2EE deployment descriptors, <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> artifacts, resources, Web services,
-databases, and dynamic Web project artifacts.</p>
-<p>You should use this view to work with your J2EE deployment descriptors
-and their content. You can view an enterprise application project and see
-all of the modules associated with it. </p>
-<p>You can also filter what you see in the Project Explorer view to hide projects,
-folders, or files that you don't want to see. To enable or disable filters,
-select <uicontrol>Customize View...</uicontrol> from the drop-down menu at
-the top right corner of the view. For more information, see <xref href="cjviewfilters.dita">Filters
-in the Project Explorer view</xref>.</p>
-<p>Alternately, you can filter what you see by showing or hiding working sets,
-groups of related resources or projects. For more information, see <xref format="html"
-href="../../org.eclipse.platform.doc.user/concepts/cworkset.htm" scope="peer">Working
-Sets<desc></desc></xref>.</p>
-<p outputclass="anchor_topicbottom"></p>
-</conbody>
-</concept>
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 5938c0d..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjview.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 content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="concept" name="DC.Type" />
-<meta name="DC.Title" content="Project Explorer view in the Java EE perspective" />
-<meta name="abstract" content="While developing J2EE applications in the Java EE perspective, the Project Explorer view is your main view of your J2EE projects and resources." />
-<meta name="description" content="While developing J2EE applications in the Java EE perspective, the Project Explorer view is your main view of your J2EE projects and resources." />
-<meta content="views, Project Explorer" name="DC.subject" />
-<meta content="views, Project Explorer" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjviewfilters.html" />
-<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.platform.doc.user/concepts/cworkset.htm" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="cjview" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Project Explorer view in the Java EE
-perspective</title>
-</head>
-<body id="cjview"><a name="cjview"><!-- --></a>
-
-
-<h1 class="id_title">Project Explorer view in the Java EE
-perspective</h1>
-
-
-
-<div class="id_conbody"><p class="id_shortdesc">While developing J2EE applications in
-the Java™ EE
-perspective, the Project Explorer view is your main view of your J2EE projects
-and resources.</p>
-
-<p class="anchor_topictop" />
-
-<p>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>
-
-<p>You should use this view to work with your J2EE deployment descriptors
-and their content. You can view an enterprise application project and see
-all of the modules associated with it. </p>
-
-<p>You can also filter what you see in the Project Explorer view to hide projects,
-folders, or files that you don't want to see. To enable or disable filters,
-select <span class="uicontrol">Customize View...</span> from the drop-down menu at
-the top right corner of the view. For more information, see <a href="cjviewfilters.html">Filters in the Project Explorer view</a>.</p>
-
-<p>Alternately, you can filter what you see by showing or hiding working sets,
-groups of related resources or projects. For more information, see <a href="../../org.eclipse.platform.doc.user/concepts/cworkset.htm" title="">Working Sets</a>.</p>
-
-<p class="anchor_topicbottom" />
-
-</div>
-
-<div><div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="../topics/tjviewfilters.html" title="You can filter the Project Explorer view to hide projects, folders, or files that you do not want to see.">Filtering in the Project Explorer view</a></div>
-</div>
-<div class="relinfo"><strong>Related information</strong><br />
-<div><a href="../../org.eclipse.platform.doc.user/concepts/cworkset.htm">Working sets</a></div>
-</div>
-</div>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjviewfilters.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjviewfilters.dita
deleted file mode 100644
index be377a1..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjviewfilters.dita
+++ /dev/null
@@ -1,33 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<concept id="cjviewfilters" xml:lang="en-us">
-<title outputclass="id_title">Filters in the Project Explorer view</title>
-<shortdesc outputclass="id_shortdesc">You can filter the Project Explorer
-view to hide projects, folders, or files that you do not want to see.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>filters<indexterm>Project Explorer view</indexterm></indexterm>
-<indexterm>views<indexterm>Project Explorer filters</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody outputclass="id_conbody">
-<p outputclass="anchor_topictop"></p>
-<p>To enable or disable filters, complete the following steps:<ol>
-<li>Open the Select Common Navigator Filters window by selecting <uicontrol>Customize
-View...</uicontrol> from the drop-down menu at the top right corner of the
-view.</li>
-<li>On the <uicontrol>Filters</uicontrol> tab, select the check boxes next
-to the filters you want to enable. For example, when the <uicontrol>Closed
- projects</uicontrol> filter is enabled, closed projects are not shown in
-the Project Explorer view. Other filters can hide empty packages, non-java
-files, and files with names ending in ".class".</li>
-<li>On the Available Extensions and Filters tab, the filters work in the opposite
-way: the selected check boxes describe the projects, folders, and files that
-are shown in the Project Explorer view. For example, if you clear the checkbox
-next to <uicontrol>J2EE Deployment Descriptors</uicontrol>, the deployment
-descriptors are hidden from each project in the view.</li>
-</ol></p>
-<p outputclass="anchor_topicbottom"></p>
-</conbody>
-</concept>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjviewfilters.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjviewfilters.html
deleted file mode 100644
index 621bba3..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjviewfilters.html
+++ /dev/null
@@ -1,60 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="concept" name="DC.Type" />
-<meta name="DC.Title" content="Filters in the Project Explorer view" />
-<meta name="abstract" content="You can filter the Project Explorer view to hide projects, folders, or files that you do not want to see." />
-<meta name="description" content="You can filter the Project Explorer view to hide projects, folders, or files that you do not want to see." />
-<meta content="filters, Project Explorer view, views, Project Explorer filters" name="DC.subject" />
-<meta content="filters, Project Explorer view, views, Project Explorer filters" name="keywords" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="cjviewfilters" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Filters in the Project Explorer view</title>
-</head>
-<body id="cjviewfilters"><a name="cjviewfilters"><!-- --></a>
-
-
-<h1 class="id_title">Filters in the Project Explorer view</h1>
-
-
-
-<div class="id_conbody"><p class="id_shortdesc">You can filter the Project Explorer
-view to hide projects, folders, or files that you do not want to see.</p>
-
-<p class="anchor_topictop" />
-
-<div class="p">To enable or disable filters, complete the following steps:<ol>
-<li>Open the Select Common Navigator Filters window by selecting <span class="uicontrol">Customize
-View...</span> from the drop-down menu at the top right corner of the
-view.</li>
-
-<li>On the <span class="uicontrol">Filters</span> tab, select the check boxes next
-to the filters you want to enable. For example, when the <span class="uicontrol">Closed
- projects</span> filter is enabled, closed projects are not shown in
-the Project Explorer view. Other filters can hide empty packages, non-java
-files, and files with names ending in ".class".</li>
-
-<li>On the Available Extensions and Filters tab, the filters work in the opposite
-way: the selected check boxes describe the projects, folders, and files that
-are shown in the Project Explorer view. For example, if you clear the checkbox
-next to <span class="uicontrol">J2EE Deployment Descriptors</span>, the deployment
-descriptors are hidden from each project in the view.</li>
-
-</ol>
-</div>
-
-<p class="anchor_topicbottom" />
-
-</div>
-
-
-</body>
-</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/ctypesofanno.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/ctypesofanno.dita
deleted file mode 100644
index f1288bf..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/ctypesofanno.dita
+++ /dev/null
@@ -1,35 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<concept id="cjavaee5" xml:lang="en-us">
-<title outputclass="id_title">Types of annotations</title>
-<shortdesc outputclass="id_shortdesc"><tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> EE 5 defines a number of types or groups
-of annotations, defined in a number of <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> Specification Requests (JSRs).</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>Java EE 5<indexterm>annotations<indexterm>types</indexterm></indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody outputclass="id_conbody">
-<p outputclass="anchor_topictop"></p>
-<p><tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> EE
-5 defines the following types of annotations:</p>
-<ul>
-<li>JSR 250: Common annotations<b></b></li>
-<li>JSR-220: EJB 3.0 annotations</li>
-<li>JSR-181: Web Services annotations</li>
-<li>JSR-220: Java Persistence API annotations</li>
-<li>JSR-222: JaxB annotations</li>
-<li>JSR-224: WS2 annotations</li>
-</ul>
-<p>For additional information on <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> EE 5.0, see the official specification: <xref
-href="http://jcp.org/en/jsr/detail?id=244" scope="external">JSR 244: <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> Platform,
-Enterprise Edition 5 (<tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> EE 5) Specification</xref></p>
-<p outputclass="anchor_topicbottom"></p>
-</conbody>
-</concept>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/ctypesofanno.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/ctypesofanno.html
deleted file mode 100644
index 5bc623b..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/ctypesofanno.html
+++ /dev/null
@@ -1,66 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="concept" name="DC.Type" />
-<meta name="DC.Title" content="Types of annotations" />
-<meta name="abstract" content="Java EE 5 defines a number of types or groups of annotations, defined in a number of Java Specification Requests (JSRs)." />
-<meta name="description" content="Java EE 5 defines a number of types or groups of annotations, defined in a number of Java Specification Requests (JSRs)." />
-<meta content="Java EE 5, annotations, types" name="DC.subject" />
-<meta content="Java EE 5, annotations, types" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tdefiningannotations.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="cjavaee5" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Types of annotations</title>
-</head>
-<body id="cjavaee5"><a name="cjavaee5"><!-- --></a>
-
-
-<h1 class="id_title">Types of annotations</h1>
-
-
-
-<div class="id_conbody"><p class="id_shortdesc">Java™ EE 5 defines a number of types or groups
-of annotations, defined in a number of Java Specification Requests (JSRs).</p>
-
-<p class="anchor_topictop" />
-
-<p>Java EE
-5 defines the following types of annotations:</p>
-
-<ul>
-<li>JSR 250: Common annotations<strong /></li>
-
-<li>JSR-220: EJB 3.0 annotations</li>
-
-<li>JSR-181: Web Services annotations</li>
-
-<li>JSR-220: Java Persistence API annotations</li>
-
-<li>JSR-222: JaxB annotations</li>
-
-<li>JSR-224: WS2 annotations</li>
-
-</ul>
-
-<p>For additional information on Java EE 5.0, see the official specification: <a href="http://jcp.org/en/jsr/detail?id=244" target="_blank">JSR 244: Java Platform, Enterprise Edition 5 (Java EE 5) Specification</a></p>
-
-<p class="anchor_topicbottom" />
-
-</div>
-
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/tdefiningannotations.html" title="You can use the @Interface annotation to define your own annotation definition.">Defining and using annotations</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.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-importexport.dita
deleted file mode 100644
index 833c39f..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-importexport.dita
+++ /dev/null
@@ -1,15 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN"
- "topic.dtd">
-<topic id="ph-importexport" xml:lang="en-us">
-<title outputclass="id_title">Importing and exporting projects and files</title>
-<shortdesc outputclass="id_shortdesc">These topics cover how to import files
-and projects into the workbench and export files and projects to disk.</shortdesc>
-<prolog><metadata>
-<keywords></keywords>
-</metadata></prolog>
-<body outputclass="id_body">
-<p outputclass="anchor_topictop"></p>
-<p outputclass="anchor_topicbottom"></p>
-</body>
-</topic>
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 d050edb..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-importexport.html
+++ /dev/null
@@ -1,83 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="topic" name="DC.Type" />
-<meta name="DC.Title" content="Importing and exporting projects and files" />
-<meta name="abstract" content="These topics cover how to import files and projects into the workbench and export files and projects to disk." />
-<meta name="description" content="These topics cover how to import files and projects into the workbench and export files and projects to disk." />
-<meta scheme="URI" name="DC.Relation" content="../topics/ph-projects.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjexpapp.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjexpear.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjexprar.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjimpear.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjimpapp.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjimprar.html" />
-<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.wst.webtools.doc.user/topics/twimpwar.html" />
-<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.wst.webtools.doc.user/topics/twcrewar.html" />
-<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ejb.doc.user/topics/teimp.html" />
-<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ejb.doc.user/topics/teexp.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjcircle.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjcircleb.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="ph-importexport" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Importing and exporting projects and files</title>
-</head>
-<body id="ph-importexport"><a name="ph-importexport"><!-- --></a>
-
-
-<h1 class="id_title">Importing and exporting projects and files</h1>
-
-
-
-<div class="id_body"><p class="id_shortdesc">These topics cover how to import files
-and projects into the workbench and export files and projects to disk.</p>
-
-<p class="anchor_topictop" />
-
-<p class="anchor_topicbottom" />
-
-</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="../../org.eclipse.wst.webtools.doc.user/topics/twimpwar.html">Importing Web archive (WAR) files</a></strong><br />
-</li>
-<li class="ulchildlink"><strong><a href="../../org.eclipse.wst.webtools.doc.user/topics/twcrewar.html">Exporting Web Archive (WAR) files</a></strong><br />
-</li>
-<li class="ulchildlink"><strong><a href="../../org.eclipse.jst.ejb.doc.user/topics/teimp.html">Importing EJB JAR files</a></strong><br />
-</li>
-<li class="ulchildlink"><strong><a href="../../org.eclipse.jst.ejb.doc.user/topics/teexp.html">Exporting EJB projects to EJB JAR files</a></strong><br />
-</li>
-<li class="ulchildlink"><strong><a href="../topics/cjcircle.html">Cyclical dependencies between Java EE modules</a></strong><br />
-A cyclical dependency between two or more modules in an enterprise application most commonly occurs when projects are imported from outside the Workbench.</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.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-j2eeapp.dita
deleted file mode 100644
index 5f6b4eb..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-j2eeapp.dita
+++ /dev/null
@@ -1,17 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN"
- "topic.dtd">
-<topic id="ph-j2eeapp" xml:lang="en-us">
-<title outputclass="id_title">Java EE applications</title>
-<shortdesc outputclass="id_shortdesc">These topics deal with the <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> Enterprise
-Edition (Java EE).</shortdesc>
-<prolog><metadata>
-<keywords></keywords>
-</metadata></prolog>
-<body outputclass="id_body">
-<p outputclass="anchor_topictop"></p>
-<p outputclass="anchor_topicbottom"></p>
-</body>
-</topic>
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 dacf3fa..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-j2eeapp.html
+++ /dev/null
@@ -1,66 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="topic" name="DC.Type" />
-<meta name="DC.Title" content="Java EE applications" />
-<meta name="abstract" content="These topics deal with the Java Enterprise Edition (Java EE)." />
-<meta name="description" content="These topics deal with the Java Enterprise Edition (Java EE)." />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjavaee5.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjarch.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjpers.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjview.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjviewfilters.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/ph-projects.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjval.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/ph-ref.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="ph-j2eeapp" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Java EE applications</title>
-</head>
-<body id="ph-j2eeapp"><a name="ph-j2eeapp"><!-- --></a>
-
-
-<h1 class="id_title">Java EE applications</h1>
-
-
-
-<div class="id_body"><p class="id_shortdesc">These topics deal with the Java™ Enterprise
-Edition (Java EE).</p>
-
-<p class="anchor_topictop" />
-
-<p class="anchor_topicbottom" />
-
-</div>
-
-<div>
-<ul class="ullinks">
-<li class="ulchildlink"><strong><a href="../topics/cjavaee5.html">Developing Java EE 5 Applications</a></strong><br />
-The Java EE 5 programming model simplifies the process of creating Java applications.</li>
-<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 applications.</li>
-<li class="ulchildlink"><strong><a href="../topics/cjpers.html">Java EE perspective</a></strong><br />
-The Java EE 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 Java EE perspective</a></strong><br />
-While developing J2EE applications in the Java EE perspective, the Project Explorer view is your main view of your J2EE projects and resources.</li>
-<li class="ulchildlink"><strong><a href="../topics/tjviewfilters.html">Filtering in the Project Explorer view</a></strong><br />
-You can filter the Project Explorer view to hide projects, folders, or files that you do not want to see.</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 />
-The workbench includes validators that check certain files in your enterprise application module projects for errors.</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.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-projects.dita
deleted file mode 100644
index 57572fa..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-projects.dita
+++ /dev/null
@@ -1,16 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN"
- "topic.dtd">
-<topic id="phprojects" xml:lang="en-us">
-<title outputclass="id_title">Working with projects</title>
-<shortdesc outputclass="id_shortdesc">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.</shortdesc>
-<prolog><metadata>
-<keywords></keywords>
-</metadata></prolog>
-<body outputclass="id_body">
-<p outputclass="anchor_topictop"></p>
-<p outputclass="anchor_topicbottom"></p>
-</body>
-</topic>
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 14c861f..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-projects.html
+++ /dev/null
@@ -1,72 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="topic" name="DC.Type" />
-<meta name="DC.Title" content="Working with projects" />
-<meta name="abstract" content="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." />
-<meta name="description" content="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." />
-<meta scheme="URI" name="DC.Relation" content="../topics/ph-j2eeapp.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjearproj.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjappcliproj.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjear.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjappproj.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjrar.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjtargetserver.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cfacets.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/ph-importexport.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="phprojects" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Working with projects</title>
-</head>
-<body id="phprojects"><a name="phprojects"><!-- --></a>
-
-
-<h1 class="id_title">Working with projects</h1>
-
-
-
-<div class="id_body"><p class="id_shortdesc">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>
-
-<p class="anchor_topictop" />
-
-<p class="anchor_topicbottom" />
-
-</div>
-
-<div>
-<ul class="ullinks">
-<li class="ulchildlink"><strong><a href="../topics/cjearproj.html">Enterprise application projects</a></strong><br />
-An enterprise application project ties together the resources that are required to deploy a J2EE enterprise application.</li>
-<li class="ulchildlink"><strong><a href="../topics/cjappcliproj.html">Application client projects</a></strong><br />
-Application client projects contain programs that run on networked client systems so the project can benefit from a server's tools.</li>
-<li class="ulchildlink"><strong><a href="../topics/tjear.html">Creating an enterprise application project</a></strong><br />
-Using the wizard to create an enterprise application project allows you to package many web applications and modules in a project and deploy these modules as a J2EE enterprise application.</li>
-<li class="ulchildlink"><strong><a href="../topics/tjappproj.html">Creating an application client project</a></strong><br />
-You can use a wizard to create a new application client project and add it to a new or existing enterprise application project.</li>
-<li class="ulchildlink"><strong><a href="../topics/tjrar.html">Creating a connector project</a></strong><br />
-A connector is a J2EE standard extension mechanism for containers to provide connectivity to enterprise information systems (EISs).</li>
-<li class="ulchildlink"><strong><a href="../topics/tjtargetserver.html">Specifying target servers for J2EE projects</a></strong><br />
-When you develop J2EE applications, you can 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/cfacets.html">Project facets</a></strong><br />
-Facets define characteristics and requirements for Java EE projects and are used as part of the runtime configuration.</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 Enterprise Edition (Java EE).">Java EE 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.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-ref.dita
deleted file mode 100644
index 71f8c8c..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-ref.dita
+++ /dev/null
@@ -1,15 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN"
- "topic.dtd">
-<topic id="ph-ref" xml:lang="en-us">
-<title outputclass="id_title">Reference</title>
-<shortdesc outputclass="id_shortdesc">The following reference material on
-J2EE is available:</shortdesc>
-<prolog><metadata>
-<keywords></keywords>
-</metadata></prolog>
-<body outputclass="id_body">
-<p outputclass="anchor_topictop"></p>
-<p outputclass="anchor_topicbottom"></p>
-</body>
-</topic>
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 3469e98..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-ref.html
+++ /dev/null
@@ -1,56 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="topic" name="DC.Type" />
-<meta name="DC.Title" content="Reference" />
-<meta name="abstract" content="The following reference material on J2EE is available:" />
-<meta name="description" content="The following reference material on J2EE is available:" />
-<meta scheme="URI" name="DC.Relation" content="../topics/ph-j2eeapp.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/rvalidators.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/rvalerr.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/rjlimitcurrent.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="ph-ref" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Reference</title>
-</head>
-<body id="ph-ref"><a name="ph-ref"><!-- --></a>
-
-
-<h1 class="id_title">Reference</h1>
-
-
-
-<div class="id_body"><p class="id_shortdesc">The following reference material on
-J2EE is available:</p>
-
-<p class="anchor_topictop" />
-
-<p class="anchor_topicbottom" />
-
-</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 />
-This table lists the common error messages you may encounter 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 Enterprise Edition (Java EE).">Java EE 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.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/rjlimitcurrent.dita
deleted file mode 100644
index 9cbad09..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/rjlimitcurrent.dita
+++ /dev/null
@@ -1,71 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN"
- "reference.dtd">
-<reference id="rjlimitcurrent" xml:lang="en-us">
-<title outputclass="id_title">Limitations of J2EE development tools</title>
-<shortdesc outputclass="id_shortdesc">This topic outlines current known limitations
-and restrictions for J2EE tooling.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>J2EE<indexterm>tool limitations</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<refbody outputclass="id_refbody">
-<section outputclass="id_spacesLimitation"><p outputclass="anchor_topictop"></p><title>Spaces
-not supported in JAR URIs within an enterprise application</title>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.</section>
-<section outputclass="id_EARDBCSLimitation"><title>Enterprise application
-project names should not contain DBCS characters</title><p id="limitation_ear_dbcs">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></section>
-<section outputclass="id_utilityJARLimitation"><title><tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> build
-path updates when removing the dependency on a Utility JAR file</title>When
-removing the dependency on a Utility JAR, the corresponding <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> project
-will be removed from the <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> 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 <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> Example project. Next, add the JUnit
-project as a Utility JAR in the EAR, then add JUnit as a <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> JAR
-Dependency of the Web project. If you then wanted to remove the dependency
-between JUnit and the Web project, remove the <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> JAR Dependency from the Web project
-first, then remove the Utility JAR from the EAR. Follow this order to ensure
-that this works correctly.</section>
-<section outputclass="id_JARdepLimitation"><title><tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> JAR Dependencies page fails to update <tm
-tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> build
-path</title>The <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="Java">Java</tm> JAR Dependencies page is not synchronized with
-the <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> 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 <uicontrol>OK</uicontrol> button
-is clicked or if the <uicontrol>Apply</uicontrol> button is clicked prior
-to the <uicontrol>OK</uicontrol> button. Typically this will appear as if
-a JAR dependency was added, but the project did not get added to the <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> 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 <uicontrol>OK</uicontrol>.</section>
-<section outputclass="id_locationLimitation"><title>'Invalid project description'
-error when using a non-default project location for a new J2EE project</title>When
-you create a new J2EE project (including <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm>, 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.</section>
-<example outputclass="anchor_topicbottom"></example>
-</refbody>
-</reference>
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 f446bac..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/rjlimitcurrent.html
+++ /dev/null
@@ -1,89 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="reference" name="DC.Type" />
-<meta name="DC.Title" content="Limitations of J2EE development tools" />
-<meta name="abstract" content="This topic outlines current known limitations and restrictions for J2EE tooling." />
-<meta name="description" content="This topic outlines current known limitations and restrictions for J2EE tooling." />
-<meta content="J2EE, tool limitations" name="DC.subject" />
-<meta content="J2EE, tool limitations" name="keywords" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="rjlimitcurrent" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Limitations of J2EE development tools</title>
-</head>
-<body id="rjlimitcurrent"><a name="rjlimitcurrent"><!-- --></a>
-
-
-<h1 class="id_title">Limitations of J2EE development tools</h1>
-
-
-
-<div class="id_refbody"><p class="id_shortdesc">This topic outlines current known limitations
-and restrictions for J2EE tooling.</p>
-
-<div class="id_spacesLimitation"><h4 class="sectiontitle">Spaces
-not supported in JAR URIs within an enterprise application</h4><p class="anchor_topictop" />
-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="id_EARDBCSLimitation"><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="id_utilityJARLimitation"><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="id_JARdepLimitation"><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="id_locationLimitation"><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 class="anchor_topicbottom" />
-
-</div>
-
-
-</body>
-</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/rtunevalidat.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/rtunevalidat.dita
deleted file mode 100644
index fd4f2de..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/rtunevalidat.dita
+++ /dev/null
@@ -1,54 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN"
- "reference.dtd">
-<reference id="rtunevalidat" xml:lang="en-us">
-<title>Tuning validators</title>
-<shortdesc>Whether or not a validator validates a particular resource depends
-on the filters that are in place for that validator.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>code validation<indexterm>tuning</indexterm></indexterm>
-<indexterm>validation<indexterm>tuning</indexterm></indexterm></keywords>
-</metadata></prolog>
-<refbody>
-<section><p>When a validator is first developed, the implementer of the validator
-defines a default set of filters. These filters may be based on:<ul>
-<li>file extensions</li>
-<li>folder of file names</li>
-<li>project natures</li>
-<li>project facets</li>
-<li>content types</li>
-</ul>Through the Validation Filters dialog, you are able to further tune these
-settings.Normally you would simply keep the defaults, however two reasons
-why you may want to tune validation are:<ul>
-<li>Performance: if you have a very large workspace, you could reduce the
-amount of validation.</li>
-<li>Non standard conventions: if you use a non standard naming convention
-(for example stores XML in files with an .acme-xml extension), you could still
-enable the appropriate validators to run against those files.</li>
-</ul>You can access this dialog by clicking <menucascade><uicontrol>Window</uicontrol>
-<uicontrol>Preferences</uicontrol><uicontrol>Validation</uicontrol></menucascade> and
-then clicking <uicontrol>Settings</uicontrol> beside each validator.</p><p>Filters
-are stored in groups. There are two types of groups: Include groups and Exclude
-groups. You can have as many Include groups as you like. Filters inside of
-an Include group cause resources to be validated. If any rule matches then
-the entire group matches. Inside of a group the filter rules are OR’d together.
-However individual Include groups are AND’ed together. You can have one Exclude
-group. If any of its filter rules match, then the resource is excluded. Exclusion
-takes precedence over inclusion.</p></section>
-<example><p>These rules are illustrated with this hypothetical example:<image
-href="../images/validatefilters.jpg" placement="break"><alt>screen capture
-of the validation filters panel showing include and exclude groups</alt></image><ul>
-<li>If the resource is in the disabled folder, it will be excluded because
-exclusion takes precedence over everything else.</li>
-<li>If the resource does not have the JSP source content type, and it does
-not have the JSP fragment source content type, and it does not have a file
-extension of .jsp or .jspf then it will be excluded because none of the rules
-in the first group matched.</li>
-<li>If the project does not have the module core nature then it will be excluded
-because the single rule in the second group did not match.</li>
-<li>Otherwise the resource will be validated by this particular validator.</li>
-</ul>To add a rule to a group, select the group on the left, and click <uicontrol>Add
-Rule</uicontrol>.</p></example>
-</refbody>
-</reference>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/rtunevalidat.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/rtunevalidat.html
deleted file mode 100644
index e733159..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/rtunevalidat.html
+++ /dev/null
@@ -1,103 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="reference" name="DC.Type" />
-<meta name="DC.Title" content="Tuning validators" />
-<meta name="abstract" content="Whether or not a validator validates a particular resource depends on the filters that are in place for that validator." />
-<meta name="description" content="Whether or not a validator validates a particular resource depends on the filters that are in place for that validator." />
-<meta content="code validation, tuning, validation" name="DC.subject" />
-<meta content="code validation, tuning, validation" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjvaldisable.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjvalglobalpref.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjvalmanual.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjvalselect.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="rtunevalidat" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Tuning validators</title>
-</head>
-<body id="rtunevalidat"><a name="rtunevalidat"><!-- --></a>
-
-
-<h1 class="topictitle1">Tuning validators</h1>
-
-
-
-<div><p>Whether or not a validator validates a particular resource depends
-on the filters that are in place for that validator.</p>
-
-<div class="section"><div class="p">When a validator is first developed, the implementer of the validator
-defines a default set of filters. These filters may be based on:<ul>
-<li>file extensions</li>
-
-<li>folder of file names</li>
-
-<li>project natures</li>
-
-<li>project facets</li>
-
-<li>content types</li>
-
-</ul>
-Through the Validation Filters dialog, you are able to further tune these
-settings.Normally you would simply keep the defaults, however two reasons
-why you may want to tune validation are:<ul>
-<li>Performance: if you have a very large workspace, you could reduce the
-amount of validation.</li>
-
-<li>Non standard conventions: if you use a non standard naming convention
-(for example stores XML in files with an .acme-xml extension), you could still
-enable the appropriate validators to run against those files.</li>
-
-</ul>
-You can access this dialog by clicking <span class="menucascade"><span class="uicontrol">Window</span>
- > <span class="uicontrol">Preferences</span> > <span class="uicontrol">Validation</span></span> and
-then clicking <span class="uicontrol">Settings</span> beside each validator.</div>
-<p>Filters
-are stored in groups. There are two types of groups: Include groups and Exclude
-groups. You can have as many Include groups as you like. Filters inside of
-an Include group cause resources to be validated. If any rule matches then
-the entire group matches. Inside of a group the filter rules are OR’d together.
-However individual Include groups are AND’ed together. You can have one Exclude
-group. If any of its filter rules match, then the resource is excluded. Exclusion
-takes precedence over inclusion.</p>
-</div>
-
-<div class="example"><div class="p">These rules are illustrated with this hypothetical example:<br /><img src="../images/validatefilters.jpg" alt="screen capture of the validation filters panel showing include and exclude groups" /><br /><ul>
-<li>If the resource is in the disabled folder, it will be excluded because
-exclusion takes precedence over everything else.</li>
-
-<li>If the resource does not have the JSP source content type, and it does
-not have the JSP fragment source content type, and it does not have a file
-extension of .jsp or .jspf then it will be excluded because none of the rules
-in the first group matched.</li>
-
-<li>If the project does not have the module core nature then it will be excluded
-because the single rule in the second group did not match.</li>
-
-<li>Otherwise the resource will be validated by this particular validator.</li>
-
-</ul>
-To add a rule to a group, select the group on the left, and click <span class="uicontrol">Add
-Rule</span>.</div>
-</div>
-
-</div>
-
-<div><div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="../topics/tjvaldisable.html" title="You can disable one or more validators individually or disable validation entirely. Also, you can set validation settings for your entire workspace and for individual projects.">Disabling validation</a></div>
-<div><a href="../topics/tjvalglobalpref.html" title="For a given project, you can override the global validation preferences.">Overriding global validation preferences</a></div>
-<div><a href="../topics/tjvalmanual.html" title="When you run a manual validation, all resources in the selected project are validated according to the validation settings.">Manually validating code</a></div>
-<div><a href="../topics/tjvalselect.html" title="You can select specific validators to run during manual and build code validation. You can set each validator to run on manual validation, build validation, both, or neither.">Selecting code validators</a></div>
-</div>
-</div>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/rvalerr.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/rvalerr.dita
deleted file mode 100644
index b4c14df..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/rvalerr.dita
+++ /dev/null
@@ -1,191 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN"
- "reference.dtd">
-<reference id="rvalerr" xml:lang="en-us">
-<title outputclass="id_title">Common validation errors and solutions</title>
-<shortdesc outputclass="id_shortdesc">This table lists the common error messages<?Pub Caret?>
-you may encounter when you validate your projects.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>code validation<indexterm>error solutions</indexterm></indexterm>
-<indexterm>validation<indexterm>error solutions</indexterm></indexterm></keywords>
-</metadata></prolog>
-<refbody outputclass="id_refbody">
-<example outputclass="anchor_topictop"></example>
-<table frame="all">
-<tgroup cols="3" colsep="1" rowsep="1"><colspec colname="col1" colwidth="60*"/>
-<colspec colname="col2" colwidth="72*"/><colspec colname="col3" colwidth="164*"/>
-<thead>
-<row outputclass="id_tableHeadRow">
-<entry>Message prefix</entry>
-<entry>Message</entry>
-<entry>Explanation</entry>
-</row>
-</thead>
-<tbody>
-<row outputclass="id_appclientValidator">
-<entry nameend="col3" namest="col1"><uicontrol>Application Client validator</uicontrol></entry>
-</row>
-<row outputclass="id_CHKJ1000">
-<entry colname="col1">CHKJ1000</entry>
-<entry colname="col2">Validation failed because the application client file
-is not valid. Ensure that the deployment descriptor is valid.</entry>
-<entry colname="col3">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 <uicontrol>Validate
-XML file</uicontrol>.</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> </entry>
-</row>
-<row outputclass="id_EARValidator">
-<entry nameend="col3" namest="col1"><uicontrol>EAR validator</uicontrol></entry>
-</row>
-<row outputclass="id_CHKJ1001">
-<entry colname="col1">CHKJ1001</entry>
-<entry colname="col2">The EAR project {0} is invalid.</entry>
-<entry colname="col3">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 <codeph>application.xml</codeph></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 <uicontrol>Validate
-XML file</uicontrol>.</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></entry>
-</row>
-<row outputclass="id_EJBValidator">
-<entry nameend="col3" namest="col1"><uicontrol>EJB validator</uicontrol></entry>
-</row>
-<row outputclass="id_CHKJ2019">
-<entry>CHKJ2019</entry>
-<entry>The {0} key class must be serializable at runtime. </entry>
-<entry morerows="2">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. </entry>
-</row>
-<row outputclass="id_CHKJ2412">
-<entry>CHKJ2412</entry>
-<entry>The return type must be serializable at runtime. </entry>
-</row>
-<row outputclass="id_CHKJ2413">
-<entry>CHKJ2413</entry>
-<entry>Argument {1} of {0} must be serializable at runtime.</entry>
-</row>
-<row outputclass="id_CHKJ2102">
-<entry>CHKJ2102</entry>
-<entry>Either a finder descriptor, or a matching custom finder method on the
-{0} class, must be defined.</entry>
-<entry>A finder descriptor must exist for every finder method. </entry>
-</row>
-<row outputclass="id_CHKJ2873">
-<entry>CHKJ2873</entry>
-<entry>Migrate this bean's datasource binding to a CMP Connection Factory
-binding.</entry>
-<entry></entry>
-</row>
-<row outputclass="id_CHKJ2874">
-<entry>CHKJ2874</entry>
-<entry>Migrate this EJB module's default datasource binding to a default CMP
-Connection Factory binding.</entry>
-<entry></entry>
-</row>
-<row outputclass="id_CHKJ2875E">
-<entry colname="col1">CHKJ2875E </entry>
-<entry colname="col2"><ejb-client-jar> {0} must exist in every EAR file
-that contains this EJB module.</entry>
-<entry colname="col3">If <codeph><ejb-client-jar></codeph> is specified
-in <filepath>ejb-jar.xml</filepath>, 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 <codeph><ejb-client-jar></codeph> 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.</entry>
-</row>
-<row outputclass="id_CHKJ2905">
-<entry>CHKJ2905</entry>
-<entry>The EJB validator did not run because ejb-jar.xml could not be loaded.
-Run the XML validator for more information.</entry>
-<entry>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 <uicontrol>Validate XML file</uicontrol>.</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></entry>
-</row>
-<row outputclass="id_JSPValidator">
-<entry nameend="col3" namest="col1"><uicontrol>JSP validator</uicontrol></entry>
-</row>
-<row outputclass="id_IWAW0482">
-<entry colname="col1">IWAW0482</entry>
-<entry colname="col2">No valid JspTranslator</entry>
-<entry colname="col3">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 (<uicontrol>Window > Preferences > Java >Installed
-JREs</uicontrol>) and make sure that the location for the JRE is pointing
-to a valid JRE directory. </li>
-<li>Ensure that the classpath variables (<uicontrol>Window > Preferences >
-Java > Classpath Variables</uicontrol>) are set correctly.</li>
-</ol> </entry>
-</row>
-<row outputclass="id_WARValidator">
-<entry nameend="col3" namest="col1"><uicontrol>WAR validator</uicontrol></entry>
-</row>
-<row outputclass="id_CHKJ3008">
-<entry colname="col1">CHKJ3008</entry>
-<entry colname="col2">Missing or invalid WAR file.</entry>
-<entry colname="col3">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 <uicontrol>Validate XML file</uicontrol>.</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></entry>
-</row>
-<row outputclass="id_XMLValidator">
-<entry nameend="col3" namest="col1"><uicontrol>XML validator</uicontrol></entry>
-</row>
-<row>
-<entry> </entry>
-<entry>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?)".</entry>
-<entry>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.</entry>
-</row>
-</tbody>
-</tgroup>
-</table>
-<example outputclass="anchor_topicbottom"></example>
-</refbody>
-</reference>
-<?Pub *0000008883?>
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 d9d30cb..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/rvalerr.html
+++ /dev/null
@@ -1,326 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="reference" name="DC.Type" />
-<meta name="DC.Title" content="Common validation errors and solutions" />
-<meta name="abstract" content="This table lists the common error messages you may encounter when you validate your projects." />
-<meta name="description" content="This table lists the common error messages you may encounter when you validate your projects." />
-<meta content="code validation, error solutions, validation" name="DC.subject" />
-<meta content="code validation, error solutions, validation" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/rvalidators.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjval.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="rvalerr" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Common validation errors and solutions</title>
-</head>
-<body id="rvalerr"><a name="rvalerr"><!-- --></a>
-
-
-<h1 class="id_title">Common validation errors and solutions</h1>
-
-
-
-<div class="id_refbody"><p class="id_shortdesc">This table lists the common error messages
-you may encounter when you validate your projects.</p>
-
-<div class="anchor_topictop" />
-
-
-<div class="tablenoborder"><table summary="" cellspacing="0" cellpadding="4" frame="border" border="1" rules="all">
-
-<thead align="left">
-<tr class="id_tableHeadRow">
-<th valign="top" width="20.27027027027027%" id="N10078">Message prefix</th>
-
-<th valign="top" width="24.324324324324326%" id="N1007F">Message</th>
-
-<th valign="top" width="55.4054054054054%" id="N10086">Explanation</th>
-
-</tr>
-
-</thead>
-
-<tbody>
-<tr class="id_appclientValidator">
-<td colspan="3" valign="top" headers="N10078 N1007F N10086 "><span class="uicontrol">Application Client validator</span></td>
-
-</tr>
-
-<tr class="id_CHKJ1000">
-<td valign="top" width="20.27027027027027%" headers="N10078 ">CHKJ1000</td>
-
-<td valign="top" width="24.324324324324326%" headers="N1007F ">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="N10086 ">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 class="id_EARValidator">
-<td colspan="3" valign="top" headers="N10078 N1007F N10086 "><span class="uicontrol">EAR validator</span></td>
-
-</tr>
-
-<tr class="id_CHKJ1001">
-<td valign="top" width="20.27027027027027%" headers="N10078 ">CHKJ1001</td>
-
-<td valign="top" width="24.324324324324326%" headers="N1007F ">The EAR project {0} is invalid.</td>
-
-<td valign="top" width="55.4054054054054%" headers="N10086 ">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 class="id_EJBValidator">
-<td colspan="3" valign="top" headers="N10078 N1007F N10086 "><span class="uicontrol">EJB validator</span></td>
-
-</tr>
-
-<tr class="id_CHKJ2019">
-<td valign="top" width="20.27027027027027%" headers="N10078 ">CHKJ2019</td>
-
-<td valign="top" width="24.324324324324326%" headers="N1007F ">The {0} key class must be serializable at runtime. </td>
-
-<td rowspan="3" valign="top" width="55.4054054054054%" headers="N10086 ">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 class="id_CHKJ2412">
-<td valign="top" width="20.27027027027027%" headers="N10078 ">CHKJ2412</td>
-
-<td valign="top" width="24.324324324324326%" headers="N1007F ">The return type must be serializable at runtime. </td>
-
-</tr>
-
-<tr class="id_CHKJ2413">
-<td valign="top" width="20.27027027027027%" headers="N10078 ">CHKJ2413</td>
-
-<td valign="top" width="24.324324324324326%" headers="N1007F ">Argument {1} of {0} must be serializable at runtime.</td>
-
-</tr>
-
-<tr class="id_CHKJ2102">
-<td valign="top" width="20.27027027027027%" headers="N10078 ">CHKJ2102</td>
-
-<td valign="top" width="24.324324324324326%" headers="N1007F ">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="N10086 ">A finder descriptor must exist for every finder method. </td>
-
-</tr>
-
-<tr class="id_CHKJ2873">
-<td valign="top" width="20.27027027027027%" headers="N10078 ">CHKJ2873</td>
-
-<td valign="top" width="24.324324324324326%" headers="N1007F ">Migrate this bean's datasource binding to a CMP Connection Factory
-binding.</td>
-
-<td valign="top" width="55.4054054054054%" headers="N10086 "> </td>
-
-</tr>
-
-<tr class="id_CHKJ2874">
-<td valign="top" width="20.27027027027027%" headers="N10078 ">CHKJ2874</td>
-
-<td valign="top" width="24.324324324324326%" headers="N1007F ">Migrate this EJB module's default datasource binding to a default CMP
-Connection Factory binding.</td>
-
-<td valign="top" width="55.4054054054054%" headers="N10086 "> </td>
-
-</tr>
-
-<tr class="id_CHKJ2875E">
-<td valign="top" width="20.27027027027027%" headers="N10078 ">CHKJ2875E </td>
-
-<td valign="top" width="24.324324324324326%" headers="N1007F "><ejb-client-jar> {0} must exist in every EAR file
-that contains this EJB module.</td>
-
-<td valign="top" width="55.4054054054054%" headers="N10086 ">If <samp class="codeph"><ejb-client-jar></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"><ejb-client-jar></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 class="id_CHKJ2905">
-<td valign="top" width="20.27027027027027%" headers="N10078 ">CHKJ2905</td>
-
-<td valign="top" width="24.324324324324326%" headers="N1007F ">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="N10086 ">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 class="id_JSPValidator">
-<td colspan="3" valign="top" headers="N10078 N1007F N10086 "><span class="uicontrol">JSP validator</span></td>
-
-</tr>
-
-<tr class="id_IWAW0482">
-<td valign="top" width="20.27027027027027%" headers="N10078 ">IWAW0482</td>
-
-<td valign="top" width="24.324324324324326%" headers="N1007F ">No valid JspTranslator</td>
-
-<td valign="top" width="55.4054054054054%" headers="N10086 ">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 > Preferences > Java >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 > Preferences >
-Java > Classpath Variables</span>) are set correctly.</li>
-
-</ol>
- </td>
-
-</tr>
-
-<tr class="id_WARValidator">
-<td colspan="3" valign="top" headers="N10078 N1007F N10086 "><span class="uicontrol">WAR validator</span></td>
-
-</tr>
-
-<tr class="id_CHKJ3008">
-<td valign="top" width="20.27027027027027%" headers="N10078 ">CHKJ3008</td>
-
-<td valign="top" width="24.324324324324326%" headers="N1007F ">Missing or invalid WAR file.</td>
-
-<td valign="top" width="55.4054054054054%" headers="N10086 ">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 class="id_XMLValidator">
-<td colspan="3" valign="top" headers="N10078 N1007F N10086 "><span class="uicontrol">XML validator</span></td>
-
-</tr>
-
-<tr>
-<td valign="top" width="20.27027027027027%" headers="N10078 "> </td>
-
-<td valign="top" width="24.324324324324326%" headers="N1007F ">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="N10086 ">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 class="anchor_topicbottom" />
-
-</div>
-
-<div><div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="../topics/tjval.html" title="The workbench includes validators that check certain files in your enterprise application module projects for errors.">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.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/rvalidators.dita
deleted file mode 100644
index 51bdd7f..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/rvalidators.dita
+++ /dev/null
@@ -1,150 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN"
- "reference.dtd">
-<reference id="rvalidators" xml:lang="en-us">
-<title outputclass="id_title">J2EE Validators</title>
-<shortdesc outputclass="id_shortdesc">This table lists the validators that
-are available for the different project types and gives a brief description
-of each validator.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>validation<indexterm>J2EE validators</indexterm></indexterm>
-<indexterm>code validation<indexterm>J2EE validators</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<refbody outputclass="id_refbody">
-<example outputclass="anchor_topictop"></example>
-<table frame="all">
-<tgroup cols="2" colsep="1" rowsep="1"><colspec colname="col1" colwidth="50*"/>
-<colspec colname="col2" colwidth="50*"/>
-<thead>
-<row outputclass="id_toprow">
-<entry>Validator name</entry>
-<entry>Description</entry>
-</row>
-</thead>
-<tbody>
-<row outputclass="id_appclientValidator">
-<entry align="left" valign="top">Application Client Validator</entry>
-<entry align="left" valign="top">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></entry>
-</row>
-<row outputclass="id_connectorValidator">
-<entry colname="col1">Connector Validator</entry>
-<entry colname="col2">The Connector validator checks for invalid J2EE specification
-levels in connector projects.</entry>
-</row>
-<row outputclass="id_DTDValidator">
-<entry align="left" valign="top">DTD Validator</entry>
-<entry align="left" valign="top">The DTD validator determines whether the
-current state of a DTD is semantically valid. XML files are validated according
-to the XML specification <xref format="html" href="http://www.w3.org/TR/2000/REC-xml-20001006"
-scope="external"> Extensible Markup Language (XML) 1.0<desc></desc></xref> from
-the W3C Web site. As well, the DTD validator checks for errors such as references
-to entities and elements that do not exist.</entry>
-</row>
-<row outputclass="id_EARValidator">
-<entry align="left" valign="top">EAR Validator</entry>
-<entry align="left" valign="top">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></entry>
-</row>
-<row outputclass="id_EJBValidator">
-<entry align="left" valign="top">EJB Validator</entry>
-<entry align="left" valign="top">The EJB Validator verifies that enterprise
-beans contained in an EJB project comply with the Sun Enterprise <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="JavaBeans">JavaBeans</tm> 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. Specifically, the EJB Validator
-validates the following resources: <ul>
-<li><tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> .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></entry>
-</row>
-<row outputclass="id_ELValidator">
-<entry colname="col1">EL Syntax Validator</entry>
-<entry colname="col2"></entry>
-</row>
-<row outputclass="id_HTMLValidator">
-<entry align="left" valign="top">HTML Syntax Validator</entry>
-<entry align="left" valign="top">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></entry>
-</row>
-<row outputclass="id_JSPValidator">
-<entry align="left" valign="top">JSP Syntax Validator</entry>
-<entry align="left" valign="top">The JSP Syntax Validator validates JSP files
-in a project by translating them into the corresponding <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> code
-and then checking the <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> code for compile errors.</entry>
-</row>
-<row outputclass="id_WARValidator">
-<entry align="left" valign="top">War Validator</entry>
-<entry align="left" valign="top">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 & servlet mappings</li>
-<li>EJB references</li>
-</ul></entry>
-</row>
-<row outputclass="id_WSDLValidator">
-<entry colname="col1">WSDL Validator</entry>
-<entry colname="col2">The WSDL validator checks the following in WSDL files: <ul>
-<li>XML syntax</li>
-<li>XML Schema types in the <types> 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. </entry>
-</row>
-<row outputclass="id_WSIValidator">
-<entry colname="col1">WS-I Message Validator</entry>
-<entry colname="col2">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.</entry>
-</row>
-<row outputclass="id_XMLSchemaValidator">
-<entry align="left" valign="top">XML Schema Validator</entry>
-<entry align="left" valign="top">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 <xref format="html"
-href="http://www.w3.org/TR/xmlschema-1/" scope="local"> XML Schema Part 1:
-Structures<desc></desc></xref> from the W3C Web site.</entry>
-</row>
-<row outputclass="id_XMLValidator">
-<entry align="left" valign="top">XML Validator</entry>
-<entry align="left" valign="top">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.</entry>
-</row>
-</tbody>
-</tgroup>
-</table>
-<example outputclass="anchor_topicbottom"></example>
-</refbody>
-</reference>
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 f2de783..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/rvalidators.html
+++ /dev/null
@@ -1,249 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="reference" name="DC.Type" />
-<meta name="DC.Title" content="J2EE Validators" />
-<meta name="abstract" content="This table lists the validators that are available for the different project types and gives a brief description of each validator." />
-<meta name="description" content="This table lists the validators that are available for the different project types and gives a brief description of each validator." />
-<meta content="validation, J2EE validators, code validation" name="DC.subject" />
-<meta content="validation, J2EE validators, code validation" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/rvalerr.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjval.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="rvalidators" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>J2EE Validators</title>
-</head>
-<body id="rvalidators"><a name="rvalidators"><!-- --></a>
-
-
-<h1 class="id_title">J2EE Validators</h1>
-
-
-
-<div class="id_refbody"><p class="id_shortdesc">This table lists the validators that
-are available for the different project types and gives a brief description
-of each validator.</p>
-
-<div class="anchor_topictop" />
-
-
-<div class="tablenoborder"><table summary="" cellspacing="0" cellpadding="4" frame="border" border="1" rules="all">
-
-<thead align="left">
-<tr class="id_toprow">
-<th valign="top" width="50%" id="N10073">Validator name</th>
-
-<th valign="top" width="50%" id="N1007A">Description</th>
-
-</tr>
-
-</thead>
-
-<tbody>
-<tr class="id_appclientValidator">
-<td align="left" valign="top" width="50%" headers="N10073 ">Application Client Validator</td>
-
-<td align="left" valign="top" width="50%" headers="N1007A ">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 class="id_connectorValidator">
-<td valign="top" width="50%" headers="N10073 ">Connector Validator</td>
-
-<td valign="top" width="50%" headers="N1007A ">The Connector validator checks for invalid J2EE specification
-levels in connector projects.</td>
-
-</tr>
-
-<tr class="id_DTDValidator">
-<td align="left" valign="top" width="50%" headers="N10073 ">DTD Validator</td>
-
-<td align="left" valign="top" width="50%" headers="N1007A ">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" title="">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 class="id_EARValidator">
-<td align="left" valign="top" width="50%" headers="N10073 ">EAR Validator</td>
-
-<td align="left" valign="top" width="50%" headers="N1007A ">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 class="id_EJBValidator">
-<td align="left" valign="top" width="50%" headers="N10073 ">EJB Validator</td>
-
-<td align="left" valign="top" width="50%" headers="N1007A ">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. Specifically, the EJB Validator
-validates the following resources: <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 class="id_ELValidator">
-<td valign="top" width="50%" headers="N10073 ">EL Syntax Validator</td>
-
-<td valign="top" width="50%" headers="N1007A "> </td>
-
-</tr>
-
-<tr class="id_HTMLValidator">
-<td align="left" valign="top" width="50%" headers="N10073 ">HTML Syntax Validator</td>
-
-<td align="left" valign="top" width="50%" headers="N1007A ">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 class="id_JSPValidator">
-<td align="left" valign="top" width="50%" headers="N10073 ">JSP Syntax Validator</td>
-
-<td align="left" valign="top" width="50%" headers="N1007A ">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 class="id_WARValidator">
-<td align="left" valign="top" width="50%" headers="N10073 ">War Validator</td>
-
-<td align="left" valign="top" width="50%" headers="N1007A ">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 & servlet mappings</li>
-
-<li>EJB references</li>
-
-</ul>
-</td>
-
-</tr>
-
-<tr class="id_WSDLValidator">
-<td valign="top" width="50%" headers="N10073 ">WSDL Validator</td>
-
-<td valign="top" width="50%" headers="N1007A ">The WSDL validator checks the following in WSDL files: <ul>
-<li>XML syntax</li>
-
-<li>XML Schema types in the <types> 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 class="id_WSIValidator">
-<td valign="top" width="50%" headers="N10073 ">WS-I Message Validator</td>
-
-<td valign="top" width="50%" headers="N1007A ">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 class="id_XMLSchemaValidator">
-<td align="left" valign="top" width="50%" headers="N10073 ">XML Schema Validator</td>
-
-<td align="left" valign="top" width="50%" headers="N1007A ">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/" title="">XML Schema Part 1: Structures</a> from the W3C Web site.</td>
-
-</tr>
-
-<tr class="id_XMLValidator">
-<td align="left" valign="top" width="50%" headers="N10073 ">XML Validator</td>
-
-<td align="left" valign="top" width="50%" headers="N1007A ">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 class="anchor_topicbottom" />
-
-</div>
-
-<div><div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="../topics/tjval.html" title="The workbench includes validators that check certain files in your enterprise application module projects for errors.">Validating code in enterprise applications</a></div>
-</div>
-<div class="relref"><strong>Related reference</strong><br />
-<div><a href="../topics/rvalerr.html" title="This table lists the common error messages you may encounter 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/taddingfacet.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/taddingfacet.dita
deleted file mode 100644
index 41da49a..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/taddingfacet.dita
+++ /dev/null
@@ -1,55 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="taddingfacet" xml:lang="en-us">
-<title outputclass="id_title">Adding a facet to a Java EE project</title>
-<shortdesc outputclass="id_shortdesc">This topic explains how to add a facet
-to an existing project in your workspace.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>projects<indexterm>facets<indexterm>adding</indexterm></indexterm></indexterm>
-<indexterm>Java EE<indexterm>adding project facets</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody outputclass="id_taskbody">
-<context outputclass="id_context"><p outputclass="anchor_topictop"></p><p
-conref="cfacets.dita#cfacets/aboutfacet"></p> <p>New projects generally have
-facets added to them when they are created. To add another facet to a project
-that already exists, complete the following steps:</p></context>
-<steps outputclass="id_steps">
-<step><cmd>In the Project Explorer view of the <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> EE perspective, right-click the project
-and then select <uicontrol>Properties</uicontrol>.</cmd></step>
-<step><cmd>Select the <uicontrol>Project Facets</uicontrol> page in the in
-the Properties window.</cmd><info>This page lists the facets in the project
-and their versions.</info></step>
-<step><cmd>Click <uicontrol>Modify Project</uicontrol> and select the check
-boxes next to the facets you want the project to have.</cmd><info><p>Only
-the facets that are valid for the project are listed:<ul>
-<li>The list of runtimes selected for the project limits the facets shown
-in the list. Only the facets compatible with all selected target runtimes
-are shown.</li>
-<li>The currently selected facets and their version numbers limit the other
-facets shown in the list. For example, if the project contains the Dynamic
-Web Module facet, the EJB Module facet is not listed because these two facets
-cannot be in the same project.</li>
-</ul>You can find out more about the requirements and limitations for each
-facet by right-clicking the facet name and then clicking <uicontrol>Show Constraints</uicontrol>.</p><p>You
-can also choose a preset combination of facets from the <uicontrol>Presets</uicontrol> list.</p></info>
-</step>
-<step><cmd>Choose a version number for the facet by clicking the current version
-number and selecting the version number you want from the drop-down list.</cmd>
-</step>
-<step importance="optional"><cmd>To remove a facet, clear its check box.</cmd>
-<info>Not all facets can be removed.</info></step>
-<step importance="optional"><cmd>If you want to limit the project so it will
-be compatible with one or more runtimes, click on the Runtimes tab and select
-the runtimes that you want the project to be compatible with.</cmd><info>For
-more information on runtimes, see <xref href="tjtargetserver.dita"></xref>.</info>
-</step>
-<step><cmd>Click <uicontrol>Finish</uicontrol> to exit the Modify Faceted
-Project dialog and then click <uicontrol>OK</uicontrol>.</cmd></step>
-</steps>
-<postreq outputclass="id_postreq"><p outputclass="anchor_topicbottom"></p></postreq>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/taddingfacet.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/taddingfacet.html
deleted file mode 100644
index 2453d13..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/taddingfacet.html
+++ /dev/null
@@ -1,107 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="task" name="DC.Type" />
-<meta name="DC.Title" content="Adding a facet to a Java EE project" />
-<meta name="abstract" content="This topic explains how to add a facet to an existing project in your workspace." />
-<meta name="description" content="This topic explains how to add a facet to an existing project in your workspace." />
-<meta content="projects, facets, adding, Java EE, adding project facets" name="DC.subject" />
-<meta content="projects, facets, adding, Java EE, adding project facets" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tchangejavalevel.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tchangefacet.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cfacets.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="taddingfacet" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Adding a facet to a Java EE project</title>
-</head>
-<body id="taddingfacet"><a name="taddingfacet"><!-- --></a>
-
-
-<h1 class="id_title">Adding a facet to a Java EE project</h1>
-
-
-
-<div class="id_taskbody"><p class="id_shortdesc">This topic explains how to add a facet
-to an existing project in your workspace.</p>
-
-<div class="id_context"><p class="anchor_topictop" />
-<p>When you add a facet to a project, that project is configured
-to perform a certain task, fulfill certain requirements, or have certain characteristics.
-For example, the EAR facet sets up a project to function as an enterprise
-application by adding a deployment descriptor and setting up the project's
-classpath.</p>
- <p>New projects generally have
-facets added to them when they are created. To add another facet to a project
-that already exists, complete the following steps:</p>
-</div>
-
-<ol class="id_steps">
-<li class="stepexpand"><span>In the Project Explorer view of the Java™ EE perspective, right-click the project
-and then select <span class="uicontrol">Properties</span>.</span></li>
-
-<li class="stepexpand"><span>Select the <span class="uicontrol">Project Facets</span> page in the in
-the Properties window.</span> This page lists the facets in the project
-and their versions.</li>
-
-<li class="stepexpand"><span>Click <span class="uicontrol">Modify Project</span> and select the check
-boxes next to the facets you want the project to have.</span> <div class="p">Only
-the facets that are valid for the project are listed:<ul>
-<li>The list of runtimes selected for the project limits the facets shown
-in the list. Only the facets compatible with all selected target runtimes
-are shown.</li>
-
-<li>The currently selected facets and their version numbers limit the other
-facets shown in the list. For example, if the project contains the Dynamic
-Web Module facet, the EJB Module facet is not listed because these two facets
-cannot be in the same project.</li>
-
-</ul>
-You can find out more about the requirements and limitations for each
-facet by right-clicking the facet name and then clicking <span class="uicontrol">Show Constraints</span>.</div>
-<p>You
-can also choose a preset combination of facets from the <span class="uicontrol">Presets</span> list.</p>
-
-</li>
-
-<li class="stepexpand"><span>Choose a version number for the facet by clicking the current version
-number and selecting the version number you want from the drop-down list.</span>
-</li>
-
-<li class="stepexpand"><strong>Optional: </strong><span>To remove a facet, clear its check box.</span>
- Not all facets can be removed.</li>
-
-<li class="stepexpand"><strong>Optional: </strong><span>If you want to limit the project so it will
-be compatible with one or more runtimes, click on the Runtimes tab and select
-the runtimes that you want the project to be compatible with.</span> For
-more information on runtimes, see <a href="tjtargetserver.html" title="When you develop J2EE applications, you can 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.">Specifying target servers for J2EE projects</a>.
-</li>
-
-<li class="stepexpand"><span>Click <span class="uicontrol">Finish</span> to exit the Modify Faceted
-Project dialog and then click <span class="uicontrol">OK</span>.</span></li>
-
-</ol>
-
-<div class="id_postreq"><p class="anchor_topicbottom" />
-</div>
-
-</div>
-
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="../topics/cfacets.html" title="Facets define characteristics and requirements for Java EE projects and are used as part of the runtime configuration.">Project facets</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="../topics/tchangejavalevel.html" title="You can change the version of Java used in a Java EE project by changing the value of the Java facet.">Changing the Java compiler version for a Java EE project</a></div>
-<div><a href="../topics/tchangefacet.html" title="You can change the version of a facet in a Java EE project by editing the facets for the project.">Changing the version of a facet</a></div>
-</div>
-</div>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tchangefacet.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/tchangefacet.dita
deleted file mode 100644
index 212244d..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tchangefacet.dita
+++ /dev/null
@@ -1,37 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="tchangefacet" xml:lang="en-us">
-<title outputclass="id_title">Changing the version of a facet</title>
-<shortdesc outputclass="id_shortdesc">You can change the version of a facet
-in a Java EE project by editing the facets for the project.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>facets<indexterm>changing versions</indexterm></indexterm>
-<indexterm>Java EE<indexterm>changing facet versions</indexterm></indexterm>
-<indexterm>projects<indexterm>changing facet versions</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody outputclass="id_taskbody">
-<context outputclass="id_context"><p outputclass="anchor_topictop"></p> <p>Changing
-the <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> compiler
-version of a Java EE project involves changing the version of the <uicontrol>Java</uicontrol> facet.
-For more information, see <xref href="tchangejavalevel.dita"></xref>.</p><p>To
-change the version of a facet in your project, complete the following steps:</p></context>
-<steps outputclass="id_steps">
-<step><cmd>In the Project Explorer view of the <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> EE perspective, right-click the project
-and then select <uicontrol>Properties</uicontrol>.</cmd></step>
-<step><cmd>Select the <uicontrol>Project Facets</uicontrol> page in the in
-the Properties window.</cmd><info> This page lists the facets in the project
-and their versions.</info></step>
-<step><cmd>Click <uicontrol>Modify Project</uicontrol> and click the facet
-you want to change.</cmd></step>
-<step><cmd>Select the version of the facet from the drop-down box next to
-the facet's name.</cmd></step>
-<step><cmd>Click <uicontrol>Finish</uicontrol> to close the Modify Faceted
-Project window and then click <uicontrol>OK</uicontrol>.</cmd></step>
-</steps>
-<postreq outputclass="id_postreq"><p outputclass="anchor_topicbottom"></p></postreq>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tchangefacet.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tchangefacet.html
deleted file mode 100644
index 0b96230..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tchangefacet.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 content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="task" name="DC.Type" />
-<meta name="DC.Title" content="Changing the version of a facet" />
-<meta name="abstract" content="You can change the version of a facet in a Java EE project by editing the facets for the project." />
-<meta name="description" content="You can change the version of a facet in a Java EE project by editing the facets for the project." />
-<meta content="facets, changing versions, Java EE, changing facet versions, projects" name="DC.subject" />
-<meta content="facets, changing versions, Java EE, changing facet versions, projects" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/taddingfacet.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tchangejavalevel.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cfacets.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="tchangefacet" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Changing the version of a facet</title>
-</head>
-<body id="tchangefacet"><a name="tchangefacet"><!-- --></a>
-
-
-<h1 class="id_title">Changing the version of a facet</h1>
-
-
-
-<div class="id_taskbody"><p class="id_shortdesc">You can change the version of a facet
-in a Java EE project by editing the facets for the project.</p>
-
-<div class="id_context"><p class="anchor_topictop" />
- <p>Changing
-the Java™ compiler
-version of a Java EE project involves changing the version of the <span class="uicontrol">Java</span> facet.
-For more information, see <a href="tchangejavalevel.html" title="You can change the version of Java used in a Java EE project by changing the value of the Java facet.">Changing the Java compiler version for a Java EE project</a>.</p>
-<p>To
-change the version of a facet in your project, complete the following steps:</p>
-</div>
-
-<ol class="id_steps">
-<li class="stepexpand"><span>In the Project Explorer view of the Java EE perspective, right-click the project
-and then select <span class="uicontrol">Properties</span>.</span></li>
-
-<li class="stepexpand"><span>Select the <span class="uicontrol">Project Facets</span> page in the in
-the Properties window.</span> This page lists the facets in the project
-and their versions.</li>
-
-<li class="stepexpand"><span>Click <span class="uicontrol">Modify Project</span> and click the facet
-you want to change.</span></li>
-
-<li class="stepexpand"><span>Select the version of the facet from the drop-down box next to
-the facet's name.</span></li>
-
-<li class="stepexpand"><span>Click <span class="uicontrol">Finish</span> to close the Modify Faceted
-Project window and then click <span class="uicontrol">OK</span>.</span></li>
-
-</ol>
-
-<div class="id_postreq"><p class="anchor_topicbottom" />
-</div>
-
-</div>
-
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="../topics/cfacets.html" title="Facets define characteristics and requirements for Java EE projects and are used as part of the runtime configuration.">Project facets</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="../topics/taddingfacet.html" title="This topic explains how to add a facet to an existing project in your workspace.">Adding a facet to a Java EE project</a></div>
-<div><a href="../topics/tchangejavalevel.html" title="You can change the version of Java used in a Java EE project by changing the value of the Java facet.">Changing the Java compiler version for a Java EE project</a></div>
-</div>
-</div>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tchangejavalevel.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/tchangejavalevel.dita
deleted file mode 100644
index f85e99e..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tchangejavalevel.dita
+++ /dev/null
@@ -1,41 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="tchangejavalevel" xml:lang="en-us">
-<title outputclass="id_title">Changing the <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> compiler version for a Java EE project</title>
-<shortdesc outputclass="id_shortdesc">You can change the version of <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> used
-in a Java EE project by changing the value of the <uicontrol>Java</uicontrol> facet.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>Java EE<indexterm>project compiler level</indexterm></indexterm>
-<indexterm>projects<indexterm>Java compiler level</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody outputclass="id_taskbody">
-<context outputclass="id_context"><p outputclass="anchor_topictop"></p> <p>The <uicontrol>Java</uicontrol> facet
-applies only to J2EE projects. To set the <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> compiler level of a non-Java EE project,
-such as a <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="Java">Java</tm> project, see <xref format="html" href="../../org.eclipse.jdt.doc.user/reference/ref-properties-compiler.htm"
-scope="peer">Java Compiler</xref>.</p><p>To change the <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> compiler
-version, complete the following steps:</p></context>
-<steps outputclass="id_steps">
-<step><cmd>In the Project Explorer view of the <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> EE perspective, right-click the project
-and then select <uicontrol>Properties</uicontrol>.</cmd></step>
-<step><cmd>Select the <uicontrol>Project Facets</uicontrol> page in the in
-the Properties window.</cmd><info> This page lists the facets in the project
-and their versions.</info></step>
-<step><cmd>Click <uicontrol>Modify Project</uicontrol>.</cmd></step>
-<step><cmd>Double click the version number next to the<uicontrol>Java</uicontrol> facet
-to select a different level of <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> compiler.</cmd></step>
-<step><cmd>Click <uicontrol>Finish</uicontrol> to close the Modify Faceted
-Project window and then click <uicontrol>OK</uicontrol>.</cmd></step>
-</steps>
-<postreq outputclass="id_postreq"><p outputclass="anchor_topicbottom"></p></postreq>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tchangejavalevel.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tchangejavalevel.html
deleted file mode 100644
index cdd9d4d..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tchangejavalevel.html
+++ /dev/null
@@ -1,76 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="task" name="DC.Type" />
-<meta name="DC.Title" content="Changing the Java compiler version for a Java EE project" />
-<meta name="abstract" content="You can change the version of Java used in a Java EE project by changing the value of the Java facet." />
-<meta name="description" content="You can change the version of Java used in a Java EE project by changing the value of the Java facet." />
-<meta content="Java EE, project compiler level, projects, Java compiler level" name="DC.subject" />
-<meta content="Java EE, project compiler level, projects, Java compiler level" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/taddingfacet.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tchangefacet.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cfacets.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="tchangejavalevel" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Changing the Java compiler version for a Java EE project</title>
-</head>
-<body id="tchangejavalevel"><a name="tchangejavalevel"><!-- --></a>
-
-
-<h1 class="id_title">Changing the Java compiler version for a Java EE project</h1>
-
-
-
-<div class="id_taskbody"><p class="id_shortdesc">You can change the version of Java™ used
-in a Java EE project by changing the value of the <span class="uicontrol">Java</span> facet.</p>
-
-<div class="id_context"><p class="anchor_topictop" />
- <p>The <span class="uicontrol">Java</span> facet
-applies only to J2EE projects. To set the Java compiler level of a non-Java EE project,
-such as a Java project, see <a href="../../org.eclipse.jdt.doc.user/reference/ref-properties-compiler.htm">Java Compiler</a>.</p>
-<p>To change the Java compiler
-version, complete the following steps:</p>
-</div>
-
-<ol class="id_steps">
-<li class="stepexpand"><span>In the Project Explorer view of the Java EE perspective, right-click the project
-and then select <span class="uicontrol">Properties</span>.</span></li>
-
-<li class="stepexpand"><span>Select the <span class="uicontrol">Project Facets</span> page in the in
-the Properties window.</span> This page lists the facets in the project
-and their versions.</li>
-
-<li class="stepexpand"><span>Click <span class="uicontrol">Modify Project</span>.</span></li>
-
-<li class="stepexpand"><span>Double click the version number next to the<span class="uicontrol">Java</span> facet
-to select a different level of Java compiler.</span></li>
-
-<li class="stepexpand"><span>Click <span class="uicontrol">Finish</span> to close the Modify Faceted
-Project window and then click <span class="uicontrol">OK</span>.</span></li>
-
-</ol>
-
-<div class="id_postreq"><p class="anchor_topicbottom" />
-</div>
-
-</div>
-
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="../topics/cfacets.html" title="Facets define characteristics and requirements for Java EE projects and are used as part of the runtime configuration.">Project facets</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="../topics/taddingfacet.html" title="This topic explains how to add a facet to an existing project in your workspace.">Adding a facet to a Java EE project</a></div>
-<div><a href="../topics/tchangefacet.html" title="You can change the version of a facet in a Java EE project by editing the facets for the project.">Changing the version of a facet</a></div>
-</div>
-</div>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tdefiningannotations.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/tdefiningannotations.dita
deleted file mode 100644
index fb4f6b8..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tdefiningannotations.dita
+++ /dev/null
@@ -1,79 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="tjimpear" xml:lang="en-us">
-<title outputclass="id_title">Defining and using annotations</title>
-<shortdesc outputclass="id_shortdesc">You can use the @Interface annotation
-to define your own annotation definition.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>Java EE 5<indexterm>annotations</indexterm><indexterm>defining</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody outputclass="id_taskbody">
-<context outputclass="id_context"> <p outputclass="anchor_topictop"></p><p><b>Defining
-your own annotations</b></p></context>
-<steps>
-<step><cmd>Use the @Interface annotation to define your own annotation definition:</cmd>
-<info><p><ul>
-<li>Annotation definitions resemble interface definitions</li>
-<li>Annotation method declarations have neither parameters nor <codeph>throws</codeph> clauses,
-and return one of the following elements:<ul>
-<li>primitives</li>
-<li>String</li>
-<li>Class</li>
-<li>enum</li>
-<li>array of the above types</li>
-</ul></li>
-<li>Methods may have default values</li>
-</ul></p><p><codeblock>public @interface CreatedBy{
- String name();
- String date();
- boolean contractor() default false;
-} </codeblock><codeblock>@CreatedBy(name = "Mary Smith",date="02/02/2008");
-public class MyClass{....} </codeblock></p></info></step>
-</steps>
-<postreq outputclass="id_postreq"><p><b>Meta-annotations</b>: Meta-annotations
-(annotations of annotations) provide additional information on how an annotation
-should be used:<ul>
-<li>@Target<ul>
-<li>Restricts the use of an annotation</li>
-<li>Single argument must be from Enum ElementType <ul>
-<li>{TYPE, FIELD,METHOD, PARAMETER, CONSTRUCTOR, LOCAL_VARIABLE, ANNOTATION_TYPE}</li>
-</ul></li>
-</ul></li>
-<li>@Retention<ul>
-<li>Indicates where the annotation information will be retained</li>
-<li>Single argument must be from Enum RetentionPolicy<ul>
-<li>{SOURCE, CLASS, RUNTIME}</li>
-</ul></li>
-</ul></li>
-<li>@Documented<ul>
-<li>Marker for annotations that should be included in Javadoc</li>
-</ul></li>
-<li>@Inherited<ul>
-<li>marker for Type annotations that are to be inherited by subtypes</li>
-</ul></li>
-</ul><b>Other built-in annotations</b>: <ul>
-<li>@Overrides<ul>
-<li>Applied to a method</li>
-<li>Indicates that the compiler should generate an error if the method does
-not actually override a superclass method.</li>
-</ul></li>
-<li>@Deprecated<ul>
-<li>Applied to a method</li>
-<li>Indicates that the compiler should generate a warning when the method
-is used externally</li>
-</ul></li>
-<li>@SuppressWarnings<ul>
-<li>Applies to a type or a method</li>
-<li>Indicates that the compiler should supress warnings for that element and
-all subelements<p><codeblock>@Deprecated
-public void oldMethod() {...}
-
-@ SupressWarnings
-public void yesIknowIuseDeprecatedMethods() {...}</codeblock></p></li>
-</ul></li>
-</ul></p><p outputclass="anchor_topicbottom"></p></postreq>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tdefiningannotations.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tdefiningannotations.html
deleted file mode 100644
index 2aa5ce6..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tdefiningannotations.html
+++ /dev/null
@@ -1,167 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="task" name="DC.Type" />
-<meta name="DC.Title" content="Defining and using annotations" />
-<meta name="abstract" content="You can use the @Interface annotation to define your own annotation definition." />
-<meta name="description" content="You can use the @Interface annotation to define your own annotation definition." />
-<meta content="Java EE 5, annotations, defining" name="DC.subject" />
-<meta content="Java EE 5, annotations, defining" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cannotations.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/ctypesofanno.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="tjimpear" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Defining and using annotations</title>
-</head>
-<body id="tjimpear"><a name="tjimpear"><!-- --></a>
-
-
-<h1 class="id_title">Defining and using annotations</h1>
-
-
-
-<div class="id_taskbody"><p class="id_shortdesc">You can use the @Interface annotation
-to define your own annotation definition.</p>
-
-<div class="id_context"> <p class="anchor_topictop" />
-<p><strong>Defining
-your own annotations</strong></p>
-</div>
-
-
-<div class="p"><span>Use the @Interface annotation to define your own annotation definition:</span>
- <div class="p"><ul>
-<li>Annotation definitions resemble interface definitions</li>
-
-<li>Annotation method declarations have neither parameters nor <samp class="codeph">throws</samp> clauses,
-and return one of the following elements:<ul>
-<li>primitives</li>
-
-<li>String</li>
-
-<li>Class</li>
-
-<li>enum</li>
-
-<li>array of the above types</li>
-
-</ul>
-</li>
-
-<li>Methods may have default values</li>
-
-</ul>
-</div>
-<div class="p"><pre>public @interface CreatedBy{
- String name();
- String date();
- boolean contractor() default false;
-} </pre>
-<pre>@CreatedBy(name = "Mary Smith",date="02/02/2008");
-public class MyClass{....} </pre>
-</div>
-</div>
-
-
-<div class="id_postreq"><div class="p"><strong>Meta-annotations</strong>: Meta-annotations
-(annotations of annotations) provide additional information on how an annotation
-should be used:<ul>
-<li>@Target<ul>
-<li>Restricts the use of an annotation</li>
-
-<li>Single argument must be from Enum ElementType <ul>
-<li>{TYPE, FIELD,METHOD, PARAMETER, CONSTRUCTOR, LOCAL_VARIABLE, ANNOTATION_TYPE}</li>
-
-</ul>
-</li>
-
-</ul>
-</li>
-
-<li>@Retention<ul>
-<li>Indicates where the annotation information will be retained</li>
-
-<li>Single argument must be from Enum RetentionPolicy<ul>
-<li>{SOURCE, CLASS, RUNTIME}</li>
-
-</ul>
-</li>
-
-</ul>
-</li>
-
-<li>@Documented<ul>
-<li>Marker for annotations that should be included in Javadoc</li>
-
-</ul>
-</li>
-
-<li>@Inherited<ul>
-<li>marker for Type annotations that are to be inherited by subtypes</li>
-
-</ul>
-</li>
-
-</ul>
-<strong>Other built-in annotations</strong>: <ul>
-<li>@Overrides<ul>
-<li>Applied to a method</li>
-
-<li>Indicates that the compiler should generate an error if the method does
-not actually override a superclass method.</li>
-
-</ul>
-</li>
-
-<li>@Deprecated<ul>
-<li>Applied to a method</li>
-
-<li>Indicates that the compiler should generate a warning when the method
-is used externally</li>
-
-</ul>
-</li>
-
-<li>@SuppressWarnings<ul>
-<li>Applies to a type or a method</li>
-
-<li>Indicates that the compiler should supress warnings for that element and
-all subelements<div class="p"><pre>@Deprecated
-public void oldMethod() {...}
-
-@ SupressWarnings
-public void yesIknowIuseDeprecatedMethods() {...}</pre>
-</div>
-</li>
-
-</ul>
-</li>
-
-</ul>
-</div>
-<p class="anchor_topicbottom" />
-</div>
-
-</div>
-
-<div>
-<ul class="ullinks">
-<li class="ulchildlink"><strong><a href="../topics/ctypesofanno.html">Types of annotations</a></strong><br />
-Java EE 5 defines a number of types or groups of annotations, defined in a number of Java Specification Requests (JSRs).</li>
-</ul>
-
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/cannotations.html" title="The goal of Java EE 5 platform development is to minimize the number of artifacts that you have to create and maintain, thereby simplifying the development process. Java EE 5 supports the injection of annotations into your source code, so that you can embed resources, dependencies, services, and life-cycle notifications in your source code, without having to maintain these artifacts elsewhere.">Java EE 5 support for annotations</a></div>
-</div>
-</div>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjappproj.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjappproj.dita
deleted file mode 100644
index 9639608..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjappproj.dita
+++ /dev/null
@@ -1,73 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="tjappproj" xml:lang="en-us">
-<title outputclass="id_title">Creating an application client project</title>
-<shortdesc outputclass="id_shortdesc">You can use a wizard to create a new
-application client project and add it to a new or existing enterprise application
-project.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>application client projects<indexterm>creating</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody outputclass="id_taskbody">
-<context outputclass="id_context"> <p outputclass="anchor_topictop"></p> <p>Application
-client projects contain the resources needed for application client modules
-and programs that run on networked client systems. An application client project
-is deployed as a JAR file.</p><p>Like the other types of projects, application
-client projects can contain one or more project facets, which represent units
-of functionality in the project. A new application client project should have
-the Application Client module facet. Depending on what you want to use the
-project for, you may want to enable other facets for the project.</p><p>To
-create a J2EE application client project, complete the following steps:</p></context>
-<steps outputclass="id_steps">
-<step><cmd>In the <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="Java">Java</tm> EE perspective, click <menucascade><uicontrol>File</uicontrol>
-<uicontrol>New</uicontrol><uicontrol>Project</uicontrol></menucascade>.</cmd>
-</step>
-<step><cmd>In the New Project Wizard, select <menucascade><uicontrol>Java
-EE</uicontrol><uicontrol>Application Client Project</uicontrol></menucascade> and
-click <uicontrol>Next</uicontrol>.</cmd></step>
-<step><cmd>In the <uicontrol>Project Name</uicontrol> field, type a name for
-the application client project. </cmd></step>
-<step importance="optional"><cmd>To change the default project location, clear
-the <uicontrol>Use default</uicontrol> check box under <uicontrol>Project
-contents</uicontrol> and select a new location with the <uicontrol>Browse</uicontrol> button.</cmd>
-<info>If you specify a non-default project location that is already being
-used by another project, the project creation will fail.<note>If you type
-a new EAR project name, the EAR project will be created in the default location
-with the lowest compatible Java EE 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.</note></info></step>
-<step importance="optional"><cmd>To add the new project to an enterprise application
-project, select the <uicontrol>Add project to an EAR</uicontrol> check box
-and select a project in the <uicontrol>EAR Project Name</uicontrol> list.</cmd>
-<info>If you choose to add the project to an existing EAR project, the <uicontrol>Target
-runtime</uicontrol> field becomes disabled because the target runtime for
-the new project will be the same as that of the EAR project.</info></step>
-<step><cmd>In the <uicontrol>Target runtime</uicontrol> field, select the
-target runtime for the project.</cmd></step>
-<step importance="optional"><cmd>To use a predefined configuration for your
-project, select a configuration in the <uicontrol>Configurations</uicontrol> list.
-You can click the <uicontrol>Modify</uicontrol> button to do the following:</cmd>
-<info><ul>
-<li>Customize project facets. Select the check boxes next to the facets you
-want the project to have and select a version number for each facet. Select
-a facet name to see more information about that facet in the <uicontrol>Details</uicontrol> tab.
-You can also choose a preset combination of facets from the <uicontrol>Configurations</uicontrol> list.</li>
-<li>Limit your project to be compatible with one or more runtimes. Click the <uicontrol>Show
-Runtimes</uicontrol> tab and select the runtimes that you want the project
-to be compatible with. </li>
-</ul>Click <uicontrol>Next</uicontrol>.</info></step>
-<step><cmd>In the <uicontrol>Source Folder</uicontrol> field, enter the name
-of the folder to use for source code. </cmd></step>
-<step importance="optional"><cmd>To create a default class for the module,
-select the <uicontrol>Create a default Main class</uicontrol> check box.</cmd>
-</step>
-<step><cmd>Click <uicontrol>Finish</uicontrol>.</cmd></step>
-</steps>
-<postreq outputclass="id_postreq"><p outputclass="anchor_topicbottom"></p></postreq>
-</taskbody>
-</task>
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 7768801..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjappproj.html
+++ /dev/null
@@ -1,132 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="task" name="DC.Type" />
-<meta name="DC.Title" content="Creating an application client project" />
-<meta name="abstract" content="You can use a wizard to create a new application client project and add it to a new or existing enterprise application project." />
-<meta name="description" content="You can use a wizard to create a new application client project and add it to a new or existing enterprise application project." />
-<meta content="application client projects, creating" name="DC.subject" />
-<meta content="application client projects, creating" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjexpapp.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjimpapp.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjarch.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjappcliproj.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjearproj.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cfacets.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="tjappproj" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Creating an application client project</title>
-</head>
-<body id="tjappproj"><a name="tjappproj"><!-- --></a>
-
-
-<h1 class="id_title">Creating an application client project</h1>
-
-
-
-<div class="id_taskbody"><p class="id_shortdesc">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="id_context"> <p class="anchor_topictop" />
- <p>Application
-client projects contain the resources needed for application client modules
-and programs that run on networked client systems. An application client project
-is deployed as a JAR file.</p>
-<p>Like the other types of projects, application
-client projects can contain one or more project facets, which represent units
-of functionality in the project. A new application client project should have
-the Application Client module facet. Depending on what you want to use the
-project for, you may want to enable other facets for the project.</p>
-<p>To
-create a J2EE application client project, complete the following steps:</p>
-</div>
-
-<ol class="id_steps">
-<li class="stepexpand"><span>In the Java™ EE perspective, click <span class="menucascade"><span class="uicontrol">File</span>
- > <span class="uicontrol">New</span> > <span class="uicontrol">Project</span></span>.</span>
-</li>
-
-<li class="stepexpand"><span>In the New Project Wizard, select <span class="menucascade"><span class="uicontrol">Java
-EE</span> > <span class="uicontrol">Application Client Project</span></span> and
-click <span class="uicontrol">Next</span>.</span></li>
-
-<li class="stepexpand"><span>In the <span class="uicontrol">Project Name</span> field, type a name for
-the application client project. </span></li>
-
-<li class="stepexpand"><strong>Optional: </strong><span>To change the default project location, clear
-the <span class="uicontrol">Use default</span> check box under <span class="uicontrol">Project
-contents</span> and select a new location with the <span class="uicontrol">Browse</span> button.</span>
- If you specify a non-default project location that is already being
-used by another project, the project creation will fail.<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 Java EE 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"><strong>Optional: </strong><span>To add the new project to an enterprise application
-project, select the <span class="uicontrol">Add project to an EAR</span> check box
-and select a project in the <span class="uicontrol">EAR Project Name</span> list.</span>
- If you choose to add the project to an existing EAR project, the <span class="uicontrol">Target
-runtime</span> field becomes disabled because the target runtime for
-the new project will be the same as that of the EAR project.</li>
-
-<li class="stepexpand"><span>In the <span class="uicontrol">Target runtime</span> field, select the
-target runtime for the project.</span></li>
-
-<li class="stepexpand"><strong>Optional: </strong><span>To use a predefined configuration for your
-project, select a configuration in the <span class="uicontrol">Configurations</span> list.
-You can click the <span class="uicontrol">Modify</span> button to do the following:</span>
- <ul>
-<li>Customize project facets. Select the check boxes next to the facets you
-want the project to have and select a version number for each facet. Select
-a facet name to see more information about that facet in the <span class="uicontrol">Details</span> tab.
-You can also choose a preset combination of facets from the <span class="uicontrol">Configurations</span> list.</li>
-
-<li>Limit your project to be compatible with one or more runtimes. Click the <span class="uicontrol">Show
-Runtimes</span> tab and select the runtimes that you want the project
-to be compatible with. </li>
-
-</ul>
-Click <span class="uicontrol">Next</span>.</li>
-
-<li class="stepexpand"><span>In the <span class="uicontrol">Source Folder</span> field, enter the name
-of the folder to use for source code. </span></li>
-
-<li class="stepexpand"><strong>Optional: </strong><span>To create a default class for the module,
-select the <span class="uicontrol">Create a default Main class</span> check box.</span>
-</li>
-
-<li class="stepexpand"><span>Click <span class="uicontrol">Finish</span>.</span></li>
-
-</ol>
-
-<div class="id_postreq"><p class="anchor_topicbottom" />
-</div>
-
-</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 applications.">J2EE architecture</a></div>
-<div><a href="../topics/cjappcliproj.html" title="Application client projects contain programs that run on networked client systems so the project can benefit from a server's tools.">Application client projects</a></div>
-<div><a href="../topics/cjearproj.html" title="An enterprise application project ties together the resources that are required to deploy a J2EE enterprise application.">Enterprise application projects</a></div>
-<div><a href="../topics/cfacets.html" title="Facets define characteristics and requirements for Java EE projects and are used as part of the runtime configuration.">Project facets</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.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjcircleb.dita
deleted file mode 100644
index de2003e..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjcircleb.dita
+++ /dev/null
@@ -1,41 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="tjcircleb" xml:lang="en-us">
-<title outputclass="id_title">Correcting cyclical dependencies after an EAR
-is imported</title>
-<shortdesc outputclass="id_shortdesc">You can resolve cyclical dependencies
-after an EAR is imported.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>dependencies<indexterm>correcting cyclical</indexterm></indexterm>
-<indexterm>EAR files<indexterm>correcting cyclical dependencies</indexterm></indexterm>
-<indexterm>projects<indexterm>correcting cyclical dependencies</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody outputclass="id_taskbody">
-<context outputclass="id_context"><p outputclass="anchor_topictop"></p> <p>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 <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> 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 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><p>To reorganize your project to correct cyclical dependencies,
-complete the following steps:</p></context>
-<steps outputclass="id_steps">
-<step><cmd>Identify all the classes within the JAR files that have cyclical
-dependencies and move those classes into a common <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> project or JAR file.</cmd></step>
-<step><cmd>Use the enterprise application editor to map utility JAR files
-to the common projects.</cmd></step>
-<step><cmd>For each module of the JAR in the application, use the JAR dependency
-editor or properties page to set dependencies only to the JAR files that are
-truly required.</cmd></step>
-</steps>
-<postreq outputclass="id_postreq"><p outputclass="anchor_topicbottom"></p></postreq>
-</taskbody>
-</task>
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 ab4d048..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjcircleb.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 content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="task" name="DC.Type" />
-<meta name="DC.Title" content="Correcting cyclical dependencies after an EAR is imported" />
-<meta name="abstract" content="You can resolve cyclical dependencies after an EAR is imported." />
-<meta name="description" content="You can resolve cyclical dependencies after an EAR is imported." />
-<meta content="dependencies, correcting cyclical, EAR files, correcting cyclical dependencies, projects" name="DC.subject" />
-<meta content="dependencies, correcting cyclical, EAR files, correcting cyclical dependencies, projects" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjimpear.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjcircle.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="tjcircleb" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Correcting cyclical dependencies after an EAR
-is imported</title>
-</head>
-<body id="tjcircleb"><a name="tjcircleb"><!-- --></a>
-
-
-<h1 class="id_title">Correcting cyclical dependencies after an EAR
-is imported</h1>
-
-
-
-<div class="id_taskbody"><p class="id_shortdesc">You can resolve cyclical dependencies
-after an EAR is imported.</p>
-
-<div class="id_context"><p class="anchor_topictop" />
- <p>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>
-<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>
-<p>To reorganize your project to correct cyclical dependencies,
-complete the following steps:</p>
-</div>
-
-<ol class="id_steps">
-<li><span>Identify all the classes within the JAR files that have cyclical
-dependencies and 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>For each module of the JAR in the application, use the JAR dependency
-editor or properties page to set dependencies only to the JAR files that are
-truly required.</span></li>
-
-</ol>
-
-<div class="id_postreq"><p class="anchor_topicbottom" />
-</div>
-
-</div>
-
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="../topics/cjcircle.html" title="A cyclical dependency between two or more modules in an enterprise application most commonly occurs when projects are imported from outside the Workbench.">Cyclical dependencies between Java EE 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.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjear.dita
deleted file mode 100644
index c89f633..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjear.dita
+++ /dev/null
@@ -1,82 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="tjear" xml:lang="en-us">
-<title outputclass="id_title">Creating an enterprise application project</title>
-<shortdesc outputclass="id_shortdesc">Using the wizard to create an enterprise
-application project allows you to package many web applications and modules
-in a project and deploy these modules as a J2EE enterprise application.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>enterprise applications<indexterm>projects<indexterm>creating</indexterm></indexterm></indexterm>
-<indexterm>J2EE<indexterm>enterprise application projects<indexterm>creating</indexterm></indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody outputclass="id_taskbody">
-<context outputclass="id_context"><p outputclass="anchor_topictop"></p> <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>Like the other types of projects, enterprise application projects
-can contain one or more project facets, which represent units of functionality
-in the project. To be deployed as an EAR file, the new project must have the
-EAR facet. Depending on what you want to use the project for, you may want
-to enable other facets for the project.</p><p conref="rjlimitcurrent.dita#rjlimitcurrent/limitation_ear_dbcs"></p><p>To
-create a J2EE enterprise application project, complete the following steps:</p></context>
-<steps outputclass="id_steps">
-<step><cmd>In the <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="Java">Java</tm> EE perspective, click <menucascade><uicontrol>File</uicontrol>
-<uicontrol>New</uicontrol><uicontrol>Project</uicontrol></menucascade>.</cmd>
-</step>
-<step><cmd>In the New Project Wizard, select <menucascade><uicontrol>J2EE</uicontrol>
-<uicontrol>Enterprise Application Project</uicontrol></menucascade> and click <uicontrol>Next</uicontrol>.</cmd>
-</step>
-<step><cmd>In the <uicontrol>Project Name</uicontrol> field, type a name for
-the new project. </cmd></step>
-<step importance="optional"><cmd>To change the default project location, clear
-the <uicontrol>Use default</uicontrol> check box under <uicontrol>Project
-contents</uicontrol> and select a new location with the <uicontrol>Browse</uicontrol> button.</cmd>
-</step>
-<step><cmd>In the <uicontrol>Target runtime</uicontrol> field, select the
-target runtime for the project.</cmd><info>You can click the <uicontrol>New</uicontrol> button
-to create a new runtime for the project to use.</info></step>
-<step importance="optional"><cmd>To use a predefined configuration for your
-project, select a configuration in the <uicontrol>Configuration</uicontrol> list.
-You can click the <uicontrol>Modify</uicontrol> button to do the following:</cmd>
-<info><ul>
-<li>Customize project facets. Select the check boxes next to the facets you
-want the project to have and select a version number for each facet. Select
-a facet name to see more information about that facet in the <uicontrol>Details</uicontrol> tab.
-You can also choose a preset combination of facets from the <uicontrol>Configurations</uicontrol> list.</li>
-<li>Limit your project to be compatible with one or more runtimes. Click the <uicontrol>Show
-Runtimes</uicontrol> tab and select the runtimes that you want the project
-to be compatible with. </li>
-</ul>Click <uicontrol>Next</uicontrol>.</info></step>
-<step><cmd>On the J2EE Modules to Add to the EAR page of the wizard, select
-the existing modules that you want to add to the new enterprise application
-project.</cmd></step>
-<step importance="optional"><cmd>To create new modules to add to the project,
-click the <uicontrol>New Module</uicontrol> button to do one of the following:</cmd>
-<choicetable keycol="0">
-<chrow><choption>Creating one module</choption><chdesc>Clear the <uicontrol>Create
-default modules</uicontrol> check box, select the type of module you want
-to create, click <uicontrol>Next</uicontrol> and follow the New Project wizard
-for that type of project.</chdesc></chrow>
-<chrow><choption>Creating two or more modules</choption><chdesc>Select the <uicontrol>Create
-default modules</uicontrol> check box, select the check boxes for each type
-of project you want to create, and click <uicontrol>Finish</uicontrol>.</chdesc>
-</chrow>
-</choicetable>
-<info>You can enter a name for each module. Each of these modules will have
-the default settings for that type of project and they will have the same
-server target as the new enterprise application.</info></step>
-<step><cmd>Click <uicontrol>Finish</uicontrol>.</cmd></step>
-</steps>
-<postreq outputclass="id_postreq"><p outputclass="anchor_topicbottom"></p></postreq>
-</taskbody>
-</task>
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 4780da1..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjear.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 content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="task" name="DC.Type" />
-<meta name="DC.Title" content="Creating an enterprise application project" />
-<meta name="abstract" content="Using the wizard to create an enterprise application project allows you to package many web applications and modules in a project and deploy these modules as a J2EE enterprise application." />
-<meta name="description" content="Using the wizard to create an enterprise application project allows you to package many web applications and modules in a project and deploy these modules as a J2EE enterprise application." />
-<meta content="enterprise applications, projects, creating, J2EE, enterprise application projects" name="DC.subject" />
-<meta content="enterprise applications, projects, creating, J2EE, enterprise application projects" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjimpear.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjexpear.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjarch.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjearproj.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjearproj.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cfacets.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="tjear" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Creating an enterprise application project</title>
-</head>
-<body id="tjear"><a name="tjear"><!-- --></a>
-
-
-<h1 class="id_title">Creating an enterprise application project</h1>
-
-
-
-<div class="id_taskbody"><p class="id_shortdesc">Using the wizard to create an enterprise
-application project allows you to package many web applications and modules
-in a project and deploy these modules as a J2EE enterprise application.</p>
-
-<div class="id_context"><p class="anchor_topictop" />
- <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>Like the other types of projects, enterprise application projects
-can contain one or more project facets, which represent units of functionality
-in the project. To be deployed as an EAR file, the new project must have the
-EAR facet. Depending on what you want to use the project for, you may want
-to enable other facets for the project.</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, complete the following steps:</p>
-</div>
-
-<ol class="id_steps">
-<li class="stepexpand"><span>In the Java™ EE perspective, click <span class="menucascade"><span class="uicontrol">File</span>
- > <span class="uicontrol">New</span> > <span class="uicontrol">Project</span></span>.</span>
-</li>
-
-<li class="stepexpand"><span>In the New Project Wizard, select <span class="menucascade"><span class="uicontrol">J2EE</span>
- > <span class="uicontrol">Enterprise Application Project</span></span> and click <span class="uicontrol">Next</span>.</span>
-</li>
-
-<li class="stepexpand"><span>In the <span class="uicontrol">Project Name</span> field, type a name for
-the new project. </span></li>
-
-<li class="stepexpand"><strong>Optional: </strong><span>To change the default project location, clear
-the <span class="uicontrol">Use default</span> check box under <span class="uicontrol">Project
-contents</span> and select a new location with the <span class="uicontrol">Browse</span> button.</span>
-</li>
-
-<li class="stepexpand"><span>In the <span class="uicontrol">Target runtime</span> field, select the
-target runtime for the project.</span> You can click the <span class="uicontrol">New</span> button
-to create a new runtime for the project to use.</li>
-
-<li class="stepexpand"><strong>Optional: </strong><span>To use a predefined configuration for your
-project, select a configuration in the <span class="uicontrol">Configuration</span> list.
-You can click the <span class="uicontrol">Modify</span> button to do the following:</span>
- <ul>
-<li>Customize project facets. Select the check boxes next to the facets you
-want the project to have and select a version number for each facet. Select
-a facet name to see more information about that facet in the <span class="uicontrol">Details</span> tab.
-You can also choose a preset combination of facets from the <span class="uicontrol">Configurations</span> list.</li>
-
-<li>Limit your project to be compatible with one or more runtimes. Click the <span class="uicontrol">Show
-Runtimes</span> tab and select the runtimes that you want the project
-to be compatible with. </li>
-
-</ul>
-Click <span class="uicontrol">Next</span>.</li>
-
-<li class="stepexpand"><span>On the J2EE Modules to Add to the EAR page of the wizard, select
-the existing modules that you want to add to the new enterprise application
-project.</span></li>
-
-<li class="stepexpand"><strong>Optional: </strong><span>To create new modules to add to the project,
-click the <span class="uicontrol">New Module</span> button to do one of the following:</span>
-
-<table class="choicetableborder" summary="" cellspacing="0" cellpadding="4" rules="rows" frame="hsides" border="1">
-<thead><tr><th valign="bottom" id="N1016C-option" align="left">Option</th>
-<th valign="bottom" id="N1016C-desc" align="left">Description</th></tr></thead>
-<tbody>
-<tr><td valign="top" headers="N1016C-option" id="N10176">Creating one module</td>
-<td valign="top" headers="N1016C-desc N10176">Clear the <span class="uicontrol">Create
-default modules</span> check box, select the type of module you want
-to create, click <span class="uicontrol">Next</span> and follow the New Project wizard
-for that type of project.</td>
-</tr>
-
-<tr><td valign="top" headers="N1016C-option" id="N10191">Creating two or more modules</td>
-<td valign="top" headers="N1016C-desc N10191">Select the <span class="uicontrol">Create
-default modules</span> check box, select the check boxes for each type
-of project you want to create, and click <span class="uicontrol">Finish</span>.</td>
-
-</tr>
-
-</tbody></table>
-
- You can enter a name for each module. Each of these modules will have
-the default settings for that type of project and they will have the same
-server target as the new enterprise application.</li>
-
-<li class="stepexpand"><span>Click <span class="uicontrol">Finish</span>.</span></li>
-
-</ol>
-
-<div class="id_postreq"><p class="anchor_topicbottom" />
-</div>
-
-</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 applications.">J2EE architecture</a></div>
-<div><a href="../topics/cjearproj.html" title="An enterprise application project ties together the resources that are required to deploy a J2EE enterprise application.">Enterprise application projects</a></div>
-<div><a href="../topics/cfacets.html" title="Facets define characteristics and requirements for Java EE projects and are used as part of the runtime configuration.">Project facets</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.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexpapp.dita
deleted file mode 100644
index d99519b..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexpapp.dita
+++ /dev/null
@@ -1,38 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="tjexpapp" xml:lang="en-us">
-<title outputclass="id_title">Exporting an application client project</title>
-<shortdesc outputclass="id_shortdesc">You can export an application client
-project as a JAR file.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>application client projects<indexterm>exporting</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody outputclass="id_taskbody">
-<context outputclass="id_context"><p outputclass="anchor_topictop"></p> <p>To
-export an application client project from the workbench, complete the following
-steps:</p></context>
-<steps outputclass="id_steps">
-<step><cmd>In the <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="Java">Java</tm> EE perspective, click <menucascade><uicontrol>File</uicontrol>
-<uicontrol>Export</uicontrol></menucascade>.</cmd></step>
-<step><cmd>Under <uicontrol>Select an export destination</uicontrol>, click <menucascade>
-<uicontrol>J2EE</uicontrol><uicontrol>App Client JAR file</uicontrol></menucascade>,
-and then click <uicontrol>Next</uicontrol>.</cmd></step>
-<step><cmd>In the <uicontrol>Application Client project</uicontrol> list,
-select the application client project you want to export.</cmd></step>
-<step><cmd>In the <uicontrol>Destination</uicontrol> field, enter the full
-path and JAR file name where you want to export the application client project.</cmd>
-</step>
-<step importance="optional"><cmd>To export source files, select the <uicontrol>Export
-source files</uicontrol> check box.</cmd></step>
-<step importance="optional"><cmd>If you are exporting to an existing JAR file
-and you do not want to be warned about overwriting it, select the <uicontrol>Overwrite
-existing file</uicontrol> check box.</cmd></step>
-<step><cmd>Click <uicontrol>Finish</uicontrol>.</cmd></step>
-</steps>
-<postreq outputclass="id_postreq"><p outputclass="anchor_topicbottom"></p></postreq>
-</taskbody>
-</task>
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 acf2bf7..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexpapp.html
+++ /dev/null
@@ -1,84 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="task" name="DC.Type" />
-<meta name="DC.Title" content="Exporting an application client project" />
-<meta name="abstract" content="You can export an application client project as a JAR file." />
-<meta name="description" content="You can export an application client project as a JAR file." />
-<meta content="application client projects, exporting" name="DC.subject" />
-<meta content="application client projects, exporting" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjappproj.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjimpapp.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjarch.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjappcliproj.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="tjexpapp" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Exporting an application client project</title>
-</head>
-<body id="tjexpapp"><a name="tjexpapp"><!-- --></a>
-
-
-<h1 class="id_title">Exporting an application client project</h1>
-
-
-
-<div class="id_taskbody"><p class="id_shortdesc">You can export an application client
-project as a JAR file.</p>
-
-<div class="id_context"><p class="anchor_topictop" />
- <p>To
-export an application client project from the workbench, complete the following
-steps:</p>
-</div>
-
-<ol class="id_steps">
-<li><span>In the Java™ EE perspective, click <span class="menucascade"><span class="uicontrol">File</span>
- > <span class="uicontrol">Export</span></span>.</span></li>
-
-<li><span>Under <span class="uicontrol">Select an export destination</span>, click <span class="menucascade">
-<span class="uicontrol">J2EE</span> > <span class="uicontrol">App Client JAR file</span></span>,
-and then click <span class="uicontrol">Next</span>.</span></li>
-
-<li><span>In the <span class="uicontrol">Application Client project</span> list,
-select the application client project you want to export.</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.</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 the <span class="uicontrol">Overwrite
-existing file</span> check box.</span></li>
-
-<li><span>Click <span class="uicontrol">Finish</span>.</span></li>
-
-</ol>
-
-<div class="id_postreq"><p class="anchor_topicbottom" />
-</div>
-
-</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 applications.">J2EE architecture</a></div>
-<div><a href="../topics/cjappcliproj.html" title="Application client projects contain programs that run on networked client systems so the project can benefit from a server's tools.">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.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexpear.dita
deleted file mode 100644
index c51e5b2..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexpear.dita
+++ /dev/null
@@ -1,48 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="tjexpear" xml:lang="en-us">
-<title outputclass="id_title">Exporting an enterprise application into an
-EAR file</title>
-<shortdesc outputclass="id_shortdesc">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.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>EAR<indexterm>files<indexterm>exporting</indexterm></indexterm></indexterm>
-<indexterm>enterprise applications<indexterm>projects<indexterm>exporting</indexterm></indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody outputclass="id_taskbody">
-<context outputclass="id_context"> <p outputclass="anchor_topictop"></p> <p>To
-export an enterprise application project into an EAR file, complete the following
-steps:</p></context>
-<steps outputclass="id_steps">
-<step><cmd>In the <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="Java">Java</tm> EE perspective, click <menucascade><uicontrol>File</uicontrol>
-<uicontrol>Export</uicontrol></menucascade>.</cmd></step>
-<step><cmd>Under <uicontrol>Select an export destination</uicontrol>, click <menucascade>
-<uicontrol>J2EE</uicontrol><uicontrol>EAR file</uicontrol></menucascade>,
-and then click <uicontrol>Next</uicontrol>.</cmd></step>
-<step><cmd>In the <uicontrol>EAR project</uicontrol> list, select the enterprise
-application project you want to export.</cmd></step>
-<step><cmd>In the <uicontrol>Destination</uicontrol> field, enter the full
-path and EAR file name where you want to export the enterprise application
-project that is selected in the <uicontrol>EAR application</uicontrol> field.</cmd>
-</step>
-<step importance="optional"><cmd>To export source files, select the <uicontrol>Export
-source files</uicontrol> check box.</cmd></step>
-<step importance="optional"><cmd>If you are exporting to an existing EAR file
-and you do not want to be warned about overwriting it, select the <uicontrol>Overwrite
-existing file</uicontrol> check box.</cmd></step>
-<step><cmd>Click <uicontrol>Finish</uicontrol>.</cmd></step>
-</steps>
-<result outputclass="id_result">The wizard exports the contents of the EAR
-project to the specified EAR file. Additionally, for each project that corresponds
-to a module or utility JAR in the application, the project contents are exported
-into a nested module or JAR file in the EAR file. If any unsaved changes exist
-on any of the files in any of the referenced projects, you are prompted to
-save these files prior to export.</result>
-<postreq outputclass="id_postreq"><p outputclass="anchor_topicbottom"></p></postreq>
-</taskbody>
-</task>
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 bee3bf5..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexpear.html
+++ /dev/null
@@ -1,95 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="task" name="DC.Type" />
-<meta name="DC.Title" content="Exporting an enterprise application into an EAR file" />
-<meta name="abstract" content="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." />
-<meta name="description" content="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." />
-<meta content="EAR, files, exporting, enterprise applications, projects" name="DC.subject" />
-<meta content="EAR, files, exporting, enterprise applications, projects" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjear.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjimpear.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjarch.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjearproj.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="tjexpear" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Exporting an enterprise application into an
-EAR file</title>
-</head>
-<body id="tjexpear"><a name="tjexpear"><!-- --></a>
-
-
-<h1 class="id_title">Exporting an enterprise application into an
-EAR file</h1>
-
-
-
-<div class="id_taskbody"><p class="id_shortdesc">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.</p>
-
-<div class="id_context"> <p class="anchor_topictop" />
- <p>To
-export an enterprise application project into an EAR file, complete the following
-steps:</p>
-</div>
-
-<ol class="id_steps">
-<li><span>In the Java™ EE perspective, click <span class="menucascade"><span class="uicontrol">File</span>
- > <span class="uicontrol">Export</span></span>.</span></li>
-
-<li><span>Under <span class="uicontrol">Select an export destination</span>, click <span class="menucascade">
-<span class="uicontrol">J2EE</span> > <span class="uicontrol">EAR file</span></span>,
-and then click <span class="uicontrol">Next</span>.</span></li>
-
-<li><span>In the <span class="uicontrol">EAR project</span> list, select the enterprise
-application project you want to export.</span></li>
-
-<li><span>In the <span class="uicontrol">Destination</span> field, enter the full
-path and EAR file name where you want to export the enterprise application
-project that is selected in the <span class="uicontrol">EAR application</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 EAR file
-and you do not want to be warned about overwriting it, select the <span class="uicontrol">Overwrite
-existing file</span> check box.</span></li>
-
-<li><span>Click <span class="uicontrol">Finish</span>.</span></li>
-
-</ol>
-
-<div class="id_result">The wizard exports the contents of the EAR
-project to the specified EAR file. Additionally, for each project that corresponds
-to a module or utility JAR in the application, the project contents are exported
-into a nested module or JAR file in the EAR file. If any unsaved changes exist
-on any of the files in any of the referenced projects, you are prompted to
-save these files prior to export.</div>
-
-<div class="id_postreq"><p class="anchor_topicbottom" />
-</div>
-
-</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 applications.">J2EE architecture</a></div>
-<div><a href="../topics/cjearproj.html" title="An enterprise application project ties together the resources that are required to deploy a J2EE enterprise application.">Enterprise application projects</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="../topics/tjear.html" title="Using the wizard to create an enterprise application project allows you to package many web applications and modules in a project and deploy these modules as a J2EE enterprise application.">Creating an enterprise application project</a></div>
-<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/tjexprar.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexprar.dita
deleted file mode 100644
index aa2405b..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexprar.dita
+++ /dev/null
@@ -1,40 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="tjexprar" xml:lang="en-us">
-<title outputclass="id_title">Exporting connector projects to RAR files</title>
-<shortdesc outputclass="id_shortdesc">You can export a connector project to
-a RAR file in preparation for deploying it to a server.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>connector projects<indexterm>exporting</indexterm></indexterm>
-<indexterm>RAR files<indexterm>exporting</indexterm></indexterm></keywords>
-</metadata></prolog>
-<taskbody outputclass="id_taskbody">
-<context outputclass="id_context"> <p outputclass="anchor_topictop"></p> <p>To
-export the contents of a connector project to a RAR file, complete the following
-steps:</p></context>
-<steps outputclass="id_steps">
-<step><cmd>In the <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="Java">Java</tm> EE perspective, click <menucascade><uicontrol>File</uicontrol>
-<uicontrol>Export</uicontrol></menucascade>.</cmd></step>
-<step><cmd>Under <uicontrol>Select an export destination</uicontrol>, click <menucascade>
-<uicontrol>J2EE</uicontrol><uicontrol>RAR file</uicontrol></menucascade>,
-and then click <uicontrol>Next</uicontrol>.</cmd></step>
-<step><cmd>In the <uicontrol>Connector project</uicontrol> list, select the
-connector project to export.</cmd></step>
-<step><cmd>In the <uicontrol>Destination</uicontrol> field, enter the full
-path and RAR file name where you want to export the connector project.</cmd>
-</step>
-<step importance="optional"><cmd>To export source files, select the <uicontrol>Export
-source files</uicontrol> check box.</cmd></step>
-<step importance="optional"><cmd>If you are exporting to an existing RAR file
-and you do not want to be warned about overwriting it, select the <uicontrol>Overwrite
-existing file</uicontrol> check box.</cmd></step>
-<step><cmd>Click <uicontrol>Finish</uicontrol>.</cmd><stepresult outputclass="id_result">The
-wizard exports the contents of the RAR project to the specified RAR file.</stepresult>
-</step>
-</steps>
-<postreq outputclass="id_postreq"><p outputclass="anchor_topicbottom"></p></postreq>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexprar.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexprar.html
deleted file mode 100644
index 0a50592..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexprar.html
+++ /dev/null
@@ -1,79 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="task" name="DC.Type" />
-<meta name="DC.Title" content="Exporting connector projects to RAR files" />
-<meta name="abstract" content="You can export a connector project to a RAR file in preparation for deploying it to a server." />
-<meta name="description" content="You can export a connector project to a RAR file in preparation for deploying it to a server." />
-<meta content="connector projects, exporting, RAR files" name="DC.subject" />
-<meta content="connector projects, exporting, RAR files" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/ph-importexport.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="tjexprar" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Exporting connector projects to RAR files</title>
-</head>
-<body id="tjexprar"><a name="tjexprar"><!-- --></a>
-
-
-<h1 class="id_title">Exporting connector projects to RAR files</h1>
-
-
-
-<div class="id_taskbody"><p class="id_shortdesc">You can export a connector project to
-a RAR file in preparation for deploying it to a server.</p>
-
-<div class="id_context"> <p class="anchor_topictop" />
- <p>To
-export the contents of a connector project to a RAR file, complete the following
-steps:</p>
-</div>
-
-<ol class="id_steps">
-<li class="stepexpand"><span>In the Java™ EE perspective, click <span class="menucascade"><span class="uicontrol">File</span>
- > <span class="uicontrol">Export</span></span>.</span></li>
-
-<li class="stepexpand"><span>Under <span class="uicontrol">Select an export destination</span>, click <span class="menucascade">
-<span class="uicontrol">J2EE</span> > <span class="uicontrol">RAR file</span></span>,
-and then click <span class="uicontrol">Next</span>.</span></li>
-
-<li class="stepexpand"><span>In the <span class="uicontrol">Connector project</span> list, select the
-connector project to export.</span></li>
-
-<li class="stepexpand"><span>In the <span class="uicontrol">Destination</span> field, enter the full
-path and RAR file name where you want to export the connector project.</span>
-</li>
-
-<li class="stepexpand"><strong>Optional: </strong><span>To export source files, select the <span class="uicontrol">Export
-source files</span> check box.</span></li>
-
-<li class="stepexpand"><strong>Optional: </strong><span>If you are exporting to an existing RAR file
-and you do not want to be warned about overwriting it, select the <span class="uicontrol">Overwrite
-existing file</span> check box.</span></li>
-
-<li class="stepexpand"><span>Click <span class="uicontrol">Finish</span>.</span> The
-wizard exports the contents of the RAR project to the specified RAR file.
-</li>
-
-</ol>
-
-<div class="id_postreq"><p class="anchor_topicbottom" />
-</div>
-
-</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>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimpapp.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimpapp.dita
deleted file mode 100644
index 78a47c1..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimpapp.dita
+++ /dev/null
@@ -1,51 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="tjimpapp" xml:lang="en-us">
-<title outputclass="id_title">Importing an application client JAR file</title>
-<shortdesc outputclass="id_shortdesc">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.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>application client projects<indexterm>importing</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody outputclass="id_taskbody">
-<context outputclass="id_context"> <p outputclass="anchor_topictop"></p> <p>To
-import an application client JAR file using the wizard, complete the following
-steps:</p></context>
-<steps outputclass="id_steps">
-<step><cmd>In the <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="Java">Java</tm> EE perspective, click <menucascade><uicontrol>File</uicontrol>
-<uicontrol>Import</uicontrol></menucascade>.</cmd></step>
-<step><cmd>Under <uicontrol>Select an import source</uicontrol>, click <menucascade>
-<uicontrol>J2EE</uicontrol><uicontrol>App Client JAR file</uicontrol></menucascade>.</cmd>
-</step>
-<step><cmd>In the <uicontrol>Application Client file</uicontrol> field, enter
-the location and name of the application client JAR file that you want to
-import.</cmd></step>
-<step><cmd>In the <uicontrol>Application Client project</uicontrol> field,
-type a new project name or accept the default project name. </cmd><info>The
-application client project will be created based on the version of the application
-client JAR file, and it will use the default location.</info></step>
-<step><cmd>In the <uicontrol>Target runtime</uicontrol> 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.</cmd></step>
-<step importance="optional"><cmd>To add the new module to an enterprise application
-project, select the <uicontrol>Add project to an EAR</uicontrol> check box
-and then select an existing enterprise application project from the list or
-create a new one by clicking <uicontrol>New</uicontrol>.</cmd><info><note>If
-you type a new enterprise application project name, the enterprise application
-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.</note></info>
-</step>
-<step><cmd>Click <uicontrol>Finish</uicontrol> to import the application client
-JAR file.</cmd></step>
-</steps>
-<postreq outputclass="id_postreq"><p outputclass="anchor_topicbottom"></p></postreq>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimpapp.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimpapp.html
deleted file mode 100644
index 6cbdb2a..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimpapp.html
+++ /dev/null
@@ -1,98 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="task" name="DC.Type" />
-<meta name="DC.Title" content="Importing an application client JAR file" />
-<meta name="abstract" content="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." />
-<meta name="description" content="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." />
-<meta content="application client projects, importing" name="DC.subject" />
-<meta content="application client projects, importing" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjappproj.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjexpapp.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjarch.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjappcliproj.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="tjimpapp" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Importing an application client JAR file</title>
-</head>
-<body id="tjimpapp"><a name="tjimpapp"><!-- --></a>
-
-
-<h1 class="id_title">Importing an application client JAR file</h1>
-
-
-
-<div class="id_taskbody"><p class="id_shortdesc">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.</p>
-
-<div class="id_context"> <p class="anchor_topictop" />
- <p>To
-import an application client JAR file using the wizard, complete the following
-steps:</p>
-</div>
-
-<ol class="id_steps">
-<li class="stepexpand"><span>In the Java™ EE perspective, click <span class="menucascade"><span class="uicontrol">File</span>
- > <span class="uicontrol">Import</span></span>.</span></li>
-
-<li class="stepexpand"><span>Under <span class="uicontrol">Select an import source</span>, click <span class="menucascade">
-<span class="uicontrol">J2EE</span> > <span class="uicontrol">App Client JAR file</span></span>.</span>
-</li>
-
-<li class="stepexpand"><span>In the <span class="uicontrol">Application Client file</span> field, enter
-the location and name of the application client JAR file that you want to
-import.</span></li>
-
-<li class="stepexpand"><span>In the <span class="uicontrol">Application Client project</span> field,
-type a new project name or accept the default project name. </span> The
-application client project will be created based on the version of the application
-client JAR file, and it will use the default location.</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"><strong>Optional: </strong><span>To add the new module to an enterprise application
-project, select the <span class="uicontrol">Add project to an EAR</span> check box
-and then select an existing enterprise application project from the list or
-create a new one by clicking <span class="uicontrol">New</span>.</span> <div class="note"><span class="notetitle">Note:</span> If
-you type a new enterprise application project name, the enterprise application
-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> to import the application client
-JAR file.</span></li>
-
-</ol>
-
-<div class="id_postreq"><p class="anchor_topicbottom" />
-</div>
-
-</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 applications.">J2EE architecture</a></div>
-<div><a href="../topics/cjappcliproj.html" title="Application client projects contain programs that run on networked client systems so the project can benefit from a server's tools.">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/tjexpapp.html" title="You can export an application client project as a JAR file.">Exporting an application client project</a></div>
-</div>
-</div>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimpear.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimpear.dita
deleted file mode 100644
index cd6c4ae..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimpear.dita
+++ /dev/null
@@ -1,51 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="tjimpear" xml:lang="en-us">
-<title outputclass="id_title">Importing an enterprise application EAR file</title>
-<shortdesc outputclass="id_shortdesc">Enterprise application projects are
-deployed into EAR files. You can import an enterprise application project
-by importing it from a deployed EAR file.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>EAR<indexterm>files<indexterm>importing</indexterm></indexterm></indexterm>
-<indexterm>enterprise applications<indexterm>projects<indexterm>importing</indexterm></indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody outputclass="id_taskbody">
-<context outputclass="id_context"> <p outputclass="anchor_topictop"></p> <p>You
-can also choose to import utility JAR files as utility <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> projects.
-You can also use the wizard to change the new project names for the EAR file
-and modules that will be imported.</p><p>To import an EAR file using the wizard,
-complete the following steps:</p></context>
-<steps outputclass="id_steps">
-<step><cmd>In the <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="Java">Java</tm> EE perspective, click <menucascade><uicontrol>File</uicontrol>
-<uicontrol>Import</uicontrol></menucascade>.</cmd></step>
-<step><cmd>Under <uicontrol>Select an import source</uicontrol>, click <menucascade>
-<uicontrol>J2EE</uicontrol><uicontrol>EAR file</uicontrol></menucascade> and
-click <uicontrol>Next</uicontrol>.</cmd></step>
-<step><cmd>In the <uicontrol>EAR file</uicontrol> field, enter the location
-and name of the application client JAR file that you want to import. </cmd>
-</step>
-<step><cmd>In the <uicontrol>EAR project</uicontrol> field, accept the default
-project name or type a new project name. </cmd></step>
-<step><cmd>In the <uicontrol>Target runtime</uicontrol> drop-down list, select
-the application server that you want to target for your development.</cmd>
-<info>This selection affects the run time settings by modifying the class
-path entries for the project. Click <uicontrol>Next</uicontrol>.</info></step>
-<step><cmd>Select any utility JAR files from the project that you want to
-import as utility projects.</cmd></step>
-<step><cmd>In the <uicontrol>Module Root Location</uicontrol> field, specify
-the root directory for all of the projects that will be imported or created
-during import, and click <uicontrol>Next</uicontrol>.</cmd></step>
-<step><cmd>On the EAR Module and Utility JAR Projects page, select the projects
-that you want to import with the EAR file. You can edit the new project name
-for each module and utility project to be imported.</cmd><info></info></step>
-<step><cmd>Click <uicontrol>Finish</uicontrol> to import the contents of the
-EAR file.</cmd></step>
-</steps>
-<postreq outputclass="id_postreq"><p outputclass="anchor_topicbottom"></p></postreq>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimpear.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimpear.html
deleted file mode 100644
index e179f22..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimpear.html
+++ /dev/null
@@ -1,102 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="task" name="DC.Type" />
-<meta name="DC.Title" content="Importing an enterprise application EAR file" />
-<meta name="abstract" content="Enterprise application projects are deployed into EAR files. You can import an enterprise application project by importing it from a deployed EAR file." />
-<meta name="description" content="Enterprise application projects are deployed into EAR files. You can import an enterprise application project by importing it from a deployed EAR file." />
-<meta content="EAR, files, importing, enterprise applications, projects" name="DC.subject" />
-<meta content="EAR, files, importing, enterprise applications, projects" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjear.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjexpear.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjarch.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjearproj.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjcircleb.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjcircle.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="tjimpear" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Importing an enterprise application EAR file</title>
-</head>
-<body id="tjimpear"><a name="tjimpear"><!-- --></a>
-
-
-<h1 class="id_title">Importing an enterprise application EAR file</h1>
-
-
-
-<div class="id_taskbody"><p class="id_shortdesc">Enterprise application projects are
-deployed into EAR files. You can import an enterprise application project
-by importing it from a deployed EAR file.</p>
-
-<div class="id_context"> <p class="anchor_topictop" />
- <p>You
-can also choose to import utility JAR files as utility Java™ projects.
-You can also use the wizard to change the new project names for the EAR file
-and modules that will be imported.</p>
-<p>To import an EAR file using the wizard,
-complete the following steps:</p>
-</div>
-
-<ol class="id_steps">
-<li class="stepexpand"><span>In the Java EE perspective, click <span class="menucascade"><span class="uicontrol">File</span>
- > <span class="uicontrol">Import</span></span>.</span></li>
-
-<li class="stepexpand"><span>Under <span class="uicontrol">Select an import source</span>, click <span class="menucascade">
-<span class="uicontrol">J2EE</span> > <span class="uicontrol">EAR file</span></span> and
-click <span class="uicontrol">Next</span>.</span></li>
-
-<li class="stepexpand"><span>In the <span class="uicontrol">EAR file</span> field, enter the location
-and name of the application client JAR file that you want to import. </span>
-</li>
-
-<li class="stepexpand"><span>In the <span class="uicontrol">EAR project</span> field, accept the default
-project name or type a new project name. </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>
- This selection affects the run time settings by modifying the class
-path entries for the project. Click <span class="uicontrol">Next</span>.</li>
-
-<li class="stepexpand"><span>Select any utility JAR files from the project that you want to
-import as utility projects.</span></li>
-
-<li class="stepexpand"><span>In the <span class="uicontrol">Module Root Location</span> field, specify
-the root directory for all of the projects that will be imported or created
-during import, and click <span class="uicontrol">Next</span>.</span></li>
-
-<li class="stepexpand"><span>On the EAR Module and Utility JAR Projects page, select the projects
-that you want to import with the EAR file. You can edit the new project name
-for each module and utility project to be imported.</span> </li>
-
-<li class="stepexpand"><span>Click <span class="uicontrol">Finish</span> to import the contents of the
-EAR file.</span></li>
-
-</ol>
-
-<div class="id_postreq"><p class="anchor_topicbottom" />
-</div>
-
-</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 applications.">J2EE architecture</a></div>
-<div><a href="../topics/cjearproj.html" title="An enterprise application project ties together the resources that are required to deploy a J2EE enterprise application.">Enterprise application projects</a></div>
-<div><a href="../topics/cjcircle.html" title="A cyclical dependency between two or more modules in an enterprise application most commonly occurs when projects are imported from outside the Workbench.">Cyclical dependencies between Java EE modules</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="../topics/tjear.html" title="Using the wizard to create an enterprise application project allows you to package many web applications and modules in a project and deploy these modules as a J2EE enterprise application.">Creating an enterprise application project</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/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/tjimprar.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimprar.dita
deleted file mode 100644
index 5d9a294..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimprar.dita
+++ /dev/null
@@ -1,55 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="tjimprar" xml:lang="en-us">
-<title outputclass="id_title">Importing a connector project RAR file</title>
-<shortdesc outputclass="id_shortdesc">Connector projects are deployed into
-RAR files. You can import a connector project by importing a deployed RAR
-file.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>connector projects<indexterm>importing</indexterm></indexterm>
-<indexterm>RAR files<indexterm>importing</indexterm></indexterm></keywords>
-</metadata></prolog>
-<taskbody outputclass="id_taskbody">
-<context outputclass="id_context"><p outputclass="anchor_topictop"></p> <p>To
-import a connector project RAR file using the wizard, complete the following
-steps:</p></context>
-<steps outputclass="id_steps">
-<step><cmd>In the <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="Java">Java</tm> EE perspective, click <menucascade><uicontrol>File</uicontrol>
-<uicontrol>Import</uicontrol></menucascade>.</cmd></step>
-<step><cmd>Under <uicontrol>Select an import source</uicontrol>, click <menucascade>
-<uicontrol>J2EE</uicontrol><uicontrol>RAR file</uicontrol></menucascade>.</cmd>
-</step>
-<step><cmd>In the <uicontrol>Connector file</uicontrol> field, enter the full
-path and name of the connector RAR file that you want to import. </cmd></step>
-<step><cmd>In the <uicontrol>Connector module</uicontrol> combination box,
-type a new project name or select a connector project from the drop-down list. </cmd>
-<info>If you type a new project name in this field, the connector project
-will be created based on the version of the connector RAR file, and it will
-use the default location.</info></step>
-<step><cmd>In the <uicontrol>Target runtime</uicontrol> drop-down list, select
-the application server that you want to target for your development. </cmd>
-<info>This selection affects the run-time settings by modifying the class
-path entries for the project.</info></step>
-<step importance="optional"><cmd>To add the new module to an enterprise application
-project, select the <uicontrol>Add project to an EAR</uicontrol> check box
-and then select an existing enterprise application project from the list
-or create a new one by clicking <uicontrol>New</uicontrol>.</cmd></step>
-<step><cmd>In the <uicontrol>EAR application</uicontrol> combination box,
-type a new project name or select an existing enterprise application project
-from the drop-down list. Or, click the <uicontrol>New</uicontrol> button to
-launch the New Enterprise Application Project wizard.</cmd><info><note>If
-you type a new enterprise application project name, the enterprise application
- 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.</note></info>
-</step>
-<step><cmd>Click <uicontrol>Finish</uicontrol> to import the connector RAR
-file.</cmd></step>
-</steps>
-<postreq outputclass="id_postreq"><p outputclass="anchor_topicbottom"></p></postreq>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimprar.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimprar.html
deleted file mode 100644
index ec292ed..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimprar.html
+++ /dev/null
@@ -1,96 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="task" name="DC.Type" />
-<meta name="DC.Title" content="Importing a connector project RAR file" />
-<meta name="abstract" content="Connector projects are deployed into RAR files. You can import a connector project by importing a deployed RAR file." />
-<meta name="description" content="Connector projects are deployed into RAR files. You can import a connector project by importing a deployed RAR file." />
-<meta content="connector projects, importing, RAR files" name="DC.subject" />
-<meta content="connector projects, importing, RAR files" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/ph-importexport.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="tjimprar" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Importing a connector project RAR file</title>
-</head>
-<body id="tjimprar"><a name="tjimprar"><!-- --></a>
-
-
-<h1 class="id_title">Importing a connector project RAR file</h1>
-
-
-
-<div class="id_taskbody"><p class="id_shortdesc">Connector projects are deployed into
-RAR files. You can import a connector project by importing a deployed RAR
-file.</p>
-
-<div class="id_context"><p class="anchor_topictop" />
- <p>To
-import a connector project RAR file using the wizard, complete the following
-steps:</p>
-</div>
-
-<ol class="id_steps">
-<li class="stepexpand"><span>In the Java™ EE perspective, click <span class="menucascade"><span class="uicontrol">File</span>
- > <span class="uicontrol">Import</span></span>.</span></li>
-
-<li class="stepexpand"><span>Under <span class="uicontrol">Select an import source</span>, click <span class="menucascade">
-<span class="uicontrol">J2EE</span> > <span class="uicontrol">RAR file</span></span>.</span>
-</li>
-
-<li class="stepexpand"><span>In the <span class="uicontrol">Connector file</span> field, enter the full
-path and name of the connector RAR file that you want to import. </span></li>
-
-<li class="stepexpand"><span>In the <span class="uicontrol">Connector module</span> combination box,
-type a new project name or select a connector project from the drop-down list. </span>
- If you type a new project name in this field, the connector project
-will be created based on the version of the connector RAR file, and it will
-use the default location.</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>
- This selection affects the run-time settings by modifying the class
-path entries for the project.</li>
-
-<li class="stepexpand"><strong>Optional: </strong><span>To add the new module to an enterprise application
-project, select the <span class="uicontrol">Add project to an EAR</span> check box
-and then select an existing enterprise application project from the list
-or create a new one by clicking <span class="uicontrol">New</span>.</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 enterprise application project name, the enterprise application
- 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> to import the connector RAR
-file.</span></li>
-
-</ol>
-
-<div class="id_postreq"><p class="anchor_topicbottom" />
-</div>
-
-</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>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjrar.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjrar.dita
deleted file mode 100644
index 861366d..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjrar.dita
+++ /dev/null
@@ -1,73 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="tjrar" xml:lang="en-us">
-<title outputclass="id_title">Creating a connector project</title>
-<shortdesc outputclass="id_shortdesc">A connector is a J2EE standard extension
-mechanism for containers to provide connectivity to enterprise information
-systems (EISs).</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>connector projects<indexterm>creating</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody outputclass="id_taskbody">
-<context outputclass="id_context"> <p outputclass="anchor_topictop"></p> <p>A
-connector is specific to an EIS and consists of a resource adapter and application
-development tools. A resource adapter is a system-level software driver that
-is used by an EJB container or an application client to connect to an EIS.
-Connectors comply with the J2EE Connector architecture (JCA).</p><p>Like the
-other types of projects, connector projects can contain one or more project
-facets, which represent units of functionality in the project. A new connector
-project should have the J2C Module facet. Depending on what you want to use
-the project for, you may want to enable other facets for the project.</p><note
-type="restriction">J2EE 1.2 specification level does not include connector
-capability.</note><p>To create a new connector project, complete the following
-steps:</p></context>
-<steps outputclass="id_steps">
-<step><cmd>In the <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="Java">Java</tm> EE perspective, click <menucascade><uicontrol>File</uicontrol>
-<uicontrol>New</uicontrol><uicontrol>Project</uicontrol></menucascade>.</cmd>
-</step>
-<step><cmd>In the New Project Wizard, select <menucascade><uicontrol>J2EE</uicontrol>
-<uicontrol>Connector Project</uicontrol></menucascade> and click <uicontrol>Next</uicontrol>.</cmd>
-</step>
-<step><cmd>In the <uicontrol>Project Name</uicontrol> field, type a name for
-the connector project. </cmd></step>
-<step importance="optional"><cmd>To change the default project location, clear
-the <uicontrol>Use default</uicontrol> check box under <uicontrol>Project
-contents</uicontrol> and select a new location with the <uicontrol>Browse</uicontrol> button.</cmd>
-<info>If you specify a non-default project location that is already being
-used by another project, the project creation will fail.<note>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.</note></info></step>
-<step importance="optional"><cmd>If you want to add the new project to an
-enterprise application project, select the <uicontrol>Add project to an EAR</uicontrol> check
-box and select a project in the <uicontrol>EAR Project Name</uicontrol> list.</cmd>
-<info>If you choose to add the project to an existing EAR project, the <uicontrol>Target
-runtime</uicontrol> field becomes disabled because the target runtime for
-the new project will be the same as that of the EAR project.</info></step>
-<step><cmd>In the <uicontrol>Target runtime</uicontrol> field, select the
-target runtime for the project.</cmd></step>
-<step importance="optional"><cmd>To use a predefined configuration for your
-project, select a configuration in the <uicontrol>Configuration</uicontrol> list.
-You can click the <uicontrol>Modify</uicontrol> button to do the following:</cmd>
-<info><ul>
-<li>Customize project facets. Select the check boxes next to the facets you
-want the project to have and select a version number for each facet. Select
-a facet name to see more information about that facet in the <uicontrol>Details</uicontrol> tab.
-You can also choose a preset combination of facets from the <uicontrol>Configurations</uicontrol> list.</li>
-<li>Limit your project to be compatible with one or more runtimes. Click the <uicontrol>Show
-Runtimes</uicontrol> tab and select the runtimes that you want the project
-to be compatible with. </li>
-</ul>Click <uicontrol>Next</uicontrol>.</info></step>
-<step><cmd>In the <uicontrol>Source Folder</uicontrol> field, enter the name
-of the folder to use for source code.</cmd></step>
-<step><cmd>Click <uicontrol>Finish</uicontrol>.</cmd></step>
-</steps>
-<postreq outputclass="id_postreq"><p outputclass="anchor_topicbottom"></p></postreq>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjrar.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjrar.html
deleted file mode 100644
index bc3f6bb..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjrar.html
+++ /dev/null
@@ -1,121 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="task" name="DC.Type" />
-<meta name="DC.Title" content="Creating a connector project" />
-<meta name="abstract" content="A connector is a J2EE standard extension mechanism for containers to provide connectivity to enterprise information systems (EISs)." />
-<meta name="description" content="A connector is a J2EE standard extension mechanism for containers to provide connectivity to enterprise information systems (EISs)." />
-<meta content="connector projects, creating" name="DC.subject" />
-<meta content="connector projects, creating" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjearproj.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cfacets.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="tjrar" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Creating a connector project</title>
-</head>
-<body id="tjrar"><a name="tjrar"><!-- --></a>
-
-
-<h1 class="id_title">Creating a connector project</h1>
-
-
-
-<div class="id_taskbody"><p class="id_shortdesc">A connector is a J2EE standard extension
-mechanism for containers to provide connectivity to enterprise information
-systems (EISs).</p>
-
-<div class="id_context"> <p class="anchor_topictop" />
- <p>A
-connector is specific to an EIS and consists of a resource adapter and application
-development tools. A resource adapter is a system-level software driver that
-is used by an EJB container or an application client to connect to an EIS.
-Connectors comply with the J2EE Connector architecture (JCA).</p>
-<p>Like the
-other types of projects, connector projects can contain one or more project
-facets, which represent units of functionality in the project. A new connector
-project should have the J2C Module facet. Depending on what you want to use
-the project for, you may want to enable other facets for the project.</p>
-<div class="restriction"><span class="restrictiontitle">Restriction:</span> J2EE 1.2 specification level does not include connector
-capability.</div>
-<p>To create a new connector project, complete the following
-steps:</p>
-</div>
-
-<ol class="id_steps">
-<li class="stepexpand"><span>In the Java™ EE perspective, click <span class="menucascade"><span class="uicontrol">File</span>
- > <span class="uicontrol">New</span> > <span class="uicontrol">Project</span></span>.</span>
-</li>
-
-<li class="stepexpand"><span>In the New Project Wizard, select <span class="menucascade"><span class="uicontrol">J2EE</span>
- > <span class="uicontrol">Connector Project</span></span> and click <span class="uicontrol">Next</span>.</span>
-</li>
-
-<li class="stepexpand"><span>In the <span class="uicontrol">Project Name</span> field, type a name for
-the connector project. </span></li>
-
-<li class="stepexpand"><strong>Optional: </strong><span>To change the default project location, clear
-the <span class="uicontrol">Use default</span> check box under <span class="uicontrol">Project
-contents</span> and select a new location with the <span class="uicontrol">Browse</span> button.</span>
- If you specify a non-default project location that is already being
-used by another project, the project creation will fail.<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"><strong>Optional: </strong><span>If you want to add the new project to an
-enterprise application project, select the <span class="uicontrol">Add project to an EAR</span> check
-box and select a project in the <span class="uicontrol">EAR Project Name</span> list.</span>
- If you choose to add the project to an existing EAR project, the <span class="uicontrol">Target
-runtime</span> field becomes disabled because the target runtime for
-the new project will be the same as that of the EAR project.</li>
-
-<li class="stepexpand"><span>In the <span class="uicontrol">Target runtime</span> field, select the
-target runtime for the project.</span></li>
-
-<li class="stepexpand"><strong>Optional: </strong><span>To use a predefined configuration for your
-project, select a configuration in the <span class="uicontrol">Configuration</span> list.
-You can click the <span class="uicontrol">Modify</span> button to do the following:</span>
- <ul>
-<li>Customize project facets. Select the check boxes next to the facets you
-want the project to have and select a version number for each facet. Select
-a facet name to see more information about that facet in the <span class="uicontrol">Details</span> tab.
-You can also choose a preset combination of facets from the <span class="uicontrol">Configurations</span> list.</li>
-
-<li>Limit your project to be compatible with one or more runtimes. Click the <span class="uicontrol">Show
-Runtimes</span> tab and select the runtimes that you want the project
-to be compatible with. </li>
-
-</ul>
-Click <span class="uicontrol">Next</span>.</li>
-
-<li class="stepexpand"><span>In the <span class="uicontrol">Source Folder</span> field, enter the name
-of the folder to use for source code.</span></li>
-
-<li class="stepexpand"><span>Click <span class="uicontrol">Finish</span>.</span></li>
-
-</ol>
-
-<div class="id_postreq"><p class="anchor_topicbottom" />
-</div>
-
-</div>
-
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="../topics/cjearproj.html" title="An enterprise application project ties together the resources that are required to deploy a J2EE enterprise application.">Enterprise application projects</a></div>
-<div><a href="../topics/cfacets.html" title="Facets define characteristics and requirements for Java EE projects and are used as part of the runtime configuration.">Project facets</a></div>
-</div>
-</div>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjtargetserver.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjtargetserver.dita
deleted file mode 100644
index 17a51dd..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjtargetserver.dita
+++ /dev/null
@@ -1,86 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="tjtargetserver" xml:lang="en-us">
-<title outputclass="id_title">Specifying target servers for J2EE projects</title>
-<shortdesc outputclass="id_shortdesc">When you develop J2EE applications,
-you can 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.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>J2EE<indexterm>target servers</indexterm></indexterm>
-<indexterm>projects<indexterm>target servers</indexterm></indexterm><indexterm>target
-servers<indexterm>J2EE applications</indexterm></indexterm></keywords>
-</metadata></prolog>
-<taskbody outputclass="id_taskbody">
-<context outputclass="id_context"><p outputclass="anchor_topictop"></p> <p>In
-order to support different application servers that use different JDK levels
-for their <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="Java">Java</tm> Runtime Environment (JRE), the workbench prompts
-you for a target server setting for each J2EE project. For example, if you
-want to take advantage of the features of JDK 1.4.2, your applications require
-different class path entries than those that were used in previous versions
-of the workbench. By prompting you to specify a target server, the workbench
-enforces that proper entries are added for running on the server you choose.</p><p>You
-can also add more than one target server for your project. In this case, the
-workbench prevents you from adding any facets not supported by all of the
-target servers. If you add more than one target server, choose a server that
-will contribute to the project's class path as the primary server.</p><p>When
-the project is created, the class path of the project is updated with two
-class path containers. One container is the JDK container and the other is
-the server container. The JDK container points to the directory that contains
-the JAR files that are necessary to support the JDK version. The server container
-points to the directory that contains the multiple public JAR files available
-in the selected server. The project then compiles based on the required JAR
-files located in these folders, and you do not need to worry about adding
-additional JAR files from the server during development. When the project
-is compiled, the JAR files are included in the class path. You can still add
-your own JAR files to the class path.</p><p>The target runtime environment
-is specified in the org.eclipse.wst.common.project.facet.core.xml file in
-the project's .settings folder. You should not edit this file manually; instead,
-use the properties window as described in this topic.</p><p>All J2EE project
-creation and import wizards prompt you to specify the target server for the
-resulting projects. The list of target servers that you can choose from is
-filtered based on installed runtimes, the J2EE level of the application, and
-the J2EE module type. For example, for EJB projects only application servers
-that support Enterprise <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="JavaBeans">JavaBeans</tm> are displayed. All projects
-inside a single EAR file must be targeted to the same server. If you create
-a new project and add it to an existing EAR project during creation, the project
-inherits the target server setting of the EAR project.</p><note>Utility <tm
-tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> projects
-that are added to an application are targeted to the same target server as
-the application. Web library projects that are added to a Web project are
-targeted to the same target server as the Web project.</note><p>To modify
-the target runtime and default server for an existing project, complete the
-following steps:</p></context>
-<steps outputclass="id_steps">
-<step><cmd>In the Project Explorer view of the <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> EE perspective, right-click the enterprise
-application or module project, and select <uicontrol>Properties</uicontrol>.</cmd>
-</step>
-<step><cmd>Select the <uicontrol>Targeted Runtimes</uicontrol> page in the
-Properties dialog.</cmd></step>
-<step><cmd>In the <uicontrol>Targeted Runtimes</uicontrol> list, select the
-check boxes next to each of the runtimes that you want to develop the project
-for. If you don't see the runtime that you want to use, you need to add it
-to the runtimes in the workbench. For more information, see <xref format=""
-href="../../org.eclipse.wst.server.ui.doc.user/topics/twinstprf.dita" scope="peer">Defining
-the installed server runtime environments</xref>.</cmd><info><note>Only the
-runtimes compatible with the project's facets are shown. You can select the <uicontrol>Show
-all runtimes</uicontrol> check box to display the runtimes not compatible
-with the project's current facet configuration. These runtimes are grayed
-out.</note></info></step>
-<step><cmd>To select the primary runtime, click on a runtime and then click
-the <uicontrol>Make Primary</uicontrol> button.</cmd><info>If you select any
-runtimes for the project, you must make one of those runtimes the primary
-runtime for the project. If you select only one runtime from the list, that
-runtime is automatically made the primary runtime. The primary runtime is
-shown in bold text.</info></step>
-<step><cmd>Click <uicontrol>OK</uicontrol>.</cmd></step>
-</steps>
-<postreq outputclass="id_postreq"><p outputclass="anchor_topicbottom"></p></postreq>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjtargetserver.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjtargetserver.html
deleted file mode 100644
index 481a9da..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjtargetserver.html
+++ /dev/null
@@ -1,127 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="task" name="DC.Type" />
-<meta name="DC.Title" content="Specifying target servers for J2EE projects" />
-<meta name="abstract" content="When you develop J2EE applications, you can 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." />
-<meta name="description" content="When you develop J2EE applications, you can 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." />
-<meta content="J2EE, target servers, projects, target servers, J2EE applications" name="DC.subject" />
-<meta content="J2EE, target servers, projects, target servers, J2EE applications" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjarch.html" />
-<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.wst.server.ui.doc.user/topics/twinstprf.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="tjtargetserver" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Specifying target servers for J2EE projects</title>
-</head>
-<body id="tjtargetserver"><a name="tjtargetserver"><!-- --></a>
-
-
-<h1 class="id_title">Specifying target servers for J2EE projects</h1>
-
-
-
-<div class="id_taskbody"><p class="id_shortdesc">When you develop J2EE applications,
-you can 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.</p>
-
-<div class="id_context"><p class="anchor_topictop" />
- <p>In
-order to support different application servers that use different JDK levels
-for their Java™ Runtime Environment (JRE), the workbench prompts
-you for a target server setting for each J2EE project. For example, if you
-want to take advantage of the features of JDK 1.4.2, your applications require
-different class path entries than those that were used in previous versions
-of the workbench. By prompting you to specify a target server, the workbench
-enforces that proper entries are added for running on the server you choose.</p>
-<p>You
-can also add more than one target server for your project. In this case, the
-workbench prevents you from adding any facets not supported by all of the
-target servers. If you add more than one target server, choose a server that
-will contribute to the project's class path as the primary server.</p>
-<p>When
-the project is created, the class path of the project is updated with two
-class path containers. One container is the JDK container and the other is
-the server container. The JDK container points to the directory that contains
-the JAR files that are necessary to support the JDK version. The server container
-points to the directory that contains the multiple public JAR files available
-in the selected server. The project then compiles based on the required JAR
-files located in these folders, and you do not need to worry about adding
-additional JAR files from the server during development. When the project
-is compiled, the JAR files are included in the class path. You can still add
-your own JAR files to the class path.</p>
-<p>The target runtime environment
-is specified in the org.eclipse.wst.common.project.facet.core.xml file in
-the project's .settings folder. You should not edit this file manually; instead,
-use the properties window as described in this topic.</p>
-<p>All J2EE project
-creation and import wizards prompt you to specify the target server for the
-resulting projects. The list of target servers that you can choose from is
-filtered based on installed runtimes, the J2EE level of the application, and
-the J2EE module type. For example, for EJB projects only application servers
-that support Enterprise JavaBeans™ are displayed. All projects
-inside a single EAR file must be targeted to the same server. If you create
-a new project and add it to an existing EAR project during creation, the project
-inherits the target server setting of the EAR project.</p>
-<div class="note"><span class="notetitle">Note:</span> Utility Java projects
-that are added to an application are targeted to the same target server as
-the application. Web library projects that are added to a Web project are
-targeted to the same target server as the Web project.</div>
-<p>To modify
-the target runtime and default server for an existing project, complete the
-following steps:</p>
-</div>
-
-<ol class="id_steps">
-<li class="stepexpand"><span>In the Project Explorer view of the Java EE perspective, right-click the enterprise
-application or module project, and select <span class="uicontrol">Properties</span>.</span>
-</li>
-
-<li class="stepexpand"><span>Select the <span class="uicontrol">Targeted Runtimes</span> page in the
-Properties dialog.</span></li>
-
-<li class="stepexpand"><span>In the <span class="uicontrol">Targeted Runtimes</span> list, select the
-check boxes next to each of the runtimes that you want to develop the project
-for. If you don't see the runtime that you want to use, you need to add it
-to the runtimes in the workbench. For more information, see <a href="../../org.eclipse.wst.server.ui.doc.user/topics/twinstprf.html">Defining the installed server runtime environments</a>.</span> <div class="note"><span class="notetitle">Note:</span> Only the
-runtimes compatible with the project's facets are shown. You can select the <span class="uicontrol">Show
-all runtimes</span> check box to display the runtimes not compatible
-with the project's current facet configuration. These runtimes are grayed
-out.</div>
-</li>
-
-<li class="stepexpand"><span>To select the primary runtime, click on a runtime and then click
-the <span class="uicontrol">Make Primary</span> button.</span> If you select any
-runtimes for the project, you must make one of those runtimes the primary
-runtime for the project. If you select only one runtime from the list, that
-runtime is automatically made the primary runtime. The primary runtime is
-shown in bold text.</li>
-
-<li class="stepexpand"><span>Click <span class="uicontrol">OK</span>.</span></li>
-
-</ol>
-
-<div class="id_postreq"><p class="anchor_topicbottom" />
-</div>
-
-</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 applications.">J2EE architecture</a></div>
-</div>
-<div class="relinfo"><strong>Related information</strong><br />
-<div><a href="../../org.eclipse.wst.server.ui.doc.user/topics/twinstprf.html">Defining the installed server runtime environments</a></div>
-</div>
-</div>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjval.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjval.dita
deleted file mode 100644
index d17be81..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjval.dita
+++ /dev/null
@@ -1,70 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="tjval" xml:lang="en-us">
-<title outputclass="id_title">Validating code in enterprise applications</title>
-<shortdesc outputclass="id_shortdesc">The workbench includes validators that
-check certain files in your enterprise application module projects for errors.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>build validation<indexterm>enabling</indexterm></indexterm>
-<indexterm>code validation<indexterm>overview</indexterm></indexterm><indexterm>validation<indexterm>overview</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody outputclass="id_taskbody">
-<context outputclass="id_context"> <p outputclass="anchor_topictop"></p> <p>By
-default, the workbench validates your files automatically after any build,
-including automatic builds. You can also begin the validation process manually
-without building.</p><p>On the workbench Preferences window, you can enable
-or disable validators to be used on your projects. Also, you can enable or
-disable validators for each enterprise application module project individually
-on the Properties page for that project.</p><p>Each validator can apply to
-certain types of files, certain project natures, and certain project facets.
-When a validator applies to a project facet or nature, the workbench uses
-that validator only on projects that have that facet or nature. Likewise,
-most validators apply only to certain types of files, so the workbench uses
-those validators only on those types of files.</p><p>To validate your files,
-complete the following steps:</p></context>
-<steps outputclass="id_steps">
-<step><cmd>Click <menucascade><uicontrol>Window</uicontrol><uicontrol>Preferences</uicontrol>
-</menucascade> and select <uicontrol>Validation</uicontrol> in the left pane.</cmd>
-<stepresult>The Validation page of the Preferences window lists the validators
-available in your project and their settings.</stepresult></step>
-<step importance="optional"><cmd>Review the check box options available near
-the top of the window to customize your validation settings:</cmd>
-<choicetable>
-<chhead><choptionhd>Option</choptionhd><chdeschd>Description</chdeschd></chhead>
-<chrow><choption>Allow projects to override these preference settings</choption>
-<chdesc>Select to set individual validation settings for one or more of your
-projects.</chdesc></chrow>
-<chrow><choption>Suspend all validators</choption><chdesc>Select to prevent
-validation at the global level.</chdesc></chrow>
-<chrow><choption>Save all modified resources automatically prior to validating</choption>
-<chdesc>Select to save resources you have modified before the validation begins.</chdesc>
-</chrow><chrow><choption>Show a confirmation dialog when performing manual validation</choption>
-<chdesc>Select to show an informational dialog after a manual validation request has completed.</chdesc>
-</chrow>
-</choicetable>
-</step>
-<step><cmd>In the list of validators, select the check boxes next to each
-validator you want to use at the global level.</cmd><info>Each validator has
-a check box to specify whether it is used on manual validation and/or on build
-validation.</info></step>
-<step><cmd>Tune a validator by clicking
-the button in the <uicontrol>Settings</uicontrol> column.</cmd>
-<info>Not all validators have additional settings.</info></step>
-<step><cmd>Begin the validation process by one of the following methods:</cmd>
-<choices>
-<choice>Right-click a project and click <uicontrol>Validate</uicontrol>.</choice>
-<choice>Start a build.</choice>
-</choices>
-</step>
-</steps>
-<result outputclass="id_result">Any err<?Pub Caret?>ors found by the validators
-are listed in the Problems view.<p>If you want to set individual validation
-settings for one or more of your projects, see <xref href="tjvalglobalpref.dita"></xref> for
-more information.</p></result>
-<postreq outputclass="id_postreq"><p outputclass="anchor_topicbottom"></p></postreq>
-</taskbody>
-</task>
-<?Pub *0000003949?>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjval.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjval.html
deleted file mode 100644
index 04ab6a2..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjval.html
+++ /dev/null
@@ -1,132 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="task" name="DC.Type" />
-<meta name="DC.Title" content="Validating code in enterprise applications" />
-<meta name="abstract" content="The workbench includes validators that check certain files in your enterprise application module projects for errors." />
-<meta name="description" content="The workbench includes validators that check certain files in your enterprise application module projects for errors." />
-<meta content="build validation, enabling, code validation, overview, validation" name="DC.subject" />
-<meta content="build validation, enabling, code validation, overview, validation" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/rvalerr.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/rvalidators.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="tjval" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Validating code in enterprise applications</title>
-</head>
-<body id="tjval"><a name="tjval"><!-- --></a>
-
-
-<h1 class="id_title">Validating code in enterprise applications</h1>
-
-
-
-<div class="id_taskbody"><p class="id_shortdesc">The workbench includes validators that
-check certain files in your enterprise application module projects for errors.</p>
-
-<div class="id_context"> <p class="anchor_topictop" />
- <p>By
-default, the workbench validates your files automatically after any build,
-including automatic builds. You can also begin the validation process manually
-without building.</p>
-<p>On the workbench Preferences window, you can enable
-or disable validators to be used on your projects. Also, you can enable or
-disable validators for each enterprise application module project individually
-on the Properties page for that project.</p>
-<p>Each validator can apply to
-certain types of files, certain project natures, and certain project facets.
-When a validator applies to a project facet or nature, the workbench uses
-that validator only on projects that have that facet or nature. Likewise,
-most validators apply only to certain types of files, so the workbench uses
-those validators only on those types of files.</p>
-<p>To validate your files,
-complete the following steps:</p>
-</div>
-
-<ol class="id_steps">
-<li class="stepexpand"><span>Click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span>
-</span> and select <span class="uicontrol">Validation</span> in the left pane.</span>
- The Validation page of the Preferences window lists the validators
-available in your project and their settings.</li>
-
-<li class="stepexpand"><strong>Optional: </strong><span>Review the check box options available near
-the top of the window to customize your validation settings:</span>
-
-<table class="choicetableborder" summary="" cellspacing="0" cellpadding="4" rules="rows" frame="hsides" border="1">
-<thead><tr><th valign="bottom" id="N100A9-option">Option</th>
-<th valign="bottom" id="N100A9-desc">Description</th></tr></thead>
-<tbody>
-
-<tr><td valign="top" headers="N100A9-option" id="N100C2"><strong>Allow projects to override these preference settings</strong></td>
-
-<td valign="top" headers="N100A9-desc N100C2">Select to set individual validation settings for one or more of your
-projects.</td>
-</tr>
-
-<tr><td valign="top" headers="N100A9-option" id="N100D2"><strong>Suspend all validators</strong></td>
-<td valign="top" headers="N100A9-desc N100D2">Select to prevent
-validation at the global level.</td>
-</tr>
-
-<tr><td valign="top" headers="N100A9-option" id="N100E1"><strong>Save all modified resources automatically prior to validating</strong></td>
-
-<td valign="top" headers="N100A9-desc N100E1">Select to save resources you have modified before the validation begins.</td>
-
-</tr>
-<tr><td valign="top" headers="N100A9-option" id="N100F1"><strong>Show a confirmation dialog when performing manual validation</strong></td>
-
-<td valign="top" headers="N100A9-desc N100F1">Select to show an informational dialog after a manual validation request has completed.</td>
-
-</tr>
-
-</tbody></table>
-
-</li>
-
-<li class="stepexpand"><span>In the list of validators, select the check boxes next to each
-validator you want to use at the global level.</span> Each validator has
-a check box to specify whether it is used on manual validation and/or on build
-validation.</li>
-
-<li class="stepexpand"><span>Tune a validator by clicking
-the button in the <span class="uicontrol">Settings</span> column.</span>
- Not all validators have additional settings.</li>
-
-<li class="stepexpand"><span>Begin the validation process by one of the following methods:</span>
-<ul>
-<li>Right-click a project and click <span class="uicontrol">Validate</span>.</li>
-
-<li>Start a build.</li>
-
-</ul>
-
-</li>
-
-</ol>
-
-<div class="id_result">Any errors found by the validators
-are listed in the Problems view.<p>If you want to set individual validation
-settings for one or more of your projects, see <a href="tjvalglobalpref.html" title="For a given project, you can override the global validation preferences.">Overriding global validation preferences</a> for
-more information.</p>
-</div>
-
-<div class="id_postreq"><p class="anchor_topicbottom" />
-</div>
-
-</div>
-
-<div><div class="relref"><strong>Related reference</strong><br />
-<div><a href="../topics/rvalerr.html" title="This table lists the common error messages you may encounter when you validate your projects.">Common validation errors and solutions</a></div>
-<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/tjvaldisable.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvaldisable.dita
deleted file mode 100644
index afe3aa1..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvaldisable.dita
+++ /dev/null
@@ -1,45 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="tjvaldisable" xml:lang="en-us">
-<title outputclass="id_title">Disabling validation</title>
-<shortdesc outputclass="id_shortdesc">You can disable one or more validators
-individually or disable validation entirely. Also, you can set validation
-settings for your entire workspace and for individual projects.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>validation<indexterm>disabling</indexterm></indexterm>
-<indexterm>code validation<indexterm>disabling</indexterm></indexterm></keywords>
-</metadata></prolog>
-<taskbody outputclass="id_taskbody">
-<context outputclass="id_context"><p outputclass="anchor_topictop"></p><p>To
-disable validators in your project or workspace, complete the following steps:</p></context>
-<steps outputclass="id_steps">
-<step><cmd>Click <menucascade><uicontrol>Window</uicontrol><uicontrol>Preferences</uicontrol>
-</menucascade> and select <uicontrol>Validation</uicontrol> in the left pane.</cmd>
-<stepresult>The Validation page of the Preferences window lists the validators
-available in your project and their settings.</stepresult></step>
-<step><cmd>To disable individual validators, clear the check boxes next to
-each validator that you want to disable.</cmd><info>Each validator has a check
-box to specify whether it is enabled for manual validation or on a build.</info>
-</step>
-<step importance="optional"><cmd><?Pub Caret1?>You can also change the following
-check box options on this page:</cmd>
-<choicetable>
-<chhead><choptionhd>Option</choptionhd><chdeschd>Description</chdeschd></chhead>
-<chrow><choption>Allow projects to override these preference settings</choption>
-<chdesc>Select to set individual validation settings for one or more of your
-projects.</chdesc></chrow>
-<chrow><choption>Suspend all validators</choption><chdesc>Select to prevent
-validation at the global level. If you select this check box, you can still
-enable validation at the project level.</chdesc></chrow>
-</choicetable>
-</step>
-<step><cmd>Click <uicontrol>OK</uicontrol>.</cmd></step>
-</steps>
-<result>If you want to set individual validation settings for one or more
-of your projects, see <xref href="tjvalglobalpref.dita"></xref></result>
-<postreq outputclass="id_postreq"><p outputclass="anchor_topicbottom"></p></postreq>
-</taskbody>
-</task>
-<?Pub *0000002445?>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvaldisable.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvaldisable.html
deleted file mode 100644
index 15fbb8f..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvaldisable.html
+++ /dev/null
@@ -1,100 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="task" name="DC.Type" />
-<meta name="DC.Title" content="Disabling validation" />
-<meta name="abstract" content="You can disable one or more validators individually or disable validation entirely. Also, you can set validation settings for your entire workspace and for individual projects." />
-<meta name="description" content="You can disable one or more validators individually or disable validation entirely. Also, you can set validation settings for your entire workspace and for individual projects." />
-<meta content="validation, disabling, code validation" name="DC.subject" />
-<meta content="validation, disabling, code validation" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjvalglobalpref.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjvalmanual.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjvalselect.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/rtunevalidat.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="tjvaldisable" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Disabling validation</title>
-</head>
-<body id="tjvaldisable"><a name="tjvaldisable"><!-- --></a>
-
-
-<h1 class="id_title">Disabling validation</h1>
-
-
-
-<div class="id_taskbody"><p class="id_shortdesc">You can disable one or more validators
-individually or disable validation entirely. Also, you can set validation
-settings for your entire workspace and for individual projects.</p>
-
-<div class="id_context"><p class="anchor_topictop" />
-<p>To
-disable validators in your project or workspace, complete the following steps:</p>
-</div>
-
-<ol class="id_steps">
-<li class="stepexpand"><span>Click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span>
-</span> and select <span class="uicontrol">Validation</span> in the left pane.</span>
- The Validation page of the Preferences window lists the validators
-available in your project and their settings.</li>
-
-<li class="stepexpand"><span>To disable individual validators, clear the check boxes next to
-each validator that you want to disable.</span> Each validator has a check
-box to specify whether it is enabled for manual validation or on a build.
-</li>
-
-<li class="stepexpand"><strong>Optional: </strong><span>You can also change the following
-check box options on this page:</span>
-
-<table class="choicetableborder" summary="" cellspacing="0" cellpadding="4" rules="rows" frame="hsides" border="1">
-<thead><tr><th valign="bottom" id="N1009D-option">Option</th>
-<th valign="bottom" id="N1009D-desc">Description</th></tr></thead>
-<tbody>
-
-<tr><td valign="top" headers="N1009D-option" id="N100B6"><strong>Allow projects to override these preference settings</strong></td>
-
-<td valign="top" headers="N1009D-desc N100B6">Select to set individual validation settings for one or more of your
-projects.</td>
-</tr>
-
-<tr><td valign="top" headers="N1009D-option" id="N100C6"><strong>Suspend all validators</strong></td>
-<td valign="top" headers="N1009D-desc N100C6">Select to prevent
-validation at the global level. If you select this check box, you can still
-enable validation at the project level.</td>
-</tr>
-
-</tbody></table>
-
-</li>
-
-<li class="stepexpand"><span>Click <span class="uicontrol">OK</span>.</span></li>
-
-</ol>
-
-<div class="section">If you want to set individual validation settings for one or more
-of your projects, see <a href="tjvalglobalpref.html" title="For a given project, you can override the global validation preferences.">Overriding global validation preferences</a></div>
-
-<div class="id_postreq"><p class="anchor_topicbottom" />
-</div>
-
-</div>
-
-<div><div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="../topics/tjvalglobalpref.html" title="For a given project, you can override the global validation preferences.">Overriding global validation preferences</a></div>
-<div><a href="../topics/tjvalmanual.html" title="When you run a manual validation, all resources in the selected project are validated according to the validation settings.">Manually validating code</a></div>
-<div><a href="../topics/tjvalselect.html" title="You can select specific validators to run during manual and build code validation. You can set each validator to run on manual validation, build validation, both, or neither.">Selecting code validators</a></div>
-</div>
-<div class="relref"><strong>Related reference</strong><br />
-<div><a href="../topics/rtunevalidat.html" title="Whether or not a validator validates a particular resource depends on the filters that are in place for that validator.">Tuning validators</a></div>
-</div>
-</div>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalglobalpref.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalglobalpref.dita
deleted file mode 100644
index 50487df..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalglobalpref.dita
+++ /dev/null
@@ -1,48 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="tjvalglobalpref" xml:lang="en-us">
-<title outputclass="id_title">Overriding global validation preferences</title>
-<shortdesc outputclass="id_shortdesc">For a given project, you can override
-the global validation preferences.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>validation<indexterm>overriding global preferences</indexterm></indexterm>
-<indexterm>code validation<indexterm>overriding global preferences</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody outputclass="id_taskbody">
-<context outputclass="id_context"> <p outputclass="anchor_topictop"></p> <p>The
-default validation preferences are specified globally on the Validation page
-of the Preferences dialog. To allow projects to override these default validation
-preferences, complete the following steps:</p></context>
-<steps outputclass="id_steps">
-<step><cmd>Click <menucascade><uicontrol>Window</uicontrol><uicontrol>Preferences</uicontrol>
-</menucascade> and select <uicontrol>Validation</uicontrol> in the left pane.</cmd>
-<stepresult>The Validation page of the Preferences window lists the validators
-available in your project and their settings.</stepresult></step>
-<step><cmd>Select the <uicontrol>Allow projects to override these preference
-settings</uicontrol> check box and click <uicontrol>OK</uicontrol>.</cmd>
-<stepresult>Now individual projects can override the global preferences.</stepresult>
-</step>
-<step><cmd>Right-click a project and then click <uicontrol>Properties</uicontrol>.</cmd><?Pub Caret?>
-</step>
-<step><cmd>In the left pane of the Properties window, click <uicontrol>Validation</uicontrol>.</cmd>
-</step>
-<step><cmd>Select the <uicontrol>Override validation preferences</uicontrol> check
-box.</cmd><info>This check box is available only if you checked the <uicontrol>Allow
-projects to override these preference settings</uicontrol> check box on the
-workbench validation preferences page.</info></step>
-<step><cmd>To prevent validation for this project, select the <uicontrol>Suspend
-all validators</uicontrol> check box.</cmd></step>
-<step><cmd>In the list of validators, select the check boxes next to each
-validator you want to use.</cmd><info>Each validator has a check box to specify
-whether it is used on manual validation or on a build.</info></step>
-<step><cmd>Choose an alternate implementation for a validator by clicking
-the button in the <uicontrol>Settings</uicontrol> column, then click <uicontrol>OK</uicontrol>.</cmd>
-<info>Not all validators have alternate implementations.</info></step>
-</steps>
-<postreq outputclass="id_postreq"><p outputclass="anchor_topicbottom"></p></postreq>
-</taskbody>
-</task>
-<?Pub *0000002816?>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalglobalpref.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalglobalpref.html
deleted file mode 100644
index 894560d..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalglobalpref.html
+++ /dev/null
@@ -1,94 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="task" name="DC.Type" />
-<meta name="DC.Title" content="Overriding global validation preferences" />
-<meta name="abstract" content="For a given project, you can override the global validation preferences." />
-<meta name="description" content="For a given project, you can override the global validation preferences." />
-<meta content="validation, overriding global preferences, code validation" name="DC.subject" />
-<meta content="validation, overriding global preferences, code validation" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjvaldisable.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjvalmanual.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjvalselect.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/rtunevalidat.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="tjvalglobalpref" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Overriding global validation preferences</title>
-</head>
-<body id="tjvalglobalpref"><a name="tjvalglobalpref"><!-- --></a>
-
-
-<h1 class="id_title">Overriding global validation preferences</h1>
-
-
-
-<div class="id_taskbody"><p class="id_shortdesc">For a given project, you can override
-the global validation preferences.</p>
-
-<div class="id_context"> <p class="anchor_topictop" />
- <p>The
-default validation preferences are specified globally on the Validation page
-of the Preferences dialog. To allow projects to override these default validation
-preferences, complete the following steps:</p>
-</div>
-
-<ol class="id_steps">
-<li class="stepexpand"><span>Click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span>
-</span> and select <span class="uicontrol">Validation</span> in the left pane.</span>
- The Validation page of the Preferences window lists the validators
-available in your project and their settings.</li>
-
-<li class="stepexpand"><span>Select the <span class="uicontrol">Allow projects to override these preference
-settings</span> check box and click <span class="uicontrol">OK</span>.</span>
- Now individual projects can override the global preferences.
-</li>
-
-<li class="stepexpand"><span>Right-click a project and then click <span class="uicontrol">Properties</span>.</span>
-</li>
-
-<li class="stepexpand"><span>In the left pane of the Properties window, click <span class="uicontrol">Validation</span>.</span>
-</li>
-
-<li class="stepexpand"><span>Select the <span class="uicontrol">Override validation preferences</span> check
-box.</span> This check box is available only if you checked the <span class="uicontrol">Allow
-projects to override these preference settings</span> check box on the
-workbench validation preferences page.</li>
-
-<li class="stepexpand"><span>To prevent validation for this project, select the <span class="uicontrol">Suspend
-all validators</span> check box.</span></li>
-
-<li class="stepexpand"><span>In the list of validators, select the check boxes next to each
-validator you want to use.</span> Each validator has a check box to specify
-whether it is used on manual validation or on a build.</li>
-
-<li class="stepexpand"><span>Choose an alternate implementation for a validator by clicking
-the button in the <span class="uicontrol">Settings</span> column, then click <span class="uicontrol">OK</span>.</span>
- Not all validators have alternate implementations.</li>
-
-</ol>
-
-<div class="id_postreq"><p class="anchor_topicbottom" />
-</div>
-
-</div>
-
-<div><div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="../topics/tjvaldisable.html" title="You can disable one or more validators individually or disable validation entirely. Also, you can set validation settings for your entire workspace and for individual projects.">Disabling validation</a></div>
-<div><a href="../topics/tjvalmanual.html" title="When you run a manual validation, all resources in the selected project are validated according to the validation settings.">Manually validating code</a></div>
-<div><a href="../topics/tjvalselect.html" title="You can select specific validators to run during manual and build code validation. You can set each validator to run on manual validation, build validation, both, or neither.">Selecting code validators</a></div>
-</div>
-<div class="relref"><strong>Related reference</strong><br />
-<div><a href="../topics/rtunevalidat.html" title="Whether or not a validator validates a particular resource depends on the filters that are in place for that validator.">Tuning validators</a></div>
-</div>
-</div>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalmanual.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalmanual.dita
deleted file mode 100644
index 03b800f..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalmanual.dita
+++ /dev/null
@@ -1,41 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="tjvalmanual" xml:lang="en-us">
-<title outputclass="id_title">Manually validating code</title>
-<shortdesc outputclass="id_shortdesc">When you run a manual validation, all
-resources in the selected project are validated according to the validation
-settings.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>validation<indexterm>manual</indexterm></indexterm><indexterm>code
-validation<indexterm>manual</indexterm></indexterm></keywords>
-</metadata></prolog>
-<taskbody outputclass="id_taskbody">
-<context outputclass="id_context"><p outputclass="anchor_topictop"></p> <p>The
-validators used depend on the global and project validation settings. When
-you validate a project manually, the global settings are used unless both
-of the following are true:<ul>
-<li>The <uicontrol>Allow projects to override these preference settings</uicontrol> check
-box is selected on the global validation preferences page.</li>
-<li>The <uicontrol>Override validation preferences</uicontrol> check box is
-selected on the project's validation preferences page.</li>
-</ul></p><p>Whether the workbench uses the global or project validation preferences,
-only the validators selected to run on manual validation are used when you
-run a manual validation.</p><p>To manually invoke an immediate code validation,
-complete the following steps<?Pub Caret?>:</p></context>
-<steps outputclass="id_steps">
-<step><cmd>Select the project that you want to validate.</cmd></step>
-<step><cmd>Right-click the project and then click <uicontrol>Validate</uicontrol>.</cmd>
-<info>If this option is not available, validation is disabled or there are
-no validators enabled for the project. To enable validation at the global
-level, see <xref href="tjval.dita"></xref>. To enable validators for this
-project, see <xref href="tjvalglobalpref.dita"></xref>.</info></step>
-</steps>
-<result outputclass="id_result">The workbench validates the project using
-the enabled validators. Any errors found by the validators are listed in the
-Problems view.</result>
-<postreq outputclass="id_postreq"><p outputclass="anchor_topicbottom"></p></postreq>
-</taskbody>
-</task>
-<?Pub *0000002296?>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalmanual.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalmanual.html
deleted file mode 100644
index b5bbfd2..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalmanual.html
+++ /dev/null
@@ -1,88 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="task" name="DC.Type" />
-<meta name="DC.Title" content="Manually validating code" />
-<meta name="abstract" content="When you run a manual validation, all resources in the selected project are validated according to the validation settings." />
-<meta name="description" content="When you run a manual validation, all resources in the selected project are validated according to the validation settings." />
-<meta content="validation, manual, code validation" name="DC.subject" />
-<meta content="validation, manual, code validation" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjvaldisable.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjvalglobalpref.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjvalselect.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/rtunevalidat.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="tjvalmanual" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Manually validating code</title>
-</head>
-<body id="tjvalmanual"><a name="tjvalmanual"><!-- --></a>
-
-
-<h1 class="id_title">Manually validating code</h1>
-
-
-
-<div class="id_taskbody"><p class="id_shortdesc">When you run a manual validation, all
-resources in the selected project are validated according to the validation
-settings.</p>
-
-<div class="id_context"><p class="anchor_topictop" />
- <div class="p">The
-validators used depend on the global and project validation settings. When
-you validate a project manually, the global settings are used unless both
-of the following are true:<ul>
-<li>The <span class="uicontrol">Allow projects to override these preference settings</span> check
-box is selected on the global validation preferences page.</li>
-
-<li>The <span class="uicontrol">Override validation preferences</span> check box is
-selected on the project's validation preferences page.</li>
-
-</ul>
-</div>
-<p>Whether the workbench uses the global or project validation preferences,
-only the validators selected to run on manual validation are used when you
-run a manual validation.</p>
-<p>To manually invoke an immediate code validation,
-complete the following steps:</p>
-</div>
-
-<ol class="id_steps">
-<li class="stepexpand"><span>Select the project that you want to validate.</span></li>
-
-<li class="stepexpand"><span>Right-click the project and then click <span class="uicontrol">Validate</span>.</span>
- If this option is not available, validation is disabled or there are
-no validators enabled for the project. To enable validation at the global
-level, see <a href="tjval.html" title="The workbench includes validators that check certain files in your enterprise application module projects for errors.">Validating code in enterprise applications</a>. To enable validators for this
-project, see <a href="tjvalglobalpref.html" title="For a given project, you can override the global validation preferences.">Overriding global validation preferences</a>.</li>
-
-</ol>
-
-<div class="id_result">The workbench validates the project using
-the enabled validators. Any errors found by the validators are listed in the
-Problems view.</div>
-
-<div class="id_postreq"><p class="anchor_topicbottom" />
-</div>
-
-</div>
-
-<div><div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="../topics/tjvaldisable.html" title="You can disable one or more validators individually or disable validation entirely. Also, you can set validation settings for your entire workspace and for individual projects.">Disabling validation</a></div>
-<div><a href="../topics/tjvalglobalpref.html" title="For a given project, you can override the global validation preferences.">Overriding global validation preferences</a></div>
-<div><a href="../topics/tjvalselect.html" title="You can select specific validators to run during manual and build code validation. You can set each validator to run on manual validation, build validation, both, or neither.">Selecting code validators</a></div>
-</div>
-<div class="relref"><strong>Related reference</strong><br />
-<div><a href="../topics/rtunevalidat.html" title="Whether or not a validator validates a particular resource depends on the filters that are in place for that validator.">Tuning validators</a></div>
-</div>
-</div>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalselect.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalselect.dita
deleted file mode 100644
index 5e5e5cf..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalselect.dita
+++ /dev/null
@@ -1,48 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="tjvalselect" xml:lang="en-us">
-<title outputclass="id_title">Selecting code validators</title>
-<shortdesc outputclass="id_shortdesc">You can select specific validators to
-run during manual and build code validation. You can set each validator to
-run on manual validation, build validation, both, or neither. </shortdesc>
-<prolog><metadata>
-<keywords><indexterm>validation<indexterm>selecting validators</indexterm></indexterm>
-<indexterm>code validation<indexterm>selecting validators</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody outputclass="id_taskbody">
-<context outputclass="id_context"><p outputclass="anchor_topictop"></p><p>To
-choose the validators that you want to use for a project, complete the following
-steps:</p></context>
-<steps outputclass="id_steps">
-<step><cmd>Click <menucascade><uicontrol>Window</uicontrol><uicontrol>Preferences</uicontrol>
-</menucascade> and select <uicontrol>Validation</uicontrol> in the left pane.</cmd>
-<stepresult>The Validation page of the Preferences window lists the validators
-available in your project and their settings.</stepresult></step>
-<step><cmd>Clear the <uicontrol>Suspend all validators</uicontrol> check box.</cmd>
-</step>
-<step importance="optional"><cmd><?Pub Caret1?>If you want to set individual
-validation settings for one or more of your projects, select the <uicontrol>Allow
-projects to override these preference settings</uicontrol> check box.</cmd>
-</step>
-<step><cmd>In the list of validators, select the check boxes next to each
-validator you want to use at the global level.</cmd><info>Each validator has
-a check box to specify whether it is used on manual validation or on a build.<note>If
-you deselect any validator that is currently selected, any messages associated
-with the deselected validator will be removed from the task list,
-the next time you perform a full build.</note></info>
-</step>
-<step><cmd>Tune a validator by clicking
-the button in the <uicontrol>Settings</uicontrol> column.</cmd>
-<info>Not all validators have additional settings.</info></step>
-</steps>
-<result>If you want to set individual validation settings for one or more
-of your projects, see <xref href="tjvalglobalpref.dita"></xref>. Like the
-global validation preferences, you can set validators at the project level
-to run on manual validation, build validation, both, or neither.</result>
-<postreq outputclass="id_postreq"><p outputclass="anchor_topicbottom"></p></postreq>
-</taskbody>
-</task>
-<?Pub *0000002685?>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalselect.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalselect.html
deleted file mode 100644
index c4e4aa2..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalselect.html
+++ /dev/null
@@ -1,93 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="task" name="DC.Type" />
-<meta name="DC.Title" content="Selecting code validators" />
-<meta name="abstract" content="You can select specific validators to run during manual and build code validation. You can set each validator to run on manual validation, build validation, both, or neither." />
-<meta name="description" content="You can select specific validators to run during manual and build code validation. You can set each validator to run on manual validation, build validation, both, or neither." />
-<meta content="validation, selecting validators, code validation" name="DC.subject" />
-<meta content="validation, selecting validators, code validation" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjvaldisable.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjvalglobalpref.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/tjvalmanual.html" />
-<meta scheme="URI" name="DC.Relation" content="../topics/rtunevalidat.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="tjvalselect" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Selecting code validators</title>
-</head>
-<body id="tjvalselect"><a name="tjvalselect"><!-- --></a>
-
-
-<h1 class="id_title">Selecting code validators</h1>
-
-
-
-<div class="id_taskbody"><p class="id_shortdesc">You can select specific validators to
-run during manual and build code validation. You can set each validator to
-run on manual validation, build validation, both, or neither. </p>
-
-<div class="id_context"><p class="anchor_topictop" />
-<p>To
-choose the validators that you want to use for a project, complete the following
-steps:</p>
-</div>
-
-<ol class="id_steps">
-<li class="stepexpand"><span>Click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span>
-</span> and select <span class="uicontrol">Validation</span> in the left pane.</span>
- The Validation page of the Preferences window lists the validators
-available in your project and their settings.</li>
-
-<li class="stepexpand"><span>Clear the <span class="uicontrol">Suspend all validators</span> check box.</span>
-</li>
-
-<li class="stepexpand"><strong>Optional: </strong><span>If you want to set individual
-validation settings for one or more of your projects, select the <span class="uicontrol">Allow
-projects to override these preference settings</span> check box.</span>
-</li>
-
-<li class="stepexpand"><span>In the list of validators, select the check boxes next to each
-validator you want to use at the global level.</span> Each validator has
-a check box to specify whether it is used on manual validation or on a build.<div class="note"><span class="notetitle">Note:</span> If
-you deselect any validator that is currently selected, any messages associated
-with the deselected validator will be removed from the task list,
-the next time you perform a full build.</div>
-
-</li>
-
-<li class="stepexpand"><span>Tune a validator by clicking
-the button in the <span class="uicontrol">Settings</span> column.</span>
- Not all validators have additional settings.</li>
-
-</ol>
-
-<div class="section">If you want to set individual validation settings for one or more
-of your projects, see <a href="tjvalglobalpref.html" title="For a given project, you can override the global validation preferences.">Overriding global validation preferences</a>. Like the
-global validation preferences, you can set validators at the project level
-to run on manual validation, build validation, both, or neither.</div>
-
-<div class="id_postreq"><p class="anchor_topicbottom" />
-</div>
-
-</div>
-
-<div><div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="../topics/tjvaldisable.html" title="You can disable one or more validators individually or disable validation entirely. Also, you can set validation settings for your entire workspace and for individual projects.">Disabling validation</a></div>
-<div><a href="../topics/tjvalglobalpref.html" title="For a given project, you can override the global validation preferences.">Overriding global validation preferences</a></div>
-<div><a href="../topics/tjvalmanual.html" title="When you run a manual validation, all resources in the selected project are validated according to the validation settings.">Manually validating code</a></div>
-</div>
-<div class="relref"><strong>Related reference</strong><br />
-<div><a href="../topics/rtunevalidat.html" title="Whether or not a validator validates a particular resource depends on the filters that are in place for that validator.">Tuning validators</a></div>
-</div>
-</div>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjviewfilters.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjviewfilters.dita
deleted file mode 100644
index c6bcc6b..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjviewfilters.dita
+++ /dev/null
@@ -1,36 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="cjviewfiltersCait" xml:lang="en-us">
-<title id="id_title">Filtering in the Project Explorer view</title>
-<shortdesc outputclass="id_shortdesc">You can filter the Project Explorer
-view to hide projects, folders, or files that you do not want to see.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>filters<indexterm>Project Explorer view</indexterm></indexterm>
-<indexterm>views<indexterm>Project Explorer filters</indexterm></indexterm>
-<indexterm>projects<indexterm>filtering</indexterm></indexterm></keywords>
-</metadata></prolog>
-<taskbody outputclass="id_taskbody">
-<context outputclass="id_context"><p outputclass="anchor_topictop"></p><p>To
-enable or disable filters, complete the following steps</p></context>
-<steps>
-<step><cmd>Open the Select Common Navigator Filters window by selecting <uicontrol>Customize
-View...</uicontrol> from the drop-down menu at the top right corner of the
-view. </cmd></step>
-<step><cmd>On the <uicontrol>Filters</uicontrol> tab, select the check boxes
-next to the filters you want to enable.</cmd><info> For example, when the <uicontrol>Closed
-projects</uicontrol> filter is enabled, closed projects are not shown in the
-Project Explorer view. Other filters can hide empty packages, non-java files,
-and files with names ending in ".class".</info></step>
-<step><cmd>On the <uicontrol>Content</uicontrol> tab, the filters work in
-the opposite way: the selected check boxes describe the projects, folders,
-and files that are shown in the Project Explorer view. Select the check boxes
-next to the filters you want to hide.</cmd><info>For example, if you clear
-the check box next to <uicontrol>J2EE EJB Deployment Descriptors</uicontrol>,
-the deployment descriptors are hidden from each project in the view.</info>
-</step>
-</steps>
-<postreq outputclass="id_postreq"><p outputclass="anchor_topicbottom"></p></postreq>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjviewfilters.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjviewfilters.html
deleted file mode 100644
index 6288e32..0000000
--- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjviewfilters.html
+++ /dev/null
@@ -1,70 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
-<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
-<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
-<meta content="public" name="security" />
-<meta content="index,follow" name="Robots" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta content="task" name="DC.Type" />
-<meta name="DC.Title" content="Filtering in the Project Explorer view" />
-<meta name="abstract" content="You can filter the Project Explorer view to hide projects, folders, or files that you do not want to see." />
-<meta name="description" content="You can filter the Project Explorer view to hide projects, folders, or files that you do not want to see." />
-<meta content="filters, Project Explorer view, views, Project Explorer filters, projects, filtering" name="DC.subject" />
-<meta content="filters, Project Explorer view, views, Project Explorer filters, projects, filtering" name="keywords" />
-<meta scheme="URI" name="DC.Relation" content="../topics/cjview.html" />
-<meta content="XHTML" name="DC.Format" />
-<meta content="cjviewfiltersCait" name="DC.Identifier" />
-<meta content="en-us" name="DC.Language" />
-<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
-<title>Filtering in the Project Explorer view</title>
-</head>
-<body id="cjviewfiltersCait"><a name="cjviewfiltersCait"><!-- --></a>
-
-
-<h1 class="topictitle1">Filtering in the Project Explorer view</h1>
-
-
-
-<div class="id_taskbody"><p class="id_shortdesc">You can filter the Project Explorer
-view to hide projects, folders, or files that you do not want to see.</p>
-
-<div class="id_context"><p class="anchor_topictop" />
-<p>To
-enable or disable filters, complete the following steps</p>
-</div>
-
-<ol>
-<li class="stepexpand"><span>Open the Select Common Navigator Filters window by selecting <span class="uicontrol">Customize
-View...</span> from the drop-down menu at the top right corner of the
-view. </span></li>
-
-<li class="stepexpand"><span>On the <span class="uicontrol">Filters</span> tab, select the check boxes
-next to the filters you want to enable.</span> For example, when the <span class="uicontrol">Closed
-projects</span> filter is enabled, closed projects are not shown in the
-Project Explorer view. Other filters can hide empty packages, non-java files,
-and files with names ending in ".class".</li>
-
-<li class="stepexpand"><span>On the <span class="uicontrol">Content</span> tab, the filters work in
-the opposite way: the selected check boxes describe the projects, folders,
-and files that are shown in the Project Explorer view. Select the check boxes
-next to the filters you want to hide.</span> For example, if you clear
-the check box next to <span class="uicontrol">J2EE EJB Deployment Descriptors</span>,
-the deployment descriptors are hidden from each project in the view.
-</li>
-
-</ol>
-
-<div class="id_postreq"><p class="anchor_topicbottom" />
-</div>
-
-</div>
-
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="../topics/cjview.html" title="While developing J2EE applications in the Java EE perspective, the Project Explorer view is your main view of your J2EE projects and resources.">Project Explorer view in the Java EE perspective</a></div>
-</div>
-</div>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/features/org.eclipse.jst.enterprise_userdoc.feature/.cvsignore b/features/org.eclipse.jst.enterprise_userdoc.feature/.cvsignore
deleted file mode 100644
index 4b5f609..0000000
--- a/features/org.eclipse.jst.enterprise_userdoc.feature/.cvsignore
+++ /dev/null
@@ -1,2 +0,0 @@
-build.xml
-org.eclipse.jst.enterprise_userdoc.feature_1.0.0.jar
diff --git a/features/org.eclipse.jst.enterprise_userdoc.feature/.project b/features/org.eclipse.jst.enterprise_userdoc.feature/.project
deleted file mode 100644
index ffcfb55..0000000
--- a/features/org.eclipse.jst.enterprise_userdoc.feature/.project
+++ /dev/null
@@ -1,17 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
- <name>org.eclipse.jst.enterprise_userdoc.feature</name>
- <comment></comment>
- <projects>
- </projects>
- <buildSpec>
- <buildCommand>
- <name>org.eclipse.pde.FeatureBuilder</name>
- <arguments>
- </arguments>
- </buildCommand>
- </buildSpec>
- <natures>
- <nature>org.eclipse.pde.FeatureNature</nature>
- </natures>
-</projectDescription>
diff --git a/features/org.eclipse.jst.enterprise_userdoc.feature/build.properties b/features/org.eclipse.jst.enterprise_userdoc.feature/build.properties
deleted file mode 100644
index 7f47694..0000000
--- a/features/org.eclipse.jst.enterprise_userdoc.feature/build.properties
+++ /dev/null
@@ -1,5 +0,0 @@
-bin.includes = feature.xml,\
- eclipse_update_120.jpg,\
- epl-v10.html,\
- license.html,\
- feature.properties
diff --git a/features/org.eclipse.jst.enterprise_userdoc.feature/eclipse_update_120.jpg b/features/org.eclipse.jst.enterprise_userdoc.feature/eclipse_update_120.jpg
deleted file mode 100644
index bfdf708..0000000
--- a/features/org.eclipse.jst.enterprise_userdoc.feature/eclipse_update_120.jpg
+++ /dev/null
Binary files differ
diff --git a/features/org.eclipse.jst.enterprise_userdoc.feature/epl-v10.html b/features/org.eclipse.jst.enterprise_userdoc.feature/epl-v10.html
deleted file mode 100644
index ed4b196..0000000
--- a/features/org.eclipse.jst.enterprise_userdoc.feature/epl-v10.html
+++ /dev/null
@@ -1,328 +0,0 @@
-<html xmlns:o="urn:schemas-microsoft-com:office:office"
-xmlns:w="urn:schemas-microsoft-com:office:word"
-xmlns="http://www.w3.org/TR/REC-html40">
-
-<head>
-<meta http-equiv=Content-Type content="text/html; charset=windows-1252">
-<meta name=ProgId content=Word.Document>
-<meta name=Generator content="Microsoft Word 9">
-<meta name=Originator content="Microsoft Word 9">
-<link rel=File-List
-href="./Eclipse%20EPL%202003_11_10%20Final_files/filelist.xml">
-<title>Eclipse Public License - Version 1.0</title>
-<!--[if gte mso 9]><xml>
- <o:DocumentProperties>
- <o:Revision>2</o:Revision>
- <o:TotalTime>3</o:TotalTime>
- <o:Created>2004-03-05T23:03:00Z</o:Created>
- <o:LastSaved>2004-03-05T23:03:00Z</o:LastSaved>
- <o:Pages>4</o:Pages>
- <o:Words>1626</o:Words>
- <o:Characters>9270</o:Characters>
- <o:Lines>77</o:Lines>
- <o:Paragraphs>18</o:Paragraphs>
- <o:CharactersWithSpaces>11384</o:CharactersWithSpaces>
- <o:Version>9.4402</o:Version>
- </o:DocumentProperties>
-</xml><![endif]--><!--[if gte mso 9]><xml>
- <w:WordDocument>
- <w:TrackRevisions/>
- </w:WordDocument>
-</xml><![endif]-->
-<style>
-<!--
- /* Font Definitions */
-@font-face
- {font-family:Tahoma;
- panose-1:2 11 6 4 3 5 4 4 2 4;
- mso-font-charset:0;
- mso-generic-font-family:swiss;
- mso-font-pitch:variable;
- mso-font-signature:553679495 -2147483648 8 0 66047 0;}
- /* Style Definitions */
-p.MsoNormal, li.MsoNormal, div.MsoNormal
- {mso-style-parent:"";
- margin:0in;
- margin-bottom:.0001pt;
- mso-pagination:widow-orphan;
- font-size:12.0pt;
- font-family:"Times New Roman";
- mso-fareast-font-family:"Times New Roman";}
-p
- {margin-right:0in;
- mso-margin-top-alt:auto;
- mso-margin-bottom-alt:auto;
- margin-left:0in;
- mso-pagination:widow-orphan;
- font-size:12.0pt;
- font-family:"Times New Roman";
- mso-fareast-font-family:"Times New Roman";}
-p.BalloonText, li.BalloonText, div.BalloonText
- {mso-style-name:"Balloon Text";
- margin:0in;
- margin-bottom:.0001pt;
- mso-pagination:widow-orphan;
- font-size:8.0pt;
- font-family:Tahoma;
- mso-fareast-font-family:"Times New Roman";}
-@page Section1
- {size:8.5in 11.0in;
- margin:1.0in 1.25in 1.0in 1.25in;
- mso-header-margin:.5in;
- mso-footer-margin:.5in;
- mso-paper-source:0;}
-div.Section1
- {page:Section1;}
--->
-</style>
-</head>
-
-<body lang=EN-US style='tab-interval:.5in'>
-
-<div class=Section1>
-
-<p align=center style='text-align:center'><b>Eclipse Public License - v 1.0</b>
-</p>
-
-<p><span style='font-size:10.0pt'>THE ACCOMPANYING PROGRAM IS PROVIDED UNDER
-THE TERMS OF THIS ECLIPSE PUBLIC LICENSE ("AGREEMENT"). ANY USE,
-REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE
-OF THIS AGREEMENT.</span> </p>
-
-<p><b><span style='font-size:10.0pt'>1. DEFINITIONS</span></b> </p>
-
-<p><span style='font-size:10.0pt'>"Contribution" means:</span> </p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>a)
-in the case of the initial Contributor, the initial code and documentation
-distributed under this Agreement, and<br clear=left>
-b) in the case of each subsequent Contributor:</span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>i)
-changes to the Program, and</span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>ii)
-additions to the Program;</span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>where
-such changes and/or additions to the Program originate from and are distributed
-by that particular Contributor. A Contribution 'originates' from a Contributor
-if it was added to the Program by such Contributor itself or anyone acting on
-such Contributor's behalf. Contributions do not include additions to the
-Program which: (i) are separate modules of software distributed in conjunction
-with the Program under their own license agreement, and (ii) are not derivative
-works of the Program. </span></p>
-
-<p><span style='font-size:10.0pt'>"Contributor" means any person or
-entity that distributes the Program.</span> </p>
-
-<p><span style='font-size:10.0pt'>"Licensed Patents " mean patent
-claims licensable by a Contributor which are necessarily infringed by the use
-or sale of its Contribution alone or when combined with the Program. </span></p>
-
-<p><span style='font-size:10.0pt'>"Program" means the Contributions
-distributed in accordance with this Agreement.</span> </p>
-
-<p><span style='font-size:10.0pt'>"Recipient" means anyone who
-receives the Program under this Agreement, including all Contributors.</span> </p>
-
-<p><b><span style='font-size:10.0pt'>2. GRANT OF RIGHTS</span></b> </p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>a)
-Subject to the terms of this Agreement, each Contributor hereby grants Recipient
-a non-exclusive, worldwide, royalty-free copyright license to<span
-style='color:red'> </span>reproduce, prepare derivative works of, publicly
-display, publicly perform, distribute and sublicense the Contribution of such
-Contributor, if any, and such derivative works, in source code and object code
-form.</span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>b)
-Subject to the terms of this Agreement, each Contributor hereby grants
-Recipient a non-exclusive, worldwide,<span style='color:green'> </span>royalty-free
-patent license under Licensed Patents to make, use, sell, offer to sell, import
-and otherwise transfer the Contribution of such Contributor, if any, in source
-code and object code form. This patent license shall apply to the combination
-of the Contribution and the Program if, at the time the Contribution is added
-by the Contributor, such addition of the Contribution causes such combination
-to be covered by the Licensed Patents. The patent license shall not apply to
-any other combinations which include the Contribution. No hardware per se is
-licensed hereunder. </span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>c)
-Recipient understands that although each Contributor grants the licenses to its
-Contributions set forth herein, no assurances are provided by any Contributor
-that the Program does not infringe the patent or other intellectual property
-rights of any other entity. Each Contributor disclaims any liability to Recipient
-for claims brought by any other entity based on infringement of intellectual
-property rights or otherwise. As a condition to exercising the rights and
-licenses granted hereunder, each Recipient hereby assumes sole responsibility
-to secure any other intellectual property rights needed, if any. For example,
-if a third party patent license is required to allow Recipient to distribute
-the Program, it is Recipient's responsibility to acquire that license before
-distributing the Program.</span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>d)
-Each Contributor represents that to its knowledge it has sufficient copyright
-rights in its Contribution, if any, to grant the copyright license set forth in
-this Agreement. </span></p>
-
-<p><b><span style='font-size:10.0pt'>3. REQUIREMENTS</span></b> </p>
-
-<p><span style='font-size:10.0pt'>A Contributor may choose to distribute the
-Program in object code form under its own license agreement, provided that:</span>
-</p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>a)
-it complies with the terms and conditions of this Agreement; and</span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>b)
-its license agreement:</span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>i)
-effectively disclaims on behalf of all Contributors all warranties and
-conditions, express and implied, including warranties or conditions of title
-and non-infringement, and implied warranties or conditions of merchantability
-and fitness for a particular purpose; </span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>ii)
-effectively excludes on behalf of all Contributors all liability for damages,
-including direct, indirect, special, incidental and consequential damages, such
-as lost profits; </span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>iii)
-states that any provisions which differ from this Agreement are offered by that
-Contributor alone and not by any other party; and</span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>iv)
-states that source code for the Program is available from such Contributor, and
-informs licensees how to obtain it in a reasonable manner on or through a
-medium customarily used for software exchange.<span style='color:blue'> </span></span></p>
-
-<p><span style='font-size:10.0pt'>When the Program is made available in source
-code form:</span> </p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>a)
-it must be made available under this Agreement; and </span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>b) a
-copy of this Agreement must be included with each copy of the Program. </span></p>
-
-<p><span style='font-size:10.0pt'>Contributors may not remove or alter any
-copyright notices contained within the Program. </span></p>
-
-<p><span style='font-size:10.0pt'>Each Contributor must identify itself as the
-originator of its Contribution, if any, in a manner that reasonably allows
-subsequent Recipients to identify the originator of the Contribution. </span></p>
-
-<p><b><span style='font-size:10.0pt'>4. COMMERCIAL DISTRIBUTION</span></b> </p>
-
-<p><span style='font-size:10.0pt'>Commercial distributors of software may
-accept certain responsibilities with respect to end users, business partners
-and the like. While this license is intended to facilitate the commercial use
-of the Program, the Contributor who includes the Program in a commercial
-product offering should do so in a manner which does not create potential
-liability for other Contributors. Therefore, if a Contributor includes the
-Program in a commercial product offering, such Contributor ("Commercial
-Contributor") hereby agrees to defend and indemnify every other
-Contributor ("Indemnified Contributor") against any losses, damages and
-costs (collectively "Losses") arising from claims, lawsuits and other
-legal actions brought by a third party against the Indemnified Contributor to
-the extent caused by the acts or omissions of such Commercial Contributor in
-connection with its distribution of the Program in a commercial product
-offering. The obligations in this section do not apply to any claims or Losses
-relating to any actual or alleged intellectual property infringement. In order
-to qualify, an Indemnified Contributor must: a) promptly notify the Commercial
-Contributor in writing of such claim, and b) allow the Commercial Contributor
-to control, and cooperate with the Commercial Contributor in, the defense and
-any related settlement negotiations. The Indemnified Contributor may participate
-in any such claim at its own expense.</span> </p>
-
-<p><span style='font-size:10.0pt'>For example, a Contributor might include the
-Program in a commercial product offering, Product X. That Contributor is then a
-Commercial Contributor. If that Commercial Contributor then makes performance
-claims, or offers warranties related to Product X, those performance claims and
-warranties are such Commercial Contributor's responsibility alone. Under this
-section, the Commercial Contributor would have to defend claims against the
-other Contributors related to those performance claims and warranties, and if a
-court requires any other Contributor to pay any damages as a result, the
-Commercial Contributor must pay those damages.</span> </p>
-
-<p><b><span style='font-size:10.0pt'>5. NO WARRANTY</span></b> </p>
-
-<p><span style='font-size:10.0pt'>EXCEPT AS EXPRESSLY SET FORTH IN THIS
-AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS" BASIS, WITHOUT
-WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING,
-WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT,
-MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely
-responsible for determining the appropriateness of using and distributing the
-Program and assumes all risks associated with its exercise of rights under this
-Agreement , including but not limited to the risks and costs of program errors,
-compliance with applicable laws, damage to or loss of data, programs or
-equipment, and unavailability or interruption of operations. </span></p>
-
-<p><b><span style='font-size:10.0pt'>6. DISCLAIMER OF LIABILITY</span></b> </p>
-
-<p><span style='font-size:10.0pt'>EXCEPT AS EXPRESSLY SET FORTH IN THIS
-AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR
-ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY
-OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
-NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF
-THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF
-THE POSSIBILITY OF SUCH DAMAGES.</span> </p>
-
-<p><b><span style='font-size:10.0pt'>7. GENERAL</span></b> </p>
-
-<p><span style='font-size:10.0pt'>If any provision of this Agreement is invalid
-or unenforceable under applicable law, it shall not affect the validity or
-enforceability of the remainder of the terms of this Agreement, and without
-further action by the parties hereto, such provision shall be reformed to the
-minimum extent necessary to make such provision valid and enforceable.</span> </p>
-
-<p><span style='font-size:10.0pt'>If Recipient institutes patent litigation
-against any entity (including a cross-claim or counterclaim in a lawsuit)
-alleging that the Program itself (excluding combinations of the Program with
-other software or hardware) infringes such Recipient's patent(s), then such
-Recipient's rights granted under Section 2(b) shall terminate as of the date
-such litigation is filed. </span></p>
-
-<p><span style='font-size:10.0pt'>All Recipient's rights under this Agreement
-shall terminate if it fails to comply with any of the material terms or
-conditions of this Agreement and does not cure such failure in a reasonable
-period of time after becoming aware of such noncompliance. If all Recipient's
-rights under this Agreement terminate, Recipient agrees to cease use and
-distribution of the Program as soon as reasonably practicable. However,
-Recipient's obligations under this Agreement and any licenses granted by
-Recipient relating to the Program shall continue and survive. </span></p>
-
-<p><span style='font-size:10.0pt'>Everyone is permitted to copy and distribute
-copies of this Agreement, but in order to avoid inconsistency the Agreement is
-copyrighted and may only be modified in the following manner. The Agreement
-Steward reserves the right to publish new versions (including revisions) of
-this Agreement from time to time. No one other than the Agreement Steward has
-the right to modify this Agreement. The Eclipse Foundation is the initial
-Agreement Steward. The Eclipse Foundation may assign the responsibility to
-serve as the Agreement Steward to a suitable separate entity. Each new version
-of the Agreement will be given a distinguishing version number. The Program
-(including Contributions) may always be distributed subject to the version of
-the Agreement under which it was received. In addition, after a new version of
-the Agreement is published, Contributor may elect to distribute the Program
-(including its Contributions) under the new version. Except as expressly stated
-in Sections 2(a) and 2(b) above, Recipient receives no rights or licenses to
-the intellectual property of any Contributor under this Agreement, whether
-expressly, by implication, estoppel or otherwise. All rights in the Program not
-expressly granted under this Agreement are reserved.</span> </p>
-
-<p><span style='font-size:10.0pt'>This Agreement is governed by the laws of the
-State of New York and the intellectual property laws of the United States of
-America. No party to this Agreement will bring a legal action under this
-Agreement more than one year after the cause of action arose. Each party waives
-its rights to a jury trial in any resulting litigation.</span> </p>
-
-<p class=MsoNormal><![if !supportEmptyParas]> <![endif]><o:p></o:p></p>
-
-</div>
-
-</body>
-
-</html>
\ No newline at end of file
diff --git a/features/org.eclipse.jst.enterprise_userdoc.feature/feature.properties b/features/org.eclipse.jst.enterprise_userdoc.feature/feature.properties
deleted file mode 100644
index 18dcbf5..0000000
--- a/features/org.eclipse.jst.enterprise_userdoc.feature/feature.properties
+++ /dev/null
@@ -1,145 +0,0 @@
-###############################################################################
-# Copyright (c) 2006 IBM Corporation and others.
-# All rights reserved. This program and the accompanying materials
-# are made available under the terms of the Eclipse Public License v1.0
-# which accompanies this distribution, and is available at
-# http://www.eclipse.org/legal/epl-v10.html
-#
-# Contributors:
-# IBM Corporation - initial API and implementation
-###############################################################################
-# feature.properties
-# contains externalized strings for feature.xml
-# "%foo" in feature.xml corresponds to the key "foo" in this file
-# java.io.Properties file (ISO 8859-1 with "\" escapes)
-# This file should be translated.
-
-# "featureName" property - name of the feature
-featureName=JST Enterprise User Documentation
-
-# "providerName" property - name of the company that provides the feature
-providerName=Eclipse.org
-
-# "updateSiteName" property - label for the update site
-updateSiteName=The Eclipse Web Tools Platform (WTP) Project update site
-
-# "description" property - description of the feature
-description=JST enterprise user documentation
-
-# "copyright" property - text of the "Feature Update Copyright"
-copyright=\
-Copyright (c) 2006 IBM Corporation and others.\n\
-All rights reserved. This program and the accompanying materials\n\
-are made available under the terms of the Eclipse Public License v1.0\n\
-which accompanies this distribution, and is available at\n\
-http://www.eclipse.org/legal/epl-v10.html\n\
-\n\
-Contributors:\n\
- IBM Corporation - initial API and implementation\n
-################ end of copyright property ####################################
-
-# "licenseURL" property - URL of the "Feature License"
-# do not translate value - just change to point to a locale-specific HTML page
-licenseURL=license.html
-
-# "license" property - text of the "Feature Update License"
-# should be plain text version of license agreement pointed to be "licenseURL"
-license=\
-ECLIPSE FOUNDATION SOFTWARE USER AGREEMENT\n\
-June 06, 2007\n\
-\n\
-Usage Of Content\n\
-\n\
-THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR\n\
-OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY "CONTENT").\n\
-USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS\n\
-AGREEMENT AND/OR THE TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR\n\
-NOTICES INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU\n\
-AGREE THAT YOUR USE OF THE CONTENT IS GOVERNED BY THIS AGREEMENT\n\
-AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS\n\
-OR NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE\n\
-TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND CONDITIONS\n\
-OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED\n\
-BELOW, THEN YOU MAY NOT USE THE CONTENT.\n\
-\n\
-Applicable Licenses\n\
-\n\
-Unless otherwise indicated, all Content made available by the Eclipse Foundation\n\
-is provided to you under the terms and conditions of the Eclipse Public\n\
-License Version 1.0 ("EPL"). A copy of the EPL is provided with this\n\
-Content and is also available at http://www.eclipse.org/legal/epl-v10.html.\n\
-For purposes of the EPL, "Program" will mean the Content.\n\
-\n\
-Content includes, but is not limited to, source code, object code,\n\
-documentation and other files maintained in the Eclipse.org CVS\n\
-repository ("Repository") in CVS modules ("Modules") and made available\n\
-as downloadable archives ("Downloads").\n\
-\n\
- - Content may be structured and packaged into modules to facilitate delivering,\n\
- extending, and upgrading the Content. Typical modules may include plug-ins ("Plug-ins"),\n\
- plug-in fragments ("Fragments"), and features ("Features").\n\
- - Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java? ARchive)\n\
- in a directory named "plugins".\n\
- - A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material.\n\
- Each Feature may be packaged as a sub-directory in a directory named "features".\n\
- Within a Feature, files named "feature.xml" may contain a list of the names and version\n\
- numbers of the Plug-ins and/or Fragments associated with that Feature.\n\
- - Features may also include other Features ("Included Features"). Within a Feature, files\n\
- named "feature.xml" may contain a list of the names and version numbers of Included Features.\n\
-\n\
-Features may also include other Features ("Included Features"). Files named\n\
-"feature.xml" may contain a list of the names and version numbers of\n\
-Included Features.\n\
-\n\
-The terms and conditions governing Plug-ins and Fragments should be\n\
-contained in files named "about.html" ("Abouts"). The terms and\n\
-conditions governing Features and Included Features should be contained\n\
-in files named "license.html" ("Feature Licenses"). Abouts and Feature\n\
-Licenses may be located in any directory of a Download or Module\n\
-including, but not limited to the following locations:\n\
-\n\
- - The top-level (root) directory\n\
- - Plug-in and Fragment directories\n\
- - Inside Plug-ins and Fragments packaged as JARs\n\
- - Sub-directories of the directory named "src" of certain Plug-ins\n\
- - Feature directories\n\
-\n\
-Note: if a Feature made available by the Eclipse Foundation is installed using the\n\
-Eclipse Update Manager, you must agree to a license ("Feature Update\n\
-License") during the installation process. If the Feature contains\n\
-Included Features, the Feature Update License should either provide you\n\
-with the terms and conditions governing the Included Features or inform\n\
-you where you can locate them. Feature Update Licenses may be found in\n\
-the "license" property of files named "feature.properties". Such Abouts,\n\
-Feature Licenses and Feature Update Licenses contain the terms and\n\
-conditions (or references to such terms and conditions) that govern your\n\
-use of the associated Content in that directory.\n\
-\n\
-THE ABOUTS, FEATURE LICENSES AND FEATURE UPDATE LICENSES MAY REFER\n\
-TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS.\n\
-SOME OF THESE OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):\n\
-\n\
- - Common Public License Version 1.0 (available at http://www.eclipse.org/legal/cpl-v10.html)\n\
- - Apache Software License 1.1 (available at http://www.apache.org/licenses/LICENSE)\n\
- - Apache Software License 2.0 (available at http://www.apache.org/licenses/LICENSE-2.0)\n\
- - IBM Public License 1.0 (available at http://oss.software.ibm.com/developerworks/opensource/license10.html)\n\
- - Metro Link Public License 1.00 (available at http://www.opengroup.org/openmotif/supporters/metrolink/license.html)\n\
- - Mozilla Public License Version 1.1 (available at http://www.mozilla.org/MPL/MPL-1.1.html)\n\
- - Common Development and Distribution License (CDDL) Version 1.0 (available at http://www.sun.com/cddl/cddl.html)\n\
-\n\
-IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR\n\
-TO USE OF THE CONTENT. If no About, Feature License or Feature Update License\n\
-is provided, please contact the Eclipse Foundation to determine what terms and conditions\n\
-govern that particular Content.\n\
-\n\
-Cryptography\n\
-\n\
-Content may contain encryption software. The country in which you are\n\
-currently may have restrictions on the import, possession, and use,\n\
-and/or re-export to another country, of encryption software. BEFORE\n\
-using any encryption software, please check the country's laws,\n\
-regulations and policies concerning the import, possession, or use,\n\
-and re-export of encryption software, to see if this is permitted.\n\
-\n\
-Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.\n
-########### end of license property ##########################################
diff --git a/features/org.eclipse.jst.enterprise_userdoc.feature/feature.xml b/features/org.eclipse.jst.enterprise_userdoc.feature/feature.xml
deleted file mode 100644
index 784c255..0000000
--- a/features/org.eclipse.jst.enterprise_userdoc.feature/feature.xml
+++ /dev/null
@@ -1,59 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<feature
- id="org.eclipse.jst.enterprise_userdoc.feature"
- label="%featureName"
- version="3.0.3.qualifier"
- provider-name="%providerName">
-
- <description>
- %description
- </description>
-
- <copyright>
- %copyright
- </copyright>
-
- <license url="license.html">
- %license
- </license>
-
- <url>
- <update label="%updateSiteName" url="http://download.eclipse.org/webtools/updates/"/>
- </url>
-
- <plugin
- id="org.eclipse.jst.ejb.doc.user"
- download-size="0"
- install-size="0"
- version="0.0.0"
- unpack="false"/>
-
- <plugin
- id="org.eclipse.jst.j2ee.doc.user"
- download-size="0"
- install-size="0"
- version="0.0.0"
- unpack="false"/>
-
- <plugin
- id="org.eclipse.jst.ws.axis.ui.doc.user"
- download-size="0"
- install-size="0"
- version="0.0.0"
- unpack="false"/>
-
- <plugin
- id="org.eclipse.jst.ws.consumption.ui.doc.user"
- download-size="0"
- install-size="0"
- version="0.0.0"
- unpack="false"/>
-
- <plugin
- id="org.eclipse.jst.ws.doc.user"
- download-size="0"
- install-size="0"
- version="0.0.0"
- unpack="false"/>
-
-</feature>
diff --git a/features/org.eclipse.jst.enterprise_userdoc.feature/license.html b/features/org.eclipse.jst.enterprise_userdoc.feature/license.html
deleted file mode 100644
index 5644598..0000000
--- a/features/org.eclipse.jst.enterprise_userdoc.feature/license.html
+++ /dev/null
@@ -1,98 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3c.org/TR/1999/REC-html401-19991224/loose.dtd">
-<!-- saved from url=(0044)http://www.eclipse.org/legal/epl/notice.html -->
-<HTML><HEAD><TITLE>Eclipse.org Software User Agreement</TITLE>
-<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
-<META content="MSHTML 6.00.2800.1479" name=GENERATOR></HEAD>
-<BODY lang=EN-US vLink=purple link=blue>
-<H2>Eclipse Foundation Software User Agreement</H2>
-<P>June 06, 2007</P>
-<H3>Usage Of Content</H3>
-<P>THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION
-AND/OR OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY "CONTENT"). USE OF
-THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS AGREEMENT AND/OR THE
-TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED
-BELOW. BY USING THE CONTENT, YOU AGREE THAT YOUR USE OF THE CONTENT IS GOVERNED
-BY THIS AGREEMENT AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE
-AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE
-TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND CONDITIONS OF ANY
-APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW, THEN YOU
-MAY NOT USE THE CONTENT.</P>
-<H3>Applicable Licenses</H3>
-<P>Unless otherwise indicated, all Content made available by the Eclipse
-Foundation is provided to you under the terms and conditions of the Eclipse
-Public License Version 1.0 ("EPL"). A copy of the EPL is provided with this
-Content and is also available at <A
-href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</A>.
-For purposes of the EPL, "Program" will mean the Content.</P>
-<P>Content includes, but is not limited to, source code, object code,
-documentation and other files maintained in the Eclipse.org CVS repository
-("Repository") in CVS modules ("Modules") and made available as downloadable
-archives ("Downloads").</P>
-<P>Content may be apportioned into plug-ins ("Plug-ins"), plug-in fragments
-("Fragments"), and features ("Features"). A Feature is a bundle of one or more
-Plug-ins and/or Fragments and associated material. Files named "feature.xml" may
-contain a list of the names and version numbers of the Plug-ins and/or Fragments
-associated with a Feature. Plug-ins and Fragments are located in directories
-named "plugins" and Features are located in directories named "features".</P>
-<P>Features may also include other Features ("Included Features"). Files named
-"feature.xml" may contain a list of the names and version numbers of Included
-Features.</P>
-<P>The terms and conditions governing Plug-ins and Fragments should be contained
-in files named "about.html" ("Abouts"). The terms and conditions governing
-Features and Included Features should be contained in files named "license.html"
-("Feature Licenses"). Abouts and Feature Licenses may be located in any
-directory of a Download or Module including, but not limited to the following
-locations:</P>
-<UL>
- <LI>The top-level (root) directory
- <LI>Plug-in and Fragment directories
- <LI>Subdirectories of the directory named "src" of certain Plug-ins
- <LI>Feature directories </LI></UL>
-<P>Note: if a Feature made available by the Eclipse Foundation is installed
-using the Eclipse Update Manager, you must agree to a license ("Feature Update
-License") during the installation process. If the Feature contains Included
-Features, the Feature Update License should either provide you with the terms
-and conditions governing the Included Features or inform you where you can
-locate them. Feature Update Licenses may be found in the "license" property of
-files named "feature.properties". Such Abouts, Feature Licenses and Feature
-Update Licenses contain the terms and conditions (or references to such terms
-and conditions) that govern your use of the associated Content in that
-directory.</P>
-<P>THE ABOUTS, FEATURE LICENSES AND FEATURE UPDATE LICENSES MAY REFER TO THE EPL
-OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS. SOME OF THESE
-OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):</P>
-<UL>
- <LI>Common Public License Version 1.0 (available at <A
- href="http://www.eclipse.org/legal/cpl-v10.html">http://www.eclipse.org/legal/cpl-v10.html</A>)
-
- <LI>Apache Software License 1.1 (available at <A
- href="http://www.apache.org/licenses/LICENSE">http://www.apache.org/licenses/LICENSE</A>)
-
- <LI>Apache Software License 2.0 (available at <A
- href="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</A>)
-
- <LI>IBM Public License 1.0 (available at <A
- href="http://oss.software.ibm.com/developerworks/opensource/license10.html">http://oss.software.ibm.com/developerworks/opensource/license10.html</A>)
-
- <LI>Metro Link Public License 1.00 (available at <A
- href="http://www.opengroup.org/openmotif/supporters/metrolink/license.html">http://www.opengroup.org/openmotif/supporters/metrolink/license.html</A>)
-
- <LI>Mozilla Public License Version 1.1 (available at <A
- href="http://www.mozilla.org/MPL/MPL-1.1.html">http://www.mozilla.org/MPL/MPL-1.1.html</A>)
- </LI>
-
- <LI>Common Development and Distribution License (CDDL) Version 1.0 (available at <A
- href="http://www.sun.com/cddl/cddl.html">http://www.sun.com/cddl/cddl.html)</A>
- </LI>
-</UL>
-<P>IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR
-TO USE OF THE CONTENT. If no About, Feature License or Feature Update License is
-provided, please contact the Eclipse Foundation to determine what terms and
-conditions govern that particular Content.</P>
-<H3>Cryptography</H3>
-<P>Content may contain encryption software. The country in which you are
-currently may have restrictions on the import, possession, and use, and/or
-re-export to another country, of encryption software. BEFORE using any
-encryption software, please check the country's laws, regulations and policies
-concerning the import, possession, or use, and re-export of encryption software,
-to see if this is permitted.</P></BODY></HTML>
