> > @Oliver Rettig > > I use the possiblity, that the users can dynamically add nb modules very > > intensive and also the possitlibty that needed lib modules are > > automatically added if needed ... > But how often do your users add / remove modules (or enable/disable)? > And how important is the dynamic aspect -- would an IDE restart break > the workflow so much?
It is a very handy workflow for me to develop new modules and gives the users the possibility to add them to a self descided point of time. A typicall situation is that my users use my application in very different contexts and for each context they add/remove lots of modules. E.g. a medical PD student removes all "modelling" featuers of my software and the post docs are mainly focussed on modelling but do not need excel import/export functionality. I have hundrets of modules and if all modules are installed you run into out of memory problems and it is also not very convinient to have too much menu entries. I think your are right, a application restart after add/remove modules should be no limitation. In the past I have forced a restart of my applications in case of add/remove for some specfic modules due to some problems I cauld not solve. I got no negative feedback of any users. Most of the users dont realize the change to a forced restart at all. Are there interesting osgi modules e.g. in the Apache world we can win?
