blob: f13c70bf55d6aaef72d8429247e637ab716b4bf2 [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="../../../../webtools/wtp.xsl"?>
<html>
<head>
<meta
name="root"
content="../../../.." />
<title>j2ee components</title>
</head>
<body>
<a name="top" />
<h1>jst j2ee</h1>
<h2>Component Overview</h2>
<p>
The J2EE component provides frameworks and tools focused on the
development of J2EE artifacts. Currently, the component supports J2EE
1.2, 1.3 and 1.4. The following use cases are supported:
<ul>
<li>
<p>
create J2EE module structures and artifacts within projects,
</p>
</li>
<li>
<p>import J2EE deployable archives,</p>
</li>
<li>
<p>export development modules into a deployable J2EE archive</p>
</li>
<li>
<p>
validate J2EE artifacts to ensure compliance with the
specification, and
</p>
</li>
<li>
<p>
provide navigable EMF model representations of the J2EE
artifact deployment descriptors within the Project Explorer
</p>
</li>
</ul>
</p>
<p>
A more detailed
<a href="api/j2ee_componentoverview.html">functional overview</a>
is also available.
</p>
<h2>Page Quick Index</h2>
<h3>
<a href="#milestones">Milestone Plans</a>
</h3>
<h3>
<a href="#scenarios">Test Scenarios</a>
</h3>
<h3>
<a href="../../../development/proposals/index.html">Proposals</a>
</h3>
<h3>
<a href="#noteworthy">New and Noteworthy</a>
</h3>
<h3>
<a href="#currentapi">Available API</a>
</h3>
<a name="milestones" />
<h2>Milestone plans</h2>
<h3>
<a href="M2/milestone_plan.html">Milestone 2</a>
</h3>
<h3>
<a href="M3/milestone_plan.html">Milestone 3</a>
</h3>
<h3>
<a href="M4/milestone_plan.html">Milestone 4</a>
</h3>
<h3>
<a href="M5/milestone_plan.html">Milestone 5</a>
</h3>
<h3>
<a href="../../../plans/1.0/jst/j2ee/M8/milestone_plan.html">Milestone 8</a>
</h3>
<h3>
<a href="../../../plans/1.0/jst/j2ee/M9/milestone_plan.html">Milestone 9</a>
</h3>
<a href="#top">top</a>
<a name="scenarios" />
<h2>Test scenarios</h2>
<p>
Our purpose in detailing these features is to allow users of all
backgrounds to begin testing and providing feedback. Each Milestone Test
Plan includes detailed tutorials of the usecases that were available at
the end of the milestone.
</p>
<h3>
<a href="../../../plans/1.5/jst/j2ee/RC5/test_plan.html">General J2EE Test Plan</a>
</h3>
<a href="#top">top</a>
<a name="noteworthy" />
<h2>New and Noteworthy</h2>
<p>
Each milestone produces some new notewothy features. This also contains readme items...
</p>
<h3>
<a href="M3/news/j2ee-news-m3.html">Milestone 3 News</a>
</h3>
<h3>
<a href="M4/news/j2ee-news-m4.html">Milestone 4 News</a>
</h3>
<h3>
<a href="M5/news/j2ee-news-M5.html">Milestone 5 News</a>
</h3>
<a href="#top">top</a>
<a name="currentapi" />
<h2>J2EE API</h2>
<h3>
<a href="../../../wst/api">
WST API JavaDoc
</a>
<a href="../../../jst/api">
JST API JavaDoc
</a>
</h3>
<h3>
<a href="api/j2ee_models_overview.html">
The J2EE Deployment Descriptor Models
</a>
</h3>
<p>
These EMF-based models allow for model-driven access and modification of
J2EE deployment descriptors. Clients may use these models to build
operations, wizards, editors, or whatever they can envision! For the
diagram-happy,
<a href="models/j2ee_rose.html">Rose diagrams and overviews</a>
are also available.
</p>
<h3>
<a href="api/j2ee_operationsAPI.html">
J2EE Module Operations(module creation, import and export) API
</a>
</h3>
<p>
J2EE operations provide capabilities to create J2EE artifacts within
projects, import deployable archives, and export modules from a project
into a deployable archive.
</p>
<h3>
<a href="api/j2ee_wizardsAPI.html">
J2EE Module UI (module creation, import and export) API
</a>
</h3>
<p>
J2EE Wizards depend on the J2EE Operations and allow users to create J2EE
artifacts within projects, import deployable archives, and export modules
from a project into a deployable archive.
</p>
<h3>
<a href="api/module_core_api.html">Flexible Project Structure API</a>
</h3>
<p>
The Flexible Project Structure API, also referred to as ModuleCore,
allows consumers to build J2EE compliant modules from arbitrary
structures within Eclipse projects. The overview discussed the core
pieces of the API with appropriate diagrams and code snippets.
</p>
<h3>
<a href="api/flexibleProjectApiAndUsage.html">Flexible Project Content MetaModel API</a>
</h3>
<p>
The Flexible Project Content Model API allows consumers to build J2EE compliant components from arbitrary structures within Eclipse projects. This document covers the J2EE Artifact Edit api usage and migration info from old NatureRuntime and EditModel api and some code snippets on how to use the ArtifactEdits.
</p>
<a href="#top">top</a>
</body>
</html>