In an Eclipse 3.x app I worked on, we used activity bindings as part of a user authorization system to hide UI elements (menu items, view parts, perspectives) that an account did not have access to. The app was composed of bundles which each contributed "permissions" and activity bindings, and a global service tied permission enablement to the activity system.
In Eclipse 4.x, I read about the Model Processor which could crawl the application model and make changes.
Is it a recommended or even practical approach to use model processors in e4 as a replacement to activity bindings from 3.x, or do activity bindings still work as they did?
Is it a good practice to have a model processor react live to the application, or should its lifecycle simply be on application startup? How about having a model processor register listeners to the model that react?
Where can I look for more information about better use of model processors? I've checked the help.eclipse.org and a tutorial, but did not find info about it on wiki.eclipse.org