Community
Participate
Working Groups
While working with Common Navigator I got the following error in the Error Log: Contributor org.hibernate.eclipse.navigator.KnownConfigurationsViewer cannot be created from the plugin: org.eclipse.ui.views.properties.tabbed And this happen even though I haven't done or defined anything in relationship to the properties view. I assume it is something occurring because of CN calling into the properties setup, but do not know for sure. Michael D. Elder wrote on the newsgroup: "The CN framework has integration with the Tabbed Properties View built in. It's my impression that the error your seeing simply indicates that the Tabbed Properties View tried to create a contributor (to it) using the id of the view part, and was unsuccessful (e.g., no contributor to the Tabbed Properties View is available with that id). I don't believe it actually indicates an error condition."
Anthony -- can you confirm that this error message is not an issue in this scenario and consider removing it?
If you do not have a properties view for your viewer, you need to override the getAdapter() to not use the tabbed properties view. As you code exists now, you are saying to use the tabbed properties view with id org.hibernate.eclipse.navigator.KnownConfigurationsViewer , which is the id of the view.
In this case, it is the default implementation of the view part (org.eclipse.ui.navigator.CommonNavigator). The view part class uses the ID of the viewer when looking for a tabbed properties view provider. I would really rather not contribute a wholly separate default implementation without Tabbed Properties View support. Is there some middle ground here?
Perhaps we should change getContributorId() in the base to return "org.eclipse.ui.navigator.CommonNavigator" and not getSite().getId(). Then extenders would get the default properties view configuration defined for the CommonNavigator.
Remember that a "Common Navigator" is a type of viewer, not a specific viewer. There are at least two "Common Navigator"s provided in the Platform (the Team Synchronize views and the Project Explorer). In addition, other products that build on the Platform may have their own viewer instances for customized applications (indeed I know of two instances). These views may end up rendering some of the same things (Projects are a good example), so I think this could lead to a bad user experience where many properties that are not applicable in a certain context are exposed to the user.
ok, how about this. Since org.hibernate.eclipse.navigator.KnownConfigurationsViewer is using the tabbed properties view with id org.hibernate.eclipse.navigator.KnownConfigurationsViewer , the best way to get rid of the error message is to simply add the propertyContributor extension point with nothing in it and you will get the "Properties are not available" in the properties view. The customer should add this to plugin.xml <extension point="org.eclipse.ui.views.properties.tabbed.propertyContributor"> <propertyContributor contributorId="org.hibernate.eclipse.navigator.KnownConfigurationsViewer "/> </extension>
Not significant enough to justify a fix for 3.2.1.
Hi Max (or Rob), can you see if this is happening in build 3.4.1? There were some fixes in this area that I think might have resolved this.
*** This bug has been marked as a duplicate of bug 244354 ***
