I'm all for deprecating the properties file if it's deprecated in the JDK sense. ie, it's available, it can be used (and is by anyone who was using it), but you shouldn't use it if you're starting afresh. Eg, new features that might be added to the xml file might not be added to the deprecated properties file.
I think a good guiding principle is that while it's nice to cater to those who know their asses from an action, they are not the main target audience for webwork, and hopefully never will be. Making them happy is definitely a bonus and something that should happen, but if it's at the cost of anyone else...then tough luck!
On Monday, November 4, 2002, at 05:55 PM, Patrick Lightbody wrote:
Ugg... but leaving the option there for people like me who know our ass fromMultiple configuration methods make webwork more confusing, not less
an Action would sure like to be able to do powerful things. Limiting to
views.properties or actions.xml would not let me use webwork in ways I'd
like to.
Now, multiple DEFAULT configuration methods is surely confusing, I agree
with that. Allowing users to select their configuration methods (simple or
complex) is not a bad thing, however.
-Pat
-------------------------------------------------------
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF. http://www.apachecon.com
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
------------------------------------------------------- This SF.net email is sponsored by: ApacheCon, November 18-21 in Las Vegas (supported by COMDEX), the only Apache event to be fully supported by the ASF. http://www.apachecon.com _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
