On Wed, 4 Jul 2001, Valeriy Zavidnoy wrote:
> Our team is starting to use Struts, that means each developer needs to edit
> struts-config.xml and *.properties files. The issue we encountered is that
> several guys (12-15) want to edit these getting huge files at the same time.
> Of course, we are using currently source control by VSS, we thought about
> moving to CVS, but it won't completely let us avoid a headache.
> Can anyone give a suggestion how to solve this?
> Thanks.
>
Which source code environment you are running in only has a minor impact
on this. The key issue is that you want developers to be able to manage
their own entries in each of the major struts-config.xml sections
independently.
One appropach to this involves modifying your web app build procedure to
assemble the overall struts-config.xml file dynamically, rather than
maintaining it as a single file.
An example of this technique would be that each sub-project of an overall
web application would maintain it's own individual copies of the
<data-sources>, <global-forwards>, <form-beans>, and
<action-mappings>) sections of the complete struts-config.xml file. Then,
your build process would also include a script that assembled the
"real" struts-config.xml file from all of the relevant pieces, instead of
maintaining it as a single entity in the source code repository.
Craig
