Domino OSGI Update Site Creation

0
votes

This is a continuation of a question I asked a few days ago regarding a designer connection for Domino OSGI dev and testing.

In eclipse, I do have the "debugging plug-in" installed (as mentioned by stwissel), and I am fairy certain that it is configured properly. enter image description here

enter image description here

In a second attempt, I tried to export my plug-in in an update site.
1. import plug-in to feature
2. import feature to update site
3. build update site

I first tried to install using My Widgets in the notes sidebar. I did not get the thing to run with that so, then went into designer and installed it there directly, also nothing.

current stand

  1. I built the update site and deployed using an nsf Update Site as a widget. I use this for openNTF Domino API, the ExtLibs -- it is comfortable and I like it. enter image description here

  2. I can verify that the feature is available in the application Management window of designer.

enter image description here

3 I expect to see those libraries in the xsp.properties page generation tab, but do not. enter image description here

questions
1. Am I missing something?
2. Must I add some sort of class/code/flag in order to choose this library/plug-in in designer?
3. How can I best verify that the plug in and not just the feature is installed?

3
osgixpages

3 Answers

2
votes

if your XspLibrary is not a 'global' one you probably won't see the activator run until the first nsf that uses it activates it.

seeing as you can't select it in an nsf this is probably why no nsf is ever activating it

can I ask have you correctly defined the library as an extension of com.ibm.commons.Extensions as type com.ibm.xsp.Library

if you don't define the extension you will not see it in the list of libraries.

also you must make sure you set the plugin settings to export the XspLibrary class (or package of the class) otherwise designer can't use the class

see this article on the domino designer wiki for an overview of necessary steps to correctly set up the XspLibrary plugin. the manifest.mf / plugin.xml settings are important.

another thing to double check, is to inspect the actual built plugin jar, using something like 7zip. you can open it up like a zip and have a look to make sure the .class files are actually included in the jar. if your build settings are incorrect it may not include them in the jar properly. also make sure the manifest.mf and plugin.xml are in there properly

EDIT from Greg
This should be the link for a non-mobile user

2
votes

When you setup the debug plugin, it should create an entry in the workspace directory of the Notes client and Domino server (I think down in the RCP directory). This entry points back to the Eclipse workspace. So you don't need to deploy the plug-in. You also should see a warning when loading Notes ( with rparams -console) or Domino on the console about the debug.

Also what I found: auto deployment via Widget works when the update site sits on a server via http or nrpc. It doesn't when it is specified as file:/// so I run a Apache http on local (I need it for other stuff too, so no big deal for me).

I'll check the exact settings when I get back to my Dev workstation

1
votes

You can identify if a plugin is installed via Help > About IBM Domino Designer, then clicking on the Plug-in Details button in the dialog.

Help > Support > View Log and View Trace should give more details. Trace is more detailed and allows you to write content, as we do for the OpenNTF Domino API. It may allow you to see how far through the code it's going.

enter image description here

That first message is in the XspLibrary class, in the constructor, just using a sysout

    /**
 * Constructor
 */
public XspLibrary() {
    System.out.println("Loading org.openntf.domino.xsp library");
}

Hopefully that should help you see where it's failing.