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
