Re: [Webwork-devel] RE: Refactorings... Again

[<Jim...@do...>]

My opinion is we should have one configuration file for core WebWork 
settings, and one configuration per view technology incorporated.

For example, if I choose to use WebWork-Velocity, I should have 2 
configuration files.

jim





Mike Cannon-Brookes <mi...@at...>
Sent by: web...@li...
03/01/2002 09:15 AM

 
        To:     "web...@li..." 
<web...@li...>
        cc: 
        Subject:        Re: [Webwork-devel] RE: Refactorings... Again


On 1/3/02 8:11 PM, "Kjetil Paulsen" (kje...@mo...) penned the
words:

<lots of crap deleted>

> 
> And also the property files, we introduced common.properties, not 
completly
> sure yet what goes in here from default.props

PLEASE tell me this does not mean there are more configuration files? WW
already has too many! (webwork.properties, views.properties - which should
go IMHO, actions.xml, log4j config - and now more!)

Is there no way we can aggregate this all into one config file? I see no
reason for views.properties to hang around (especially considering 
everyone
needs to refactor their code after this rewrite anyway!) - can we axe that
in favour of actions.xml?

Log4J config is probably hard to get rid of - but I usually have 1 log4j
config per server or application which is good enough.

What does common.properties do? How does this relate to 
default.properties?
Why can't we roll it all into webwork.xml? ;)

-mike


_______________________________________________
Webwork-devel mailing list
Web...@li...
https://lists.sourceforge.net/lists/listinfo/webwork-devel