Dan You address a typical Java webapp "issue" - this actually is not specific for Magnolia.
The WAR file (Web application ARchive) *is* your webapp. If you redeploy the WAR file, the webapp is "down" for a certain time. Since a Magnolia instance is a webapplication - e.g. deployed as WAR file - the Magnolia instance is down for a certain time. In a productive environment you may have more then one public instance. With such a scenario you can avoid "down time" for the webiste even when redeploying. See https://documentation.magnolia-cms.com/display/DOCS/Instances While developing with an IDE such as eclipse or intelliJ (and probably even using JRebel) - you won't have to redeploy the complete webapp all the time when adding a label (or whatever). (But that's another story.) i hope this helps, kind regards, Christoph -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=e5e78cef-8b5e-41f6-882a-38fb9ce9db12 ---------------------------------------------------------------- For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
