--- Don Brown <[EMAIL PROTECTED]> wrote:
> Craig R. McClanahan wrote:
> 
> > <snip />
> >
> > I personally believe that, even if we implemented dynamic 
> > reconfiguration support for the config files themselves, developers 
> > will be disappointed in how little this helps in a development cycle 
> > -- you're not going to pick up added or changed Java classes without a
> 
> > container-managed restart of the webapp (except on *some* containers 
> > where you haven't yet loaded the class in question), so typical 
> > development use cases like "add the next Action" are going to require 
> > restarts anyway.
> 
> True, however that is only if your actions are Java classes.  I've 
> developed Struts apps using scripting languages, particularly BeanShell,
> 
> to get a quick prototype of the application up and running.  Later, I 
> can easily change those scripts to Java classes if there is need.  For 
> Struts to detect a configuration file change and automatically reload 
> the config, as Cocoon can do (can be turned off of course), would go a 
> long way to make it possible to quickly develop/prototype Struts 
> applications.

That's an interesting point.  I really think ease of use should be a major
priority for Struts 2.0 and this factors into that goal.  There are people
who strongly dislike Struts and we should listen to their complaints; a
large number of which center around complexity.

David

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


__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway 
http://promotions.yahoo.com/design_giveaway/

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

Reply via email to