| Runtime state - Behaviour of osgi.clean option in equinox [message #120426] |
Fri, 31 October 2008 14:24 |
 Florian Pepping
Messages: 1
Registered: July 2009 |
Junior Member |
|
|
Hi,
I've got a question concerning the behaviour of the "-clean" option of
osgi/equinox.
We've got an application, that consists of two parts. One "server" part,
that is started during system boot, running all the time and a GUI-part,
that can be started and stopped manually within this server. So,
unfortunately both parts are running in the same VM (they must run in the
same VM) and the bundles of the GUI are downloaded and installed/activated
at first manual startup. Stopping the GUI-part, the GUI is disposed, but
the bundles are not deinstalled.
The required default behaviour of OSGI is to persist all bundle states and
rebuild this state while restarting. This leads to the effect, that our
application always starts with the GUI-part visible, because the bundles
of the GUI have been started/installed at the last shutdown of the server.
One solution to avoid this behaviour is to start up our application with
the "-clean" option each time. However, this involves severe performance
decrease and is not really necessary.
So my question: Is there a way to configure equinox, so that the bundles
are being cached but the runtime state is cleaned every time?! Or can this
being reached by deleting some files programatically?!
Sorry for this long explanation but I hope you can understand my problem.
Thanks for your help
Bye
Florian
|
|
|
Powered by
FUDForum. Page generated in 0.02139 seconds
] 
Search
Help
Register
Login
Home
