7 developers... working in one location or distributed?

if it's local: I do not think it's already a critical size, because the
edits on the struts-config.xml should not be SO frequent that it becomes
a problem. EG. when you meet for a coffee in the morning all it takes are 
30 seconds to check who needs to make changes "today"... and then
coordinate them.

If it's distributed: You'll have the same problems with other files as well...

And then CVS usually is quite clever at handling such edits. I think that 
conflicting edits will happen VERY rarely.

The struts modules might be another way to split the whole app into smaller
parts.

hth
Alexander

-----Original Message-----
From: Laran Evans [mailto:[EMAIL PROTECTED] 
Sent: Thursday, August 12, 2004 7:59 PM
To: Struts Users Mailing List
Subject: Re: xdoclet and struts forms

I hear what you're saying.  However, I work in a team of 7 developers.  
If each developer can make changes to the struts-config.xml file we'll 
have 7 people working on the same file at the same time.  If we generate 
the struts-config.xml file with XDoclet we will all in fact be working 
on separate files, with the struts-config.xml file being generated 
consistently, with changes integrated as they're committed to CVS.

I think it's a tradeoff.

Rick Reumann wrote:

> Laran Evans wrote:
>
>> I have a struts ActionForm which I would like to markup with xdoclet 
>> tags.
>
>
> Don't do it:) Seriously, IMO, I think it's a waste. I think it's nice 
> having one configuration file to look it to set up all my mappings 
> (your config.xml file). Think about it, using xdoclet if you decide 
> that after your form submits you'd rather the user forward to a 
> different page, you end up having to track down the action class and 
> modify the xdoclet tag and then rebuild. I'd rather modify one simple 
> xml file. I'm yet to see how xdoclet helps in a Struts environment.
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to