Plug in with cyclic dependencies? [message #582697] |
Mon, 13 October 2008 17:23 |
Glenn Boysko Messages: 6 Registered: July 2009 |
Junior Member |
|
|
Hello:
I have a graphical editor plugin that relies on another plugin. This other
plugin, is a pure data, API plugin. This all works fine.
Let's call the editor plugin, "A". Let's call the pure Data API plugin,
"B".
Now, I would like plugin "A" to expose a package that may be needed in
plugin "B". Plugin "B" uses a JAXP-compliant XML Parser. When the "B"
plugin is being used with plugin "A" (plugin "B" can be used without
plugin "A"), I would like plugin "A" to expose it's own JAXP-compliant
parser. In effect, it means that it would expose a
META-INF/services/javax.xml.parsers.DocumentBuilderFactory file which
contains the name of a class to invoke. This class would be exposed by A
so that it could be invoked by B.
Unfortunately, I am not able to expose this new class/package.
I am adding to plugin "A" the new package which exports. However, when I
am inside in plugin "B", calls to Class.forName() are failing for the
class exposed by "A".
Is this possible? I would not like to have to require the class exposed in
plugin "A" to be required in "B". Like I said, I would like "B" to work
independently of "A".
Thanks in advance,
Glenn
|
|
|
Powered by
FUDForum. Page generated in 0.03078 seconds