Community
Participate
Working Groups
The org.eclipse.jst.j2ee.webservice.ui plugin and some of its dependencies are activated when I open the Project Explorer in an workspace that has only simple projects (and even in an empty workspace). This seems to be because the WebServicesNavigatorContentProvider has a trigger point on the workspace root. Is it possible to narrow the content provider criteria or rework things so that the content provider doesn't cause the plugin and its dependencies to be activated at this point? It seems unnecessary for the jst and wst plugins to be activated at this time. Steps to reproduce the problem: 1. Install Eclipse 2. Install the Web and J2EE Development feature (and its required dependencies) from the Callisto discovery site. 3. Enable the OSGI bundle tracing and launch a new runtime workspace. 4. Close the welcome page and open the Project Explorer view. The following plugins are activated: org.eclipse.ui.navigator org.eclipse.ui.navigator.resources org.eclipse.emf.common org.eclipse.emf.ecore org.eclipse.jem.util org.eclipse.wst.common.frameworks org.eclipse.jst.j2ee.webservice org.eclipse.jst.j2ee.webservice.ui org.eclipse.emf.common.ui org.eclipse.emf.edit.ui org.eclipse.emf.edit org.eclipse.wst.common.emf org.eclipse.emf.ecore.xmi org.eclipse.wst.common.emfworkbench.integration org.eclipse.wst.common.project.facet.core
There has already been work to hone this down. Several plugins, including org.eclipse.jst.j2ee and org.eclipse.jst.j2ee.core were removed from this activation list. There is now a smart listening mechanism that waits before adding content to the explorer, but as it contributes content to the root of the viewer, there's no way to completely prevent it from loading.
In that case, would it be possible to at least delay the activation of those plugins that the org.eclipse.jst.j2ee.webservice.ui depends on that do work and other initialization in their #start methods? I'm thinking of the following, in particular: org.eclipse.wst.common.emf org.eclipse.wst.common.emfworkbench.integration
Can you provide a list of the classes that are touched that cause the activation of org.eclipse.wst.common.emf and org.eclipse.wst.common.emfworkbench.integration in your scenario?
Here's what I see happening when I open the Project Explorer in new, empty workspace using the following Web Standard Tools build: Version: 1.5.0.v200606092300-U4T922yjOWsGK5Y Build id: 200606281455 WebServiceNavigatorContentProvider's constructor calls #createAdapterFactory which instantiates a new DynamicAdapterFactory and causes org.eclipse.wst.common.internal.emfworkbench.integration to be activated. Then, EMFWorkbenchEditPlugin#start instantiates a new ExtendedEcoreUtil.FileNotFoundDetector, which causes org.eclipse.wst.common.emf to be activated.
The kind of changes required to prevent two plugins from loading is not merited in a point release. Therefore, this defect will be deferred to a post 1.5.1 WTP release.
Deferring to 2.0.
Still persists in 2.0 (as of Europa RC2) Having checked out a new project from an SVN repository there's a strange variation to it, that this project gets listed in the Project Explorer for a short period, but later dissapears again. Is there any way to get rid of this without completely deactivating or uninstalling WebTools?
