I've been giving this idea of mav merging with struts some thought and while I agree with Jeff's doubt that "Maverick-as-Struts-2.0 will ever happen, simply because of Not Invented Here" is almost definitely true, I still think it may be worthwhile to try and find a way to move mav to jakarta. If for no other reason, moving mav to jakarta will give maverick major street cred and almost assuredly boost its user base, and as we all know, a strong user base is the life blood of an open source project. There are a lot of organizations that would immediately be willing to consider maverick if it had the apache stamp of approval.
I think its pretty clear that replacing struts with mav is an impossibility, and merging it would probably lead to a political mess. I don't think its odd to propose that the two live side-by-side, however. I think the arguement could be made that the two are not mutually exclusive. I personally feel that with its shunting and transforming abilities, mav's major strength is as a presentation framework, while one could argue that Struts is primarily an application framework. While it does offer some application framework functionality, mav has been specifically built to be pluggable, so as Jeff points out, it should be possible to build a "ControllerSingleton base class that *exactly* mimics the Struts Action API. When Struts applications run without recompilation on Maverick, that might raise some eyebrows." I think the fact that struts can run inside maverick is a strong mark in our favor that the two can exist simultaneously as separate projects within the same organization without necessarily stepping on each other's toes. Any thoughts, --jim ------------------------------------------------------- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ Mav-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mav-user Archives are available at http://www.mail-archive.com/
