Community
Participate
Working Groups
When no org.eclipse.core,runtime.compatibility.registry is in the product, then the first opening of the New WSDL wizard fails with the following stack: java.lang.NoSuchMethodError: org.eclipse.core.runtime.IExtension.getDeclaringPluginDescriptor()Lorg/eclipse/core/runtime/IPluginDescriptor; at org.eclipse.wst.wsdl.ui.internal.ContentGeneratorUIExtensionRegistryReader.readElement(WSDLEditorPlugin.java:563) at org.eclipse.wst.wsdl.ui.internal.BaseRegistryReader.readRegistry(WSDLEditorPlugin.java:420) at org.eclipse.wst.wsdl.ui.internal.ContentGeneratorUIExtensionRegistryReader.readRegistry(WSDLEditorPlugin.java:542) at org.eclipse.wst.wsdl.ui.internal.WSDLEditorPlugin.getContentGeneratorUIExtensionRegistry(WSDLEditorPlugin.java:166) at org.eclipse.wst.wsdl.ui.internal.wizards.WSDLNewFileOptionsPage.createControl(WSDLNewFileOptionsPage.java:201) at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174) The cause is probably that this wizard uses old code that has been deprecated and then moved to the compatibility fragment. The wizard should use newer code.
Created attachment 205706 [details] Proposed patch that delegates loadClass to a bundle