| How does extension registration occur? [message #323280] |
Mon, 17 December 2007 18:25  |
Eclipse User |
|
|
|
Originally posted by: tizzo.computer.org
I've run across a problem that seems odd to me. I'm developing an
application that is to be deployed in two flavors. For the sake of
argument let's say that one of these flavors is analogous to an open
source deployment, and the other flavor is a proprietary deployment. The
plug-ins of the open source deployment declare extension points through
which the optional proprietary functionality is to be contributed.
The idea was supposed to be that I could deploy my open source version
anywhere, and that if someone is qualified to receive the proprietary
deployment, they should be able to get it by just copying the appropriate
plug-ins into the existing open source installation location.
The problem I'm getting is that when I do this, some of the extensions in
my proprietary plug-ins are available to the application, and some are
not. I checked this by added trace code that gets the extension registry
and iterates over all the namespaces and extensions printing them out to
the log file.
What I'm seeing is that when I run the full product from inside Eclipse,
all my extensions are picked up and everything runs great. When I deploy
to an RCP application, some of my extensions are picked up and some are
not. What is odd is that not only are the extensions from some plug-ins
present in the registry and those from others not available, but some
extensions from a single plug-in are visible while others are not. IE I
have one plug-in that contributes three extensions to two different
extension points, and when I run my app from inside Eclipse by launching
my product configuration, all is well. But if I export and run as a
standalone app, one of this plug-in's extensions is in the registry and
the rest are not.
Can anyone offers some insight into how the extension registry works, in
particular how it is populated and what elements of an application control
it? At this point I don't know whether to look at my product
configuration, my plugin.xml files, my config.ini file, or somewhere else.
Thanks.
Tony
|
|
|
| Re: How does extension registration occur? [message #323295 is a reply to message #323280] |
Tue, 18 December 2007 02:49  |
| Eclipse User |
|
|
|
Is it possible that you forgot to export the plugin.xml in your
build.properties of some of your plugins?
Tom
Tony schrieb:
> I've run across a problem that seems odd to me. I'm developing an
> application that is to be deployed in two flavors. For the sake of
> argument let's say that one of these flavors is analogous to an open
> source deployment, and the other flavor is a proprietary deployment.
> The plug-ins of the open source deployment declare extension points
> through which the optional proprietary functionality is to be contributed.
>
> The idea was supposed to be that I could deploy my open source version
> anywhere, and that if someone is qualified to receive the proprietary
> deployment, they should be able to get it by just copying the
> appropriate plug-ins into the existing open source installation location.
>
> The problem I'm getting is that when I do this, some of the extensions
> in my proprietary plug-ins are available to the application, and some
> are not. I checked this by added trace code that gets the extension
> registry and iterates over all the namespaces and extensions printing
> them out to the log file.
>
> What I'm seeing is that when I run the full product from inside Eclipse,
> all my extensions are picked up and everything runs great. When I
> deploy to an RCP application, some of my extensions are picked up and
> some are not. What is odd is that not only are the extensions from some
> plug-ins present in the registry and those from others not available,
> but some extensions from a single plug-in are visible while others are
> not. IE I have one plug-in that contributes three extensions to two
> different extension points, and when I run my app from inside Eclipse by
> launching my product configuration, all is well. But if I export and
> run as a standalone app, one of this plug-in's extensions is in the
> registry and the rest are not.
>
> Can anyone offers some insight into how the extension registry works, in
> particular how it is populated and what elements of an application
> control it? At this point I don't know whether to look at my product
> configuration, my plugin.xml files, my config.ini file, or somewhere
> else. Thanks.
>
> Tony
>
>
--
B e s t S o l u t i o n . at
------------------------------------------------------------ --------
Tom Schindl JFace-Committer
------------------------------------------------------------ --------
|
|
|
Powered by
FUDForum. Page generated in 0.02912 seconds
Home