| Best Practices for debugging Extension Points [message #598187] |
Tue, 09 June 2009 21:54 |
 Oliver Wong
Messages: 47
Registered: July 2009 |
Member |
|
|
I was wondering what were some best practices for debugging extension
points. In particular, for seeing how the OSGI or P2 or whatever it is
that is handling the loading and unloading of plugins and their extension
points, are doing.
The reason this comes up is that I was working on a project, and I noticed
all of a sudden, one of the extensions that this project provides to an
extension point no longer seems to be loading. That is, when I use the
following code:
IExtension[] tempExtensions = new IExtension[0];
final IExtensionRegistry registry = Platform.getExtensionRegistry();
final IExtensionPoint extensionPoint =
registry.getExtensionPoint(extensionPointID);
tempExtensions = extensionPoint.getExtensions();
my tempExtensions array contains some of the extensions, but not the ones
for the project I'm working on.
I've not changed the plugin.xml nor manifest.mf files of any of the
projects, and I've made sure that the class providing the service
described in the extension is public, has a public 0-arg constructor, and
is exported. I've also checked the runtime-configuration of my launch
settings to make sure my PluginProject is loaded at runtime, and then in
the runtime environment, I went into help->about and checked that yes, my
plugin was successfully loaded.
I really don't know what to look at next to figure out why this particular
extension can't be found. I've tried googling for terms like "debugging
eclipse extension points" but there doesn't seem to be much material on
the web.
Any help appreciated.
|
|
|
Powered by
FUDForum. Page generated in 0.03161 seconds
] 
Search
Help
Register
Login
Home
