> A few things are still outstanding, of course: > * session timeout is only configurable in web.xml (requires a WAR > rebuild) > * application logging is... tricky (requires a WAR rebuild) > * probably other stuff, too
Yes, you're correct. An additional item I can think of that is configurable but only in the WAR file is the timing for batch jobs (which can be configured and is located in the task.xml file in the WAR file). When we write instructions geared for deployments, we can determine which require full WAR rebuild versus just unpacking the WAR file, editing and repacking. There are some tricks around doing this easily (e.g. WAR files can be decompressed using any standard zip/unzip utility and then can be re-compressed by zipping up and renaming file extension, etc) which may be useful to include. Hopefully we can figure out a way for all of the configuration to be done without needing to do a true 'rebuild' of the WAR (requiring other tools such as Ant, JDK, etc to be installed). ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Mifos-functional mailing list Mifos-functional@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mifos-functional
