Community
Participate
Working Groups
If a common nav content extensions is filtered out based on its trigger points, and later something happens to the project that makes the trigger points apply the content extensions are never reevaluated. We need a lazy way (via ext pts) to specify under what conditions the project content extensions should be reevaluated. A common case is in WTP when content extensions only apply based on a certain combination of facets. Would be nice to re-query the relevent content extensions when one of the facets that it requires is added or removed from the project.
The best work around for now is to trigger the cache to flush itself. You can do this by activating an empty set. This will not change the active extensions, but will cause the flush event to clear out the remembered evaluations. INavigatorContentService.getActivationService().activateExtensions(new String[]{}, false)
I would like to know whether this would be fixed for WTP 1.5.1 ? Otherwise - I'll have to look into implementing the workaround. Thanks. Ying
Currently, this is not targeted to 1.5.1.
Don't forget about this! Please fix!
(In reply to comment #0) > A common case is in WTP when content extensions only apply based on a certain > combination of facets. Would be nice to re-query the relevent content > extensions when one of the facets that it requires is added or removed from the > project. This seems like a resource-related request related the Project Explorer, as opposed to something that should be part of the CNF itself. If I understand it correctly, your use case would be triggered by a resource change notification which should then cause certain NCEs to be reevaluated. So one way to do this might be to add an extension point to the org.eclipse.ui.navigator.resources plugin that specifies an expression (using the normal extension point expression mechanism) and specifies the identifier of the NCE that's to be reevaluated if that expression is true. The expression would be evaluated on resource change events, and if true, trigger the reevalation of the specified NCE. I'm a bit concerned about the performance of this mechanism however, as it would be checking this on every resource change (there is no way to register a resource change listener on only a subset of resources). Does this seem in line with what you need?
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
