Hi Radu,
here is what I have found
Radu wrote:
What exact version of Eclipse RCP do you have?
We use the 3.6 version of Eclipse.
Radu wrote:
Basically when our plugin's org.eclipse.core.runtime.Plugin#stop(BundleContext) method gets called
Exactly here lays the problem, because we do store all preferences beforehand in order to persist them on the server-side so that a user can have equal preferences at different locations/maschines or even have different preferences for different purposes.
So you do save your preferences too late for us, because we do attach an
IWorkbenchListener and save all preferences, when the
IWorkbenchListener#preShutdown method is invoked.
By Default preferences are directly stored, when the user presses the
OK Button in the Preferences Dialog.
Under the circumstance that you do not use the PreferenceDialog in that case, we would really appreciate, if you would save your preference directly.
The direct saving of Preferences is also preferable, because listeners for each preference value can be attached, so that the changes can directly be executed. So we would also be able to read your preferences and get to know, when they have changed during a client session.
Would direct saving of your preferences, when they are changed possible for you?
As a workaround until you hopefully implement the
"direct saving of preferences", I do like to know, if we are able to store your preferences on our side.
Best regards,
Simon