We have a ‘suite’ of applications that are all deployed under one context in Tomcat. They are related applications, and share some common java code, the odd jpeg/gif, css files and (external) configuration files. However, as running applications, they do not interact with each other in any way – no one application relies on the existence of any other.
My first thought was that these applications should have all been deployed under separate tomcat contexts, so that they could be deployed independently and using the application manager, could be brought up and down independently for maintenance and upgrades etc. BUT as they do share non-java files as described above, is this the right approach? Should we leave things as they are or is there a better way to organise them as separate tomcat contexts??
Thanks for any pointers.
Andrew Waters.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
