Entry points for projects with Plug-In nature
SAFE two special options to specify entrypoints for typestate analysis of Plug-In project. You have also the option of Redefining plug-ins list.
Redefining plug-ins list

When analyzing a plug-in, it is possible that some extension points implementation in the list of external plug-in dependencies can call part of the code analyzed via some call back mechanism.

For this particular reason, and for the fact that you might want to analyze only external plugins code, you need to be able to select those external plugins. If you select check box button Consider plugins list different from input, then all the plugin elements you will select in the box will be used for automatic detection of entry points coming in the two next sections below.

Extension points as entry points
Methods specified as extension points of a plug-in are clearly logical entry point candidates for typestate analysis. SAFE will automatically detect extension points as entrypoints.
For this feature, simply click on button Detect. Then you will see all the classes detected among the plugins defined with extensions. And for each class, the list of methods is provided for entry point identification.
Plug-ins main classes as entry points
Once a plug-in is activated, the method "void start( BundleContext )" is called for specific initialization operation(s).
SAFE can detect these methods automatically for use as entrypoints. Click on the button Detect and all the classes with a "start" method overridding will appear.
Privacy |  Legal |  Feedback |  IBM Home |  Research Home |  Project List |  Research Sites |  Contact Us