| RC1: Fragment have no access to other plugins ??? [message #249911] |
Sat, 05 June 2004 17:45 |
Eclipse User |
|
|
|
I recently started migrating some plugins to the new 3.0 framework, and i found
many problems linked to the plugin/fragment relationship.
I have tracked down the main problem I have to its most simplest expression
which is:
* Given a plugin A, one of its fragments FA which uses some classes from plugin B.
* Plugin A declares an extension point EP (a simple element with an attribute
"class" of type "Java" to make it and executable extension).
* Fragment FA declares an extension of EP whose "class" attribute is a class from B.
Plugins and fragments are 3.0 compatible and OSGI bundles with a MANIFEST.
1/ while fragment FA declares B in its prerequisite list (and thus correctly
compiles when using code from B), the PDE extension editor only list types from
FA when the "Browse..." button is pressed (obviously, this should bring the list
of types known to FA, including those from B).
2/ as a turnaround, when declaring inside FA a class that extends the required
class from B (to make it visible from the PDE), a "class not found" exception is
raised each time an attempt to create an instance of this type is made: the
missing type being the class ancestor from B.
3/ no change even if plugin A is forced to have B in its dependencies.
To conclude (and be clearer): whatever i do there is no way to get a fragment
using classes from another plugin.
Reading the compatibility document and the javadoc, it is said that execution
extensions may activate the required plugin.
And that's true for 2.X because the above configuration perfectly works.
Does anybody knows the exact status for 3.0?
From my point of view it is a strong regression without a clear rational.
Any ideas/insight will be appreciated before i fill a bugzilla form.
--
Christophe
|
|
|
Powered by
FUDForum. Page generated in 0.04669 seconds
Home