diff options
| author | kprice | 2008-01-30 21:16:47 +0000 |
|---|---|---|
| committer | kprice | 2008-01-30 21:16:47 +0000 |
| commit | 50192854da7f9daa43b022687ea79d122941e6e8 (patch) | |
| tree | e01105087d3332a6435ede4db601e3340d9a1f9d /docs/org.eclipse.jst.j2ee.doc.user | |
| parent | 245dbf90f1558be0c821e751e6e3e2f9839be1fa (diff) | |
| download | webtools.javaee-50192854da7f9daa43b022687ea79d122941e6e8.tar.gz webtools.javaee-50192854da7f9daa43b022687ea79d122941e6e8.tar.xz webtools.javaee-50192854da7f9daa43b022687ea79d122941e6e8.zip | |
[216965] updates to J2EE docs for WTP 3.0. Plugin ver# increased.
Diffstat (limited to 'docs/org.eclipse.jst.j2ee.doc.user')
76 files changed, 1988 insertions, 1926 deletions
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/DocBuild.xml b/docs/org.eclipse.jst.j2ee.doc.user/DocBuild.xml index 4b0eefe35..9653340d1 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/DocBuild.xml +++ b/docs/org.eclipse.jst.j2ee.doc.user/DocBuild.xml @@ -21,7 +21,8 @@ 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 --> <project name="eclipsehelp" default="all"> @@ -44,14 +45,14 @@ <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.csspath" value="../org.eclipse.wst.doc.user" /> <property name="args.eclipse.provider" value="Eclipse.org" /> - <property name="args.eclipse.version" value="1.5.0" /> - <property name="args.input" location="jst_j2ee_toc.ditamap" /> + <property name="args.eclipse.version" value="3.3.0" /> + <property name="args.input" location="jst_j2ee_relsmap.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="output.dir" location="" /> <property name="transtype" value="eclipsehelp" /> </ant> <copy file="myplugin.xml" tofile="plugin.xml" overwrite="yes" /> 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 index 5c059b0a0..351b03929 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/META-INF/MANIFEST.MF +++ b/docs/org.eclipse.jst.j2ee.doc.user/META-INF/MANIFEST.MF @@ -2,6 +2,6 @@ Manifest-Version: 1.0 Bundle-ManifestVersion: 2 Bundle-Name: %pluginName Bundle-SymbolicName: org.eclipse.jst.j2ee.doc.user; singleton:=true -Bundle-Version: 1.0.300.qualifier +Bundle-Version: 1.1.0.qualifier Bundle-Vendor: %pluginProvider Bundle-Localization: plugin 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 index 5007e004e..499435bf3 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/jst_j2ee_relsmap.ditamap +++ b/docs/org.eclipse.jst.j2ee.doc.user/jst_j2ee_relsmap.ditamap @@ -1,4 +1,5 @@ <?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">
@@ -96,12 +97,13 @@ scope="peer"></topicref> </relrow>
<relrow>
<relcell collection-type="family">
-<topicref href="topics/cjviewfilters.dita" navtitle="Filters in the Project Explorer view">
-</topicref>
<topicref href="topics/cjview.dita" navtitle="Project Explorer view in the J2EE perspective">
</topicref>
</relcell>
-<relcell></relcell>
+<relcell>
+<topicref href="topics/tjviewfilters.dita" navtitle="Filtering in the Project Explorer view">
+</topicref>
+</relcell>
<relcell></relcell>
</relrow>
<relrow>
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 index 0ffcf8543..74d6d08c8 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/jst_j2ee_toc.ditamap +++ b/docs/org.eclipse.jst.j2ee.doc.user/jst_j2ee_toc.ditamap @@ -1,18 +1,18 @@ <?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
+<!--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="J2EE Applications">
+<topicref href="topics/ph-j2eeapp.dita" navtitle="J2EE applications">
<anchor id="before_intro_topics"/>
<topicref href="topics/cjarch.dita" navtitle="J2EE architecture"></topicref>
-<topicref href="topics/cjpers.dita" navtitle="J2EE perspective"></topicref>
-<topicref href="topics/cjview.dita" navtitle="Project Explorer view in the J2EE perspective">
+<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/cjviewfilters.dita" navtitle="Filters in the Project Explorer view">
+<topicref href="topics/tjviewfilters.dita" navtitle="Filtering in the Project Explorer view">
</topicref>
<anchor id="after_filters"/>
<anchor id="before_projects"/>
@@ -37,7 +37,7 @@ </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">
+<topicref href="topics/tchangejavalevel.dita" navtitle="Changing the Java compiler version for a J2EE project">
</topicref>
<anchor id="childof_J2EEProjectFacets"/></topicref>
<anchor id="J2EEProjectFacets"/>
@@ -61,8 +61,8 @@ <anchor id="before_dependencies"/>
<topicref href="topics/cjcircle.dita" navtitle="Cyclical dependencies between J2EE modules">
</topicref>
-<topicref href="topics/tjcircleb.dita" navtitle="Correcting cyclical dependencies after an EAR is imported">
-</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>
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 index 7f22f6ccb..f098fa07a 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/jst_j2ee_toc.xml +++ b/docs/org.eclipse.jst.j2ee.doc.user/jst_j2ee_toc.xml @@ -1,81 +1,83 @@ -<?xml version="1.0" encoding="utf-8"?> -<?NLS TYPE="org.eclipse.help.toc"?> +<?xml version="1.0" encoding="UTF-8"?> + +<?NLS TYPE="org.eclipse.help.toc"?> + <toc label="J2EE applications - WTP" topic="topics/ph-j2eeapp.html"> - <anchor id="map_top"/> - <topic label="J2EE Applications" href="topics/ph-j2eeapp.html"> - <anchor id="before_intro_topics"/> - <topic label="J2EE architecture" href="topics/cjarch.html"/> - <topic label="J2EE perspective" href="topics/cjpers.html"/> - <topic label="Project Explorer view in the J2EE perspective" href="topics/cjview.html"/> - <anchor id="after_intro_topics"/> - <anchor id="before_filters"/> - <topic label="Filters in the Project Explorer view" href="topics/cjviewfilters.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 J2EE 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 J2EE 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 J2EE 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="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>
\ No newline at end of file +<anchor id="map_top"/> +<topic label="J2EE applications" href="topics/ph-j2eeapp.html"> +<anchor id="before_intro_topics"/> +<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 J2EE 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 J2EE 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 J2EE 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="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 index 0bb43b86f..d718056ff 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/myplugin.xml +++ b/docs/org.eclipse.jst.j2ee.doc.user/myplugin.xml @@ -1,8 +1,8 @@ <?xml version="1.0" encoding="UTF-8"?> -<?eclipse version="3.0"?> +<?eclipse version="3.3"?> <?NLS TYPE="org.eclipse.help.toc"?> <!-- /******************************************************************************* - * Copyright (c) 2000, 2007 IBM Corporation and others. + * 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 @@ -20,4 +20,7 @@ <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.userindex.html b/docs/org.eclipse.jst.j2ee.doc.user/org.eclipse.jst.j2ee.doc.userindex.html deleted file mode 100644 index 469b8156a..000000000 --- a/docs/org.eclipse.jst.j2ee.doc.user/org.eclipse.jst.j2ee.doc.userindex.html +++ /dev/null @@ -1,270 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> -<meta name="copyright" content="(C) Copyright IBM Corporation 2007" /> -<meta name="security" content="public" /> -<meta name="Robots" content="index,follow" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta name="DC.Format" content="XHTML" /> -<!-- All rights reserved. Licensed Materials Property of IBM --> -<!-- US Government Users Restricted Rights --> -<!-- Use, duplication or disclosure restricted by --> -<!-- GSA ADP Schedule Contract with IBM Corp. --> -<link rel="stylesheet" type="text/css" href="ibmdita.css" /> -<title>Index</title> -</head> -<body> -<h1>Index</h1> -<a name="IDX0_41" href="#IDX1_41">A</a> -<a name="IDX0_42" href="#IDX1_42">B</a> -<a name="IDX0_43" href="#IDX1_43">C</a> -<a name="IDX0_44" href="#IDX1_44">D</a> -<a name="IDX0_45" href="#IDX1_45">E</a> -<a name="IDX0_46" href="#IDX1_46">F</a> -<a name="IDX0_4A" href="#IDX1_4A">J</a> -<a name="IDX0_50" href="#IDX1_50">P</a> -<a name="IDX0_52" href="#IDX1_52">R</a> -<a name="IDX0_54" href="#IDX1_54">T</a> -<a name="IDX0_56" href="#IDX1_56">V</a> -<hr></hr> -<strong><a name="IDX1_41" href="#IDX0_41">A</a></strong> -<ul class="indexlist"> -<li>application client projects -<ul class="indexlist"> -<li><a href="topics/tjappproj.html#tjappproj">creating</a> -</li> -<li><a href="topics/tjexpapp.html#tjexpapp">exporting</a> -</li> -<li><a href="topics/tjimpapp.html#tjimpapp">importing</a> -</li> -<li><a href="topics/cjappcliproj.html#cjappcliproj">overview</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_42" href="#IDX0_42">B</a></strong> -<ul class="indexlist"> -<li>build validation -<ul class="indexlist"> -<li><a href="topics/tjval.html#tjval">enabling</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_43" href="#IDX0_43">C</a></strong> -<ul class="indexlist"> -<li>code validation -<ul class="indexlist"> -<li><a href="topics/tjvaldisable.html#tjvaldisable">disabling</a> -</li> -<li><a href="topics/rvalerr.html#rvalerr">error solutions</a> -</li> -<li><a href="topics/rvalidators.html#rvalidators">J2EE validators</a> -</li> -<li><a href="topics/tjvalmanual.html#tjvalmanual">manual</a> -</li> -<li><a href="topics/tjvalglobalpref.html#tjvalglobalpref">overriding global preferences</a> -</li> -<li><a href="topics/tjval.html#tjval">overview</a> -</li> -<li><a href="topics/tjvalselect.html#tjvalselect">selecting validators</a> -</li> -</ul> -</li> -<li>connector projects -<ul class="indexlist"> -<li><a href="topics/tjrar.html#tjrar">creating</a> -</li> -<li><a href="topics/tjexprar.html#tjexprar">exporting</a> -</li> -<li><a href="topics/tjimprar.html#tjimprar">importing</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_44" href="#IDX0_44">D</a></strong> -<ul class="indexlist"> -<li>dependencies -<ul class="indexlist"> -<li><a href="topics/tjcircleb.html#tjcircleb">correcting cyclical</a> -</li> -<li><a href="topics/cjcircle.html#cjcircle">cycles between modules</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_45" href="#IDX0_45">E</a></strong> -<ul class="indexlist"> -<li>EAR -<ul class="indexlist"> -<li><a href="topics/tjcircleb.html#tjcircleb">correcting cyclical dependencies</a> -</li> -<li>files -<ul class="indexlist"> -<li><a href="topics/tjexpear.html#tjexpear">exporting</a> -</li> -<li><a href="topics/tjimpear.html#tjimpear">importing</a> -</li> -</ul> -</li> -</ul> -</li> -<li>enterprise applications -<ul class="indexlist"> -<li><a href="topics/cjpers.html#cjpers">J2EE perspective</a> -</li> -<li>projects -<ul class="indexlist"> -<li><a href="topics/cjearproj.html#cjearproj">artifacts</a> -</li> -<li><a href="topics/tjear.html#tjear">creating</a> -</li> -<li><a href="topics/tjexpear.html#tjexpear">exporting</a> -</li> -<li><a href="topics/tjimpear.html#tjimpear">importing</a> -</li> -</ul> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_46" href="#IDX0_46">F</a></strong> -<ul class="indexlist"> -<li>facets -<ul class="indexlist"> -<li><a href="topics/tchangefacet.html#tchangefacet">changing versions</a> -</li> -</ul> -</li> -<li>filters -<ul class="indexlist"> -<li><a href="topics/cjviewfilters.html#cjviewfilters">Project Explorer view</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_4A" href="#IDX0_4A">J</a></strong> -<ul class="indexlist"> -<li>J2EE -<ul class="indexlist"> -<li><a href="topics/taddingfacet.html#taddingfacet">adding project facets</a> -</li> -<li><a href="topics/cjappcliproj.html#cjappcliproj">application client projects</a> -</li> -<li><a href="topics/cjarch.html#cjarch">architecture</a> -</li> -<li><a href="topics/tchangefacet.html#tchangefacet">changing facet versions</a> -</li> -<li><a href="topics/cjcircle.html#cjcircle">cyclical dependencies between modules</a> -</li> -<li>enterprise application projects -<ul class="indexlist"> -<li><a href="topics/tjear.html#tjear">creating</a> -</li> -<li><a href="topics/cjearproj.html#cjearproj">overview</a> -</li> -</ul> -</li> -<li><a href="topics/cfacets.html#cfacets">project facets</a> -</li> -<li><a href="topics/tjtargetserver.html#tjtargetserver">target servers</a> -</li> -<li><a href="topics/rjlimitcurrent.html#rjlimitcurrent">tool limitations</a> -</li> -<li><a href="topics/cjpers.html#cjpers">workbench perspectives</a> -</li> -</ul> -</li> -<li>Java -<ul class="indexlist"> -<li><a href="topics/tchangejavalevel.html#tchangejavalevel">J2EE project compiler level</a> -</li> -</ul> -</li> -<li>JavaServer Faces (JSF) -<ul class="indexlist"> -<li><a href="topics/cfacets.html#cfacets">project facets</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_50" href="#IDX0_50">P</a></strong> -<ul class="indexlist"> -<li>projects -<ul class="indexlist"> -<li><a href="topics/tchangefacet.html#tchangefacet">changing facet versions</a> -</li> -<li><a href="topics/tjcircleb.html#tjcircleb">correcting cyclical dependencies</a> -</li> -<li><a href="topics/cjcircle.html#cjcircle">cyclical dependencies</a> -</li> -<li><a href="topics/cjearproj.html#cjearproj">enterprise applications</a> -</li> -<li>facets -<ul class="indexlist"> -<li><a href="topics/taddingfacet.html#taddingfacet">adding</a> -</li> -<li><a href="topics/cfacets.html#cfacets">overview</a> -</li> -</ul> -</li> -<li><a href="topics/tchangejavalevel.html#tchangejavalevel">Java compiler level</a> -</li> -<li><a href="topics/tjtargetserver.html#tjtargetserver">target servers</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_52" href="#IDX0_52">R</a></strong> -<ul class="indexlist"> -<li>RAR files -<ul class="indexlist"> -<li><a href="topics/tjexprar.html#tjexprar">exporting</a> -</li> -<li><a href="topics/tjimprar.html#tjimprar">importing</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_54" href="#IDX0_54">T</a></strong> -<ul class="indexlist"> -<li>target servers -<ul class="indexlist"> -<li><a href="topics/tjtargetserver.html#tjtargetserver">J2EE applications</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_56" href="#IDX0_56">V</a></strong> -<ul class="indexlist"> -<li>validation -<ul class="indexlist"> -<li><a href="topics/tjvaldisable.html#tjvaldisable">disabling</a> -</li> -<li><a href="topics/rvalerr.html#rvalerr">error solutions</a> -</li> -<li><a href="topics/rvalidators.html#rvalidators">J2EE validators</a> -</li> -<li><a href="topics/tjvalmanual.html#tjvalmanual">manual</a> -</li> -<li><a href="topics/tjvalglobalpref.html#tjvalglobalpref">overriding global preferences</a> -</li> -<li><a href="topics/tjval.html#tjval">overview</a> -</li> -<li><a href="topics/tjvalselect.html#tjvalselect">selecting validators</a> -</li> -</ul> -</li> -<li>views -<ul class="indexlist"> -<li><a href="topics/cjview.html#cjview">Project Explorer</a> -</li> -<li><a href="topics/cjviewfilters.html#cjviewfilters">Project Explorer filters</a> -</li> -</ul> -</li> -</ul> -</body></html> 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 index 11f1d691b..8a4c09652 100644 --- 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 @@ -5,7 +5,7 @@ <topic href="topics/cjarch.html#cjarch" title="J2EE architecture"/> </entry> <entry keyword="workbench perspectives"> - <topic href="topics/cjpers.html#cjpers" title="J2EE perspective"/> + <topic href="topics/cjpers.html#cjpers" title="Java EE perspective"/> </entry> <entry keyword="enterprise application projects"> <entry keyword="overview"> @@ -37,9 +37,12 @@ <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> <entry keyword="enterprise applications"> - <entry keyword="J2EE perspective"> - <topic href="topics/cjpers.html#cjpers" title="J2EE perspective"/> + <entry keyword="Java EE perspective"> + <topic href="topics/cjpers.html#cjpers" title="Java EE perspective"/> </entry> <entry keyword="projects"> <entry keyword="artifacts"> @@ -58,15 +61,15 @@ </entry> <entry keyword="views"> <entry keyword="Project Explorer"> - <topic href="topics/cjview.html#cjview" title="Project Explorer view in the J2EE perspective"/> + <topic href="topics/cjview.html#cjview" title="Project Explorer view in the Java EE perspective"/> </entry> <entry keyword="Project Explorer filters"> - <topic href="topics/cjviewfilters.html#cjviewfilters" title="Filters in the Project Explorer view"/> + <topic href="topics/cjviewfilters.html#cjviewfiltersCait" title="Filters in the project explorer view"/> </entry> </entry> <entry keyword="filters"> <entry keyword="Project Explorer view"> - <topic href="topics/cjviewfilters.html#cjviewfilters" title="Filters in the Project Explorer view"/> + <topic href="topics/cjviewfilters.html#cjviewfiltersCait" title="Filters in the project explorer view"/> </entry> </entry> <entry keyword="projects"> diff --git a/docs/org.eclipse.jst.j2ee.doc.user/plugin.properties b/docs/org.eclipse.jst.j2ee.doc.user/plugin.properties index 2ca2bd40a..8930de3ed 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/plugin.properties +++ b/docs/org.eclipse.jst.j2ee.doc.user/plugin.properties @@ -1,5 +1,5 @@ ############################################################################### -# Copyright (c) 2001, 2006 IBM Corporation and others. +# 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 diff --git a/docs/org.eclipse.jst.j2ee.doc.user/plugin.xml b/docs/org.eclipse.jst.j2ee.doc.user/plugin.xml index 0bb43b86f..d718056ff 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/plugin.xml +++ b/docs/org.eclipse.jst.j2ee.doc.user/plugin.xml @@ -1,8 +1,8 @@ <?xml version="1.0" encoding="UTF-8"?> -<?eclipse version="3.0"?> +<?eclipse version="3.3"?> <?NLS TYPE="org.eclipse.help.toc"?> <!-- /******************************************************************************* - * Copyright (c) 2000, 2007 IBM Corporation and others. + * 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 @@ -20,4 +20,7 @@ <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/cfacets.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/cfacets.dita index 02e897e74..c415b7cc7 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cfacets.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/cfacets.dita @@ -1,10 +1,11 @@ <?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 J2EE projects. </shortdesc>
+for J2EE projects and are used as part of the runtime configuration. </shortdesc>
<prolog><metadata>
<keywords><indexterm>J2EE<indexterm>project facets</indexterm></indexterm>
<indexterm>JavaServer Faces (JSF)<indexterm>project facets</indexterm></indexterm>
@@ -13,8 +14,8 @@ for J2EE projects. </shortdesc> </metadata></prolog>
<conbody outputclass="id_conbody">
<p outputclass="anchor_topictop"></p>
-<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.
+<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>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/cfacets.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/cfacets.html index a590cb9de..f243a4d54 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cfacets.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/cfacets.html @@ -2,17 +2,17 @@ <html lang="en-us" xml:lang="en-us"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> +<meta 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 J2EE projects." /> -<meta name="description" content="Facets define characteristics and requirements for J2EE projects." /> -<meta content="J2EE development, project facets, J2EE modules, projects, facets, overview" name="DC.subject" /> -<meta content="J2EE development, project facets, J2EE modules, projects, facets, overview" name="keywords" /> +<meta name="abstract" content="Facets define characteristics and requirements for J2EE projects and are used as part of the runtime configuration." /> +<meta name="description" content="Facets define characteristics and requirements for J2EE projects and are used as part of the runtime configuration." /> +<meta content="J2EE, project facets, JavaServer Faces (JSF), projects, facets, overview" name="DC.subject" /> +<meta content="J2EE, 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" /> @@ -29,18 +29,20 @@ <body id="cfacets"><a name="cfacets"><!-- --></a> -<h1 class="topictitle1" id="title">Project facets</h1> +<h1 class="id_title">Project facets</h1> -<div id="conbody"><div id="shortdesc">Facets define characteristics and requirements -for J2EE projects. </div> +<div class="id_conbody"><p class="id_shortdesc">Facets define characteristics and requirements +for J2EE projects and are used as part of the runtime configuration. </p> -<anchor id="topictop"></anchor><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 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 J2EE projects and other types of projects that are based on J2EE projects, such as enterprise application projects, dynamic @@ -60,7 +62,7 @@ Module facet. Some facets can be removed from a project and others cannot.</p> 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 J2EE project by editing the facets for the project.">Changing the version of a facet</a>.</p> -<anchor id="topicbottom"></anchor> +<p class="anchor_topicbottom" /> </div> @@ -68,7 +70,7 @@ the version number of a facet, see <a href="tchangefacet.html" title="You can ch <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="">Creating an enterprise application project</a></div> +<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 J2EE project</a></div> @@ -78,4 +80,4 @@ the version number of a facet, see <a href="tchangefacet.html" title="You can ch </div> </body> -</html> +</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 index f52fd0ba0..d9c651a7c 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjappcliproj.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjappcliproj.dita @@ -1,9 +1,12 @@ <?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"></shortdesc>
+<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>J2EE<indexterm>application client projects</indexterm></indexterm>
@@ -38,8 +41,8 @@ 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> <i>builder</i> is associated with the
-project so the <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
+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.
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjappcliproj.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjappcliproj.html index e8614c5fb..7192424fa 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjappcliproj.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjappcliproj.html @@ -2,17 +2,17 @@ <html lang="en-us" xml:lang="en-us"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> +<meta 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="" /> -<meta name="description" content="" /> -<meta content="projects, application client, application client projects, overview, J2EE modules" name="DC.subject" /> -<meta content="projects, application client, application client projects, overview, J2EE modules" name="keywords" /> +<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, J2EE" name="DC.subject" /> +<meta content="application client projects, overview, J2EE" 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" /> @@ -26,22 +26,26 @@ <body id="cjappcliproj"><a name="cjappcliproj"><!-- --></a> -<h1 class="topictitle1" id="title">Application client projects</h1> +<h1 class="id_title">Application client projects</h1> -<div id="conbody"><div id="shortdesc"></div> +<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> -<anchor id="topictop"></anchor><p> Application client projects contain the -resources needed for application client modules. An application client module -is used to contain a full-function client Java™ application (non Web-based) that connects -to and uses the J2EE resources defined in your server. When you place the -client code in an application client module instead of a simple JAR file, -the application client benefits from the server's resources (it does not need -to re-specify the class path to J2EE and server JAR files) as well as from -easier JNDI lookup (the client container fills in the initial context and -other parameters). The application client project allows you to work as if -you are creating a standalone Java application in a Java project.</p> +<p 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 J2EE resources defined in your server. When you place the client +code in an application client module instead of a simple JAR file, the application +client benefits from the server's resources (it does not need to re-specify +the class path to J2EE and server JAR files) as well as from easier JNDI lookup +(the client container fills in the initial context and other parameters). +The application client project allows you to work as if you are creating a +standalone Java application in a Java project.</p> <p>An application client project enables you to do the following things:</p> @@ -57,8 +61,8 @@ you are creating a standalone Java application in a Java project.</p> <p>Like Java projects, application client projects contain the resources needed for application clients, including Java class files. When you create a new application client project, the environment is -set up for Java development. A Java <em>builder</em> is associated with the -project so the Java source can be incrementally compiled as it is updated. +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 @@ -92,12 +96,12 @@ formats).</p> 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> -<anchor id="topicbottom"></anchor> +<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 services.">J2EE architecture</a></div> +<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> diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjarch.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjarch.dita index ef018ae7e..f715cd4c3 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjarch.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjarch.dita @@ -8,7 +8,8 @@ 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></keywords>
+<keywords><indexterm>J2EE<indexterm>architecture</indexterm></indexterm><indexterm>Java
+EE</indexterm></keywords>
</metadata></prolog>
<conbody outputclass="id_conbody">
<p outputclass="anchor_topictop"></p>
@@ -20,19 +21,23 @@ enterprise applications, and ensures portability of developed applications with an extensive test suite.</p>
<p>J2EE architecture supports component-based development of multi-tier enterprise
applications. A J2EE application system typically includes the following tiers:</p>
-<ul>
-<li><b>Client tier</b>: In the client tier, Web components, such as Servlets
-and JavaServer Pages (JSPs), or standalone <tm tmclass="special" tmowner="Sun Microsystems, Inc."
+<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.</li>
-<li><b>Middle tier</b>: In the server tier, or middle tier, enterprise beans
-and Web Services encapsulate reusable, distributable business logic for the
-application. These server-tier components are contained on a J2EE Application
-Server, which provides the platform for these components to perform actions
-and store data.</li>
-<li><b>Enterprise data tier</b>: In the data tier, the enterprise's data is
-stored and persisted, typically in a relational database.</li>
-</ul>
+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
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjarch.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjarch.html index c6487ae7c..c321ffc10 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjarch.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjarch.html @@ -2,17 +2,17 @@ <html lang="en-us" xml:lang="en-us"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> +<meta 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 services." /> -<meta name="description" content="The Java 2 Platform, Enterprise Edition (J2EE) provides a standard for developing multitier, enterprise services." /> -<meta content="J2EE development, architecture" name="DC.subject" /> -<meta content="J2EE development, architecture" name="keywords" /> +<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" /> @@ -30,38 +30,47 @@ <body id="cjarch"><a name="cjarch"><!-- --></a> -<h1 class="topictitle1" id="title">J2EE architecture</h1> +<h1 class="id_title">J2EE architecture</h1> -<div id="conbody"><div id="shortdesc">The Java™ 2 Platform, Enterprise Edition (J2EE) -provides a standard for developing multitier, enterprise services.</div> +<div class="id_conbody"><p class="id_shortdesc">The Java™ 2 Platform, Enterprise Edition (J2EE) +provides a standard for developing multitier, enterprise applications.</p> -<anchor id="topictop"></anchor><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 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> -<ul> -<li><strong>Client tier</strong>: In the client tier, Web components, such as Servlets -and JavaServer Pages (JSPs), or standalone Java applications provide a dynamic interface -to the middle tier.</li> +<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> + -<li><strong>Middle tier</strong>: In the server tier, or middle tier, enterprise beans -and Web Services encapsulate reusable, distributable business logic for the -application. These server-tier components are contained on a J2EE Application -Server, which provides the platform for these components to perform actions -and store data.</li> +<dt class="dlterm">Enterprise data tier</dt> -<li><strong>Enterprise data tier</strong>: In the data tier, the enterprise's data is -stored and persisted, typically in a relational database.</li> +<dd>In the data tier, the enterprise's data is stored and persisted, typically +in a relational database.</dd> -</ul> +</dl> <p>J2EE applications are comprised of components, containers, and services. Components are application-level components. Web components, such as Servlets @@ -72,16 +81,16 @@ 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> -<anchor id="topicbottom"></anchor> +<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</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="">Creating an enterprise application project</a></div> +<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> @@ -91,4 +100,4 @@ download and read the <a href="http://java.sun.com/j2ee/download.html#platformsp </div> </body> -</html> +</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 index 5e20647ae..d4be75971 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjcircle.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjcircle.dita @@ -1,9 +1,12 @@ <?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 J2EE modules</title>
-<shortdesc outputclass="id_shortdesc"></shortdesc>
+<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>J2EE<indexterm>cyclical dependencies between modules</indexterm></indexterm>
@@ -12,13 +15,10 @@ </metadata></prolog>
<conbody outputclass="id_conbody">
<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>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
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjcircle.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjcircle.html index 73fe22fa0..a4b30bfd0 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjcircle.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjcircle.html @@ -2,17 +2,17 @@ <html lang="en-us" xml:lang="en-us"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> +<meta 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 J2EE modules" /> -<meta name="abstract" content="" /> -<meta name="description" content="" /> -<meta content="cyclical dependencies, overview, projects, J2EE modules" name="DC.subject" /> -<meta content="cyclical dependencies, overview, projects, J2EE modules" name="keywords" /> +<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, J2EE, cyclical dependencies between modules, projects, cyclical dependencies" name="DC.subject" /> +<meta content="dependencies, cycles between modules, J2EE, 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" /> @@ -24,25 +24,27 @@ <body id="cjcircle"><a name="cjcircle"><!-- --></a> -<h1 class="topictitle1" id="title">Cyclical dependencies between J2EE modules</h1> +<h1 class="id_title">Cyclical dependencies between J2EE modules</h1> -<div id="conbody"><div id="shortdesc"></div> +<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> -<anchor id="topictop"></anchor><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 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> -<anchor id="topicbottom"></anchor> +<p class="anchor_topicbottom" /> </div> diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjearproj.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjearproj.dita index 8de411528..aca0056fd 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjearproj.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjearproj.dita @@ -1,4 +1,5 @@ <?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">
@@ -13,11 +14,11 @@ together the resources that are required to deploy a J2EE enterprise application </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."
+<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
@@ -32,9 +33,9 @@ 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 <i>utility JAR files.</i> 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."
+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
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjearproj.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjearproj.html index 527198640..300f77ecd 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjearproj.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjearproj.html @@ -2,8 +2,8 @@ <html lang="en-us" xml:lang="en-us"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> +<meta 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))' /> @@ -11,8 +11,8 @@ <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 application projects, overview, artifacts, projects, enterprise application, J2EE modules" name="DC.subject" /> -<meta content="enterprise application projects, overview, artifacts, projects, enterprise application, J2EE modules" name="keywords" /> +<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" /> @@ -30,17 +30,19 @@ <body id="cjearproj"><a name="cjearproj"><!-- --></a> -<h1 class="topictitle1" id="title">Enterprise application projects</h1> +<h1 class="id_title">Enterprise application projects</h1> -<div id="conbody"><div id="shortdesc">An enterprise application project ties -together the resources that are required to deploy a J2EE enterprise application.</div> +<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> -<anchor id="topictop"></anchor><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. +<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> @@ -56,9 +58,9 @@ such as Web archive (WAR) files and EJB JAR files.</p> <p>An enterprise application can contain utility JAR files that are to be used by the contained modules. This allows sharing of code at the application level by multiple Web, EJB, or application client modules. These JAR files -are commonly referred to as <em>utility JAR files.</em> The utility JAR files -defined for an enterprise application project can be actual JAR files in the -project, or you can include utility Java projects that are designated to become +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 @@ -87,7 +89,7 @@ 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 J2EE projects. ">Project facets</a>. This file is created in the <span class="uicontrol">.settings</span> folder.</dd> +<dd>This file lists the facets of the enterprise application project. See <a href="cfacets.html" title="Facets define characteristics and requirements for J2EE 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> @@ -97,16 +99,16 @@ This file is created in the <span class="uicontrol">.settings</span> folder.</dd </dl> </div> -<anchor id="topicbottom"></anchor> +<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 services.">J2EE architecture</a></div> -<div><a href="../topics/cfacets.html" title="Facets define characteristics and requirements for J2EE projects.">Project facets</a></div> +<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 J2EE 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="">Creating an enterprise application project</a></div> +<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> @@ -115,4 +117,4 @@ This file is created in the <span class="uicontrol">.settings</span> folder.</dd </div> </body> -</html> +</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 index cd97f2faa..5f0468eb9 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjpers.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjpers.dita @@ -1,26 +1,32 @@ <?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">J2EE perspective</title>
-<shortdesc outputclass="id_shortdesc">The J2EE perspective includes workbench
-views that you can use when developing resources for enterprise applications,
-EJB modules, Web modules, application client modules, and connector projects
-or modules.</shortdesc>
+<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>J2EE<indexterm>workbench perspectives</indexterm></indexterm>
-<indexterm>enterprise applications<indexterm>J2EE perspective</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 J2EE perspective by clicking <menucascade><uicontrol>Window</uicontrol>
-<uicontrol>Show View</uicontrol></menucascade> and selecting the view.</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 J2EE perspective includes the following workbench views:</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
@@ -34,11 +40,12 @@ 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 J2EE perspective shows the outline of the file
-that you are editing. For example, if you are using a tabbed deployment descriptor
-editor, the Outline view shows the outline for the selected page's elements,
-and if you are editing on the Source tab, the outline for the XML source is
-displayed. If you are editing an enterprise bean in the <tm tmclass="special"
+<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>
@@ -55,6 +62,22 @@ problem in the appropriate resource.</dd> <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
@@ -63,14 +86,6 @@ 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><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></dl>
<p outputclass="anchor_topicbottom"></p>
</conbody>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjpers.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjpers.html index e68ea9471..7ba6d878a 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjpers.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjpers.html @@ -2,45 +2,48 @@ <html lang="en-us" xml:lang="en-us"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> +<meta 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 perspective" /> -<meta name="abstract" content="The J2EE perspective includes workbench views that you can use when developing resources for enterprise applications, EJB modules, Web modules, application client modules, and connector projects or modules." /> -<meta name="description" content="The J2EE perspective includes workbench views that you can use when developing resources for enterprise applications, EJB modules, Web modules, application client modules, and connector projects or modules." /> -<meta content="perspectives, J2EE" name="DC.subject" /> -<meta content="perspectives, J2EE" name="keywords" /> +<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="J2EE, workbench perspectives, enterprise applications, Java EE perspective" name="DC.subject" /> +<meta content="J2EE, 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>J2EE perspective</title> +<title>Java EE perspective</title> </head> <body id="cjpers"><a name="cjpers"><!-- --></a> -<h1 class="topictitle1" id="title">J2EE perspective</h1> +<h1 class="id_title">Java EE perspective</h1> -<div id="conbody"><div id="shortdesc">The J2EE perspective includes workbench -views that you can use when developing resources for enterprise applications, -EJB modules, Web modules, application client modules, and connector projects -or modules.</div> +<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> -<anchor id="topictop"></anchor><p>You can rearrange the location, tiling, and -size of the views within the perspective. You can also add other views to -the J2EE perspective by clicking <span class="menucascade"><span class="uicontrol">Window</span> - > <span class="uicontrol">Show View</span></span> and selecting the view.</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 J2EE perspective includes the following workbench views:</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> @@ -48,7 +51,7 @@ This is also true in the J2EE perspective.</p> <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, +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 @@ -57,11 +60,11 @@ J2EE application server are made readily available.</dd> <dt class="dlterm"><span class="uicontrol"> Outline</span></dt> -<dd>The Outline view in the J2EE perspective shows the outline of the file -that you are editing. For example, if you are using a tabbed deployment descriptor -editor, the Outline view shows the outline for the selected page's elements, -and if you are editing on the Source tab, the outline for the XML source is -displayed. If you are editing an enterprise bean in the Java editor, +<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> @@ -83,17 +86,6 @@ problem in the appropriate resource.</dd> values of objects in files you have open in an editor.</dd> -<dt class="dlterm"><span class="uicontrol">Status bar</span></dt> - -<dd>The Status bar provides a description of the location of selected objects -in the Project Explorer views in the left side. When file and deployment descriptors -are open, the status bar shows the read-only state of the files and the line -and column numbers when applicable. Sometimes when long operations run, a -status monitor will appear in the status bar, along with a button with a stop -sign icon. Clicking the stop sign stops the operation when the operation can -be cancelled.</dd> - - <dt class="dlterm"><span class="uicontrol">Servers</span></dt> <dd>The Servers view shows all the created server instances. You can start @@ -105,9 +97,30 @@ and stop each server from this view, and you can launch the test client.</dd> <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> -<anchor id="topicbottom"></anchor> +<p class="anchor_topicbottom" /> </div> @@ -117,4 +130,4 @@ into appropriate places in your source code.</dd> </div> </body> -</html> +</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 index a9c5cac7a..8ca49e104 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjview.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjview.dita @@ -1,35 +1,37 @@ <?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 J2EE perspective</title>
+<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 J2EE perspective, the Project Explorer view is your main view of your
-J2EE projects and resources.</shortdesc>
+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>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,
-click the <uicontrol>Filters</uicontrol> button from the drop-down menu at
+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. See <xref format="html" href="../../org.eclipse.platform.doc.user/concepts/cworkset.htm"
-scope="peer">Working Sets<desc></desc></xref>.</p>
-<p>The following image shows the Project Explorer view with a few projects:<image
-alt="Screen capture of the Project Explorer view" href="../images/ProjectExplorer.gif"
-outputclass="id_projectexplorerimage" placement="break"></image></p>
+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 index 002747a6b..5938c0d59 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjview.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjview.html @@ -2,39 +2,44 @@ <html lang="en-us" xml:lang="en-us"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> +<meta 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 J2EE perspective" /> -<meta name="abstract" content="While developing J2EE applications in the J2EE 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 J2EE perspective, the Project Explorer view is your main view of your J2EE projects and resources." /> +<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/cjviewfilters.html" /> +<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 J2EE perspective</title> +<title>Project Explorer view in the Java EE +perspective</title> </head> <body id="cjview"><a name="cjview"><!-- --></a> -<h1 class="topictitle1" id="title">Project Explorer view in the J2EE perspective</h1> +<h1 class="id_title">Project Explorer view in the Java EE +perspective</h1> -<div id="conbody"><div id="shortdesc">While developing J2EE applications in -the J2EE perspective, the Project Explorer view is your main view of your -J2EE projects and resources.</div> +<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> -<anchor id="topictop"></anchor><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 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 @@ -42,20 +47,18 @@ 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, -click the <span class="uicontrol">Filters</span> button from the drop-down menu at +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. See <a href="../../org.eclipse.platform.doc.user/concepts/cworkset.htm" title="">Working Sets</a>.</p> - -<p>The following image shows the Project Explorer view with a few projects:<br /><img id="projectexplorerimage" src="../images/ProjectExplorer.gif" alt="Screen capture of the Project Explorer view" /><br /></p> +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> -<anchor id="topicbottom"></anchor> +<p class="anchor_topicbottom" /> </div> -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cjviewfilters.html" title="You can filter the Project Explorer view to hide projects, folders, or files that you don't want to see.">Filters in the Project Explorer view</a></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> @@ -63,4 +66,4 @@ groups of related resources or projects. See <a href="../../org.eclipse.platform </div> </body> -</html> +</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 d9a257d8f..000000000 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjviewfilters.dita +++ /dev/null @@ -1,31 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!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 don't 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, open the Select
-Common Navigator Filters window by clicking the <uicontrol>Filters</uicontrol> button
-from the drop-down menu at the top right corner of the view. This window lists
-the available filters.</p>
-<p>On the Select Common Navigator Filters 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".</p>
-<p>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 check
-box next to <uicontrol>J2EE Deployment Descriptors</uicontrol>, the deployment
-descriptors are hidden from each project in the view.</p>
-<p outputclass="anchor_topicbottom"></p>
-</conbody>
-</concept>
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 index 1456e930e..651a66bfb 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-importexport.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-importexport.html @@ -1,52 +1,63 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html lang="en-us" xml:lang="en-us"> <head> -<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" /> - +<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> +<meta name="copyright" content="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="../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="topictitle1">Importing and exporting projects and files</h1> -<div><p>These topics cover how to import files and projects into the workbench -and export files and projects to disk.</p> + + +<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> +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> +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> +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> +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> +Connector projects are deployed into RAR files. You can import a connector project by importing a deployed RAR file.</li> <li class="ulchildlink"><strong><a href="../topics/cjcircle.html">Cyclical dependencies between J2EE modules</a></strong><br /> -</li> +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> @@ -54,5 +65,7 @@ You can resolve cyclical dependencies after an EAR is imported.</li> <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> +</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 index 42ffd8537..5584b1dd5 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-j2eeapp.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-j2eeapp.dita @@ -1,8 +1,9 @@ <?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">J2EE Applications</title>
+<title outputclass="id_title">J2EE applications</title>
<shortdesc outputclass="id_shortdesc">These topics deal with the <tm tmclass="special"
tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> 2
Platform, Enterprise Edition (J2EE).</shortdesc>
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 index 9b6143c96..a4076301e 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-j2eeapp.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-j2eeapp.html @@ -1,47 +1,63 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html lang="en-us" xml:lang="en-us"> <head> -<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" /> - -<title>J2EE Applications</title> +<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="J2EE applications" /> +<meta name="abstract" content="These topics deal with the Java 2 Platform, Enterprise Edition (J2EE)." /> +<meta name="description" content="These topics deal with the Java 2 Platform, Enterprise Edition (J2EE)." /> +<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>J2EE applications</title> </head> <body id="ph-j2eeapp"><a name="ph-j2eeapp"><!-- --></a> -<h1 class="topictitle1">J2EE Applications</h1> -<div><p>These topics deal with the Java™ 2 Platform, Enterprise Edition (J2EE).</p> + + +<h1 class="id_title">J2EE applications</h1> + + + +<div class="id_body"><p class="id_shortdesc">These topics deal with the Java™ 2 +Platform, Enterprise Edition (J2EE).</p> + +<p class="anchor_topictop" /> + +<p class="anchor_topicbottom" /> + </div> + <div> <ul class="ullinks"> <li class="ulchildlink"><strong><a href="../topics/cjarch.html">J2EE architecture</a></strong><br /> -The Java 2 Platform, Enterprise Edition (J2EE) provides -a standard for developing multitier, enterprise services.</li> -<li class="ulchildlink"><strong><a href="../topics/cjpers.html">J2EE perspective</a></strong><br /> -The J2EE perspective includes workbench views that you can use -when developing resources for enterprise applications, EJB modules, Web modules, -application client modules, and connector projects or modules.</li> -<li class="ulchildlink"><strong><a href="../topics/cjview.html">Project Explorer view in the J2EE perspective</a></strong><br /> -While developing J2EE applications in the J2EE perspective, the -Project Explorer view is your main view of your J2EE projects and resources.</li> +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> +The workbench can work with many different types of projects. The following topics cover creating and managing some of the types of projects related to J2EE development.</li> <li class="ulchildlink"><strong><a href="../topics/tjval.html">Validating code in enterprise applications</a></strong><br /> -</li> +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> +</div> + +</body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-projects.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-projects.html index 876ce021f..f01ecfd10 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-projects.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-projects.html @@ -1,50 +1,72 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html lang="en-us" xml:lang="en-us"> <head> -<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" /> - +<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> +<meta name="copyright" content="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="topictitle1">Working with projects</h1> -<div><p>The workbench can work with many different types of projects. The -following topics cover creating and managing some of the types of projects -related to J2EE development.</p> + + +<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 contains the hierarchy of resources -that are required to deploy a J2EE enterprise application, often referred -to as an EAR file.</li> +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 /> -</li> +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, the workbench requires that -you specify the server runtime environments for your J2EE projects. The target -server is specified during project creation and import, and it can be changed -in the project properties. The target server setting is the default mechanism -for setting the class path for J2EE projects.</li> +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 J2EE 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> +These topics cover how to import files and projects into the workbench and export files and projects to disk.</li> </ul> <div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/ph-j2eeapp.html" title="These topics deal with the Java 2 Platform, Enterprise Edition (J2EE).">J2EE Applications</a></div> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/ph-j2eeapp.html" title="These topics deal with the Java 2 Platform, Enterprise Edition (J2EE).">J2EE applications</a></div> +</div> </div> -</div></body> + +</body> </html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-ref.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-ref.html index c24a9c16f..a2dac8267 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-ref.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/ph-ref.html @@ -1,42 +1,56 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html lang="en-us" xml:lang="en-us"> <head> -<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" /> - +<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> +<meta name="copyright" content="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="topictitle1">Reference</h1> -<div><p>The following reference material on J2EE is available:</p> + + +<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> +This table lists the validators that are available for the different project types and gives a brief description of each validator.</li> <li class="ulchildlink"><strong><a href="../topics/rvalerr.html">Common validation errors and solutions</a></strong><br /> -You may encounter these common error messages when you validate -your projects.</li> +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> +This topic outlines current known limitations and restrictions for J2EE tooling.</li> </ul> <div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/ph-j2eeapp.html" title="These topics deal with the Java 2 Platform, Enterprise Edition (J2EE).">J2EE Applications</a></div> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/ph-j2eeapp.html" title="These topics deal with the Java 2 Platform, Enterprise Edition (J2EE).">J2EE applications</a></div> +</div> </div> -</div></body> + +</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 index 6c5cc4b4f..9cbad0940 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/rjlimitcurrent.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/rjlimitcurrent.dita @@ -1,4 +1,5 @@ <?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">
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/rjlimitcurrent.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/rjlimitcurrent.html index 94a245e98..f446bac7a 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/rjlimitcurrent.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/rjlimitcurrent.html @@ -2,8 +2,8 @@ <html lang="en-us" xml:lang="en-us"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> +<meta 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))' /> @@ -11,8 +11,8 @@ <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 tools, limitations, J2EE development" name="DC.subject" /> -<meta content="J2EE tools, limitations, J2EE development" name="keywords" /> +<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" /> @@ -22,15 +22,15 @@ <body id="rjlimitcurrent"><a name="rjlimitcurrent"><!-- --></a> -<h1 class="topictitle1" id="title">Limitations of J2EE development tools</h1> +<h1 class="id_title">Limitations of J2EE development tools</h1> -<div id="refbody"><div id="shortdesc">This topic outlines current known limitations -and restrictions for J2EE tooling.</div> +<div class="id_refbody"><p class="id_shortdesc">This topic outlines current known limitations +and restrictions for J2EE tooling.</p> -<div id="spacesLimitation"><h4 class="sectiontitle">Spaces -not supported in JAR URIs within an enterprise application</h4><anchor id="topictop"></anchor> +<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 @@ -38,13 +38,13 @@ 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 id="EARDBCSLimitation"><h4 class="sectiontitle">Enterprise application +<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 id="utilityJARLimitation"><h4 class="sectiontitle">Java™ build +<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 @@ -56,7 +56,7 @@ between JUnit and the Web project, remove the Java JAR Dependency from the Web p first, then remove the Utility JAR from the EAR. Follow this order to ensure that this works correctly.</div> -<div id="JARdepLimitation"><h4 class="sectiontitle">Java JAR Dependencies page fails to update Java build +<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 @@ -69,7 +69,7 @@ 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 id="locationLimitation"><h4 class="sectiontitle">'Invalid project description' +<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 @@ -80,10 +80,10 @@ 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> -<anchor id="topicbottom"></anchor> +<div class="anchor_topicbottom" /> </div> </body> -</html> +</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 index 6b6a19799..b4c14dfa5 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/rvalerr.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/rvalerr.dita @@ -1,14 +1,14 @@ <?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">You may encounter these common error
-messages when you validate your projects.</shortdesc>
+<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>
+<indexterm>validation<indexterm>error solutions</indexterm></indexterm></keywords>
</metadata></prolog>
<refbody outputclass="id_refbody">
<example outputclass="anchor_topictop"></example>
@@ -188,3 +188,4 @@ the project.</entry> <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 index fc60c8661..d9d30cbae 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/rvalerr.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/rvalerr.html @@ -2,17 +2,17 @@ <html lang="en-us" xml:lang="en-us"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> +<meta 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="You may encounter these common error messages when you validate your projects." /> -<meta name="description" content="You may encounter these common error messages when you validate your projects." /> -<meta content="validation, errors, solutions to errors, code validation, solutions to errors" name="DC.subject" /> -<meta content="validation, errors, solutions to errors, code validation, solutions to errors" name="keywords" /> +<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" /> @@ -24,43 +24,43 @@ <body id="rvalerr"><a name="rvalerr"><!-- --></a> -<h1 class="topictitle1" id="title">Common validation errors and solutions</h1> +<h1 class="id_title">Common validation errors and solutions</h1> -<div id="refbody"><div id="shortdesc">You may encounter these common error -messages when you validate your projects.</div> +<div class="id_refbody"><p class="id_shortdesc">This table lists the common error messages +you may encounter when you validate your projects.</p> -<anchor id="topictop"></anchor> +<div class="anchor_topictop" /> <div class="tablenoborder"><table summary="" cellspacing="0" cellpadding="4" frame="border" border="1" rules="all"> <thead align="left"> -<tr id="tableHeadRow"> -<th valign="top" width="20.27027027027027%" id="N1008D">Message prefix</th> +<tr class="id_tableHeadRow"> +<th valign="top" width="20.27027027027027%" id="N10078">Message prefix</th> -<th valign="top" width="24.324324324324326%" id="N10094">Message</th> +<th valign="top" width="24.324324324324326%" id="N1007F">Message</th> -<th valign="top" width="55.4054054054054%" id="N1009B">Explanation</th> +<th valign="top" width="55.4054054054054%" id="N10086">Explanation</th> </tr> </thead> <tbody> -<tr id="appclientValidator"> -<td colspan="3" valign="top" headers="N1008D N10094 N1009B "><span class="uicontrol">Application Client validator</span></td> +<tr class="id_appclientValidator"> +<td colspan="3" valign="top" headers="N10078 N1007F N10086 "><span class="uicontrol">Application Client validator</span></td> </tr> -<tr id="CHKJ1000"> -<td valign="top" width="20.27027027027027%" headers="N1008D ">CHKJ1000</td> +<tr class="id_CHKJ1000"> +<td valign="top" width="20.27027027027027%" headers="N10078 ">CHKJ1000</td> -<td valign="top" width="24.324324324324326%" headers="N10094 ">Validation failed because the application client file +<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="N1009B ">The application-client.xml file cannot be loaded. The +<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> @@ -85,17 +85,17 @@ rebuild the project. The project metadata will refresh.</li> </tr> -<tr id="EARValidator"> -<td colspan="3" valign="top" headers="N1008D N10094 N1009B "><span class="uicontrol">EAR validator</span></td> +<tr class="id_EARValidator"> +<td colspan="3" valign="top" headers="N10078 N1007F N10086 "><span class="uicontrol">EAR validator</span></td> </tr> -<tr id="CHKJ1001"> -<td valign="top" width="20.27027027027027%" headers="N1008D ">CHKJ1001</td> +<tr class="id_CHKJ1001"> +<td valign="top" width="20.27027027027027%" headers="N10078 ">CHKJ1001</td> -<td valign="top" width="24.324324324324326%" headers="N10094 ">The EAR project {0} is invalid.</td> +<td valign="top" width="24.324324324324326%" headers="N1007F ">The EAR project {0} is invalid.</td> -<td valign="top" width="55.4054054054054%" headers="N1009B ">The application.xml file cannot be loaded. The project +<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> @@ -119,17 +119,17 @@ rebuild the project. The project metadata will refresh.</li> </tr> -<tr id="EJBValidator"> -<td colspan="3" valign="top" headers="N1008D N10094 N1009B "><span class="uicontrol">EJB validator</span></td> +<tr class="id_EJBValidator"> +<td colspan="3" valign="top" headers="N10078 N1007F N10086 "><span class="uicontrol">EJB validator</span></td> </tr> -<tr id="CHKJ2019"> -<td valign="top" width="20.27027027027027%" headers="N1008D ">CHKJ2019</td> +<tr class="id_CHKJ2019"> +<td valign="top" width="20.27027027027027%" headers="N10078 ">CHKJ2019</td> -<td valign="top" width="24.324324324324326%" headers="N10094 ">The {0} key class must be serializable at runtime. </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="N1009B ">The EJB is compliant with the EJB specification. This +<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 @@ -139,57 +139,57 @@ make the object serializable at compile-time or ignore the warning. </td> </tr> -<tr id="CHKJ2412"> -<td valign="top" width="20.27027027027027%" headers="N1008D ">CHKJ2412</td> +<tr class="id_CHKJ2412"> +<td valign="top" width="20.27027027027027%" headers="N10078 ">CHKJ2412</td> -<td valign="top" width="24.324324324324326%" headers="N10094 ">The return type must be serializable at runtime. </td> +<td valign="top" width="24.324324324324326%" headers="N1007F ">The return type must be serializable at runtime. </td> </tr> -<tr id="CHKJ2413"> -<td valign="top" width="20.27027027027027%" headers="N1008D ">CHKJ2413</td> +<tr class="id_CHKJ2413"> +<td valign="top" width="20.27027027027027%" headers="N10078 ">CHKJ2413</td> -<td valign="top" width="24.324324324324326%" headers="N10094 ">Argument {1} of {0} must be serializable at runtime.</td> +<td valign="top" width="24.324324324324326%" headers="N1007F ">Argument {1} of {0} must be serializable at runtime.</td> </tr> -<tr id="CHKJ2102"> -<td valign="top" width="20.27027027027027%" headers="N1008D ">CHKJ2102</td> +<tr class="id_CHKJ2102"> +<td valign="top" width="20.27027027027027%" headers="N10078 ">CHKJ2102</td> -<td valign="top" width="24.324324324324326%" headers="N10094 ">Either a finder descriptor, or a matching custom finder method on the +<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="N1009B ">A finder descriptor must exist for every finder method. </td> +<td valign="top" width="55.4054054054054%" headers="N10086 ">A finder descriptor must exist for every finder method. </td> </tr> -<tr id="CHKJ2873"> -<td valign="top" width="20.27027027027027%" headers="N1008D ">CHKJ2873</td> +<tr class="id_CHKJ2873"> +<td valign="top" width="20.27027027027027%" headers="N10078 ">CHKJ2873</td> -<td valign="top" width="24.324324324324326%" headers="N10094 ">Migrate this bean's datasource binding to a CMP Connection Factory +<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="N1009B "> </td> +<td valign="top" width="55.4054054054054%" headers="N10086 "> </td> </tr> -<tr id="CHKJ2874"> -<td valign="top" width="20.27027027027027%" headers="N1008D ">CHKJ2874</td> +<tr class="id_CHKJ2874"> +<td valign="top" width="20.27027027027027%" headers="N10078 ">CHKJ2874</td> -<td valign="top" width="24.324324324324326%" headers="N10094 ">Migrate this EJB module's default datasource binding to a default CMP +<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="N1009B "> </td> +<td valign="top" width="55.4054054054054%" headers="N10086 "> </td> </tr> -<tr id="CHKJ2875E"> -<td valign="top" width="20.27027027027027%" headers="N1008D ">CHKJ2875E </td> +<tr class="id_CHKJ2875E"> +<td valign="top" width="20.27027027027027%" headers="N10078 ">CHKJ2875E </td> -<td valign="top" width="24.324324324324326%" headers="N10094 "><ejb-client-jar> {0} must exist in every EAR file +<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="N1009B ">If <samp class="codeph"><ejb-client-jar></samp> is specified +<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 @@ -199,13 +199,13 @@ EJB project as a module.</td> </tr> -<tr id="CHKJ2905"> -<td valign="top" width="20.27027027027027%" headers="N1008D ">CHKJ2905</td> +<tr class="id_CHKJ2905"> +<td valign="top" width="20.27027027027027%" headers="N10078 ">CHKJ2905</td> -<td valign="top" width="24.324324324324326%" headers="N10094 ">The EJB validator did not run because ejb-jar.xml could not be loaded. +<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="N1009B ">CHKJ2905 means that the project's metadata could not be initialized +<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> @@ -228,17 +228,17 @@ rebuild the project. The project metadata will refresh.</li> </tr> -<tr id="JSPValidator"> -<td colspan="3" valign="top" headers="N1008D N10094 N1009B "><span class="uicontrol">JSP validator</span></td> +<tr class="id_JSPValidator"> +<td colspan="3" valign="top" headers="N10078 N1007F N10086 "><span class="uicontrol">JSP validator</span></td> </tr> -<tr id="IWAW0482"> -<td valign="top" width="20.27027027027027%" headers="N1008D ">IWAW0482</td> +<tr class="id_IWAW0482"> +<td valign="top" width="20.27027027027027%" headers="N10078 ">IWAW0482</td> -<td valign="top" width="24.324324324324326%" headers="N10094 ">No valid JspTranslator</td> +<td valign="top" width="24.324324324324326%" headers="N1007F ">No valid JspTranslator</td> -<td valign="top" width="55.4054054054054%" headers="N1009B ">There is a path problem with the project; the JSP Validator +<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 @@ -253,17 +253,17 @@ Java > Classpath Variables</span>) are set correctly.</li> </tr> -<tr id="WARValidator"> -<td colspan="3" valign="top" headers="N1008D N10094 N1009B "><span class="uicontrol">WAR validator</span></td> +<tr class="id_WARValidator"> +<td colspan="3" valign="top" headers="N10078 N1007F N10086 "><span class="uicontrol">WAR validator</span></td> </tr> -<tr id="CHKJ3008"> -<td valign="top" width="20.27027027027027%" headers="N1008D ">CHKJ3008</td> +<tr class="id_CHKJ3008"> +<td valign="top" width="20.27027027027027%" headers="N10078 ">CHKJ3008</td> -<td valign="top" width="24.324324324324326%" headers="N10094 ">Missing or invalid WAR file.</td> +<td valign="top" width="24.324324324324326%" headers="N1007F ">Missing or invalid WAR file.</td> -<td valign="top" width="55.4054054054054%" headers="N1009B ">The web.xml file cannot be loaded. The project metadata +<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> @@ -286,18 +286,18 @@ rebuild the project. The project metadata will refresh.</li> </tr> -<tr id="XMLValidator"> -<td colspan="3" valign="top" headers="N1008D N10094 N1009B "><span class="uicontrol">XML validator</span></td> +<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="N1008D "> </td> +<td valign="top" width="20.27027027027027%" headers="N10078 "> </td> -<td valign="top" width="24.324324324324326%" headers="N10094 ">The content of element type "ejb-jar" is incomplete, it must match +<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="N1009B ">The EJB 1.1 and 2.0 specifications mandate that at least one enterprise +<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 @@ -310,7 +310,7 @@ the project.</td> </table> </div> -<anchor id="topicbottom"></anchor> +<div class="anchor_topicbottom" /> </div> @@ -323,4 +323,4 @@ the project.</td> </div> </body> -</html> +</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 index d0f773aa1..51bdd7f1b 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/rvalidators.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/rvalidators.dita @@ -1,4 +1,5 @@ <?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">
@@ -68,8 +69,8 @@ of the module projects with respect to the enterprise application project.</p></ 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. <p>Specifically, the EJB Validator
-validates the following resources: </p> <ul>
+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>
@@ -141,10 +142,6 @@ 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>
-<row outputclass="anchor_bottomrow">
-<entry colname="col1"></entry>
-<entry colname="col2"></entry>
-</row>
</tbody>
</tgroup>
</table>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/rvalidators.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/rvalidators.html index bc7f6df4c..f2de7834d 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/rvalidators.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/rvalidators.html @@ -2,8 +2,8 @@ <html lang="en-us" xml:lang="en-us"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> +<meta 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))' /> @@ -24,22 +24,21 @@ <body id="rvalidators"><a name="rvalidators"><!-- --></a> -<h1 class="topictitle1" id="title">J2EE Validators</h1> +<h1 class="id_title">J2EE Validators</h1> -<div id="refbody"><div id="shortdesc">This table lists the validators that +<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.</div> +of each validator.</p> -<anchor id="topictop"></anchor> +<div class="anchor_topictop" /> <div class="tablenoborder"><table summary="" cellspacing="0" cellpadding="4" frame="border" border="1" rules="all"> <thead align="left"> -<tr> -<anchor id="toprow"></anchor> +<tr class="id_toprow"> <th valign="top" width="50%" id="N10073">Validator name</th> <th valign="top" width="50%" id="N1007A">Description</th> @@ -49,7 +48,7 @@ of each validator.</div> </thead> <tbody> -<tr id="appclientValidator"> +<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 @@ -65,7 +64,7 @@ the following Application Client project resources: <ul> </tr> -<tr id="connectorValidator"> +<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 @@ -73,7 +72,7 @@ levels in connector projects.</td> </tr> -<tr id="DTDValidator"> +<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 @@ -84,7 +83,7 @@ to entities and elements that do not exist.</td> </tr> -<tr id="EARValidator"> +<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: @@ -112,15 +111,14 @@ of the module projects with respect to the enterprise application project.</p> </tr> -<tr id="EJBValidator"> +<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. <p>Specifically, the EJB Validator -validates the following resources: </p> - <ul> +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> @@ -132,14 +130,14 @@ enterprise bean class, and, if the bean is an entity bean, the key class)</li> </tr> -<tr id="ELValidator"> +<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 id="HTMLValidator"> +<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 @@ -154,7 +152,7 @@ basic syntax and HTML DTD compliance in the following Web project resources: </tr> -<tr id="JSPValidator"> +<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 @@ -163,7 +161,7 @@ and then checking the Java code for compile errors.</td> </tr> -<tr id="WARValidator"> +<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 @@ -183,7 +181,7 @@ web project resources: <ul> </tr> -<tr id="WSDLValidator"> +<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> @@ -201,7 +199,7 @@ a WSDL file against WS-I Profiles. </td> </tr> -<tr id="WSIValidator"> +<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 @@ -211,7 +209,7 @@ Monitor. The validator checks a message log that is saved as a project resource </tr> -<tr id="XMLSchemaValidator"> +<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 @@ -220,7 +218,7 @@ are validated according to the XML Schema specification <a href="http://www.w3.o </tr> -<tr id="XMLValidator"> +<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 @@ -230,20 +228,12 @@ with.</td> </tr> -<tr> -<anchor id="bottomrow"></anchor> -<td valign="top" width="50%" headers="N10073 "> </td> - -<td valign="top" width="50%" headers="N1007A "> </td> - -</tr> - </tbody> </table> </div> -<anchor id="topicbottom"></anchor> +<div class="anchor_topicbottom" /> </div> @@ -251,9 +241,9 @@ with.</td> <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="You may encounter these common error messages when you validate your projects.">Common validation errors and solutions</a></div> +<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> +</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 index 6d1154324..ba9f271e2 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/taddingfacet.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/taddingfacet.dita @@ -1,4 +1,5 @@ <?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">
@@ -7,23 +8,23 @@ to an existing project in your workspace.</shortdesc>
<prolog><metadata>
<keywords><indexterm>projects<indexterm>facets<indexterm>adding</indexterm></indexterm></indexterm>
-<indexterm>J2EE<indexterm>adding project facets</indexterm></indexterm>
-</keywords>
+<indexterm>J2EE<indexterm>adding project facets</indexterm></indexterm></keywords>
</metadata></prolog>
<taskbody outputclass="id_taskbody">
-<context outputclass="id_context"><p outputclass="anchor_topictop"></p>
-<p>New projects generally have facets added to them when they are created. To add another
-facet to a project that already exists, follow these steps:</p></context>
+<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, right-click the project and then
-click <uicontrol>Properties</uicontrol>.</cmd></step>
-<step><cmd>In the Properties window, click <uicontrol>Project Facets</uicontrol>.</cmd>
-<stepresult>The Project Facets page lists the facets in the project. </stepresult>
-</step>
-<step><cmd>Click <uicontrol>Add/Remove Project Facets</uicontrol>.</cmd></step>
-<step><cmd>In the Add/Remove Project Facets window, select the check boxes
-next to the facets you want this project to have.</cmd><info><p>Only the facets
-that are valid for the project are listed:<ul>
+<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>
@@ -38,15 +39,15 @@ can also choose a preset combination of facets from the <uicontrol>Presets</uico <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><cmd>To remove a facet, clear its check box.</cmd><info>Not all facets
-can be removed.</info></step>
-<step><cmd>If you want to limit the project so it will be compatible with
-one or more runtimes, click the <uicontrol>Show Runtimes</uicontrol> button
-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 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>.</cmd></step>
-<step><cmd>Click <uicontrol>OK</uicontrol>.</cmd></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>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/taddingfacet.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/taddingfacet.html index 20a865641..63bd2c527 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/taddingfacet.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/taddingfacet.html @@ -2,8 +2,8 @@ <html lang="en-us" xml:lang="en-us"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> +<meta 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))' /> @@ -11,8 +11,8 @@ <meta name="DC.Title" content="Adding a facet to a J2EE 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, removing" name="DC.subject" /> -<meta content="projects, facets, adding, removing" name="keywords" /> +<meta content="projects, facets, adding, J2EE, adding project facets" name="DC.subject" /> +<meta content="projects, facets, adding, J2EE, 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" /> @@ -25,31 +25,35 @@ <body id="taddingfacet"><a name="taddingfacet"><!-- --></a> -<h1 class="topictitle1" id="title">Adding a facet to a J2EE project</h1> +<h1 class="id_title">Adding a facet to a J2EE project</h1> -<div id="taskbody"><div id="shortdesc">This topic explains how to add a facet -to an existing project in your workspace.</div> +<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="section" id="context"><anchor id="topictop"></anchor><p>New projects -generally have facets added to them when they are created. To add another -facet to a project that already exists, follow these steps:</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 id="steps"> -<li class="stepexpand"><span>In the Project Explorer view, right-click the project and then -click <span class="uicontrol">Properties</span>.</span></li> +<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>In the Properties window, click <span class="uicontrol">Project Facets</span>.</span> - The Project Facets page lists the facets in the project. -</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Add/Remove Project Facets</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>In the Add/Remove Project Facets window, select the check boxes -next to the facets you want this project to have.</span> <div class="p">Only the facets -that are valid for the project are listed:<ul> +<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> @@ -71,28 +75,27 @@ can also choose a preset combination of facets from the <span class="uicontrol"> number and selecting the version number you want from the drop-down list.</span> </li> -<li class="stepexpand"><span>To remove a facet, clear its check box.</span> Not all facets -can be removed.</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"><span>If you want to limit the project so it will be compatible with -one or more runtimes, click the <span class="uicontrol">Show Runtimes</span> button -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 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>.</span></li> - -<li class="stepexpand"><span>Click <span class="uicontrol">OK</span>.</span></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="section" id="postreq"><anchor id="topicbottom"></anchor> +<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 J2EE projects.">Project facets</a></div> +<div><a href="../topics/cfacets.html" title="Facets define characteristics and requirements for J2EE 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 J2EE project by changing the value of the Java facet.">Changing the Java compiler version for a J2EE project</a></div> @@ -101,4 +104,4 @@ and select the runtimes that you want the project to be compatible with.</span> </div> </body> -</html> +</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 index 505f96874..252889e39 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tchangefacet.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tchangefacet.dita @@ -1,4 +1,5 @@ <?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">
@@ -12,22 +13,24 @@ in a J2EE project by editing the facets for the project.</shortdesc> </keywords>
</metadata></prolog>
<taskbody outputclass="id_taskbody">
-<context outputclass="id_context"><p outputclass="anchor_topictop"></p>
-<p>Changing the Java compiler version of a J2EE project involves changing the version
-of the <uicontrol>Java</uicontrol> facet. See <xref href="tchangejavalevel.dita"></xref>.</p></context>
+<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 J2EE 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, right-click the project and then
-click <uicontrol>Properties</uicontrol>.</cmd></step>
-<step><cmd>In the Properties window, click <uicontrol>Project Facets</uicontrol>.</cmd>
-<stepresult>The Project Facets page lists the facets in the project. </stepresult>
-</step>
-<step><cmd>Click <uicontrol>Add/Remove Project Facets</uicontrol>.</cmd></step>
-<step><cmd>In the Add/Remove Project Facets window, click the facet you want
-to change to select it.</cmd></step>
+<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>.</cmd></step>
-<step><cmd>Click <uicontrol>OK</uicontrol>.</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>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tchangefacet.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tchangefacet.html index cb14233c7..031360b69 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tchangefacet.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tchangefacet.html @@ -2,8 +2,8 @@ <html lang="en-us" xml:lang="en-us"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> +<meta 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))' /> @@ -11,8 +11,8 @@ <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 J2EE project by editing the facets for the project." /> <meta name="description" content="You can change the version of a facet in a J2EE project by editing the facets for the project." /> -<meta content="projects, facets, changing, J2EE development, project facets, version, J2EE modules" name="DC.subject" /> -<meta content="projects, facets, changing, J2EE development, project facets, version, J2EE modules" name="keywords" /> +<meta content="facets, changing versions, J2EE, changing facet versions, projects" name="DC.subject" /> +<meta content="facets, changing versions, J2EE, 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" /> @@ -25,47 +25,48 @@ <body id="tchangefacet"><a name="tchangefacet"><!-- --></a> -<h1 class="topictitle1" id="title">Changing the version of a facet</h1> +<h1 class="id_title">Changing the version of a facet</h1> -<div id="taskbody"><div id="shortdesc">You can change the version of a facet -in a J2EE project by editing the facets for the project.</div> +<div class="id_taskbody"><p class="id_shortdesc">You can change the version of a facet +in a J2EE project by editing the facets for the project.</p> -<div class="section" id="context"><anchor id="topictop"></anchor><p>Changing -the Java compiler version of a J2EE project involves changing the version -of the <span class="uicontrol">Java</span> facet. See <a href="tchangejavalevel.html" title="You can change the version of Java used in a J2EE project by changing the value of the Java facet.">Changing the Java compiler version for a J2EE project</a>.</p> +<div class="id_context"><p class="anchor_topictop" /> + <p>Changing +the Java™ compiler +version of a J2EE 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 J2EE project by changing the value of the Java facet.">Changing the Java compiler version for a J2EE project</a>.</p> +<p>To +change the version of a facet in your project, complete the following steps:</p> </div> -<ol id="steps"> -<li class="stepexpand"><span>In the Project Explorer view, right-click the project and then -click <span class="uicontrol">Properties</span>.</span></li> +<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>In the Properties window, click <span class="uicontrol">Project Facets</span>.</span> - The Project Facets page lists the facets in the project. -</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">Add/Remove Project Facets</span>.</span></li> - -<li class="stepexpand"><span>In the Add/Remove Project Facets window, click the facet you want -to change to select it.</span></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>.</span></li> - -<li class="stepexpand"><span>Click <span class="uicontrol">OK</span>.</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="section" id="postreq"><anchor id="topicbottom"></anchor> +<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 J2EE projects.">Project facets</a></div> +<div><a href="../topics/cfacets.html" title="Facets define characteristics and requirements for J2EE 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 J2EE project</a></div> @@ -74,4 +75,4 @@ the facet's name.</span></li> </div> </body> -</html> +</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 index 4889d8909..443530b20 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tchangejavalevel.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tchangejavalevel.dita @@ -1,10 +1,12 @@ <?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 Java compiler version for a J2EE
-project</title>
-<shortdesc outputclass="id_shortdesc">You can change the version of Java used
+<title outputclass="id_title">Changing the <tm tmclass="special" tmowner="Sun Microsystems, Inc."
+tmtype="tm" trademark="Java">Java</tm> compiler version for a J2EE 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 J2EE project by changing the value of the <uicontrol>Java</uicontrol> facet.</shortdesc>
<prolog><metadata>
<keywords><indexterm>Java<indexterm>J2EE project compiler level</indexterm></indexterm>
@@ -12,23 +14,28 @@ in a J2EE project by changing the value of the <uicontrol>Java</uicontrol> facet </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 Java compiler level of a non-J2EE
-project, such as a Java project, see <xref format="html" href="../../org.eclipse.jdt.doc.user/reference/ref-preferences-compiler.htm"
-scope="peer">Java Compiler</xref>.</p></context>
+<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-J2EE 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-preferences-compiler.htm"
+scope="peer"><tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
+trademark="Java">Java</tm> 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, right-click the project and then
-click <uicontrol>Properties</uicontrol>.</cmd></step>
-<step><cmd>In the Properties window, click <uicontrol>Project Facets</uicontrol>.</cmd>
-<stepresult>The Project Facets page lists the facets in the project. </stepresult>
-</step>
-<step><cmd>Click <uicontrol>Add/Remove Project Facets</uicontrol>.</cmd></step>
-<step><cmd>In the Add/Remove Project Facets window, click the <uicontrol>Java</uicontrol> facet
-to select it.</cmd></step>
-<step><cmd>Select the level of Java compiler to use from the drop-down box
-next to the <uicontrol>Java</uicontrol> facet.</cmd></step>
-<step><cmd>Click <uicontrol>Finish</uicontrol>.</cmd></step>
-<step><cmd>Click <uicontrol>OK</uicontrol>.</cmd></step>
+<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>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tchangejavalevel.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tchangejavalevel.html index feadbdabe..ab843c328 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tchangejavalevel.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tchangejavalevel.html @@ -2,8 +2,8 @@ <html lang="en-us" xml:lang="en-us"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> +<meta 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))' /> @@ -11,8 +11,8 @@ <meta name="DC.Title" content="Changing the Java compiler version for a J2EE project" /> <meta name="abstract" content="You can change the version of Java used in a J2EE project by changing the value of the Java facet." /> <meta name="description" content="You can change the version of Java used in a J2EE project by changing the value of the Java facet." /> -<meta content="projects, facets, Java compiler level, J2EE projects" name="DC.subject" /> -<meta content="projects, facets, Java compiler level, J2EE projects" name="keywords" /> +<meta content="Java, J2EE project compiler level, projects, Java compiler level" name="DC.subject" /> +<meta content="Java, J2EE 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" /> @@ -20,54 +20,51 @@ <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 J2EE -project</title> +<title>Changing the Java compiler version for a J2EE project</title> </head> <body id="tchangejavalevel"><a name="tchangejavalevel"><!-- --></a> -<h1 class="topictitle1" id="title">Changing the Java compiler version for a J2EE -project</h1> +<h1 class="id_title">Changing the Java compiler version for a J2EE project</h1> -<div id="taskbody"><div id="shortdesc">You can change the version of Java used -in a J2EE project by changing the value of the <span class="uicontrol">Java</span> facet.</div> +<div class="id_taskbody"><p class="id_shortdesc">You can change the version of Java™ used +in a J2EE project by changing the value of the <span class="uicontrol">Java</span> facet.</p> -<div class="section" id="context"><anchor id="topictop"></anchor><p>The <span class="uicontrol">Java</span> facet -applies only to J2EE projects. To set the Java compiler level of a non-J2EE -project, such as a Java project, see <a href="../../org.eclipse.jdt.doc.user/reference/ref-preferences-compiler.htm">Java Compiler</a>.</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-J2EE project, +such as a Java project, see <a href="../../org.eclipse.jdt.doc.user/reference/ref-preferences-compiler.htm">Java Compiler</a>.</p> +<p>To change the Java compiler +version, complete the following steps:</p> </div> -<ol id="steps"> -<li class="stepexpand"><span>In the Project Explorer view, right-click the project and then -click <span class="uicontrol">Properties</span>.</span></li> +<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>In the Properties window, click <span class="uicontrol">Project Facets</span>.</span> - The Project Facets page lists the facets in the project. -</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">Add/Remove Project Facets</span>.</span></li> +<li class="stepexpand"><span>Click <span class="uicontrol">Modify Project</span>.</span></li> -<li class="stepexpand"><span>In the Add/Remove Project Facets window, click the <span class="uicontrol">Java</span> facet -to select it.</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>Select the level of Java compiler to use from the drop-down box -next to the <span class="uicontrol">Java</span> facet.</span></li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Finish</span>.</span></li> - -<li class="stepexpand"><span>Click <span class="uicontrol">OK</span>.</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="section" id="postreq"><anchor id="topicbottom"></anchor> +<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 J2EE projects.">Project facets</a></div> +<div><a href="../topics/cfacets.html" title="Facets define characteristics and requirements for J2EE 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 J2EE project</a></div> @@ -76,4 +73,4 @@ next to the <span class="uicontrol">Java</span> facet.</span></li> </div> </body> -</html> +</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 index 500d29147..8a01f5399 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjappproj.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjappproj.dita @@ -1,4 +1,5 @@ <?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">
@@ -11,25 +12,28 @@ project.</shortdesc> </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.
-Application client projects contain 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:</p></context>
+<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 J2EE perspective, click <menucascade><uicontrol>File</uicontrol>
-<uicontrol>New</uicontrol><uicontrol>Project</uicontrol><uicontrol>J2EE</uicontrol>
-<uicontrol>Application Client Project</uicontrol></menucascade>.</cmd></step>
+<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>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><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 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
@@ -37,7 +41,7 @@ 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>If you want to add the new project to an enterprise application
+<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
@@ -45,25 +49,23 @@ 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><cmd>If you want to use a predefined configuration for your project,
-select a configuration in the <uicontrol>Common Configurations</uicontrol> list.</cmd>
-</step>
-<step><cmd>Click <uicontrol>Next</uicontrol>.</cmd></step>
-<step><cmd>Select the check boxes next to the facets you want this project
-to have and select a version number for each facet. </cmd><info>You can also
-choose a preset combination of facets from the <uicontrol>Presets</uicontrol> list,
-and you can find out more about the requirements for each facet by right-clicking
-the facet name and then clicking <uicontrol>Show Constraints</uicontrol>.</info>
-</step>
-<step><cmd>If you want to limit your project so it will be compatible with
-one or more runtimes, click the <uicontrol>Show Runtimes</uicontrol> button
-and select the runtimes that you want the project to be compatible with.</cmd>
-</step>
-<step><cmd>Click <uicontrol>Next</uicontrol>.</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>If you want to create a default class for the module, select the <uicontrol>Create
-a default Main class</uicontrol> check box.</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>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjappproj.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjappproj.html index ba9192210..a163f0b1f 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjappproj.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjappproj.html @@ -2,8 +2,8 @@ <html lang="en-us" xml:lang="en-us"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> +<meta 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))' /> @@ -28,39 +28,43 @@ <body id="tjappproj"><a name="tjappproj"><!-- --></a> -<h1 class="topictitle1" id="title">Creating an application client project</h1> +<h1 class="id_title">Creating an application client project</h1> -<div id="taskbody"><div id="shortdesc">You can use a wizard to create a new +<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.</div> - -<div class="section" id="context"> <anchor id="topictop"></anchor><p>Application -client projects contain the resources needed for application client modules. -Application client projects contain programs that run on networked client -systems. An application client project is deployed as a JAR file.</p> -<p>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:</p> +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 id="steps"> -<li class="stepexpand"><span>In the J2EE perspective, click <span class="menucascade"><span class="uicontrol">File</span> - > <span class="uicontrol">New</span> > <span class="uicontrol">Project</span> > <span class="uicontrol">J2EE</span> - > <span class="uicontrol">Application Client Project</span></span>.</span></li> +<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">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"><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 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 @@ -70,7 +74,7 @@ for the enterprise application, you must use the New Enterprise Application Project wizard.</div> </li> -<li class="stepexpand"><span>If you want to add the new project to an enterprise application +<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 @@ -80,46 +84,43 @@ 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"><span>If you want to use a predefined configuration for your project, -select a configuration in the <span class="uicontrol">Common Configurations</span> list.</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 class="stepexpand"><span>Click <span class="uicontrol">Next</span>.</span></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> -<li class="stepexpand"><span>Select the check boxes next to the facets you want this project -to have and select a version number for each facet. </span> You can also -choose a preset combination of facets from the <span class="uicontrol">Presets</span> list, -and you can find out more about the requirements for each facet by right-clicking -the facet name and then clicking <span class="uicontrol">Show Constraints</span>. -</li> - -<li class="stepexpand"><span>If you want to limit your project so it will be compatible with -one or more runtimes, click the <span class="uicontrol">Show Runtimes</span> button -and select the runtimes that you want the project to be compatible with.</span> -</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Next</span>.</span></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>If you want 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"><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="section" id="postreq"><anchor id="topicbottom"></anchor> +<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 services.">J2EE architecture</a></div> -<div><a href="../topics/cjappcliproj.html" title="">Application client projects</a></div> +<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 J2EE projects.">Project facets</a></div> +<div><a href="../topics/cfacets.html" title="Facets define characteristics and requirements for J2EE 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> @@ -128,4 +129,4 @@ a default Main class</span> check box.</span></li> </div> </body> -</html> +</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 index 6b22b0a09..77d1b0b26 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjcircleb.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjcircleb.dita @@ -1,4 +1,5 @@ <?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">
@@ -13,27 +14,27 @@ after an EAR is imported.</shortdesc> </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
+<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></context>
+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, then 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>
+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>Use the JAR dependency editor or properties page, for each module
-of the JAR in the application, to set dependencies only to the JAR files that
-are truly required.</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>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjcircleb.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjcircleb.html index 2a1803429..112acfa2b 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjcircleb.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjcircleb.html @@ -2,8 +2,8 @@ <html lang="en-us" xml:lang="en-us"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> +<meta 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))' /> @@ -11,8 +11,8 @@ <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="cyclical dependencies, correcting, projects, correcting cyclical dependencies, J2EE modules" name="DC.subject" /> -<meta content="cyclical dependencies, correcting, projects, correcting cyclical dependencies, J2EE modules" name="keywords" /> +<meta content="dependencies, correcting cyclical, EAR, correcting cyclical dependencies, projects" name="DC.subject" /> +<meta content="dependencies, correcting cyclical, EAR, 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" /> @@ -25,47 +25,51 @@ is imported</title> <body id="tjcircleb"><a name="tjcircleb"><!-- --></a> -<h1 class="topictitle1" id="title">Correcting cyclical dependencies after an EAR +<h1 class="id_title">Correcting cyclical dependencies after an EAR is imported</h1> -<div id="taskbody"><div id="shortdesc">You can resolve cyclical dependencies -after an EAR is imported.</div> +<div class="id_taskbody"><p class="id_shortdesc">You can resolve cyclical dependencies +after an EAR is imported.</p> -<div class="section" id="context"><anchor id="topictop"></anchor><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> +<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 id="steps"> +<ol class="id_steps"> <li><span>Identify all the classes within the JAR files that have cyclical -dependencies, then move those classes into a common Java project -or JAR file.</span></li> +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>Use the JAR dependency editor or properties page, for each module -of the JAR in the application, to set dependencies only to the JAR files that -are truly required.</span></li> +<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="section" id="postreq"><anchor id="topicbottom"></anchor> +<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="">Cyclical dependencies between J2EE modules</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 J2EE modules</a></div> </div> <div class="reltasks"><strong>Related tasks</strong><br /> <div><a href="../topics/tjimpear.html" title="Enterprise application projects are deployed into EAR files. You can import an enterprise application project by importing it from a deployed EAR file.">Importing an enterprise application EAR file</a></div> @@ -73,4 +77,4 @@ are truly required.</span></li> </div> </body> -</html> +</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 index af2ec10af..c89f63317 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjear.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjear.dita @@ -1,17 +1,20 @@ <?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"></shortdesc>
+<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
+<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
@@ -24,54 +27,54 @@ 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:</p></context>
+create a J2EE enterprise application project, complete the following steps:</p></context>
<steps outputclass="id_steps">
-<step><cmd>In the J2EE perspective, click <menucascade><uicontrol>File</uicontrol>
-<uicontrol>New</uicontrol><uicontrol>Project</uicontrol><uicontrol>J2EE</uicontrol>
-<uicontrol>Enterprise Application Project</uicontrol></menucascade>.</cmd>
+<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><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 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><cmd>If you want to use a predefined configuration for your project,
-select a configuration in the <uicontrol>Common Configurations</uicontrol> list.</cmd>
-</step>
-<step><cmd>Click <uicontrol>Next</uicontrol>.</cmd></step>
-<step><cmd>Select the check boxes next to the facets you want this project
-to have and select a version number for each facet. </cmd><info>You can also
-choose a preset combination of facets from the <uicontrol>Presets</uicontrol> list,
-and you can also find out more about the requirements for each facet by right-clicking
-the facet name and then clicking <uicontrol>Show Constraints</uicontrol>.</info>
-</step>
-<step><cmd>If you want to limit your project so it will be compatible with
-one or more runtimes, click the <uicontrol>Show Runtimes</uicontrol> button
-and select the runtimes that you want the project to be compatible with.</cmd>
-</step>
-<step><cmd>Click <uicontrol>Next</uicontrol>.</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>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><cmd>You can also create new modules to add to the project:</cmd>
-<substeps>
-<substep><cmd>Click the <uicontrol>New Module</uicontrol> button.</cmd></substep>
-<substep><cmd>If you want to create one module, clear the <uicontrol>Create
+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.</cmd></substep>
-<substep><cmd>If you want to create more than one module, select the <uicontrol>Create
+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>. </cmd>
+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></substep>
-</substeps>
-</step>
+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>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjear.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjear.html index a5e61b9f8..b16bd9e57 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjear.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjear.html @@ -2,17 +2,17 @@ <html lang="en-us" xml:lang="en-us"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> +<meta 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="" /> -<meta name="description" content="" /> -<meta content="enterprise application projects, creating" name="DC.subject" /> -<meta content="enterprise application projects, creating" name="keywords" /> +<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" /> @@ -28,13 +28,16 @@ <body id="tjear"><a name="tjear"><!-- --></a> -<h1 class="topictitle1" id="title">Creating an enterprise application project</h1> +<h1 class="id_title">Creating an enterprise application project</h1> -<div id="taskbody"><div id="shortdesc"></div> +<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="section" id="context"><anchor id="topictop"></anchor><p>Enterprise +<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 @@ -53,84 +56,90 @@ to enable other facets for the project.</p> you create an enterprise application project, it is recommended that you do not give it a name that contains double-byte character set (DBCS) characters.</p> <p>To -create a J2EE enterprise application project:</p> +create a J2EE enterprise application project, complete the following steps:</p> </div> -<ol id="steps"> -<li class="stepexpand"><span>In the J2EE perspective, click <span class="menucascade"><span class="uicontrol">File</span> - > <span class="uicontrol">New</span> > <span class="uicontrol">Project</span> > <span class="uicontrol">J2EE</span> - > <span class="uicontrol">Enterprise Application Project</span></span>.</span> +<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"><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 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"><span>If you want to use a predefined configuration for your project, -select a configuration in the <span class="uicontrol">Common Configurations</span> list.</span> -</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Next</span>.</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 class="stepexpand"><span>Select the check boxes next to the facets you want this project -to have and select a version number for each facet. </span> You can also -choose a preset combination of facets from the <span class="uicontrol">Presets</span> list, -and you can also find out more about the requirements for each facet by right-clicking -the facet name and then clicking <span class="uicontrol">Show Constraints</span>. -</li> - -<li class="stepexpand"><span>If you want to limit your project so it will be compatible with -one or more runtimes, click the <span class="uicontrol">Show Runtimes</span> button -and select the runtimes that you want the project to be compatible with.</span> -</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> -<li class="stepexpand"><span>Click <span class="uicontrol">Next</span>.</span></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> +project.</span></li> -<li class="stepexpand"><span>You can also create new modules to add to the project:</span> -<ol type="a"> -<li class="substepexpand"><span>Click the <span class="uicontrol">New Module</span> button.</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> -<li class="substepexpand"><span>If you want to create one module, clear the <span class="uicontrol">Create +<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.</span></li> +for that type of project.</td> +</tr> -<li class="substepexpand"><span>If you want to create more than one module, select the <span class="uicontrol">Create +<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>. </span> +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> -</ol> - -</li> - <li class="stepexpand"><span>Click <span class="uicontrol">Finish</span>.</span></li> </ol> -<div class="section" id="postreq"><anchor id="topicbottom"></anchor> +<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 services.">J2EE architecture</a></div> +<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 J2EE projects.">Project facets</a></div> +<div><a href="../topics/cfacets.html" title="Facets define characteristics and requirements for J2EE 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> diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexpapp.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexpapp.dita index b37a9fbf3..d99519b66 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexpapp.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexpapp.dita @@ -1,4 +1,5 @@ <?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">
@@ -10,16 +11,16 @@ project as a JAR file.</shortdesc> </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:</p></context>
+<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 J2EE perspective, click <menucascade><uicontrol>File</uicontrol>
-<uicontrol>Export</uicontrol></menucascade>.</cmd><stepresult>The Export window
-opens.</stepresult></step>
+<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>.</cmd>
-</step>
-<step><cmd>Click <uicontrol>Next</uicontrol>.</cmd></step>
+<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
@@ -28,8 +29,8 @@ path and JAR file name where you want to export the application client project.< <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 <uicontrol>Overwrite
-existing file</uicontrol>.</cmd></step>
+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>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexpapp.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexpapp.html index 0c8d1d9f8..acf2bf7c4 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexpapp.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexpapp.html @@ -2,8 +2,8 @@ <html lang="en-us" xml:lang="en-us"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> +<meta 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))' /> @@ -26,54 +26,53 @@ <body id="tjexpapp"><a name="tjexpapp"><!-- --></a> -<h1 class="topictitle1" id="title">Exporting an application client project</h1> +<h1 class="id_title">Exporting an application client project</h1> -<div id="taskbody"><div id="shortdesc">You can export an application client -project as a JAR file.</div> +<div class="id_taskbody"><p class="id_shortdesc">You can export an application client +project as a JAR file.</p> -<div class="section" id="context"><anchor id="topictop"></anchor><p>To export -an application client project from the workbench:</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 id="steps"> -<li class="stepexpand"><span>In the J2EE perspective, click <span class="menucascade"><span class="uicontrol">File</span> - > <span class="uicontrol">Export</span></span>.</span> The Export window -opens.</li> +<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 class="stepexpand"><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>.</span> -</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Next</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 class="stepexpand"><span>In the <span class="uicontrol">Application Client project</span> list, +<li><span>In the <span class="uicontrol">Application Client project</span> list, select the application client project you want to export.</span></li> -<li class="stepexpand"><span>In the <span class="uicontrol">Destination</span> field, enter the full +<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 class="stepexpand"><strong>Optional: </strong><span>To export source files, select the <span class="uicontrol">Export +<li><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 JAR file -and you do not want to be warned about overwriting it, select <span class="uicontrol">Overwrite -existing file</span>.</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 class="stepexpand"><span>Click <span class="uicontrol">Finish</span>.</span></li> +<li><span>Click <span class="uicontrol">Finish</span>.</span></li> </ol> -<div class="section" id="postreq"><anchor id="topicbottom"></anchor> +<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 services.">J2EE architecture</a></div> -<div><a href="../topics/cjappcliproj.html" title="">Application client projects</a></div> +<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> @@ -82,4 +81,4 @@ existing file</span>.</span></li> </div> </body> -</html> +</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 index 1b5b3c546..c51e5b219 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexpear.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexpear.dita @@ -1,4 +1,5 @@ <?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">
@@ -13,18 +14,18 @@ application project into an EAR file for deployment.</shortdesc> </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:</p></context>
+<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 J2EE perspective, click <menucascade><uicontrol>File</uicontrol>
-<uicontrol>Export</uicontrol></menucascade>.</cmd><stepresult>The Export window
-opens.</stepresult></step>
+<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>.</cmd>
-</step>
-<step><cmd>Click <uicontrol>Next</uicontrol>.</cmd></step>
-<step><cmd>In the <uicontrol>EAR application</uicontrol> list, select the
-enterprise application project you want to export.</cmd></step>
+<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>
@@ -32,8 +33,8 @@ project that is selected in the <uicontrol>EAR application</uicontrol> field.</c <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 <uicontrol>Overwrite
-existing file</uicontrol>.</cmd></step>
+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
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexpear.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexpear.html index 84b71c046..bee3bf5ae 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexpear.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexpear.html @@ -2,8 +2,8 @@ <html lang="en-us" xml:lang="en-us"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> +<meta 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))' /> @@ -11,8 +11,8 @@ <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="enterprise application projects, exporting, EAR files" name="DC.subject" /> -<meta content="enterprise application projects, exporting, EAR files" name="keywords" /> +<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" /> @@ -27,67 +27,66 @@ EAR file</title> <body id="tjexpear"><a name="tjexpear"><!-- --></a> -<h1 class="topictitle1" id="title">Exporting an enterprise application into an +<h1 class="id_title">Exporting an enterprise application into an EAR file</h1> -<div id="taskbody"><div id="shortdesc">Enterprise applications are deployed +<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.</div> +application project into an EAR file for deployment.</p> -<div class="section" id="context"> <anchor id="topictop"></anchor><p>To export -an enterprise application project into an EAR file:</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 id="steps"> -<li class="stepexpand"><span>In the J2EE perspective, click <span class="menucascade"><span class="uicontrol">File</span> - > <span class="uicontrol">Export</span></span>.</span> The Export window -opens.</li> +<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 class="stepexpand"><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>.</span> -</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Next</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 class="stepexpand"><span>In the <span class="uicontrol">EAR application</span> list, select the -enterprise application project you want to export.</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 class="stepexpand"><span>In the <span class="uicontrol">Destination</span> field, enter the full +<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 class="stepexpand"><strong>Optional: </strong><span>To export source files, select the <span class="uicontrol">Export +<li><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 EAR file -and you do not want to be warned about overwriting it, select <span class="uicontrol">Overwrite -existing file</span>.</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 class="stepexpand"><span>Click <span class="uicontrol">Finish</span>.</span></li> +<li><span>Click <span class="uicontrol">Finish</span>.</span></li> </ol> -<div id="result">The wizard exports the contents of the EAR +<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="section" id="postreq"><anchor id="topicbottom"></anchor> +<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 services.">J2EE architecture</a></div> +<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="">Creating an enterprise application project</a></div> +<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> diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexprar.dita b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexprar.dita index 35f54bb33..aa2405b48 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexprar.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexprar.dita @@ -1,4 +1,5 @@ <?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">
@@ -10,17 +11,17 @@ a RAR file in preparation for deploying it to a server.</shortdesc> <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:</p></context>
+<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 J2EE perspective, click <menucascade><uicontrol>File</uicontrol>
-<uicontrol>Export</uicontrol></menucascade>.</cmd><stepresult>The Export window
-opens.</stepresult></step>
+<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>.</cmd>
-</step>
-<step><cmd>Click <uicontrol>Next</uicontrol>.</cmd></step>
-<step><cmd>In the <uicontrol>Connector module</uicontrol> list, select the
+<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>
@@ -28,12 +29,12 @@ path and RAR file name where you want to export the connector project.</cmd> <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 <uicontrol>Overwrite
-existing file</uicontrol></cmd></step>
-<step><cmd>Click <uicontrol>Finish</uicontrol>.</cmd></step>
+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>
-<result outputclass="id_result"> The wizard exports the contents of the RAR
-project to the specified RAR file.</result>
<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 index 52e798e90..0a50592b4 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexprar.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjexprar.html @@ -1,49 +1,79 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html lang="en-us" xml:lang="en-us"> <head> -<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" /> - +<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> +<meta name="copyright" content="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="topictitle1">Exporting connector projects to RAR files</h1> -<div><div>You can export a connector project to a RAR file in preparation -for deploying it to a server.</div><div class="section"> <p>To export the contents of a connector project to a RAR file:</p> + + +<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><li class="stepexpand"><span>In the J2EE perspective, click <span class="menucascade"><span class="uicontrol">File</span> > <span class="uicontrol">Export</span></span>.</span> The Export window -opens.</li> -<li class="stepexpand"><span>Under <span class="uicontrol">Select an export destination</span>, click <span class="menucascade"><span class="uicontrol">J2EE Enterprise Applications</span> > <span class="uicontrol">RAR file</span></span>.</span></li> -<li class="stepexpand"><span>Click <span class="uicontrol">Next</span>.</span></li> -<li class="stepexpand"><span>In the <span class="uicontrol">Connector module</span> list, select the + +<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> +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 <span class="uicontrol">Overwrite -existing file</span></span></li> -<li class="stepexpand"><span>Click <span class="uicontrol">Finish</span>.</span></li> +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="section"> The wizard exports the contents of the RAR project to the specified -RAR file.</div> + +<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> +</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 index 6e535d52f..78a47c141 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimpapp.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimpapp.dita @@ -1,4 +1,5 @@ <?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">
@@ -11,20 +12,19 @@ into a JAR file by using the Import wizard.</shortdesc> </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:</p></context>
+<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 J2EE perspective, click <menucascade><uicontrol>File</uicontrol>
-<uicontrol>Import</uicontrol></menucascade>. The Import window opens.</cmd>
-</step>
+<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>Click <uicontrol>Next</uicontrol>.</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><info>You can click the <uicontrol>Browse</uicontrol> button
-to select the JAR file from the file system.</info></step>
+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
@@ -33,12 +33,12 @@ client JAR file, and it will use the default location.</info></step> 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><cmd>If you want to add the new module to an enterprise application
+<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
+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>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimpapp.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimpapp.html index 359639ceb..6cbdb2af5 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimpapp.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimpapp.html @@ -2,8 +2,8 @@ <html lang="en-us" xml:lang="en-us"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> +<meta 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))' /> @@ -26,51 +26,48 @@ <body id="tjimpapp"><a name="tjimpapp"><!-- --></a> -<h1 class="topictitle1" id="title">Importing an application client JAR file</h1> +<h1 class="id_title">Importing an application client JAR file</h1> -<div id="taskbody"><div id="shortdesc">Application client projects are deployed +<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.</div> +into a JAR file by using the Import wizard.</p> -<div class="section" id="context"> <anchor id="topictop"></anchor><p>To import -an application client JAR file using the 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 id="steps"> -<li class="stepexpand"><span>In the J2EE perspective, click <span class="menucascade"><span class="uicontrol">File</span> - > <span class="uicontrol">Import</span></span>. The Import window opens.</span> -</li> +<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>Click <span class="uicontrol">Next</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> You can click the <span class="uicontrol">Browse</span> button -to select the JAR file from the file system.</li> +import.</span></li> <li class="stepexpand"><span>In the <span class="uicontrol">Application Client project</span> field, -type a new project name or select an application client project from the drop-down -list. </span> If you type a new name in this field, 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> +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"><span>If you want to add the new module to an enterprise application +<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 +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> @@ -82,14 +79,14 @@ JAR file.</span></li> </ol> -<div class="section" id="postreq"><anchor id="topicbottom"></anchor> +<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 services.">J2EE architecture</a></div> -<div><a href="../topics/cjappcliproj.html" title="">Application client projects</a></div> +<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> @@ -98,4 +95,4 @@ JAR file.</span></li> </div> </body> -</html> +</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 index ff1c6d471..ffd98afdf 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimpear.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimpear.dita @@ -1,4 +1,5 @@ <?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">
@@ -12,48 +13,41 @@ by importing it from a deployed EAR file.</shortdesc> </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:</p></context>
+<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 J2EE perspective, click <menucascade><uicontrol>File</uicontrol>
-<uicontrol>Import</uicontrol></menucascade>. The Import window opens.</cmd>
-</step>
+<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>.</cmd>
-</step>
-<step><cmd>Click <uicontrol>Next</uicontrol>.</cmd></step>
+<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>
-<info>You can click the <uicontrol>Browse</uicontrol> button to select the
-JAR file from the file system.</info></step>
+</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>
+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><cmd>Click <uicontrol>Next</uicontrol>, and complete the following steps:</cmd>
-<substeps>
-<substep><cmd>On the Enterprise Application Import page, select any utility
-JAR files from the project that you want to import as utility projects.</cmd>
-</substep>
-<substep><cmd>In the <uicontrol>Module Root Location field</uicontrol>, specify
+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.</cmd></substep>
-</substeps>
-</step>
-<step><cmd>Click <uicontrol>Next</uicontrol>.</cmd></step>
-<step><cmd>On the EAR Module and Utility JAR Projects page of the wizard,
-select the projects that you want to import with the EAR file. Also, you can
-edit the new project name for each module and utility project to be imported.</cmd>
-<info><note type="tip">The selection buttons on this page can help you select
-the projects to import when you are importing for partial EAR development.
-For example, if you are importing to a workspace where some projects are attached
-to a repository and other projects are in binary form, these buttons help
-you make the proper selections for which projects to import:<ul>
+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><note type="tip">The
+selection buttons on this page can help you select the projects to import
+when you are importing for partial EAR development. For example, if you are
+importing to a workspace where some projects are attached to a repository
+and other projects are in binary form, these buttons help you make the proper
+selections for which projects to import:<ul>
<li><uicontrol>Select New</uicontrol>: Selects the projects that are currently
not in your workspace.</li>
<li><uicontrol>Select All</uicontrol>: Selects all projects for import.</li>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimpear.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimpear.html index ebaf83838..459fae580 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimpear.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimpear.html @@ -2,8 +2,8 @@ <html lang="en-us" xml:lang="en-us"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> +<meta 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))' /> @@ -11,8 +11,8 @@ <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="enterprise application projects, importing, EAR files" name="DC.subject" /> -<meta content="enterprise application projects, importing, EAR files" name="keywords" /> +<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" /> @@ -28,69 +28,58 @@ <body id="tjimpear"><a name="tjimpear"><!-- --></a> -<h1 class="topictitle1" id="title">Importing an enterprise application EAR file</h1> +<h1 class="id_title">Importing an enterprise application EAR file</h1> -<div id="taskbody"><div id="shortdesc">Enterprise application projects are +<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.</div> - -<div class="section" id="context"> <anchor id="topictop"></anchor><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:</p> +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 id="steps"> -<li class="stepexpand"><span>In the J2EE perspective, click <span class="menucascade"><span class="uicontrol">File</span> - > <span class="uicontrol">Import</span></span>. The Import window opens.</span> -</li> +<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>.</span> -</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Next</span>.</span></li> +<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> - You can click the <span class="uicontrol">Browse</span> button to select the -JAR file from the file system.</li> +</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> +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> +path entries for the project. Click <span class="uicontrol">Next</span>.</li> -<li class="stepexpand"><span>Click <span class="uicontrol">Next</span>, and complete the following steps:</span> -<ol type="a"> -<li><span>On the Enterprise Application Import page, select any utility -JAR files from the project that you want to import as utility projects.</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><span>In the <span class="uicontrol">Module Root Location field</span>, specify +<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.</span></li> - -</ol> - -</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Next</span>.</span></li> - -<li class="stepexpand"><span>On the EAR Module and Utility JAR Projects page of the wizard, -select the projects that you want to import with the EAR file. Also, you can -edit the new project name for each module and utility project to be imported.</span> - <div class="tip"><span class="tiptitle">Tip:</span> The selection buttons on this page can help you select -the projects to import when you are importing for partial EAR development. -For example, if you are importing to a workspace where some projects are attached -to a repository and other projects are in binary form, these buttons help -you make the proper selections for which projects to import:<ul> +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> <div class="tip"><span class="tiptitle">Tip:</span> The +selection buttons on this page can help you select the projects to import +when you are importing for partial EAR development. For example, if you are +importing to a workspace where some projects are attached to a repository +and other projects are in binary form, these buttons help you make the proper +selections for which projects to import:<ul> <li><span class="uicontrol">Select New</span>: Selects the projects that are currently not in your workspace.</li> @@ -108,22 +97,22 @@ EAR file.</span></li> </ol> -<div class="section" id="postreq"><anchor id="topicbottom"></anchor> +<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 services.">J2EE architecture</a></div> +<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="">Cyclical dependencies between J2EE modules</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 J2EE modules</a></div> </div> <div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tjear.html" title="">Creating an enterprise application project</a></div> +<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> +</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 index 5fc2e556f..5d9a2945a 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimprar.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimprar.dita @@ -1,4 +1,5 @@ <?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">
@@ -11,20 +12,18 @@ file.</shortdesc> <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:</p></context>
+<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 J2EE perspective, click <menucascade><uicontrol>File</uicontrol>
-<uicontrol>Import</uicontrol></menucascade>. The Import window opens.</cmd>
-</step>
+<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>Click <uicontrol>Next</uicontrol>.</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><info>Click
-the <uicontrol>Browse</uicontrol> button to select the RAR file from the file
-system.</info></step>
+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
@@ -34,7 +33,7 @@ use the default location.</info></step> 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><cmd>If you want to add the new module to an enterprise application
+<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>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimprar.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimprar.html index e856b1d01..ec292edc4 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimprar.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjimprar.html @@ -1,46 +1,69 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html lang="en-us" xml:lang="en-us"> <head> -<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" /> - +<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> +<meta name="copyright" content="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="topictitle1">Importing a connector project RAR file</h1> -<div><div>Connector projects are deployed into RAR files. You can import -a connector project by importing a deployed RAR file.</div><div class="section"><p>To import a connector project RAR file using the wizard:</p> + + +<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><li class="stepexpand"><span>In the J2EE perspective, click <span class="menucascade"><span class="uicontrol">File</span> > <span class="uicontrol">Import</span></span>. The Import window opens.</span></li> -<li class="stepexpand"><span>Under <span class="uicontrol">Select an import source</span>, click <span class="menucascade"><span class="uicontrol">J2EE Enterprise Applications</span> > <span class="uicontrol">RAR file</span></span>.</span></li> -<li class="stepexpand"><span>Click <span class="uicontrol">Next</span>.</span></li> + +<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> Click -the <span class="uicontrol">Browse</span> button to select the RAR file from the file -system.</li> +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 +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 +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"><span>If you want to add the new module to an enterprise application + +<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 @@ -50,14 +73,24 @@ you type a new enterprise application project name, the enterprise application 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> +</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 index 8fa3cd9e1..861366d94 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjrar.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjrar.dita @@ -1,4 +1,5 @@ <?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">
@@ -11,28 +12,31 @@ systems (EISs).</shortdesc> </keywords>
</metadata></prolog>
<taskbody outputclass="id_taskbody">
-<context outputclass="id_context"> <p outputclass="anchor_topictop"></p>
-<p>A connector is a J2EE standard extension mechanism for containers to provide connectivity
-to enterprise information systems (EISs). 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:</p></context>
+<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 J2EE perspective, select <menucascade><uicontrol>File</uicontrol>
-<uicontrol>New</uicontrol><uicontrol>Project</uicontrol><uicontrol>J2EE</uicontrol>
-<uicontrol>Connector Project</uicontrol></menucascade>.</cmd></step>
+<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><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 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
@@ -40,31 +44,28 @@ 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>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>
+<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><cmd>If you want to use a predefined configuration for your project,
-select a configuration in the <uicontrol>Common Configurations</uicontrol> list.</cmd>
-</step>
-<step><cmd>Click <uicontrol>Next</uicontrol>.</cmd></step>
-<step><cmd>Select the check boxes next to the facets you want this project
-to have and select a version number for each facet. </cmd><info>You can also
-choose a preset combination of facets from the <uicontrol>Presets</uicontrol> list,
-and you can find out more about the requirements for each facet by right-clicking
-the facet name and then clicking <uicontrol>Show Constraints</uicontrol>.</info>
-</step>
-<step><cmd>If you want to limit your project so it will be compatible with
-one or more runtimes, click the <uicontrol>Show Runtimes</uicontrol> button
-and select the runtimes that you want the project to be compatible with.</cmd>
-</step>
-<step><cmd>Click <uicontrol>Next</uicontrol>.</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>
+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>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjrar.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjrar.html index 474bbbeb5..24fdd9c78 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjrar.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjrar.html @@ -2,8 +2,8 @@ <html lang="en-us" xml:lang="en-us"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> +<meta 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))' /> @@ -24,43 +24,46 @@ <body id="tjrar"><a name="tjrar"><!-- --></a> -<h1 class="topictitle1" id="title">Creating a connector project</h1> +<h1 class="id_title">Creating a connector project</h1> -<div id="taskbody"><div id="shortdesc">A connector is a J2EE standard extension +<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).</div> - -<div class="section" id="context"> <anchor id="topictop"></anchor><p> A connector -is a J2EE standard extension mechanism for containers to provide connectivity -to enterprise information systems (EISs). 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:</p> +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 id="steps"> -<li class="stepexpand"><span>In the J2EE perspective, select <span class="menucascade"><span class="uicontrol">File</span> - > <span class="uicontrol">New</span> > <span class="uicontrol">Project</span> > <span class="uicontrol">J2EE</span> - > <span class="uicontrol">Connector Project</span></span>.</span></li> +<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"><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 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 @@ -70,9 +73,9 @@ for the enterprise application, you must use the New Enterprise Application Project wizard.</div> </li> -<li class="stepexpand"><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> +<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> @@ -80,43 +83,39 @@ 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"><span>If you want to use a predefined configuration for your project, -select a configuration in the <span class="uicontrol">Common Configurations</span> list.</span> -</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Next</span>.</span></li> - -<li class="stepexpand"><span>Select the check boxes next to the facets you want this project -to have and select a version number for each facet. </span> You can also -choose a preset combination of facets from the <span class="uicontrol">Presets</span> list, -and you can find out more about the requirements for each facet by right-clicking -the facet name and then clicking <span class="uicontrol">Show Constraints</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 class="stepexpand"><span>If you want to limit your project so it will be compatible with -one or more runtimes, click the <span class="uicontrol">Show Runtimes</span> button -and select the runtimes that you want the project to be compatible with.</span> -</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> -<li class="stepexpand"><span>Click <span class="uicontrol">Next</span>.</span></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> +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="section" id="postreq"><anchor id="topicbottom"></anchor> +<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 J2EE projects.">Project facets</a></div> +<div><a href="../topics/cfacets.html" title="Facets define characteristics and requirements for J2EE projects and are used as part of the runtime configuration.">Project facets</a></div> </div> </div> </body> -</html> +</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 index f225fe374..b9bb0f52c 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjtargetserver.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjtargetserver.dita @@ -1,4 +1,5 @@ <?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">
@@ -10,24 +11,23 @@ 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>
+<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, one of those servers must be the primary
-server, the server that will contribute to the project's class path.</p><p>When
+<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
@@ -54,31 +54,31 @@ tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java"> 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:</p></context>
+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 J2EE perspective, right-click
-the enterprise application or module project, and select <uicontrol>Properties</uicontrol> from
-the pop-up menu.</cmd><stepresult>The Properties dialog for the project opens.</stepresult>
+<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 on the
+<step><cmd>Select the <uicontrol>Targeted Runtimes</uicontrol> page in the
Properties dialog.</cmd></step>
-<step><cmd>In the <uicontrol>Runtimes</uicontrol> list, select the check boxes
-next to each of the runtimes that you want to develop the project for.</cmd>
-<info><p>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.</p><p>If you don't see the runtime that you
-want to use, you need to add it to the runtimes in the workbench. See <xref
-format="html" href="../org.eclipse.wst.server.ui.doc.user/topics/twinstprf.html"
-scope="peer">Defining the installed server runtime environments</xref>.</p></info>
-</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="html"
+href="../org.eclipse.wst.server.ui.doc.user/topics/twinstprf.html" 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><p>If you select
-any runtimes for the project, you must make one of those runtimes the primary
+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.</p></info></step>
-<step><cmd>Click <uicontrol>Finish</uicontrol>.</cmd></step>
+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>
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjtargetserver.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjtargetserver.html index 5771305ce..5573ae640 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjtargetserver.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjtargetserver.html @@ -2,8 +2,8 @@ <html lang="en-us" xml:lang="en-us"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> +<meta 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))' /> @@ -11,8 +11,8 @@ <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 modules, target servers, projects, target servers" name="DC.subject" /> -<meta content="J2EE modules, target servers, projects, target servers" name="keywords" /> +<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" /> @@ -24,30 +24,30 @@ <body id="tjtargetserver"><a name="tjtargetserver"><!-- --></a> -<h1 class="topictitle1" id="title">Specifying target servers for J2EE projects</h1> +<h1 class="id_title">Specifying target servers for J2EE projects</h1> -<div id="taskbody"><div id="shortdesc">When you develop J2EE applications, +<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.</div> - -<div class="section" id="context"><anchor id="topictop"></anchor><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, one of those servers must be the primary -server, the server that will contribute to the project's class path.</p> +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 @@ -77,50 +77,46 @@ 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:</p> +the target runtime and default server for an existing project, complete the +following steps:</p> </div> -<ol id="steps"> -<li class="stepexpand"><span>In the Project Explorer view of the J2EE perspective, right-click -the enterprise application or module project, and select <span class="uicontrol">Properties</span> from -the pop-up menu.</span> The Properties dialog for the project opens. +<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 on the +<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">Runtimes</span> list, select the check boxes -next to each of the runtimes that you want to develop the project for.</span> - <p>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.</p> -<p>If you don't see the runtime that you -want to use, you need to add it to the runtimes in the workbench. See <a href="../org.eclipse.wst.server.ui.doc.user/topics/twinstprf.html">Defining the installed server runtime environments</a>.</p> - +<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> <p>If you select -any runtimes for the project, you must make one of those runtimes the primary +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.</p> -</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Finish</span>.</span></li> +shown in bold text.</li> <li class="stepexpand"><span>Click <span class="uicontrol">OK</span>.</span></li> </ol> -<div class="section" id="postreq"><anchor id="topicbottom"></anchor> +<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 services.">J2EE architecture</a></div> +<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> @@ -128,4 +124,4 @@ shown in bold text.</p> </div> </body> -</html> +</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 index 2298fcd9f..851f9e656 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjval.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjval.dita @@ -1,4 +1,5 @@ <?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">
@@ -7,49 +8,49 @@ 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>
+<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 Properties 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>Follow these steps to validate your files:</p></context>
+<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 Properties 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>.</cmd></step>
-<step><cmd>In the Preferences window, click <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>
+</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>
+</choicetable>
</step>
-<step><cmd>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>To prevent validation at the global level, select the <uicontrol>Suspend
-all validators</uicontrol> check box.</cmd><info>If you select this check
-box, you can still enable validation at the project level.</info></step>
-<step><cmd>If you want to save any resources you have modified before the
-validation begins, select the <uicontrol>Save all modified resources automatically
-prior to validating</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 build
validation.</info></step>
<step><cmd>Choose an alternate implementation for a validator by clicking
-the button in the <uicontrol>Settings</uicontrol> column.</cmd><info>Not all
-validators have alternate implementations.</info></step>
-<step><cmd>Click <uicontrol>OK</uicontrol>.</cmd></step>
-<step><cmd>If you want to set individual validation settings for one or more
-of your projects, see <xref href="tjvalglobalpref.dita"></xref>.</cmd></step>
+the button in the <uicontrol>Settings</uicontrol> column, then click <uicontrol>OK</uicontrol>.</cmd>
+<info>Not all validators have alternate implementations.</info></step>
<step><cmd>Begin the validation process by one of the following methods:</cmd>
<choices>
<choice>Right-click a project and click <uicontrol>Run Validation</uicontrol>.</choice>
@@ -57,8 +58,11 @@ of your projects, see <xref href="tjvalglobalpref.dita"></xref>.</cmd></step> </choices>
</step>
</steps>
-<result outputclass="id_result">Any errors found by the validators are listed
-in the Problems view.</result>
+<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 index 3f71f0da2..9e4ccd108 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjval.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjval.html @@ -2,8 +2,8 @@ <html lang="en-us" xml:lang="en-us"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> +<meta 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))' /> @@ -11,8 +11,10 @@ <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="validation, overview, code validation, automatic, build validation, enabling" name="DC.subject" /> -<meta content="validation, overview, code validation, automatic, build validation, enabling" name="keywords" /> +<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" /> @@ -30,43 +32,58 @@ 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 Properties 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>Follow these steps to validate your files:</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 Properties 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>.</span></li> +</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>In the Preferences window, click <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> -<li class="stepexpand"><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> +<td valign="top" headers="N100A9-desc N100E1">Select to save resources you have modified before the validation begins.</td> -<li class="stepexpand"><span>To prevent validation at the global level, select the <span class="uicontrol">Suspend -all validators</span> check box.</span> If you select this check -box, you can still enable validation at the project level.</li> +</tr> -<li class="stepexpand"><span>If you want to save any resources you have modified before the -validation begins, select the <span class="uicontrol">Save all modified resources automatically -prior to validating</span> check box.</span></li> +</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 @@ -74,13 +91,8 @@ a check box to specify whether it is used on manual validation or on build validation.</li> <li class="stepexpand"><span>Choose an alternate implementation for a validator by clicking -the button in the <span class="uicontrol">Settings</span> column.</span> Not all -validators have alternate implementations.</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">OK</span>.</span></li> - -<li class="stepexpand"><span>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>.</span></li> +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> <li class="stepexpand"><span>Begin the validation process by one of the following methods:</span> <ul> @@ -94,14 +106,22 @@ of your projects, see <a href="tjvalglobalpref.html" title="For a given project, </ol> -<div class="id_result">Any errors found by the validators are listed -in the Problems view.</div> +<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 index dc28f4584..afe3aa197 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvaldisable.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvaldisable.dita @@ -1,4 +1,5 @@ <?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">
@@ -11,28 +12,34 @@ settings for your entire workspace and for individual projects.</shortdesc> <indexterm>code validation<indexterm>disabling</indexterm></indexterm></keywords>
</metadata></prolog>
<taskbody outputclass="id_taskbody">
-<context outputclass="id_context"><p outputclass="anchor_topictop"></p></context>
+<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>.</cmd></step>
-<step><cmd>In the Preferences window, click <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>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>To prevent validation at the global level, select the <uicontrol>Suspend
-all validators</uicontrol> check box.</cmd><info>If you select this check
-box, you can still enable validation at the project level.</info></step>
+</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>
+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>If you want to set individual validation settings for one or more
-of your projects, see <xref href="tjvalglobalpref.dita"></xref>.</cmd></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 index baf6207cf..ee191c448 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvaldisable.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvaldisable.html @@ -2,8 +2,8 @@ <html lang="en-us" xml:lang="en-us"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> +<meta 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))' /> @@ -25,47 +25,62 @@ <body id="tjvaldisable"><a name="tjvaldisable"><!-- --></a> -<h1 class="topictitle1" id="title">Disabling validation</h1> +<h1 class="id_title">Disabling validation</h1> -<div id="taskbody"><div id="shortdesc">You can disable one or more validators +<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.</div> +settings for your entire workspace and for individual projects.</p> -<div class="section" id="context"><anchor id="topictop"></anchor> +<div class="id_context"><p class="anchor_topictop" /> +<p>To +disable validators in your project or workspace, complete the following steps:</p> </div> -<ol id="steps"> +<ol class="id_steps"> <li class="stepexpand"><span>Click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> -</span>.</span></li> +</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>In the Preferences window, click <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 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"><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"><strong>Optional: </strong><span>You can also change the following +check box options on this page:</span> -<li class="stepexpand"><span>To prevent validation at the global level, select the <span class="uicontrol">Suspend -all validators</span> check box.</span> If you select this check -box, you can still enable validation at the project level.</li> +<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> -<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> +<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> -<li class="stepexpand"><span>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>.</span></li> +<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" id="postreq"><anchor id="topicbottom"></anchor> +<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> @@ -78,4 +93,4 @@ of your projects, see <a href="tjvalglobalpref.html" title="For a given project, </div> </body> -</html> +</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 index 96a95a80d..50487df7b 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalglobalpref.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalglobalpref.dita @@ -1,4 +1,5 @@ <?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">
@@ -14,19 +15,17 @@ the global validation preferences.</shortdesc> <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:</p></context>
+preferences, complete the following steps:</p></context>
<steps outputclass="id_steps">
<step><cmd>Click <menucascade><uicontrol>Window</uicontrol><uicontrol>Preferences</uicontrol>
-</menucascade>.</cmd></step>
-<step><cmd>In the Preferences window, click <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>
+</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.</cmd></step>
-<step><cmd>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>
+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>
@@ -40,10 +39,10 @@ all validators</uicontrol> check box.</cmd></step> 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.</cmd><info>Not all
-validators have alternate implementations.</info></step>
-<step><cmd>Click <uicontrol>OK</uicontrol>.</cmd></step>
+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 index 52f4b9310..52fa59c8e 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalglobalpref.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalglobalpref.html @@ -2,8 +2,8 @@ <html lang="en-us" xml:lang="en-us"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> +<meta 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))' /> @@ -13,6 +13,9 @@ <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 content="XHTML" name="DC.Format" /> <meta content="tjvalglobalpref" name="DC.Identifier" /> <meta content="en-us" name="DC.Language" /> @@ -33,23 +36,19 @@ the global validation preferences.</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:</p> +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>.</span></li> - -<li class="stepexpand"><span>In the Preferences window, click <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> +</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.</span></li> - -<li class="stepexpand"><span>Click <span class="uicontrol">OK</span>.</span> Now individual -projects can override the global preferences.</li> +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> @@ -70,10 +69,8 @@ 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.</span> Not all -validators have alternate implementations.</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">OK</span>.</span></li> +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> @@ -82,6 +79,12 @@ validators have alternate implementations.</li> </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> </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 index 486f4a7a5..4f67f5fac 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalmanual.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalmanual.dita @@ -1,4 +1,5 @@ <?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">
@@ -11,16 +12,18 @@ settings.</shortdesc> 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>
+<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:</p></context>
+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>Run Validation</uicontrol>.</cmd>
@@ -35,3 +38,4 @@ 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 index f564ffaef..48463a0e6 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalmanual.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalmanual.html @@ -2,8 +2,8 @@ <html lang="en-us" xml:lang="en-us"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> +<meta 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))' /> @@ -25,17 +25,19 @@ <body id="tjvalmanual"><a name="tjvalmanual"><!-- --></a> -<h1 class="topictitle1" id="title">Manually validating code</h1> +<h1 class="id_title">Manually validating code</h1> -<div id="taskbody"><div id="shortdesc">When you run a manual validation, all +<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.</div> +settings.</p> -<anchor id="topicbottom"></anchor><div class="section" id="context">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> +<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> @@ -47,9 +49,11 @@ selected on the project's validation preferences page.</li> <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:</p> +<p>To manually invoke an immediate code validation, +complete the following steps:</p> +</div> -<ol id="steps"> +<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">Run Validation</span>.</span> @@ -60,11 +64,11 @@ project, see <a href="tjvalglobalpref.html" title="For a given project, you can </ol> -<div id="result">The workbench validates the project using +<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="section" id="postreq"><anchor id="topicbottom"></anchor> +<div class="id_postreq"><p class="anchor_topicbottom" /> </div> </div> @@ -77,4 +81,4 @@ Problems view.</div> </div> </body> -</html> +</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 index 87fb3adb7..d0547d594 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalselect.dita +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalselect.dita @@ -1,4 +1,5 @@ <?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">
@@ -12,20 +13,20 @@ run on manual validation, build validation, both, or neither. </shortdesc> </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:</p></context>
+<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>.</cmd></step>
-<step><cmd>In the Preferences window, click <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>
+</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><cmd>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 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
@@ -33,14 +34,14 @@ you deselect any validator that is currently selected, any messages associated with the deselected validator will be removed from the task list.</note></info>
</step>
<step><cmd>Choose an alternate implementation for a validator by clicking
-the button in the <uicontrol>Settings</uicontrol> column.</cmd><info>Not all
-validators have alternate implementations.</info></step>
-<step><cmd>Click <uicontrol>OK</uicontrol>.</cmd></step>
-<step><cmd>If you want to set individual validation settings for one or more
-of your projects, see <xref href="tjvalglobalpref.dita"></xref>.</cmd><info>Like
-the global validation preferences, you can set validators at the project level
-to run on manual validation, build validation, both, or neither.</info></step>
+the button in the <uicontrol>Settings</uicontrol> column, then click <uicontrol>OK</uicontrol>.</cmd>
+<info>Not all validators have alternate implementations.</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 index da0eb87d6..6ba8ccdef 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalselect.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjvalselect.html @@ -2,8 +2,8 @@ <html lang="en-us" xml:lang="en-us"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> +<meta 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))' /> @@ -25,33 +25,33 @@ <body id="tjvalselect"><a name="tjvalselect"><!-- --></a> -<h1 class="topictitle1" id="title">Selecting code validators</h1> +<h1 class="id_title">Selecting code validators</h1> -<div id="taskbody"><div id="shortdesc">You can select specific validators to +<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. </div> +run on manual validation, build validation, both, or neither. </p> -<div class="section" id="context"><anchor id="topictop"></anchor><p>To choose the validators that you -want to use for a project:</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 id="steps"> +<ol class="id_steps"> <li class="stepexpand"><span>Click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> -</span>.</span></li> - -<li class="stepexpand"><span>In the Preferences window, click <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> +</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"><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"><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 @@ -62,19 +62,17 @@ with the deselected validator will be removed from the task list.</div> </li> <li class="stepexpand"><span>Choose an alternate implementation for a validator by clicking -the button in the <span class="uicontrol">Settings</span> column.</span> Not all -validators have alternate implementations.</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">OK</span>.</span></li> - -<li class="stepexpand"><span>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>.</span> Like -the global validation preferences, you can set validators at the project level -to run on manual validation, build validation, both, or neither.</li> +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="section" id="postreq"><anchor id="topicbottom"></anchor> +<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> @@ -87,4 +85,4 @@ to run on manual validation, build validation, both, or neither.</li> </div> </body> -</html> +</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 new file mode 100644 index 000000000..2b0d100c3 --- /dev/null +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjviewfilters.dita @@ -0,0 +1,36 @@ +<?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>
+</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 new file mode 100644 index 000000000..e1d26ff16 --- /dev/null +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/tjviewfilters.html @@ -0,0 +1,70 @@ +<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta 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" name="DC.subject" /> +<meta content="filters, Project Explorer view, views, Project Explorer filters" 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 |