Team development with struts

[Valeriy Zavidnoy <Va...@NUBASE.com>]

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.

Re: Team development with struts

[Ted Husted <hu...@apache.org>]

The "namespace" for the properties file can be arranged so that each
developer can add new tokens to separate copies, and then the copies can
be concatenated as part of the build process.

The same sort of thing can also be done with the struts-config.xml if
you follow the workaround recently posed by Dan Miser at 

<
http://www.mail-archive.com/struts-user@jakarta.apache.org/msg10052.html
>

-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Custom Software ~ Technical Services.
-- Tel 716 737-3463.
-- http://www.husted.com/about/struts/

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.

Re: Team development with struts

["Craig R. McClanahan" <cr...@apache.org>]

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