... 'course, it's still nice to know the format of a config file, in case there's some feature you can't realize using a tool. WSAS tells me, for example, that I have a broken link in my config file as a result of referencing a tile through the forward attribute of an action. It annoys me, but, of course, it works fine (Seems WSAD 5.1.1 only supports Struts 1.1). I can imagine a circumstance where a config could change by adding an attribute or some other thing so that the tool couldn't edit these pieces.
Eddie
----- Original Message ----- From: "David Graham" <[EMAIL PROTECTED]>
To: "Struts Developers List" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, November 29, 2004 12:34 PM
Subject: Re: Spring dreaming (was Second call: add "generic" mapped property to ActionConfig)
But is adding yet another framework to Struts simplifying anything for the 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.
David
--- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0448-1, 11/26/2004 Tested on: 11/30/2004 12:22:38 PM avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
