search

mff-uk / odcs

ODCleanStore
1 stars 11 forks source link

Possibility to load target/lib folder on the fly #1311

Open tomas-knap opened 10 years ago

tomas-knap commented 10 years ago

Motiviation: If new lib bundles are added, it is not necessary to restart the app. @skodape How much time do you expect this feature will require?

skodapetr commented 10 years ago

Depends how much user friendly this should be. We should discuss on next meeting.

tomas-knap commented 10 years ago

Well, what I meant is that user uploads bundle to the given location (target/lib) and backend automatically loads such bundles while running. So it should behave similarly as in case of new DPU templates versions

skodapetr commented 10 years ago

Some questions that cross my mind: 1) How does the user load the library - currently he can not use Frontend for this. 2) What if the library has dependencies - and so can not be resolved? 3) User do not see list of already loaded libraries, and when we have such list it would be nice to have some "reload" functionality - so when big library A (that has been loaded first) but not resolved, can be "re-installed" after I add the missing dependency without reloading A again.

From he OSGI point of view this should not be complicated.

tomas-knap commented 10 years ago

I think it does not need to be superfriendly. But it should allow to add libraries as the tool (backend) is running.

1) I think it would be enough for now to copy the bundle to the given folder 2) Than, an error should be written to the log/error log. It could be also a separate error log, so that admin can quickly see the problems with the bundles newly added 3) Again, I think we can start with the solution where admin simply replaces the given lib and the tool finds out there is a new version (bundle with the same name) and reloads