| <?xml version="1.0" encoding="UTF-8"?> |
| <?xml-stylesheet type="text/xsl" href="../../../../../webtools/wtp.xsl"?> |
| <html> |
| <head> |
| <meta |
| name="root" |
| content="../" /> |
| <title>j2ee api</title> |
| </head> |
| |
| <body> |
| <h1>jst j2ee</h1> |
| <h2>Introduction</h2> |
| <p>Find links to all of the published API's of the J2EE component.</p> |
| <br /> |
| |
| <h2>J2EE API</h2> |
| <ul> |
| <li> |
| <p> |
| <a href="j2ee_models_overview.html"> |
| The J2EE Deployment Descriptor Models |
| </a> |
| . 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> |
| </li> |
| <li> |
| <p> |
| <a href="j2ee_operationsAPI.html"> |
| J2EE Module Operations(module creation, import and export) |
| API |
| </a> |
| . J2EE operations provide capabilities to create J2EE artifacts |
| within projects, import deployable archives, and export modules |
| from a project into a deployable archive. |
| </p> |
| </li> |
| <li> |
| <p> |
| <a href="j2ee_wizardsAPI.html"> |
| J2EE Module UI (module creation, import and export) API |
| </a> |
| . 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> |
| </li> |
| <li> |
| <p> |
| <a href="module_core_api.html">Flexible Project Structure API</a> |
| . 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> |
| </li> |
| </ul> |
| </body> |
| </html> |
