Table of Contents
This article contains the following sections:
- Using static links with Eclipse components
- Using dynamic links with Eclipse components
You can refer to Eclipse components in various ways. As part of the Eclipse component development process, developers typically refer to the Eclipse components via view extension names. You can launch Notes directly from the Eclipse/Expeditor IDE with your Eclipse components and then refer to the Eclipse components via the Composite Application Editor component provider "Locally installed components." Refer to the Composite Application Editor and Lotus Expeditor online help for more information.
Using static links with Eclipse components
Eclipse components can also be referred to using static links. Refer to the following for more information: http://www-10.lotus.com/ldd/compappwiki.nsf/dx/advanced-component-properties
The following provides an example. The URL property contains the server name when using static paths.
com.ibm.rcp.viewId - com.ibm.cademo.util.comp.constants.ConstantsView
id.feature - com.ibm.complib2.comp.basic.feature
version.feature - 8.1.20080530
match.feature - compatible
url.feature - http://w3.myserver.com:8080/ajax.nsf/site.xml
Notes can also access Eclipse features from different update sites such as:
- Classic Eclipse update sites via HTTP
- NSF based update site (updatesite.ntf) via NRPC
- NSF based update site (updatesite.ntf) via HTTP
There are advantages to putting Eclipse components in NSFs. One would be better manageability. Refer to the "Managing client plug-in deployment" section of the Domino Administrator help for more information.
You can access NSF based update sites either via NRPC or HTTP. HTTP, for example, is used when standalone Sametime accesses Eclipse components from Domino.
For Notes, it is recommended that you use NRPC, however, because it is more efficient. The following provides information on the correct NRPC syntax:
Domino server name: jdoe-1/JDoe
Domino ip address: 127.0.0.1
Domino DNS address: jdoe-1.us.ibm.com
Syntax for sample NSF based update site on a server:
rep id: 852574AA00371F34
Syntax for local sample NSF based update site:
rep id: 852574AA00371F34
Static links to Eclipse components create the same problems that static links to NSF components do. They may also break when applications are moved from a development environment to a production environment.
Using dynamic links with Eclipse components
To help avoid link breakage, it is recommended that you use dynamic links. Dynamic links for Eclipse components are created by leaving the "url.feature" component property empty. That way, Eclipse components can be "pushed" to Notes clients or "pulled" from the Notes client.
Eclipse components can be "pushed" to Notes clients via the Widget catalog. For more information, refer to the "Deploying client plug-ins with widgets and the widget catalog" section of the Domino Administrator help.
Eclipse components can be "pulled" from Notes when that is required. In this case, the "url.feature" component property should also not be set. You should use the Notes Administrator whitelist feature to accomplish this. Using the whitelist feature, the client will try to contact any update site the Notes client knows about in a certain order and try to locate the necessary Eclipse component. For more information, refer to the "Controlling feature install and update with update site" section of the Domino Administrator help.
Table of Contents | Next | Previous