We do have a development, integration , user acceptance and Production environment. but this is an ongoing project in which new modules( and hence, new struts-config.xml) keeps on adding. We definitely do version controlling and stuff. but, sometimes it happens that there is still time in the new module to go live and we have made more changes in we.xml(say, mapped a servlet) and need to make that live. In these cases, it becomes tedious to check the web.xml always and see if we are not maping any extra struts-config.xml . Also, if any newbie is deploying code for the first ime, it becomes difficult to give him all these set of instructions
On 12/8/05, Yujun Liang <[EMAIL PROTECTED]> wrote: > > Acutally I have a thought for Struts Developers, > > I also config the action individually in small config files, everytime I > added a new action, I needed to change the web.xml file. > > It would be nice to change the StrutsConfig to allow a directory as a > config > entry, so I just define a directory for Struts config and Struts reads all > files under the directory, so it saves the effort and checkpoint to modify > web.xml and solves the problem in the email gracefully. > > Regards > > > > > > > On 12/8/05, [EMAIL PROTECTED] < > > [EMAIL PROTECTED]> wrote: > > > > > > 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] > > > > > > > > > > > > -- > > Yujun Liang > > [EMAIL PROTECTED] > > > > > -- > Yujun Liang > [EMAIL PROTECTED] > >
