Versions Compared

Old Version 7

changes.mady.by.user Magnolia International

Saved on

compared with

New Version 8

changes.mady.by.user Magnolia International

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Magnolia should be markable as read-only; module jars should be loadable from outside the webapp folder. See MAGNOLIA-2170@jira and the linked user-list thread for some background discussion !
  • Figure out the server side: where/how do we deploy and publish modules. OSGi or Maven might provide help here.
  • Magnolia-core will probably have to remain in the webapp folder: extract more out of core, so that it can also benefit from easy updates.
  • Wiki Markup
    No need to restart the app/appserver to deploy a module update. ("updates are ready: \[apply now, silently] or \[click here for switching to the update UI when ready]"; alternatively, we could maybe make it so that the system still works while updates are being applied, and switches "atomically" at the end? - or at least provide a configurable temp page for public instances)
  • Secure the update UI (it's currently totally open) - provide a better/configurable page for public instances while updates are being performed.

Examples of existing implementations of such features: Confluence, Hudson, ...

We could(should) also evaluate OSGi, although my feeling is that it is very complex and bulky, and will incur more cost than bring benefits. Somehow I hope I'm wrong.