Community
Participate
Working Groups
Meaning to open this against M8 and high priority. The contributed mapping item providers don't display the icon and label in the j2ee navigator (they do seem to be there since I can launch editor on it, etc). I spoke to Michael Elder about this and he thinks that the core navigator framework is not locating the correct label provider or content provider properly. And there might be a need to expand the core extension framework from the navigator to support the ability to dynamically determine the enablement. This is the way I currently contribute my providers: <extension point="org.eclipse.wst.common.emfworkbench.integration.adapterFactory"> <adapterFactory className="com.ibm.etools.ejbrdbmapping.ui.provider.J2EEEjbMapItemProviderAdapte rFactory" packageURI="ejb.xmi" id="com.ibm.etools.ejbrdbmapping.ui.provider.J2EEEjbMapItemProviderAdapterFactor y"> <view id="org.eclipse.wst.navigator.ui.WTPWorkingSetCommonNavigator"> </view> </adapterFactory> <adapterFactory className="com.ibm.etools.ejbrdbmapping.ui.provider.J2EEComposedMapItemProviderA dapterFactory" packageURI="http:///ejbrdbmapping.ecore" id="com.ibm.etools.ejbrdbmapping.ui.provider.J2EEComposedMapItemProviderAdapterF actory"> <view id="org.eclipse.wst.navigator.ui.WTPWorkingSetCommonNavigator"> </view> </adapterFactory> </extension>
Part of a mass update. Based on 9/22/2005 development review meeting, it's determined this was an open bug/enhancement with tartget mistakenly set to M8. Since this will not be in M8, I am changing to "unspecified". If this is an error, please correct (for example the bug really has been fixed in M8, change back to M8, and "fixed".)
This isn't really a duplicate of 115218, but the solution for 115218 will fix this problem as well. The root of the problem is that the J2EE extension uses a further extension (the adapterFactory extension discussed here) to contribute content which is not described by the J2EE content extension's enablement clause. *** This bug has been marked as a duplicate of 115218 ***
This bug was moved to 'closed' state, since it is so old is is assumed its dup, invalid, or worksforme resolution is no longer in qustion and the bugzilla needs no further attention. Feel free to re-open, or open a new bug, if this semi-automatic processing was done in error in this case.
