|Re: Usage of XMLCorePlugin to programatically register XML Catalog in eclipse... [message #224737 is a reply to message #224615]
||Fri, 05 December 2008 16:28
| Gabriel Indik
Registered: July 2009
> Well I notice that the plugin in its manifest doesn't export packages
> exclept to friends...
> Manifest-Version: 1.0
> Bundle-RequiredExecutionEnvironment: J2SE-1.4
> Bundle-SymbolicName: org.eclipse.wst.xml.core; singleton:=true
> Bundle-ManifestVersion: 2
> Bundle-Activator: org.eclipse.wst.xml.core.internal.XMLCorePlugin
> Bundle-Localization: plugin
> Bundle-Name: %pluginName
> Bundle-Version: 1.1.306.v200810210016
> Bundle-ActivationPolicy: lazy; exclude:="org.eclipse.wst.xml.core.inte
> Bundle-Vendor: %providerName
> Export-Package: org.eclipse.wst.xml.core.internal;x-friends:="org.ecli
> pse.wst.dtd.core,org.eclipse.wst.dtd.ui,org.eclipse.wst.xml. ui,org.ec
> Now how would one go about using the plugin with this restriction?
> Is there something at a higher level that might expose packages for this
I created a small plug-in and used your code fragment to test this
scenario. Just as you mentioned, some of these classes are not accessible
due to restrictions, in fact bugzilla entries have been created to address
Even when these restrictions will create a number of warnings (i.e.
discouraged access) it is still possible to execute the code. I was able
to run it in my environment. So there could probably be something in your
environment that is causing this problem, like a missing dependency. What
version of the platform are you using?
Powered by FUDForum
. Page generated in 0.01693 seconds