However, at this point I have a rather large number of classes built off of webwork actions. I suspect that there are many other webwork users in the same boat. Now, some of these users are hobbyists and don't mind tinkering about for fun and spending a few days porting their apps to xwork so they can be on the cool side of the fence again. However, I suspect many of these users are in the same situation I'm in, and do not look forward to changing all their existing code to support a new API that after all is said and done, ends up doing pretty much the same things they always did without much in the way of advantages.
I wrote this mainly in response to the switch to Maps from ThreadLocals. All things being equal, I couldn't care less which is used. However, given the lack of strong reasons for either case, my vote very strongly goes towards keeping things the same. xwork is supposed to be a better, easier more configurable version of webwork for all its users, not the patrickization of webwork.
On Saturday, January 11, 2003, at 03:20 PM, Patrick Lightbody wrote:
No one is going to make it unpleasant... you can be sure of that. It'll be
easier and more pleasant for everything. If you look at the CVS, I think
you'll agree. Today I'm going to put in an Interceptor that reads a
components.xml file, which contains a list of "components", and pulls three
things from the file:
------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
