I got an idea today (it was entirely my idea, no one else suggested it first -- hehe, J.O.): What if XWork and WebWork were both developed actively and released as seperate projects? XWork would be the "kernel" for WebWork and would focus entirely on non-web-related stuff. Essentially, it would be be nothing more than a generic command pattern framework as well as a nice lifecycle/IoC system (thanks again, JoeW) similar to Avalon. But the point is that it'd be small. In fact, I built this in sandbox and it came out to 1500 lines of code and only 32KB as a jar file.
Then there would be WebWork, which would include a ServletDispatcher, better configuration settings for the web, and a huge amount of focus on the the taglibs and macros for JSP and Velocity. This would include Jasper Reports stuff as well, and all that jazz. And of course, WebWork 2.0 would depend on XWork 1.0 (which, as stated above, would be a tiny jar file)
I think that this would solve the complaints of both parties ("it won't be web-specific enough" and "it won't be generic enough") and would allow for both projects to bloom in the direction that they should. I don't think that this is a far-fetched idea. In fact, I know it's possible and I think it'll work out well. I've already made a WebWork subdirectory in the sandbox CVS module and moved the web-specific stuff of XWork in there.
Any thoughts?
11:34:14 PM
|
|