The question is, which part? I can identify three discrete pieces of an MVC framework which could conceivably be mixed and matched: 1) The controller/action part, including bean population, form validation, etc. 2) The view part, including jsp taglibs and (for Maverick) transformation, etc. 3) The core, which basically covers everything else. In particular, it includes the Dispatcher/ActionServlet, the configuration file, and how the components are put together. Which parts of Maverick do you want to work with which parts of Struts? A lot of interoperability with Struts is possible if you use the Maverick core. It is even possible (although I haven't tried it yet) to use Struts Actions and Struts views (with their own JSP taglibs), getting transforms, shunting, and the flexible config file from Maverick. This would require building fairly simple implementations of the ControllerSingleton base class and ViewFactory. Struts however is not very modular, so if you need to use the Struts core (including their ActionServlet), I don't know what you can do. You're going to have a rough time with XSLT, too, because it'll be very difficult to get more than a single transform configured. Jeff Schnitzer [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> -----Original Message----- From: Ed Ward Sent: Sat 4/20/2002 9:31 AM To: [EMAIL PROTECTED] Cc: Subject: [Mav-user] Maverick to Struts Hi, Hold on to your hats whilst I ask what might sound a really dumb question. How easy is it to wrap a Maverick application with Struts? The reason I ask... The client I'm working for recently made an announcement that all their future webapps will be developed with Struts :-(( I did what I could to make them see the error of their ways, but AFAIK they haven't even taken a brief look at Maverick and the lead architect hadn't even put a working Struts app together when the decision was communicated! I don't have much knowledge of Struts myself, hence the question. Suffice it to say I'd still like to rework our UI using Maverick and XSLT, but now I have to consider the implications of my client's Struts requirements. The presentation layer of the app I'm working on requires extensive rework to enable it to use either Maverick or Struts, but I've already started rewriting with Maverick in mind. Any advice as to how I can keep the client's Struts fans happy and not lose my changes based on the use of Maverick? My guess is that it's going to be easier port a Struts application to Maverick than the other way around. Ed. _______________________________________________ Mav-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mav-user
<<winmail.dat>>
