Well that's an interesting case for creating a new feature that let's you have as many struts-config files as you want.
Perhaps you could divide your application and it's resources into Modules. That way you could develop the Modules in teams. I have some good new for you. That's exactly what the new Struts 1.1 feature Modules does. I know 1.1 is not final, but it will be soon enough....and believe me, you will find this cool feature very useful. Hope that helps James Mitchell Software Engineer/Struts Evangelist http://www.open-tools.org "If you were plowing a field, which would you rather use? Two strong oxen or 1024 chickens?" - Seymour Cray (1925-1996), father of supercomputing > -----Original Message----- > From: Chiming Huang [mailto:tomcat_huang@;yahoo.com] > Sent: Tuesday, November 12, 2002 11:08 AM > To: [EMAIL PROTECTED] > Subject: Multiple struct-config.xml files > > > Hi, Is there a way to break down the struts-config.xml files into > multiple files? So that each sub-project can handle it's own > struts-config.xml. We are porting multiple projects to web using > Tomcat and Struts. Under Struts, the struts-config.xml is the > file that contains all the request mappings and forwarding. If > we merge all projects into one Tomcat-Struts project, the > struts-config.xml will be big and difficult to maintain among all > developers. A separate struts-config.xml file for each > sub-project seems to be better. If we develop each proejct as a > separate Tomcat-Struts project, does it seem normal to do it that > way. Please advise the best way to incorporate multiple > projects. Thanks.Chiming > > > --------------------------------- > Do you Yahoo!? > U2 on LAUNCH - Exclusive medley & videos from Greatest Hits CD -- To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>
