Hi Daniel, This is a standard problem, and Magnolia provides ways to develop that get around this:
Basically, if you are developing in Java, then the JVM *needs* to reload your classes when you change them. There are three levels of this: 1) restart the whole java process (restart tomcat). This will reload everything, but with a lengthy down-time, and lost sessions 2) tomcat reloads your webapp. Depending on your configuration, it will do this automatically when it detects changes. This has a shorter downtime, but otherwise the same disadvantages as 1). Additionally, most setups will only survive a certain number of reloads before running out of RAM, because tomcat usually doesn't manage to release all the memory the previous instances of the webapp allocated. 3) hot-code-deploy via your IDE. In the correct setup, while debugging, your IDE can "live-change" some java changes (not all) without restarting anything. That all applies for developing in Java. If you are are doing so called "light development", not in Java, things can be much more comfortable: When you are talking about developing templates, html, javascript, etc... then all you are changing is your resources. Magnolia can detect those changes and reload your resources and definitions automatically, without any need to restart the webapp. ***The trick to make this work is to make sure these resources are not part of the webapp, e.g. don't get loaded from the classpath.*** Magnolia provides two mechanisms for your resources outside the classpath: 1. Light development via filesystem: store your resources on the filesystem (outside the webapp!) and configure the resource base path to point to that folder. Magnolia will find your resources there, and automatically reload them as they change. 2. Store resources in JCR, in the resources workspace. Again, magnolia will automatically reload them as they change. You can use the webdav module to connect to JCR in a convenient way and thereby edit the files in your favourite editor. Hope that helps you! Regards from Vienna, Richard > -----Ursprüngliche Nachricht----- > Von: dev-list-ow...@magnolia-cms.com [mailto:dev-list-owner@magnolia- > cms.com] Im Auftrag von Daniel Baylon (via Magnolia Forums) > Gesendet: Dienstag, 23. August 2016 11:06 > An: Magnolia Dev List > Betreff: [magnolia-dev] Re: Autodeployment > > Hello Christoph, > > [quote] > > Once again: What do you want to achieve with the update? What has > changed in the modules which you want to redeploy? > > [/quote] > > Say I just did add new label. Either way, I change something on the > code that I rebuild a module. Once I rebuild the module, I build the > whole war package for the deployment. > > [quote] > > And: Which servlet container / app-server are you suing? Tomcat? JBoss? > WebLogic? Websphere? ... > > [/quote] > > I am using Tomcat 7. > > Regards, > > Dan > > -- > 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: <dev-list-unsubscr...@magnolia-cms.com> > ---------------------------------------------------------------- ---------------------------------------------------------------- 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: <dev-list-unsubscr...@magnolia-cms.com> ----------------------------------------------------------------
