> From: Anthony W. Marino [mailto:[EMAIL PROTECTED]] > > I found some emails with you and Husted discussing the potential of > merging > with Struts ( > http://www.mail-archive.com/struts-user@jakarta.apache.org/msg22749.html ). > Do you see that as a potentially happening ??? Would that be much > different > than the Struts/stxx layering???
It would be dramatically different than the Struts/stxx layering, which is very limited and does not offer orthogonality with other view types. I'll keep poking every now and then. I would be happy to contribute the Maverick code (with integration, of course) as Struts 2.0 and continue working on it there. That may sound arrogant given that we are a small community and they are a large one, but at this point I think Maverick is pretty close to a 100% superset of Struts features, and we offer a *lot* more. That said, I doubt Maverick-as-Struts-2.0 will ever happen, simply because of Not Invented Here. There is a small chance that they might become interested as they bump into the limits of the existing Struts architecture, but it'll be a hard sell. I'm not myself an Apache committer, although I'm moderately active in some of the communities. I know some of the Jakarta people personally, but none of the Struts folk. Other than trolling on their mailing lists, I don't have any inroads. The first thing that would have to happen to at least make the sell reasonable is that I (or someone) would have to write a Struts integration layer. This would be a ControllerSingleton base class that *exactly* mimics the Struts Action API. When Struts applications run without recompilation on Maverick, that might raise some eyebrows. There is the issue of the Struts tag library, but I think that will go away as JSTL replaces it. I consider the Struts tags more or less already to be obsolete. On the other hand, it's very possible to write a Maverick ViewFactory that builds Struts views... Maybe there is a week of work here, but since I don't need it myself, and nobody has asked for it, it hasn't been done. I suppose the other question is - if it were possible to merge Struts and Maverick, would the existing Maverick community want this? There is a risk that trying to integrate with Struts could produce something that is definitely not Maverick; there is a little bit of an "everything including the kitchen sink" attitude in that community. The fact that they have database connection pooling code in the framework is bewildering. Why on earth... Jeff Schnitzer [EMAIL PROTECTED] _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ Mav-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mav-user Archives are available at http://www.mail-archive.com/
