Type: New Feature
Resolution: Won't Do
Affects Version/s: None
Fix Version/s: None
Environment:Apache Tomcat/5.5.25, JVM1.5.0_11-b03, Linux 2.6.18-5-vserver-amd64
For the following Scenario,
Deploying Website-A (using Templates-A) on Server A, everything went fine
Server B subscribes from Server A, all same hardware/software environment, but does not have this new Template-A. In magnolia 2.x, when activate Website-A as an urgent deployment, Server B will receive a copy of pages, but crash down. During this procedure, there was no warning message.
I received some information regards with this issue from Boris (thank you very much indeed) and find out this is not a magnolia issue, the problem is with the system admin/web masters. But I really want to know, if there were more than 2 people in charge of taking care of magnolia and the above scenario happen, is there any method can take the precaution or damage control? Like, if one does not know there's no such template for every subscriber servers (or assume the other one did, but actually not) still directly make the deployment and activate the pages via magnolia GUI, would magnolia be able to detect the templates are the same version or at least the desired one does exist in the system?
If anyone has any thoughts or having the similar question as mine, let discuss the resolution together.