Deepa Khetan asked: > > I have faced some problems during deployment. If i have > multiple struts-config.xml in my application, i map them in > my web.xml. So far, so good!! But the problem is when i > deploy the code on producion, some of the struts-configs > might be missing from the server(for the simple reason, that > they are stll under development and have not been released to > production). I then need to change the mappings in web.xml, > else it throws an error on the first page of the application, > which looks extremely ugly and frightful!!! Is there a way in > which i can handle this exception gracefully?? Or can i > somewhere specify that it should ignore the mappings for the > non-existent struts-config.xml ??
I don't know the aswer for catching that exception, but this sounds like a configuration managment problem, to me. Why is the updated web.xml being deployed separately from the added struts-config.xml file? I suggest promoting a set of related changes from development to production all at the same time (and to have an integration or acceptance test environment between the two). The promoted build should be made from a tagged set of files in your version control system. - George http://www.idiacomputing.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
