<quote> XML configuration cannot replace traditional programming. </quote> I'd rephrase that slightly as: XML configuration cannot completely replace traditional programming.
The issue being here that with the right frameworks and tooling you can go a long way to eliminating all code except that which actually is unique to your business problem and is not worth describing in those common terms. Everything is an abstraction, XML metadata is just a at higher level. I personally feel that the more configuration and logic you can describe through some sort of metadata the better, under the proviso that the metadata you are dealing with is not more complex than the code you're substituting for, but that's just me.
Regards
Duncan Mills
Pilgrim, Peter wrote:
-----Original Message-----===
From: David Graham [mailto:[EMAIL PROTECTED]
--- Craig McClanahan <[EMAIL PROTECTED]> wrote:
I agree with Don's assessment, but wanted to add an FYInote -- Shale
does zero-config for #3 (because the mapping between a JSP page andrequire #1
the corresponding ViewController is implicit), and doesn't
But is adding yet another framework to Struts simplifying anything for theunless you need it for doing Commons Validator stuff.
Simpler is definitely better.
user or just for us developers? If we add Spring, we would need to know
the following to write a Struts webapp:
1. struts-config.xml
2. validator-rules.xml
3. spring.xml (or whatever they call the config file)
4. possibly tiles-config.xml
5. possibly jsf config files
How is learning and remembering up to 5 different configuration files
better for the user? If I was put in this position, I would seriously
consider other ways of writing Java webapps.
XML configuration cannot replace traditional programming.
You can quote me on that.
==////==
XML configuration cannot replace programming
--
Peter Pilgrim
Operations/IT - Credit Suisse First Boston, 10 South Colonnade, London E14 4QJ, United Kingdom
Tel: +44-(0)207-883-4497
============================================================================== This message is for the sole use of the intended recipient. If you received this message in error please delete it and notify us. If this message was misdirected, CSFB does not waive any confidentiality or privilege. CSFB retains and monitors electronic communications sent through its network. Instructions transmitted over this system are not binding on CSFB until they are confirmed by us. Message transmission is not guaranteed to be secure. ==============================================================================
--------------------------------------------------------------------- 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]