This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Is there any other way I can organize my struts-config.xml without using the module feature?
I have two process in my application. Like a part that totally deals with Add/update/Search Employee. Another part that deals with Add/update/Search Departments. How do I organize my struts-config.xml, if I am not using module feature?
The reason being that I have started my application without the module level struts-config.xml and I don't want to rewrite my project using modular config files.(may be will use the feature in my next project..)
If neatness is all you're after, just put in comments:
As I see it, splitting configuration information into more than one config file creates more confusion than it solves. Even if you do have more than one developer working on the project, simply using good source control management software can keep you from overwriting each other's changes.
Merrill's suggestion is about all that I can think of and it is the basic technique that I have used. You still will have to put your form definitions towards the top in your form-beans section and your action definitions in the action-mappings section as this is dictated by the DTD.