Unfortunately, the error state is not recoverable. It is also rare that
it could happen. User has killed a process vital to the plugin or
uninstalled it in the middle of using the plugin.
Once the user hits this error, the plugin has to be "restarted" before it
can be used again. Of course, one way is to just restart Eclipse.
It is probably acceptable for the user to restart Eclipse after saving
away unsaved stuff in other plugins.
The issue is that time after user gets my popup message that the vital
server process has disappeard and he needs to restart, and before user
actually restarts. During this time, our perspective is the current, our
menu buttons are everywhere, our views are open but not really functional.
Come to think of it, I am not sure what Eclipse could do for me here. I
suppose I could fire an event to all my views to shutdown.
Is there a public API for popping the current perspective? That would
clean things up some.
As for your suggestion to move the lengthy task of launching this server
process from start to first use of it, and that it could be skipped if it
took too long, I don't see anything to suggest that there is some time
limit for start. Is there? I need this server process during method
start under certain conditions!
Thank you.