To my observation, starting a bundle by its bundle id from a profile document only works if the jar is located in ${dominobin}/javaddin/rcp/eclipse/plugins.
If you place the jar in ${dominobin}/javaddin/shared/eclipse/plugins, a relative path like ../../../shared/eclipse/plugins/<bundle id> is required. The same applies to file based sites.
This is no problem because you do not have to specify the bundle's file name and therfore the path will not change when updating the bundle.
The problem with the osginsf paths ist that I do not know how to relatively address a bundle in a Notes update site database (is there a way?) and thus have to use the absolute path as reported by the diag command.
I would be perfectly happy with a relative path syntax like with the file sites (not including UNIDs, of course).
Thank you for the exellent support.
Harald