extension point docs
diff --git a/update/org.eclipse.update.core/doc/featureTypes.html b/update/org.eclipse.update.core/doc/featureTypes.html
index 71fba51..7f80447 100644
--- a/update/org.eclipse.update.core/doc/featureTypes.html
+++ b/update/org.eclipse.update.core/doc/featureTypes.html
@@ -27,7 +27,7 @@
<br><samp> ></samp>
<ul>
<li><b>point</b> - must be specified as <b>org.eclipse.update.core.featureTypes</b></li><li><b>id</b> - must be specified. Identifies the new feature type</li><li><b>name</b> - optional displayable label for the new feature type</li></ul>
-<p><samp> <!ELEMENT feature-factory (EMPTY)></samp>
+<p><samp> <!ELEMENT feature-factory EMPTY></samp>
<br><samp> <!ATTLIST feature-factory</samp>
<br><samp> class CDATA #REQUIRED</samp>
<br><samp> ></samp>
@@ -51,5 +51,5 @@
<code><b>org.eclipse.update.core.IFeatureFactory</b></code><H2>Supplied Implementation</H2>
The platform supplies two standard implementations of feature
types. One representing the default packaged feature type, and
-the other representing an installed feature type.<br><br><a href="hglegal.htm"><img SRC="ngibmcpy.gif" ALT="Copyright IBM Corp. 2000, 2002. All Rights Reserved." BORDER=0 height=12 width=195></a></BODY>
+the other representing an installed feature type.<br><br><a href="hglegal.htm"><img SRC="ngibmcpy.gif" ALT="Copyright IBM Corp. and others 2000, 2002. All Rights Reserved." BORDER=0></a></BODY>
</HTML>
diff --git a/update/org.eclipse.update.core/doc/hglegal.htm b/update/org.eclipse.update.core/doc/hglegal.htm
index cf2ced3..919e18b 100644
--- a/update/org.eclipse.update.core/doc/hglegal.htm
+++ b/update/org.eclipse.update.core/doc/hglegal.htm
@@ -2,13 +2,13 @@
<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]">
+ <meta name="GENERATOR" content="Microsoft FrontPage 4.0">
<title>Legal Notices</title>
</head>
<body>
<h3>
<a NAME="Notices"></a>Notices</h3>
-(c) Copyright IBM Corp. 2000, 2002. All Rights Reserved.
+(c) Copyright IBM Corp. and others 2000, 2002. All Rights Reserved.
</body>
</html>
diff --git a/update/org.eclipse.update.core/doc/installHandlers.html b/update/org.eclipse.update.core/doc/installHandlers.html
index ee90591..dfa4095 100644
--- a/update/org.eclipse.update.core/doc/installHandlers.html
+++ b/update/org.eclipse.update.core/doc/installHandlers.html
@@ -7,7 +7,11 @@
<H1><CENTER>Global Install Handlers</CENTER></H1>
<H2>Identifier</H2>
org.eclipse.update.core.installHandlers<H2>Description</H2>
-Extension point for registering global install handlers.<H2>Markup</H2>
+Extension point for registering global install handlers. Global
+install handlers can be referenced by features
+(using the <code><feature> <install-handler></code>
+tags) without having to include a copy of the handler code as
+part of the downloadable feature.<H2>Markup</H2>
<p><samp> <!ELEMENT extension (install-handler+)></samp>
<br><samp> <!ATTLIST extension</samp>
<br><samp> point CDATA #REQUIRED</samp>
@@ -15,15 +19,31 @@
<br><samp> name CDATA #IMPLIED</samp>
<br><samp> ></samp>
<ul>
-<li><b>point</b> - </li><li><b>id</b> - </li><li><b>name</b> - </li></ul>
-<p><samp> <!ELEMENT install-handler (EMPTY)></samp>
+<li><b>point</b> - must be specified as <b>org.eclipse.update.core.installHandlers</b></li><li><b>id</b> - must be specified. Identifies the new install handler</li><li><b>name</b> - optional displayable label for the new install handler</li></ul>
+<p><samp> <!ELEMENT install-handler EMPTY></samp>
<br><samp> <!ATTLIST install-handler</samp>
<br><samp> class CDATA #REQUIRED</samp>
<br><samp> ></samp>
<ul>
-<li><b>class</b> - </li></ul>
+<li><b>class</b> - fully qualified name of the handler implementation class for the identified
+install handler</li></ul>
<H2>Example</H2>
-[Enter extension point usage example here.]<H2>API Information</H2>
-[Enter API information here.]<H2>Supplied Implementation</H2>
-[Enter information about supplied implementation of this extension point.]</BODY>
+The following is an example of new global install handler registration.
+<br><br>
+<code>
+<extension<br>
+ id="custom"<br>
+ point="org.eclipse.update.core.installHandlers"<br>
+ name="Custom install handler"><br>
+<br>
+ <install-handler<br>
+ class="com.xyz.update.CustomInstallHandler"><br>
+ </install-handler><br>
+</extension><br>
+</code><H2>API Information</H2>
+Registered install handler classes must implement
+<code><b>org.eclipse.update.core.IInstallHandler</b></code> interface.
+Implementers should extend base class <code><b>org.eclipse.update.core.BaseInstallHandler</b></code>.<H2>Supplied Implementation</H2>
+The platform supplies a simple install handler that is registered as <code><b>org.eclipse.update.core.DefaultInstallHandler</b></code>. If used, it will copy any non-plug-in data entries provided with the feature into the feature installation directory.<br><br><a href="hglegal.htm"><img SRC="ngibmcpy.gif" ALT="Copyright
+IBM Corp. and others 2000, 2002. All Rights Reserved." BORDER=0></a></BODY>
</HTML>
diff --git a/update/org.eclipse.update.core/doc/ngibmcpy.gif b/update/org.eclipse.update.core/doc/ngibmcpy.gif
index 360f8e9..3fda87a 100644
--- a/update/org.eclipse.update.core/doc/ngibmcpy.gif
+++ b/update/org.eclipse.update.core/doc/ngibmcpy.gif
Binary files differ
diff --git a/update/org.eclipse.update.core/doc/org_eclipse_update_core_featureTypes.html b/update/org.eclipse.update.core/doc/org_eclipse_update_core_featureTypes.html
new file mode 100644
index 0000000..7f80447
--- /dev/null
+++ b/update/org.eclipse.update.core/doc/org_eclipse_update_core_featureTypes.html
@@ -0,0 +1,55 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HEAD>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+</HEAD>
+<HTML>
+<BODY>
+<H1><CENTER>Feature Type Factory</CENTER></H1>
+<H2>Identifier</H2>
+org.eclipse.update.core.featureTypes<H2>Description</H2>
+<p>The platform update mechanism supports pluggable feature type
+implementations. A new feature type can be registered in order
+to support
+alternate packaging and verification schemes.
+</p>
+<p>
+The <code>featureTypes</code>
+extension point allows alternate feature implementations to be
+registered using a symbolic type identifier. Whenever the
+type is referenced using this identifier, the supplied factory
+is used to create the correct concrete feature implementation.
+</p><H2>Markup</H2>
+<p><samp> <!ELEMENT extension (feature-factory+)></samp>
+<br><samp> <!ATTLIST extension</samp>
+<br><samp> point CDATA #REQUIRED</samp>
+<br><samp> id CDATA #IMPLIED</samp>
+<br><samp> name CDATA #IMPLIED</samp>
+<br><samp> ></samp>
+<ul>
+<li><b>point</b> - must be specified as <b>org.eclipse.update.core.featureTypes</b></li><li><b>id</b> - must be specified. Identifies the new feature type</li><li><b>name</b> - optional displayable label for the new feature type</li></ul>
+<p><samp> <!ELEMENT feature-factory EMPTY></samp>
+<br><samp> <!ATTLIST feature-factory</samp>
+<br><samp> class CDATA #REQUIRED</samp>
+<br><samp> ></samp>
+<ul>
+<li><b>class</b> - fully qualified name of the factory class for the identified feature type</li></ul>
+<H2>Example</H2>
+The following is an example of new feature type registration.
+<br><br>
+<code>
+<extension<br>
+ id="custom"<br>
+ point="org.eclipse.update.core.featureTypes"<br>
+ name="Custom packaged feature"><br>
+<br>
+ <feature-factory<br>
+ class="com.xyz.update.CustomFeatureFactory"><br>
+ </feature-factory><br>
+</extension><br>
+</code><H2>API Information</H2>
+Registered factory classes must implement
+<code><b>org.eclipse.update.core.IFeatureFactory</b></code><H2>Supplied Implementation</H2>
+The platform supplies two standard implementations of feature
+types. One representing the default packaged feature type, and
+the other representing an installed feature type.<br><br><a href="hglegal.htm"><img SRC="ngibmcpy.gif" ALT="Copyright IBM Corp. and others 2000, 2002. All Rights Reserved." BORDER=0></a></BODY>
+</HTML>
diff --git a/update/org.eclipse.update.core/doc/org_eclipse_update_core_installHandlers.html b/update/org.eclipse.update.core/doc/org_eclipse_update_core_installHandlers.html
new file mode 100644
index 0000000..dfa4095
--- /dev/null
+++ b/update/org.eclipse.update.core/doc/org_eclipse_update_core_installHandlers.html
@@ -0,0 +1,49 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HEAD>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+</HEAD>
+<HTML>
+<BODY>
+<H1><CENTER>Global Install Handlers</CENTER></H1>
+<H2>Identifier</H2>
+org.eclipse.update.core.installHandlers<H2>Description</H2>
+Extension point for registering global install handlers. Global
+install handlers can be referenced by features
+(using the <code><feature> <install-handler></code>
+tags) without having to include a copy of the handler code as
+part of the downloadable feature.<H2>Markup</H2>
+<p><samp> <!ELEMENT extension (install-handler+)></samp>
+<br><samp> <!ATTLIST extension</samp>
+<br><samp> point CDATA #REQUIRED</samp>
+<br><samp> id CDATA #IMPLIED</samp>
+<br><samp> name CDATA #IMPLIED</samp>
+<br><samp> ></samp>
+<ul>
+<li><b>point</b> - must be specified as <b>org.eclipse.update.core.installHandlers</b></li><li><b>id</b> - must be specified. Identifies the new install handler</li><li><b>name</b> - optional displayable label for the new install handler</li></ul>
+<p><samp> <!ELEMENT install-handler EMPTY></samp>
+<br><samp> <!ATTLIST install-handler</samp>
+<br><samp> class CDATA #REQUIRED</samp>
+<br><samp> ></samp>
+<ul>
+<li><b>class</b> - fully qualified name of the handler implementation class for the identified
+install handler</li></ul>
+<H2>Example</H2>
+The following is an example of new global install handler registration.
+<br><br>
+<code>
+<extension<br>
+ id="custom"<br>
+ point="org.eclipse.update.core.installHandlers"<br>
+ name="Custom install handler"><br>
+<br>
+ <install-handler<br>
+ class="com.xyz.update.CustomInstallHandler"><br>
+ </install-handler><br>
+</extension><br>
+</code><H2>API Information</H2>
+Registered install handler classes must implement
+<code><b>org.eclipse.update.core.IInstallHandler</b></code> interface.
+Implementers should extend base class <code><b>org.eclipse.update.core.BaseInstallHandler</b></code>.<H2>Supplied Implementation</H2>
+The platform supplies a simple install handler that is registered as <code><b>org.eclipse.update.core.DefaultInstallHandler</b></code>. If used, it will copy any non-plug-in data entries provided with the feature into the feature installation directory.<br><br><a href="hglegal.htm"><img SRC="ngibmcpy.gif" ALT="Copyright
+IBM Corp. and others 2000, 2002. All Rights Reserved." BORDER=0></a></BODY>
+</HTML>
diff --git a/update/org.eclipse.update.core/doc/org_eclipse_update_core_siteTypes.html b/update/org.eclipse.update.core/doc/org_eclipse_update_core_siteTypes.html
new file mode 100644
index 0000000..4363e69
--- /dev/null
+++ b/update/org.eclipse.update.core/doc/org_eclipse_update_core_siteTypes.html
@@ -0,0 +1,59 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HEAD>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+</HEAD>
+<HTML>
+<BODY>
+<H1><CENTER>Site Type Factory</CENTER></H1>
+<H2>Identifier</H2>
+org.eclipse.update.core.siteTypes<H2>Description</H2>
+<p>
+The platform update mechanism supports pluggable site type
+implementations. A new site type can be registered in order
+to support
+alternate site layout schemes.
+</p>
+
+<p>
+The <code>siteTypes</code>
+extension point allows alternate site implementations to be
+registered using a symbolic type identifier. Whenever the
+type is referenced using this identifier, the supplied factory
+is used to create the correct concrete site implementation.
+</p><H2>Markup</H2>
+<p><samp> <!ELEMENT extension (site-factory+)></samp>
+<br><samp> <!ATTLIST extension</samp>
+<br><samp> point CDATA #REQUIRED</samp>
+<br><samp> id CDATA #IMPLIED</samp>
+<br><samp> name CDATA #IMPLIED</samp>
+<br><samp> ></samp>
+<ul>
+<li><b>point</b> - must be specified as <b>org.eclipse.update.core.siteTypes</b></li><li><b>id</b> - must be specified. Identifies the new site type</li><li><b>name</b> - optional displayable label for the new site type</li></ul>
+<p><samp> <!ELEMENT site-factory EMPTY></samp>
+<br><samp> <!ATTLIST site-factory</samp>
+<br><samp> class CDATA #REQUIRED</samp>
+<br><samp> ></samp>
+<ul>
+<li><b>class</b> - fully qualified name of the factory class for the identified
+site type</li></ul>
+<H2>Example</H2>
+The following is an example of new site type registration.
+<br><br>
+<code>
+<extension<br>
+ id="custom"<br>
+ point="org.eclipse.update.core.siteTypes"<br>
+ name="Custom site"><br>
+<br>
+ <site-factory<br>
+ class="com.xyz.update.CustomSiteFactory"><br>
+ </site-factory><br>
+</extension><br>
+</code><H2>API Information</H2>
+Registered factory classes must implement
+<code><b>org.eclipse.update.core.ISiteFactory</b></code><H2>Supplied Implementation</H2>
+The platform supplies two standard implementations of site
+types. One representing the default update server type, and
+the other representing the local file system site.<br><br><a href="hglegal.htm"><img SRC="ngibmcpy.gif" ALT="Copyright
+IBM Corp. and others 2000, 2002. All Rights Reserved." BORDER=0></a></BODY>
+</HTML>
diff --git a/update/org.eclipse.update.core/doc/siteTypes.html b/update/org.eclipse.update.core/doc/siteTypes.html
index 511aa00..4363e69 100644
--- a/update/org.eclipse.update.core/doc/siteTypes.html
+++ b/update/org.eclipse.update.core/doc/siteTypes.html
@@ -4,10 +4,23 @@
</HEAD>
<HTML>
<BODY>
-<H1><CENTER>Install/Update Concrete Site Type Implementation Factory</CENTER></H1>
+<H1><CENTER>Site Type Factory</CENTER></H1>
<H2>Identifier</H2>
-org.eclipse.update.core.org.eclipse.update.core.siteTypes<H2>Description</H2>
-[Enter description of this extension point]<H2>Markup</H2>
+org.eclipse.update.core.siteTypes<H2>Description</H2>
+<p>
+The platform update mechanism supports pluggable site type
+implementations. A new site type can be registered in order
+to support
+alternate site layout schemes.
+</p>
+
+<p>
+The <code>siteTypes</code>
+extension point allows alternate site implementations to be
+registered using a symbolic type identifier. Whenever the
+type is referenced using this identifier, the supplied factory
+is used to create the correct concrete site implementation.
+</p><H2>Markup</H2>
<p><samp> <!ELEMENT extension (site-factory+)></samp>
<br><samp> <!ATTLIST extension</samp>
<br><samp> point CDATA #REQUIRED</samp>
@@ -15,8 +28,8 @@
<br><samp> name CDATA #IMPLIED</samp>
<br><samp> ></samp>
<ul>
-<li><b>point</b> - </li><li><b>id</b> - </li><li><b>name</b> - </li></ul>
-<p><samp> <!ELEMENT site-factory (EMPTY)></samp>
+<li><b>point</b> - must be specified as <b>org.eclipse.update.core.siteTypes</b></li><li><b>id</b> - must be specified. Identifies the new site type</li><li><b>name</b> - optional displayable label for the new site type</li></ul>
+<p><samp> <!ELEMENT site-factory EMPTY></samp>
<br><samp> <!ATTLIST site-factory</samp>
<br><samp> class CDATA #REQUIRED</samp>
<br><samp> ></samp>
@@ -24,7 +37,23 @@
<li><b>class</b> - fully qualified name of the factory class for the identified
site type</li></ul>
<H2>Example</H2>
-[Enter extension point usage example here.]<H2>API Information</H2>
-[Enter API information here.]<H2>Supplied Implementation</H2>
-[Enter information about supplied implementation of this extension point.]</BODY>
+The following is an example of new site type registration.
+<br><br>
+<code>
+<extension<br>
+ id="custom"<br>
+ point="org.eclipse.update.core.siteTypes"<br>
+ name="Custom site"><br>
+<br>
+ <site-factory<br>
+ class="com.xyz.update.CustomSiteFactory"><br>
+ </site-factory><br>
+</extension><br>
+</code><H2>API Information</H2>
+Registered factory classes must implement
+<code><b>org.eclipse.update.core.ISiteFactory</b></code><H2>Supplied Implementation</H2>
+The platform supplies two standard implementations of site
+types. One representing the default update server type, and
+the other representing the local file system site.<br><br><a href="hglegal.htm"><img SRC="ngibmcpy.gif" ALT="Copyright
+IBM Corp. and others 2000, 2002. All Rights Reserved." BORDER=0></a></BODY>
</HTML>
diff --git a/update/org.eclipse.update.core/schema/featureTypes.exsd b/update/org.eclipse.update.core/schema/featureTypes.exsd
index 8041986..c5de0af 100644
--- a/update/org.eclipse.update.core/schema/featureTypes.exsd
+++ b/update/org.eclipse.update.core/schema/featureTypes.exsd
@@ -112,7 +112,7 @@
<meta.section type="copyright"/>
</appInfo>
<documentation>
- <br><br><a href="hglegal.htm"><img SRC="ngibmcpy.gif" ALT="Copyright IBM Corp. 2000, 2002. All Rights Reserved." BORDER=0 height=12 width=195></a>
+ <br><br><a href="hglegal.htm"><img SRC="ngibmcpy.gif" ALT="Copyright IBM Corp. and others 2000, 2002. All Rights Reserved." BORDER=0></a>
</documentation>
</annotation>
diff --git a/update/org.eclipse.update.core/schema/installHandlers.exsd b/update/org.eclipse.update.core/schema/installHandlers.exsd
index 3a5040f..74ef8a3 100644
--- a/update/org.eclipse.update.core/schema/installHandlers.exsd
+++ b/update/org.eclipse.update.core/schema/installHandlers.exsd
@@ -6,7 +6,11 @@
<meta.schema plugin="org.eclipse.update.core" id="installHandlers" name="Global Install Handlers"/>
</appInfo>
<documentation>
- Extension point for registering global install handlers.
+ Extension point for registering global install handlers. Global
+install handlers can be referenced by features
+(using the <code>&ltfeature&gt; &lt;install-handler&gt;</code>
+tags) without having to include a copy of the handler code as
+part of the downloadable feature.
</documentation>
</annotation>
@@ -18,21 +22,21 @@
<attribute name="point" type="string" use="required">
<annotation>
<documentation>
-
+ must be specified as <b>org.eclipse.update.core.installHandlers</b>
</documentation>
</annotation>
</attribute>
<attribute name="id" type="string">
<annotation>
<documentation>
-
+ must be specified. Identifies the new install handler
</documentation>
</annotation>
</attribute>
<attribute name="name" type="string">
<annotation>
<documentation>
-
+ optional displayable label for the new install handler
</documentation>
</annotation>
</attribute>
@@ -44,7 +48,8 @@
<attribute name="class" type="string" use="required">
<annotation>
<documentation>
-
+ fully qualified name of the handler implementation class for the identified
+install handler
</documentation>
</annotation>
</attribute>
@@ -56,7 +61,19 @@
<meta.section type="examples"/>
</appInfo>
<documentation>
- [Enter extension point usage example here.]
+ The following is an example of new global install handler registration.
+<br><br>
+<code>
+&lt;extension<br>
+&nbsp;&nbsp;&nbsp;id="custom"<br>
+&nbsp;&nbsp;&nbsp;point="org.eclipse.update.core.installHandlers"<br>
+&nbsp;&nbsp;&nbsp;name="Custom install handler"&gt;<br>
+<br>
+&nbsp;&nbsp;&nbsp;&lt;install-handler<br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;class="com.xyz.update.CustomInstallHandler"&gt;<br>
+&nbsp;&nbsp;&nbsp;&lt;/install-handler&gt;<br>
+&lt;/extension&gt;<br>
+</code>
</documentation>
</annotation>
@@ -65,7 +82,9 @@
<meta.section type="apiInfo"/>
</appInfo>
<documentation>
- [Enter API information here.]
+ Registered install handler classes must implement
+<code><b>org.eclipse.update.core.IInstallHandler</b></code> interface.
+Implementers should extend base class <code><b>org.eclipse.update.core.BaseInstallHandler</b></code>.
</documentation>
</annotation>
@@ -74,7 +93,7 @@
<meta.section type="implementation"/>
</appInfo>
<documentation>
- [Enter information about supplied implementation of this extension point.]
+ The platform supplies a simple install handler that is registered as <code><b>org.eclipse.update.core.DefaultInstallHandler</b></code>. If used, it will copy any non-plug-in data entries provided with the feature into the feature installation directory.
</documentation>
</annotation>
@@ -83,7 +102,8 @@
<meta.section type="copyright"/>
</appInfo>
<documentation>
-
+ <br><br><a href="hglegal.htm"><img SRC="ngibmcpy.gif" ALT="Copyright
+IBM Corp. and others 2000, 2002. All Rights Reserved." BORDER=0></a>
</documentation>
</annotation>
diff --git a/update/org.eclipse.update.core/schema/siteTypes.exsd b/update/org.eclipse.update.core/schema/siteTypes.exsd
index c255845..835613d 100644
--- a/update/org.eclipse.update.core/schema/siteTypes.exsd
+++ b/update/org.eclipse.update.core/schema/siteTypes.exsd
@@ -1,12 +1,25 @@
<?xml version='1.0' encoding='UTF-8'?>
<!-- Schema file written by PDE -->
-<schema targetNamespace="org.eclipse.update.core.org.eclipse.update.core">
+<schema targetNamespace="org.eclipse.update.core">
<annotation>
<appInfo>
- <meta.schema plugin="org.eclipse.update.core.org.eclipse.update.core" id="siteTypes" name="Install/Update Concrete Site Type Implementation Factory"/>
+ <meta.schema plugin="org.eclipse.update.core" id="siteTypes" name="Site Type Factory"/>
</appInfo>
<documentation>
- [Enter description of this extension point]
+ <p>
+The platform update mechanism supports pluggable site type
+implementations. A new site type can be registered in order
+to support
+alternate site layout schemes.
+</p>
+
+<p>
+The <code>siteTypes</code>
+extension point allows alternate site implementations to be
+registered using a symbolic type identifier. Whenever the
+type is referenced using this identifier, the supplied factory
+is used to create the correct concrete site implementation.
+</p>
</documentation>
</annotation>
@@ -18,21 +31,21 @@
<attribute name="point" type="string" use="required">
<annotation>
<documentation>
-
+ must be specified as <b>org.eclipse.update.core.siteTypes</b>
</documentation>
</annotation>
</attribute>
<attribute name="id" type="string">
<annotation>
<documentation>
-
+ must be specified. Identifies the new site type
</documentation>
</annotation>
</attribute>
<attribute name="name" type="string">
<annotation>
<documentation>
-
+ optional displayable label for the new site type
</documentation>
</annotation>
</attribute>
@@ -44,7 +57,7 @@
<attribute name="class" type="string" use="required">
<annotation>
<documentation>
- fully qualified name of the factory class for the identified
+ fully qualified name of the factory class for the identified
site type
</documentation>
</annotation>
@@ -57,7 +70,19 @@
<meta.section type="examples"/>
</appInfo>
<documentation>
- [Enter extension point usage example here.]
+ The following is an example of new site type registration.
+<br><br>
+<code>
+&lt;extension<br>
+&nbsp;&nbsp;&nbsp;id="custom"<br>
+&nbsp;&nbsp;&nbsp;point="org.eclipse.update.core.siteTypes"<br>
+&nbsp;&nbsp;&nbsp;name="Custom site"&gt;<br>
+<br>
+&nbsp;&nbsp;&nbsp;&lt;site-factory<br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;class="com.xyz.update.CustomSiteFactory"&gt;<br>
+&nbsp;&nbsp;&nbsp;&lt;/site-factory&gt;<br>
+&lt;/extension&gt;<br>
+</code>
</documentation>
</annotation>
@@ -66,7 +91,8 @@
<meta.section type="apiInfo"/>
</appInfo>
<documentation>
- [Enter API information here.]
+ Registered factory classes must implement
+<code><b>org.eclipse.update.core.ISiteFactory</b></code>
</documentation>
</annotation>
@@ -75,7 +101,9 @@
<meta.section type="implementation"/>
</appInfo>
<documentation>
- [Enter information about supplied implementation of this extension point.]
+ The platform supplies two standard implementations of site
+types. One representing the default update server type, and
+the other representing the local file system site.
</documentation>
</annotation>
@@ -84,7 +112,8 @@
<meta.section type="copyright"/>
</appInfo>
<documentation>
-
+ <br><br><a href="hglegal.htm"><img SRC="ngibmcpy.gif" ALT="Copyright
+IBM Corp. and others 2000, 2002. All Rights Reserved." BORDER=0></a>
</documentation>
</annotation>
