On plug-ins, features, update sites and extension.xml files...
I'm receiving quite a few e-mails asking questions about features, plug-ins, update sites and extension.xml files and how they relate so I thought I would try and clarify things.
| Term | Description |
| Plug-in | The smallest unit of code you use to create functionality for an Eclipse based client. This is where the actual Java code is. |
| Feature | Used to package and bundle plug-ins together. Features are thin wrappers for plug-ins and is basically a single file called feature.xml. You can bundle multiple plug-ins into a single feature. When installing code into Notes you actually install the features which in turn point to the plug-ins to copy to the client. You can only manage features through the Notes "code UI" (File/Application/Application Management) though you can install code into the platform by simply copying the plug-ins into the appropriate directories in the file system. This is not recommended... :-) |
| Update site |
Update sites are used to deploy features to clients. An update site is simply a directory containing a
Update Sites may be remote or local. A local update site is a directory on a local hard drive or LAN drive with the above structure or a zip-file with the above structure. An update site may also be remote and may be read using HTTP (any server will do) or it may be read using NRPC if you're using a Notes 8+ client. When using NRPC you use the Update Site Notes database template. |
| extension.xml |
These files are used when installing code using the MyWidgets sidebar plug-in and is a shorthand for manually installing code. There is no magic at work here. When you drop an extension.xml file onto the sidebar panel the following steps are performed:
|