> A little poll: As long as you are aware that any result from this poll is basically meaningless I'm fine with this. It was pretty obvious last time this type of thing was asked on the mailing list (URLTag) and it was acted on the result, that the response that was given was grossly misleading. Better safe then sorry, should be a design goal within OS just as minimising surprise is :P
Now, to answer this myself: > *) How many have actions that are used with more than one kind of > dispatcher? I have at least two actions I want to execute also from a command line. > *) How many are using WebWork in Swing apps? Not me, but I'd never touch Swing. I have from time to time considered using actions from SWT though. In my opinion, the only really solid argument for using WW over say Struts is that we are not locked up in a certain environment. I firmly believe that the core parts of XW can easily avoid being tied up to servlets, as WW does now. Note that this doesn't mean that the XW-servlet package, if you will, will be a lot easier to work with due to a number of features that simplify development. Drawing a line where servlet code can start in XW is very important, and since you don't really need to include ALL of XW in non-servlet code (after all you can't) this line doesn't need to be drawn so that the design is hampered in any way. The line is just so we can point to it and say: if you want to port this app to a non-servlet system don't cross this. Anders Hovmöller [EMAIL PROTECTED] http://boxed.killingar.net ------------------------------------------------------- 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
