On Wednesday, Nov 6, 2002, at 10:36 Europe/London, Rickard Öberg wrote:
If it's scaling _down_ you're worried about, surely making as many elements and attributes as possible optional is the Right Way? The actions.xml that's part of the source covers enough ground to allow a newbie to get started (from experience :) and seems to cover most of the obvious things that a user would like to do.Simon Stewart wrote:On Wednesday, Nov 6, 2002, at 09:51 Europe/London, Rickard Öberg wrote:Sure, I mean, I use XDoclet to generate it, so for me it doesn't really matter much. But for those who do it by hand, it will be a big difference.
> The issue about actions.xml is verbosity, not being able to figure out
> how to create it. Having a DTD doesn't change a thing in this regard.
XDoclet, perhaps?
It's about "scalability", and in this case scaling down to simpler projects.
An alternative: if each Action has a small config file specifying its views associated with it (in the same style as Hibernate), and this is documented in the javadocs for the Action and ActionSupport classes, then the problem of "not being able to create it" is trivialised.
Regards,
Simon
-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
