Skip to content
Snippets Groups Projects
Commit a9d7e5a4 authored by lmandel's avatar lmandel
Browse files

[115886] Updated WST ISV plugin.

parent a6806d43
No related branches found
No related tags found
No related merge requests found
Showing
with 0 additions and 1130 deletions
<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
<name>org.eclipse.wst.doc.isv</name>
<comment></comment>
<projects>
</projects>
<buildSpec>
<buildCommand>
<name>org.eclipse.pde.ManifestBuilder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>org.eclipse.pde.SchemaBuilder</name>
<arguments>
</arguments>
</buildCommand>
</buildSpec>
<natures>
<nature>org.eclipse.pde.PluginNature</nature>
</natures>
</projectDescription>
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: WST ISV Documentation
Bundle-Vendor: %providerName
Bundle-SymbolicName: org.eclipse.wst.doc.isv; singleton:=true
Bundle-Version: 1.0.0
Bundle-Localization: plugin
Require-Bundle: org.eclipse.help
Each API package is required to have a package overview document describing
at a high level the problem solved by the API, how the API is meant to be used,
and where applicable diagrams and images explaining the expected and correct
usage.
Like the design of the WTP website, the package overviews are stored as
XML files within the root of the package that they describe. The file
name must always be "package.xml". The XSLT stylesheet that runs as part
of the Javadoc process will transform this file into a "package.html" file,
which is expected by the javadoc tool.
Developers have four tags to be aware of, in addition to the normal
tag redefinitions that occur for the website (e.g. some header tags
are redefined as white text with light blue backgrounds that span
the page, like the Eclipse style). These four tags are:
<p> tag: Each paragraph tag will be wrapped in a table that forces
a fixed width for the text lines. Overviews that choose to add images
can often stretch the text out into a width that is difficult or at a
minimum inconvenient to read. Each <p> tag will be formatted consistently
across all overview documents. Please refrain from adding extra formatting
around paragraph tags.
<img src="" caption=""> tag: Each image will be displayed in a specialized table format, with
a caption. The <img> tag has an attribute "caption" that will be displayed
just under the image explaining in text what the picture intends to
convey graphically. For example:
<img src=".." caption="This sample text" />
__________
| |
| img |
|_________|
|__text___|
*Also note that all images used in a package overview must be placed in the
root of the project under a directory named "javadoc-images". Whenever an
image is linked to, the link must escape to the root package level
to reference the image, and include "overview" in the path. So if you want to
link "model_overview.jpg" into package overview for "com.acme.model":
(1) Place "model_overview.jpg" in <project>\javadoc-images
(2) Add the following element to your document:
<img src="../../../overview/model_overview.jpg" caption="An overview of the Acme Model API" />
--> Note that the three "../" escapes is the same number of elements in the
package path: com/acme/model/.
--> "overview/" is required as all images will be pushed into the "overview"
directory in the final javadoc layout.
<codesnippet caption=""> tag: The codesnippet is provided to allow quick addition of code
snippet examples or usage patterns for API. The content of the <codesnippet />
tag should be the actual source code. The tag will use the text exactly as it
appears in an HTML <pre> tag, and will wrap the snippet in a table for formatting.
The codesnippet tag allows for a caption just as the img tag does.
<abstract> tag: The abstract tag should always occur first in your content, and should
contain a brief synopsis of your package overview ("package overview overview"). The
contents of this tag will be displayed in the full API overview page beside the linked
package name. The tag should contain no extra HTML formatting.
\ No newline at end of file
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
<html>
<head>
<title>About</title>
<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
</head>
<body lang="EN-US">
<h2>About This Content</h2>
<p>February 24, 2005</p>
<h3>License</h3>
<p>The Eclipse Foundation makes available all content in this plug-in (&quot;Content&quot;). Unless otherwise indicated below, the Content is provided to you under the terms and conditions of the
Eclipse Public License Version 1.0 (&quot;EPL&quot;). A copy of the EPL is available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
For purposes of the EPL, &quot;Program&quot; will mean the Content.</p>
<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is being redistributed by another party (&quot;Redistributor&quot;) and different terms and conditions may
apply to your use of any object code in the Content. Check the Redistributor's license that was provided with the Content. If no such license exists, contact the Redistributor. Unless otherwise
indicated below, the terms and conditions of the EPL still apply to any source code in the Content.</p>
</body>
</html>
\ No newline at end of file
<html>
<head>
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<link rel="stylesheet" href="../apistyles.css" type="text/css">
<title>wst api overview</title>
</head>
<body>
<P>
The Web Standards Tools (WST) subproject of the Web Tools Platform
(WTP) provides some of the coolest tooling for open source enterprise
development since cheese in a can!
</P>
<P>
The following components are available as part of the WST:
<ul>
<li>
<p>Command (command):</p>
</li>
<li>
<p>
Common (common): Provides frameworks that are not tied to a
specific Web Standard, but that are useful for many other
components within WST and the Java Standards Tools (JST)
</p>
</li>
<li>
<p>CSS (css):</p>
</li>
<li>
<p>DTD (dtd):</p>
</li>
<li>
<p>HTML (html):</p>
</li>
<li>
<p>Internet (internet):</p>
</li>
<li>
<p>Javascript (javascript):</p>
</li>
<li>
<p>Relational Databases (rdb):</p>
</li>
<li>
<p>Server (server):</p>
</li>
<li>
<p>SSE (sse):</p>
</li>
<li>
<p>Validation (validation):</p>
</li>
<li>
<p>
Web (web): Provides functionality for simple (non-J2EE) web
projects.
</p>
</li>
<li>
<p>Web Services (ws):</p>
</li>
<li>
<p>Web Services Definition Language (wsdl):</p>
</li>
<li>
<p>Web Services I(?) (wsi):</p>
</li>
<li>
<p>eXtensible Modeling Language (xml):</p>
</li>
<li>
<p>eXtensible Schema Definitions (xsd):</p>
</li>
</ul>
</P>
</body>
</html>
<?xml version="1.0" encoding="UTF-8"?>
<html>
<head>
<meta name="root" content=".." />
<title>WST API Overview</title>
</head>
<body>
<P>
The Web Standard Tools (WST) subproject of the Web Tools
Platform (WTP) provides extensible tools for the development
of Web Applications and supports development, testing and
debugging with various servers using open standards,
specifications, and languages.
</P>
<P>
The following components are available as part of the WST:
<ul>
<li>
<p>Command (command):</p>
</li>
<li>
<p>
Common (common): Provides frameworks that are
not tied to a specific Web Standard, but that
are useful for many other components within WST
and the J2EE Standard Tools (JST)
</p>
</li>
<li>
<p>
CSS (css): Provides a SSE-based source model and
editor for Cascading Style Sheets
</p>
</li>
<li>
<p>
DTD (dtd): Provides a SSE-based DTD source model
and editor, as well as an EMF-based model and a
DTD validator
</p>
</li>
<li>
<p>
HTML (html): Provides a SSE-based HTML source
model, editor, and validator
</p>
</li>
<li>
<p>Internet (internet):</p>
</li>
<li>
<p>
Javascript (javascript): Provides a Javascript
source editor and source editor with preview
</p>
</li>
<li>
<p>Relational Databases (rdb):</p>
</li>
<li>
<p>Server (server):</p>
</li>
<li>
<p>
SSE (sse): Provides frameworks for extendable
and easiy embeddable source editing, with
emphasis on content-type-based behavior and
extensibility.
</p>
</li>
<li>
<p>Validation (validation):</p>
</li>
<li>
<p>
Web (web): Provides functionality for simple
(non-J2EE) web projects.
</p>
</li>
<li>
<p>Web Services (ws):</p>
</li>
<li>
<p>Web Services Definition Language (wsdl):</p>
</li>
<li>
<p>Web Services I(?) (wsi):</p>
</li>
<li>
<p>
eXtensible Modeling Language (xml): Provides a
SSE-based XML source model, editor, validator,
and an advanced XML editor with a design page
</p>
</li>
<li>
<p>eXtensible Schema Definitions (xsd):</p>
</li>
</ul>
</P>
</body>
</html>
p, table, td, th {
font-family: arial, helvetica, geneva;
font-size: 10pt
}
pre {
font-family: "Courier New", Courier, mono; font-size: 10pt}
h2 {
font-family: arial, helvetica, geneva;
font-size: 18pt;
font-weight: bold ;
line-height: 14px
}
code {
font-family: "Courier New", Courier, mono;
font-size: 10pt
}
sup {
font-family: arial,helvetica,geneva;
font-size: 10px
}
h3 {
font-family: arial, helvetica, geneva;
font-size: 14pt;
font-weight: bold
}
li {
font-family: arial, helvetica, geneva;
font-size: 10pt
}
h1 {
font-family: arial, helvetica, geneva;
font-size: 28px;
font-weight: bold
}
body {
font-family: arial, helvetica, geneva;
font-size: 10pt;
clip: rect( );
margin-top: 5mm;
margin-left: 3mm;
color: rgb(0, 0, 0);
background-color: rgb(255, 255, 255);
alink="#ff0000";
link="#0000ee";
vlink="#551a8b";
}
.indextop {
font-size: x-large;;
font-family: Verdana, Arial, Helvetica, sans-serif;
font-weight: bold
}
.indexsub {
font-size: xx-small;;
font-family: Arial, Helvetica, sans-serif;
color: #8080FF
}
a:link {
color: #0000ee;
}
a:visited {
color: #551a8b;
}
a:active {
color: #ff0000;
}
###############################################################################
# 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
###############################################################################
# use provided build.xml
custom = true
<?xml version="1.0" encoding="UTF-8"?>
<project name="org.eclipse.wst.doc.isv" default="build.jars" basedir=".">
<property name="bootclasspath" value=""/>
<property name="basews" value="${ws}"/>
<property name="baseos" value="${os}"/>
<property name="basearch" value="${arch}"/>
<property name="basenl" value="${nl}"/>
<property name="javacFailOnError" value="false"/>
<property name="javacDebugInfo" value="on"/>
<property name="javacVerbose" value="true"/>
<property name="javacSource" value="1.3"/>
<property name="javacTarget" value="1.2"/>
<property name="compilerArg" value=""/>
<target name="init" depends="properties">
<condition property="pluginTemp" value="${buildTempFolder}/plugins">
<isset property="buildTempFolder"/>
</condition>
<property name="pluginTemp" value="${basedir}"/>
<condition property="build.result.folder" value="${pluginTemp}/org.eclipse.wst.doc.isv">
<isset property="buildTempFolder"/>
</condition>
<property name="build.result.folder" value="${basedir}"/>
<property name="temp.folder" value="${basedir}/temp.folder"/>
<property name="plugin.destination" value="${basedir}"/>
</target>
<target name="properties" if="eclipse.running">
<property name="build.compiler" value="org.eclipse.jdt.core.JDTCompilerAdapter"/>
</target>
<target name="build.update.jar" depends="init" description="Build the plug-in: org.eclipse.wst.doc.isv for an update site.">
<delete dir="${temp.folder}"/>
<mkdir dir="${temp.folder}"/>
<antcall target="build.jars"/>
<antcall target="gather.bin.parts">
<param name="destination.temp.folder" value="${temp.folder}/"/>
</antcall>
<zip destfile="${plugin.destination}/org.eclipse.wst.doc.isv_0.7.0.jar" basedir="${temp.folder}/org.eclipse.wst.doc.isv_0.7.0" filesonly="false" whenempty="skip" update="false"/>
<delete dir="${temp.folder}"/>
</target>
<target name="build.jars" depends="init" description="Build all the jars for the plug-in: org.eclipse.wst.doc.isv.">
<ant antfile="javadoc.xml" dir="${basedir}"/>
</target>
<target name="build.sources" depends="init">
</target>
<target name="gather.bin.parts" depends="init" if="destination.temp.folder">
<mkdir dir="${destination.temp.folder}/org.eclipse.wst.doc.isv_0.7.0"/>
<copy todir="${destination.temp.folder}/org.eclipse.wst.doc.isv_0.7.0" failonerror="true">
<fileset dir="${basedir}" includes="plugin.xml,plugin.properties,about.html,doc.zip,toc.xml,topics_Reference.xml,META-INF/" />
</copy>
</target>
<target name="build.zips" depends="init">
</target>
<target name="gather.sources" depends="init" if="destination.temp.folder">
<mkdir dir="${destination.temp.folder}/org.eclipse.wst.doc.isv_0.7.0"/>
<copy todir="${destination.temp.folder}/org.eclipse.wst.doc.isv_0.7.0" failonerror="false">
<fileset dir="${basedir}" includes="plugin.xml,doc.zip,toc.xml,topics_Reference.xml,META-INF/" />
</copy>
</target>
<target name="gather.logs" depends="init" if="destination.temp.folder">
</target>
<target name="clean" depends="init" description="Clean the plug-in: org.eclipse.wst.doc.isv of all the zips, jars and logs created.">
<delete file="${plugin.destination}/org.eclipse.wst.doc.isv_0.7.0.jar"/>
<delete file="${plugin.destination}/org.eclipse.wst.doc.isv_0.7.0.zip"/>
<delete dir="${temp.folder}"/>
</target>
<target name="refresh" depends="init" if="eclipse.running" description="Refresh this folder.">
<!--
<eclipse.convertPath fileSystemPath="D:/wtp_v10m3/workspace_releng/org.eclipse.wst.doc.isv" property="resourcePath"/>
-->
<eclipse.refreshLocal resource="${resourcePath}" depth="infinite"/>
</target>
<target name="zip.plugin" depends="init" description="Create a zip containing all the elements for the plug-in: org.eclipse.wst.doc.isv.">
<delete dir="${temp.folder}"/>
<mkdir dir="${temp.folder}"/>
<antcall target="build.jars"/>
<antcall target="build.sources"/>
<antcall target="gather.bin.parts">
<param name="destination.temp.folder" value="${temp.folder}/"/>
</antcall>
<antcall target="gather.sources">
<param name="destination.temp.folder" value="${temp.folder}/"/>
</antcall>
<delete>
<fileset dir="${temp.folder}" includes="**/*.bin.log" />
</delete>
<zip destfile="${plugin.destination}/org.eclipse.wst.doc.isv_0.7.0.zip" basedir="${temp.folder}" filesonly="true" whenempty="skip" update="false"/>
<delete dir="${temp.folder}"/>
</target>
</project>
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
<meta
http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
<meta
name="GENERATOR"
content="Mozilla/4.73 [en] (Win98; U) [Netscape]">
<title>splash</title>
<link
rel="stylesheet"
href="sources/formate.css">
</head>
<body>
<center>
<h1>Online Help</h1>
</center>
<p>The description of the API and the plugins of the WTP and their
Extensions (-Points)</p>
</body>
</html>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta
http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
<title>Checking WTP out</title>
<link
rel="stylesheet"
type="text/css"
href="sources/formate.css">
</head>
<body>
<p class="ueberschrift">How to check out the WTP plugins</p>
<p>It is recommended to check out the plugins via the releng tools using
map files provided by the project.<br>
The main advantage of this approach is to have a reproducable build, and
that way you can easily check out exactly the code that is contained in
builds produced by the web tools project (I-Builds, M-Builds, Releases).<br>
This approach makes general handling easier and is as well more helpful
for the project when submitting bugreports or supplying pachtes.
Checking out HEAD is not recommended as it is not reproducable.<br>
</p>
<ul>
<li>
<p>First, download the current releng tools version (for Eclipse 3.1
you will find it here: <a
href="http://download.eclipse.org/eclipse/downloads/
drops/R-3.1-200506271435/index.php">(http://download.eclipse.org/eclipse/downloads/
drops/R-3.1-200506271435/index.php)</a> at the bottom of the page).</p>
</li>
</ul>
<ul>
<li>Then you will need all the map files of the includet plugins. The
whole collection (for 0.7RC1) is available here: <a
href="http://download.eclipse.org/webtools/downloads/drops/S-0.7RC1-200507150303/directory.txt">
http://download.eclipse.org/webtools/downloads/drops/S-0.7RC1-200507150303/directory.txt</a>.</li>
</ul>
<ul>
<li>Create a new project in Eclipse. Create a new file with an .map
extension. Paste all maps from the link above into the file.</li>
</ul>
<ul>
<li>Right-click on the file. Select: Team - Load Map Projects. (If you
copyed all map files into the file, it will take a little longer).</li>
</ul>
<ul>
<li>When you're finished, you've checked out all WTP plugins out of
the Eclipse CVS.<br>
The plugins are all located in the same project/directory.</li>
</ul>
</body>
</html>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>Adapter Factory Extension</title>
<link rel="stylesheet" type="text/css" href="schema.css">
</HEAD>
<BODY>
<H1><CENTER>Adapter Factory Extension</CENTER></H1>
<p></p>
<h6 class=CaptionFigColumn id=header>Identifier: </h6>com.ibm.etools.emf.workbench.adapterFactory<p></p>
<h6 class=CaptionFigColumn id=header>Since: </h6>[Enter the first release in which this extension point appears.]
<p></p>
<p>
<h6 class=CaptionFigColumn id=header>Description: </h6>This is used to register an adapter factory with the dynamic adapter factory.</p>
<p><h6 class=CaptionFigColumn id=header>Configuration Markup:</h6></p>
<p class=code id=dtd>&lt;!ELEMENT <a name="e.extension">extension</a> (<a href="#e.adapterFactory">adapterFactory</a>+)&gt;</p>
<p class=code id=dtd>&lt;!ATTLIST extension</p>
<p class=code id=dtdAttlist>point&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>id&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class=code id=dtdAttlist>name&nbsp;&nbsp;CDATA #IMPLIED&gt;</p>
<p></p>
<ul class=ConfigMarkup id=attlistDesc>
</ul>
<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.adapterFactory">adapterFactory</a> (<a href="#e.view">view</a>*)&gt;</p>
<p class=code id=dtd>&lt;!ATTLIST adapterFactory</p>
<p class=code id=dtdAttlist>packageURI&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>className&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>functionGroupID&nbsp;CDATA #IMPLIED&gt;</p>
<p></p>
<p class=ConfigMarkup id=elementDesc>
Defines the Adapter Factory being added. All added Adapter Factories are queriable whenever their Function Group and optional Viewer Id are specified.</p>
<br>
<ul class=ConfigMarkup id=attlistDesc>
<li><b>packageURI</b> - The package URI that you are extending (for example "ejb.xmi")</li>
<li><b>className</b> - The fully qualified name of the class which implements org.eclipse.emf.common.notify.AdapterFactory.</li>
<li><b>id</b> - The Unique identifier of the Adapter Factory extension. This will associate it with one or more function groups based on the function group patterns. Function Groups allow Content and Actions to be enabled or disabled based on project-specific information. Generally, they are used by vendors who wish to add functionality specific to their products, e.g. J2EE Application Servers.</li>
<li><b>functionGroupID</b> - </li>
</ul>
<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.view">view</a> EMPTY&gt;</p>
<p class=code id=dtd>&lt;!ATTLIST view</p>
<p class=code id=dtdAttlist>id&nbsp;CDATA #REQUIRED&gt;</p>
<p></p>
<ul class=ConfigMarkup id=attlistDesc>
<li><b>id</b> - An optional viewer Id which will limit the invocation of the defined Adapter Factory to the given viewer id.</li>
</ul>
<br><h6 class=CaptionFigColumn id=header>Examples: </h6>[Enter extension point usage example here.]
<p></p>
<h6 class=CaptionFigColumn id=header>API Information: </h6>[Enter API information here.]
<p></p>
<h6 class=CaptionFigColumn id=header>Supplied Implementation: </h6>[Enter information about supplied implementation of this extension point.]
<p></p>
<br>
<p class=note id=copyright>
</p>
</BODY>
</HTML>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>DataModelProvider</title>
<link rel="stylesheet" type="text/css" href="schema.css">
</HEAD>
<BODY>
<H1><CENTER>DataModelProvider</CENTER></H1>
<p></p>
<h6 class=CaptionFigColumn id=header>Identifier: </h6>org.eclipse.wst.common.frameworks.DataModelProviderExtension<p></p>
<h6 class=CaptionFigColumn id=header>Since: </h6>[Enter the first release in which this extension point appears.]
<p></p>
<p>
<h6 class=CaptionFigColumn id=header>Description: </h6>[Enter description of this extension point.]</p>
<p><h6 class=CaptionFigColumn id=header>Configuration Markup:</h6></p>
<p class=code id=dtd>&lt;!ELEMENT <a name="e.extension">extension</a> (<a href="#e.DataModelProvider">DataModelProvider</a>? , <a href="#e.ProviderDefinesType">ProviderDefinesType</a>? , <a href="#e.ProviderImplementsType">ProviderImplementsType</a>?)&gt;</p>
<p class=code id=dtd>&lt;!ATTLIST extension</p>
<p class=code id=dtdAttlist>point&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>id&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class=code id=dtdAttlist>name&nbsp;&nbsp;CDATA #IMPLIED&gt;</p>
<p></p>
<ul class=ConfigMarkup id=attlistDesc>
</ul>
<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.DataModelProvider">DataModelProvider</a> EMPTY&gt;</p>
<p class=code id=dtd>&lt;!ATTLIST DataModelProvider</p>
<p class=code id=dtdAttlist>id&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class=code id=dtdAttlist>class&nbsp;CDATA #REQUIRED&gt;</p>
<p></p>
<ul class=ConfigMarkup id=attlistDesc>
<li><b>id</b> - </li>
<li><b>class</b> - </li>
</ul>
<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.ProviderDefinesType">ProviderDefinesType</a> EMPTY&gt;</p>
<p class=code id=dtd>&lt;!ATTLIST ProviderDefinesType</p>
<p class=code id=dtdAttlist>providerType&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>providerID&nbsp;&nbsp;&nbsp;CDATA #REQUIRED&gt;</p>
<p></p>
<ul class=ConfigMarkup id=attlistDesc>
<li><b>providerType</b> - </li>
<li><b>providerID</b> - </li>
</ul>
<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.ProviderImplementsType">ProviderImplementsType</a> EMPTY&gt;</p>
<p class=code id=dtd>&lt;!ATTLIST ProviderImplementsType</p>
<p class=code id=dtdAttlist>providerType&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>providerID&nbsp;&nbsp;&nbsp;CDATA #REQUIRED&gt;</p>
<p></p>
<ul class=ConfigMarkup id=attlistDesc>
<li><b>providerType</b> - </li>
<li><b>providerID</b> - </li>
</ul>
<br><h6 class=CaptionFigColumn id=header>Examples: </h6>[Enter extension point usage example here.]
<p></p>
<h6 class=CaptionFigColumn id=header>API Information: </h6>[Enter API information here.]
<p></p>
<h6 class=CaptionFigColumn id=header>Supplied Implementation: </h6>[Enter information about supplied implementation of this extension point.]
<p></p>
<br>
<p class=note id=copyright>
</p>
</BODY>
</HTML>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>DataModelWizard</title>
<link rel="stylesheet" type="text/css" href="schema.css">
</HEAD>
<BODY>
<H1><CENTER>DataModelWizard</CENTER></H1>
<p></p>
<h6 class=CaptionFigColumn id=header>Identifier: </h6>org.eclipse.wst.common.frameworks.ui.DataModelWizardExtension<p></p>
<h6 class=CaptionFigColumn id=header>Since: </h6>[Enter the first release in which this extension point appears.]
<p></p>
<p>
<h6 class=CaptionFigColumn id=header>Description: </h6>[Enter description of this extension point.]</p>
<p><h6 class=CaptionFigColumn id=header>Configuration Markup:</h6></p>
<p class=code id=dtd>&lt;!ELEMENT <a name="e.extension">extension</a> (<a href="#e.DataModelWizard">DataModelWizard</a>)&gt;</p>
<p class=code id=dtd>&lt;!ATTLIST extension</p>
<p class=code id=dtdAttlist>point&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>id&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class=code id=dtdAttlist>name&nbsp;&nbsp;CDATA #IMPLIED&gt;</p>
<p></p>
<ul class=ConfigMarkup id=attlistDesc>
</ul>
<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.DataModelWizard">DataModelWizard</a> EMPTY&gt;</p>
<p class=code id=dtd>&lt;!ATTLIST DataModelWizard</p>
<p class=code id=dtdAttlist>id&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class=code id=dtdAttlist>class&nbsp;CDATA #IMPLIED&gt;</p>
<p></p>
<ul class=ConfigMarkup id=attlistDesc>
<li><b>id</b> - </li>
<li><b>class</b> - </li>
</ul>
<br><h6 class=CaptionFigColumn id=header>Examples: </h6>[Enter extension point usage example here.]
<p></p>
<h6 class=CaptionFigColumn id=header>API Information: </h6>[Enter API information here.]
<p></p>
<h6 class=CaptionFigColumn id=header>Supplied Implementation: </h6>[Enter information about supplied implementation of this extension point.]
<p></p>
<br>
<p class=note id=copyright>
</p>
</BODY>
</HTML>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>EMF Resource Edit Model</title>
<link rel="stylesheet" type="text/css" href="schema.css")
</HEAD>
<BODY>
<H1><CENTER>EMF Resource Edit Model</CENTER></H1>
<p></p>
<h6 class=CaptionFigColumn id=header>Identifier: </h6>com.ibm.etools.emf.workbench.editModel<p></p>
<h6 class=CaptionFigColumn id=header>Since: </h6>6.0
<p></p>
<p>
<h6 class=CaptionFigColumn id=header>Description: </h6>Edit models provide a framework for managing a set of EMF resources within a unit of work. For example, a workspace operation may affect a change to multiple EMF resources. Edit models provide basic services such as loads, saves (when necessary), and validate edit for the managed resources. Edit models are reference counted, therefore a single instance of an edit model can be shared by more than one operation or editor. By declaring an edit model, a plugin provider enables other components to contribute resources to be managed by that edit model.</p>
<p><h6 class=CaptionFigColumn id=header>Configuration Markup:</h6></p>
<p class=code id=dtd>&lt;!ELEMENT <a name="e.extension">extension</a> (<a href="#e.editModel">editModel</a>+)&gt;</p>
<p class=code id=dtd>&lt;!ATTLIST extension</p>
<p class=code id=dtdAttlist>point&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>id&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class=code id=dtdAttlist>name&nbsp;&nbsp;CDATA #IMPLIED&gt;</p>
<p></p>
<ul class=ConfigMarkup id=attlistDesc>
</ul>
<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.editModel">editModel</a> (<a href="#e.editModelResource">editModelResource</a>+)&gt;</p>
<p class=code id=dtd>&lt;!ATTLIST editModel</p>
<p class=code id=dtdAttlist>editModelID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>factoryClass&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>loadUnknownResourcesAsReadOnly&nbsp;(true | false) <p class=code id=dtdAttlist>parentModelID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED&gt;</p>
<p></p>
<p class=ConfigMarkup id=elementDesc>
The declaration for an edit model to be used in the workspace.</p>
<br>
<ul class=ConfigMarkup id=attlistDesc>
<li><b>editModelID</b> - A unique identifier for the edit model.</li>
<li><b>factoryClass</b> - An optional factory class that is used for this edit model. The class must implement the interface <code>com.ibm.etools.emf.workbench.edit.EditModelFactory</code>. If none is specified, then a generic <code>EditModel</code> is created.</li>
<li><b>loadUnknownResourcesAsReadOnly</b> - </li>
<li><b>parentModelID</b> - </li>
</ul>
<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.editModelResource">editModelResource</a> EMPTY&gt;</p>
<p class=code id=dtd>&lt;!ATTLIST editModelResource</p>
<p class=code id=dtdAttlist>URI&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>autoload&nbsp;(true | false) "false"&gt;</p>
<p></p>
<p class=ConfigMarkup id=elementDesc>
This is an individual contribution of a resource to the edit model. If more than one instance of the same URI is registered against an edit model id, the resource is still only loaded once.</p>
<br>
<ul class=ConfigMarkup id=attlistDesc>
<li><b>URI</b> - The URI of the resource relative to the root container from which EMF resources are loaded.</li>
<li><b>autoload</b> - Indicator which determines whether this resource should be autoloaded when the edit model is created, or when an IFile corresponding to this resource is added.</li>
</ul>
<br><h6 class=CaptionFigColumn id=header>Examples: </h6><br>
<code>
&nbsp;&nbsp;&nbsp;&lt;extension<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;id="editModel.acme.parent"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;name="Acme&nbsp;Parent&nbsp;Edit&nbsp;Model"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;point="com.ibm.etools.emf.workbench.editModel"&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;editModel<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;editModelID="com.acme.acmepro.parent.editModel"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;factoryClass="com.ibm.etools.emf.workbench.edit.EditModelFactory"&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;editModelResource&nbsp;URI="DIR/resource0.xml"&nbsp;/&gt;&nbsp;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;editModelResource&nbsp;URI="DIR/resource1.xml"&nbsp;/&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/editModel&gt;<br>
&nbsp;&nbsp;&nbsp;&lt;/extension&gt;&nbsp;<br>
&nbsp;&nbsp;&nbsp;<br>
&nbsp;&nbsp;&nbsp;&lt;extension<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;id="editModel.acme.child"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;name="Acme&nbsp;Child&nbsp;Edit&nbsp;Model"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;point="com.ibm.etools.emf.workbench.editModel"&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;editModel<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;editModelID="com.acme.acmepro.child.editModel"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;factoryClass="com.ibm.etools.emf.workbench.edit.EditModelFactory"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;parentModelID="com.acme.acmepro.parent.editModel"&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;editModelResource&nbsp;URI="DIR/resource2.xml"&nbsp;/&gt;&nbsp;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;editModelResource&nbsp;URI="DIR/resource3.xml"&nbsp;/&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/editModel&gt;<br>
&nbsp;&nbsp;&nbsp;&lt;/extension&gt;&nbsp;&nbsp;&nbsp;<br>
</code>
<p></p>
<h6 class=CaptionFigColumn id=header>API Information: </h6>Edit Models can be accessed through the com.ibm.etools.emf.workbench.EMFWorkbenchContext.
<p></p>
<h6 class=CaptionFigColumn id=header>Supplied Implementation: </h6>[Enter information about supplied implementation of this extension point.]
<p></p>
<br>
<p class=note id=copyright>
</p>
</BODY>
</HTML>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>Edit Model Extension</title>
<link rel="stylesheet" type="text/css" href="schema.css">
</HEAD>
<BODY>
<H1><CENTER>Edit Model Extension</CENTER></H1>
<p></p>
<h6 class=CaptionFigColumn id=header>Identifier: </h6>com.ibm.etoosl.emf.workbench.geditModelExtension<p></p>
<h6 class=CaptionFigColumn id=header>Since: </h6>6.0
<p></p>
<p>
<h6 class=CaptionFigColumn id=header>Description: </h6>The Edit Model Extension allows third parties to contribute expected resources to Edit Models. The functionGroupID allows users to select which extensions they choose to have enabled.<p>
Edit models provide a framework for managing a set of EMF resources within a unit of work. For example, a workspace operation may affect a change to multiple EMF resources. Edit models provide basic services such as loads, saves (when necessary), and validate edit for the managed resources. Edit models are reference counted, therefore a single instance of an edit model can be shared by more than one operation or editor. By declaring an edit model, a plugin provider enables other components to contribute resources to be managed by that edit model.</p>
<p><h6 class=CaptionFigColumn id=header>Configuration Markup:</h6></p>
<p class=code id=dtd>&lt;!ELEMENT <a name="e.extension">extension</a> (<a href="#e.editModelExtension">editModelExtension</a>+)&gt;</p>
<p class=code id=dtd>&lt;!ATTLIST extension</p>
<p class=code id=dtdAttlist>point&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>id&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class=code id=dtdAttlist>name&nbsp;&nbsp;CDATA #IMPLIED&gt;</p>
<p></p>
<ul class=ConfigMarkup id=attlistDesc>
</ul>
<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.editModelExtension">editModelExtension</a> (<a href="#e.editModelResource">editModelResource</a>+)&gt;</p>
<p class=code id=dtd>&lt;!ATTLIST editModelExtension</p>
<p class=code id=dtdAttlist>editModelID&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED&gt;</p>
<p></p>
<p class=ConfigMarkup id=elementDesc>
Edit model extensions allow components to contribute known resource URIs to an edit model. Whenever an edit model is loaded, the resources will automatically be loaded and managed by the edit model. Changes to the resources will be tracked and saved during operations or editor saves.</p>
<br>
<ul class=ConfigMarkup id=attlistDesc>
<li><b>editModelID</b> - The unique id of the edit model being extended.</li>
<li><b>id</b> - The unique identifier for this extension. This will be used to associate it with a function group pattern binding.</li>
</ul>
<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.extension">extension</a> (<a href="#e.editModel">editModel</a>+)&gt;</p>
<p class=code id=dtd>&lt;!ATTLIST extension</p>
<p class=code id=dtdAttlist>point&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>id&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class=code id=dtdAttlist>name&nbsp;&nbsp;CDATA #IMPLIED&gt;</p>
<p></p>
<ul class=ConfigMarkup id=attlistDesc>
</ul>
<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.editModel">editModel</a> (<a href="#e.editModelResource">editModelResource</a>+)&gt;</p>
<p class=code id=dtd>&lt;!ATTLIST editModel</p>
<p class=code id=dtdAttlist>editModelID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>factoryClass&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>loadUnknownResourcesAsReadOnly&nbsp;(true | false) <p class=code id=dtdAttlist>parentModelID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED&gt;</p>
<p></p>
<p class=ConfigMarkup id=elementDesc>
The declaration for an edit model to be used in the workspace.</p>
<br>
<ul class=ConfigMarkup id=attlistDesc>
<li><b>editModelID</b> - A unique identifier for the edit model.</li>
<li><b>factoryClass</b> - An optional factory class that is used for this edit model. The class must implement the interface <code>com.ibm.etools.emf.workbench.edit.EditModelFactory</code>. If none is specified, then a generic <code>EditModel</code> is created.</li>
<li><b>loadUnknownResourcesAsReadOnly</b> - </li>
<li><b>parentModelID</b> - </li>
</ul>
<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.editModelResource">editModelResource</a> EMPTY&gt;</p>
<p class=code id=dtd>&lt;!ATTLIST editModelResource</p>
<p class=code id=dtdAttlist>URI&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>autoload&nbsp;(true | false) "false"&gt;</p>
<p></p>
<p class=ConfigMarkup id=elementDesc>
This is an individual contribution of a resource to the edit model. If more than one instance of the same URI is registered against an edit model id, the resource is still only loaded once.</p>
<br>
<ul class=ConfigMarkup id=attlistDesc>
<li><b>URI</b> - The URI of the resource relative to the root container from which EMF resources are loaded.</li>
<li><b>autoload</b> - Indicator which determines whether this resource should be autoloaded when the edit model is created, or when an IFile corresponding to this resource is added.</li>
</ul>
<br><h6 class=CaptionFigColumn id=header>Examples: </h6><br>
<code>
&nbsp;&nbsp;&nbsp;&lt;extension<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;point="com.ibm.etools.emf.workbench.editModelExtension"&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;editModelExtension<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;editModelID="com.ibm.etools.inheritance.parent.editModel"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;functionGroupID="com.ibm.etools.websphere.group"&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;editModelResource&nbsp;URI="DIR/extension0.xml"/&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;editModelResource&nbsp;URI="DIR/extension1.xml"/&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/editModelExtension&gt;<br>
&nbsp;&nbsp;&nbsp;&lt;/extension&gt;<br>
</code>
<p></p>
<h6 class=CaptionFigColumn id=header>API Information: </h6>[Enter API information here.]
<p></p>
<h6 class=CaptionFigColumn id=header>Supplied Implementation: </h6>[Enter information about supplied implementation of this extension point.]
<p></p>
<br>
<p class=note id=copyright>
</p>
</BODY>
</HTML>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>ExtendabledOperation</title>
<link rel="stylesheet" type="text/css" href="schema.css">
</HEAD>
<BODY>
<H1><CENTER>ExtendabledOperation</CENTER></H1>
<p></p>
<h6 class=CaptionFigColumn id=header>Identifier: </h6>com.ibm.etools.j2ee.ExtendableOperation<p></p>
<h6 class=CaptionFigColumn id=header>Since: </h6>[Enter the first release in which this extension point appears.]
<p></p>
<p>
<h6 class=CaptionFigColumn id=header>Description: </h6>[Enter description of this extension point.]</p>
<p><h6 class=CaptionFigColumn id=header>Configuration Markup:</h6></p>
<p class=code id=dtd>&lt;!ELEMENT <a name="e.extension">extension</a> (<a href="#e.extendableOperation">extendableOperation</a>)&gt;</p>
<p class=code id=dtd>&lt;!ATTLIST extension</p>
<p class=code id=dtdAttlist>point&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>id&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class=code id=dtdAttlist>name&nbsp;&nbsp;CDATA #IMPLIED&gt;</p>
<p></p>
<ul class=ConfigMarkup id=attlistDesc>
</ul>
<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.extendableOperation">extendableOperation</a> EMPTY&gt;</p>
<p class=code id=dtd>&lt;!ATTLIST extendableOperation</p>
<p class=code id=dtdAttlist>class&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>id&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED&gt;</p>
<p></p>
<ul class=ConfigMarkup id=attlistDesc>
<li><b>class</b> - </li>
<li><b>id</b> - </li>
</ul>
<br><h6 class=CaptionFigColumn id=header>Examples: </h6>[Enter extension point usage example here.]
<p></p>
<h6 class=CaptionFigColumn id=header>API Information: </h6>[Enter API information here.]
<p></p>
<h6 class=CaptionFigColumn id=header>Supplied Implementation: </h6>[Enter information about supplied implementation of this extension point.]
<p></p>
<br>
<p class=note id=copyright>
</p>
</BODY>
</HTML>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>Grouping for function contribution</title>
<link rel="stylesheet" type="text/css" href="schema.css">
</HEAD>
<BODY>
<H1><CENTER>Grouping for function contribution</CENTER></H1>
<p></p>
<h6 class=CaptionFigColumn id=header>Identifier: </h6>com.ibm.etools.emf.workbench.group<p></p>
<h6 class=CaptionFigColumn id=header>Since: </h6>6.0
<p></p>
<p>
<h6 class=CaptionFigColumn id=header>Description: </h6>A functionGroup provides a grouping of related function that can be contributed to the tools. For example, a third party component may want to contribute actions, editor pages, edit model resources, and many other functions specific to a given product. By associating all these functions with a group id, a mechanism is exposed for users to selectively enable and disable baskets of function. Extension points that allow for a "groupID" attribute generally will hide those functions when the group id is disabled.</p>
<p><h6 class=CaptionFigColumn id=header>Configuration Markup:</h6></p>
<p class=code id=dtd>&lt;!ELEMENT <a name="e.extension">extension</a> (<a href="#e.functionGroup">functionGroup</a>+ | <a href="#e.functionGroupPatternBinding">functionGroupPatternBinding</a>+)&gt;</p>
<p class=code id=dtd>&lt;!ATTLIST extension</p>
<p class=code id=dtdAttlist>point&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>id&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class=code id=dtdAttlist>name&nbsp;&nbsp;CDATA #IMPLIED&gt;</p>
<p></p>
<ul class=ConfigMarkup id=attlistDesc>
</ul>
<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.functionGroup">functionGroup</a> EMPTY&gt;</p>
<p class=code id=dtd>&lt;!ATTLIST functionGroup</p>
<p class=code id=dtdAttlist>functionGroupID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>description&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>icon&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class=code id=dtdAttlist>url&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class=code id=dtdAttlist>priority&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>initializerClassName&nbsp;CDATA #REQUIRED&gt;</p>
<p></p>
<p class=ConfigMarkup id=elementDesc>
Extension point definition for a group.</p>
<br>
<ul class=ConfigMarkup id=attlistDesc>
<li><b>functionGroupID</b> - A unique id for the group.</li>
<li><b>name</b> - A human readable name.</li>
<li><b>description</b> - A short description of the group.</li>
<li><b>icon</b> - </li>
<li><b>url</b> - </li>
<li><b>priority</b> - Ordering magnitude of plugins</li>
<li><b>initializerClassName</b> - Class used to determine plugin enablement</li>
</ul>
<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.functionGroupPatternBinding">functionGroupPatternBinding</a> EMPTY&gt;</p>
<p class=code id=dtd>&lt;!ATTLIST functionGroupPatternBinding</p>
<p class=code id=dtdAttlist>functionGroupID&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>pattern&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED&gt;</p>
<p></p>
<p class=ConfigMarkup id=elementDesc>
This element allows one to bind function groups to patterns.</p>
<br>
<ul class=ConfigMarkup id=attlistDesc>
<li><b>functionGroupID</b> - The unique identifier of the function group to bind.</li>
<li><b>pattern</b> - The pattern to be bound. Patterns are regular expressions which match unique identifiers.</li>
</ul>
<br><h6 class=CaptionFigColumn id=header>Examples: </h6><code>
&nbsp;&nbsp;&nbsp;<br>
&nbsp;&nbsp;&nbsp;&lt;extension<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;point="com.ibm.wtp.common.functionGroup"&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;functionGroup<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;name="Acme&nbsp;Co.&nbsp;Function&nbsp;Extension"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;functionGroupID="com.acme.acmepro"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;description="The&nbsp;AcmePro&nbsp;Extensions&nbsp;add&nbsp;integration&nbsp;to&nbsp;the&nbsp;Acme&nbsp;Web&nbsp;Server."<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;enabledByDefault="true"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;icon="..."<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;url="http://www.acme.com/"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;/&gt;<br>
&nbsp;&nbsp;&nbsp;&lt;/extension&gt;<br>
</code>
<p></p>
<h6 class=CaptionFigColumn id=header>API Information: </h6>WTP Function Groups can be referenced through com.ibm.wtp.common.group.WTPFunctionGroupRegistry.
<p></p>
<br>
<p class=note id=copyright>
</p>
</BODY>
</HTML>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>ModifierHelperFactory</title>
<link rel="stylesheet" type="text/css" href="schema.css">
</HEAD>
<BODY>
<H1><CENTER>ModifierHelperFactory</CENTER></H1>
<p></p>
<h6 class=CaptionFigColumn id=header>Identifier: </h6>com.ibm.wtp.emf.workbench.edit.ModifierHelperFactory<p></p>
<h6 class=CaptionFigColumn id=header>Since: </h6>[Enter the first release in which this extension point appears.]
<p></p>
<p>
<h6 class=CaptionFigColumn id=header>Description: </h6>[Enter description of this extension point.]</p>
<p><h6 class=CaptionFigColumn id=header>Configuration Markup:</h6></p>
<p class=code id=dtd>&lt;!ELEMENT <a name="e.extension">extension</a> (<a href="#e.factory">factory</a>+)&gt;</p>
<p class=code id=dtd>&lt;!ATTLIST extension</p>
<p class=code id=dtdAttlist>point&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>id&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class=code id=dtdAttlist>name&nbsp;&nbsp;CDATA #IMPLIED&gt;</p>
<p></p>
<p class=ConfigMarkup id=elementDesc>
This is used to register for the model modifiers.</p>
<br>
<ul class=ConfigMarkup id=attlistDesc>
</ul>
<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.factory">factory</a> (<a href="#e.package">package</a>+)&gt;</p>
<p class=code id=dtd>&lt;!ATTLIST factory</p>
<p class=code id=dtdAttlist>class&nbsp;CDATA #REQUIRED&gt;</p>
<p></p>
<ul class=ConfigMarkup id=attlistDesc>
<li><b>class</b> - </li>
</ul>
<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.package">package</a> (<a href="#e.type">type</a>+)&gt;</p>
<p class=code id=dtd>&lt;!ATTLIST package</p>
<p class=code id=dtdAttlist>uri&nbsp;CDATA #IMPLIED&gt;</p>
<p></p>
<ul class=ConfigMarkup id=attlistDesc>
<li><b>uri</b> - </li>
</ul>
<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.type">type</a> (<a href="#e.feature">feature</a>+)&gt;</p>
<p class=code id=dtd>&lt;!ATTLIST type</p>
<p class=code id=dtdAttlist>name&nbsp;CDATA #REQUIRED&gt;</p>
<p></p>
<ul class=ConfigMarkup id=attlistDesc>
<li><b>name</b> - </li>
</ul>
<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.feature">feature</a> EMPTY&gt;</p>
<p class=code id=dtd>&lt;!ATTLIST feature</p>
<p class=code id=dtdAttlist>name&nbsp;&nbsp;&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>action&nbsp;CDATA #IMPLIED&gt;</p>
<p></p>
<ul class=ConfigMarkup id=attlistDesc>
<li><b>name</b> - </li>
<li><b>action</b> - </li>
</ul>
<br><h6 class=CaptionFigColumn id=header>Examples: </h6>[Enter extension point usage example here.]
<p></p>
<h6 class=CaptionFigColumn id=header>API Information: </h6>[Enter API information here.]
<p></p>
<h6 class=CaptionFigColumn id=header>Supplied Implementation: </h6>[Enter information about supplied implementation of this extension point.]
<p></p>
<br>
<p class=note id=copyright>
</p>
</BODY>
</HTML>
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment