I’ve been reviewing the Maverick code base and was wondering how difficult it would be to tailor it to web services.

 

I need to integrate a MVC framework _behind_ a SOAP web service interface to be used in building applications.  Basically, requests come into the web service with parameters, the web service processes the request and returns a response.  The response contains a String of xml, html, etc.  For arguments sake, lets say the interface is:

 

Response process(Request req);

 

So, it’s very similar to the service method in a servlet, but the result is returned instead of being included as an argument.  The Request and Response objects are not servlet related, but they are similar.  I want the MVC framework to dispatch the req to the proper Command based on a command parameter in the request (or something similar), possibly chain commands, and then load views/transforms all based on a config file.  Maverick seems to be a perfect fit, although it seems to be fairly tied to a servlet container.

 

So basically I want a MVC architecture totally independent from a web container (i.e. no HttpServletResponse references, no ServletContext references).  I was hoping someone experienced with the Maverick code base could give me some estimate on the difficulty I would encounter modifying Maverick to work in this environment.  Or if you know of other libraries I could use that would be great.  I’ve looked at Struts, WebWork, and Maverick.  Since Maverick seems to be the simplest, I thought I would start there.  I’m looking for something along the lines of the XWork project at OpenSymphony, but unfortunately that project is not yet stable.   Thanks!

-Brian

 

Reply via email to