I wrote the other day
about how to move composite apps with NSF components from one environment to another one without breaking the links to the NSF components. The same problem actually exists also for Eclipse components inside of composite applications.
In Notes 8.0 you have to refer to a specific update site via an URL. This information is stored in the preferences of the component (in the CA XML). When you add an Eclipse component to the CAE palette via 'update site provider' the CAE sets this information automatically for you. When another user then opens the app the first time the Eclipse component is provisioned from the exact URL as defined in the component preferences in the CA XML. In order to deploy a composite application to another environment the composite application has to manually be changed after the deployment. In order to do this the application can be opened, then CAE can be launched and the URLs can be manually changed in the advanced component properties.
In Notes 8.0.1 I'd like to extend this. I don't want to define URLs in the CA XML but basically leave the update site server information empty in the CA XML and then leverage a feature that Expeditor supports in 6.1.1 (to my knowledge) but not in Lotus Notes 8.0 yet. This new feature allows defining lists of update sites that are defined on the client. The client then uses the ordered list of update sites to locate the appropriate Eclipse features/plugins. This allows defining composite applications that can be deployed to other environments without having to change the application definition. The application will just work since clients/users in another environments will have other update site lists.
For Notes 8.0.1 the idea is that Lotus Notes actually leverages these lists. Additionally these lists can be define via Domino Admin policy and pushed to the clients. Here are some more details. Essentially there could be three settings:
1. updateSiteList - list of update site URLs
2. whiteList - boolean whether to use the list as white list (this is a security feature to restrict access to certain update sites only)
3. useFeatureURL - boolean to define whether the URLs in the CA XML, feature.xml or install manifest are supposed to be used or not
With these extensions you would be able to deploy composite applications to different environments without changing the links to the Eclipse components. This should be especially important for ISVs who want to sell their applications to different customers.[Read More