Now, to make me sound less like a whiner and more like someone with good ideas, here is a practical proposal:
The way you have to declare each action in a rather complex XML config file before even rudimentary testing increases the learning-curve needlessly. I propose a few simple features that will help the average users:
Actions can be run with the fully qualified class name.
Actions map by default to
1. a view document with the name of the action.
2. if 1 fails, a debug document that displays a list of the exposed properties and their current value.
This will cut the amount of explaining needed for a hello world type app down by an entire step. Anyone else got ideas like this that will cut down on the learning curve for newbies?
Anders Hovmöller
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
