| customized plugin converter [message #40639] |
Sat, 24 April 2004 17:52 |
 Martin Lippert
Messages: 124
Registered: July 2009 |
Senior Member |
|
|
Hi,
I have a question regarding the plugin conversation that is done in 3.0.
This is my setting:
I wrote a plugin that defines an extension point. Extensions for this
extension point define a class. The package for this class needs to be
exported via an Export-Package definition inside the manifest of the
plugin that defines the extension (this is needed by the way the
extension is used).
This is what I would love to implement somehow:
To ease development for this extension point I would like to be able to
let people write extensions by purely define the extension in the
plugin.xml (without writing OSGi manifest files). Some part of my code
(from the plugin that defines the extension point) should take care that
all extensions to this point automatically export the package via the
OSGi bundle Export-Package mechanism.
I have two different ideas how this might be realizable:
1. The plugin that defines the extension point takes care of that by
adding the export-package information to the bundle-loader if an
extension is found. Then I would need an API to do this.
2. The plugin that defines the extension point adds functionality to the
plugin converter that does the job. In this case I would need to be able
to specialize the plugin converter.
What do you think?
Thanks fot the help!
-Martin
|
|
|
Powered by
FUDForum. Page generated in 0.02454 seconds
] 
Search
Help
Register
Login
Home
