The notifyPropertyChangeListeners() method was
never intended to be called by anyone outside the framework,
but since it was visible, it got used for all sort of
nefarious deeds. Like signaling property change when the
property hasn’t changed…
The refresh() migration works in some cases, but
not in others. There is no direct/universal replacement.
The sad aspect of this situation is that there is
no API for refreshing property editor assist outside of an
actual property change event. This deficiency was not made
evident earlier because notifyPropertyChangeListeners()
workaround was found.
Go ahead and open a bug to support custom
PropertyEditorAssistContributor refresh.
- Konstantin
In the migration guide,
element.notifyPropertyChangeListeners
( property );
should be replaced with:
element.refresh
( property );
This migration broke the my custom content assist which extends PropertyEditorAssistContributor. The original call refreshed the content assist.
How can I programmatically refresh the content assist?
Thanks,
Ling