Adam Hardy wrote:
So struts marshalls the HTTP request params into a form bean and perhaps
validates them.
Also struts interfaces with the model when it calls business methods
from action classes.
But for Ajax requests then there is only ever one possible actionForward
(or 2 if you count a glob
So struts marshalls the HTTP request params into a form bean and perhaps validates them.
Also struts interfaces with the model when it calls business methods from action classes.
But for Ajax requests then there is only ever one possible actionForward (or 2 if you count a global error). I can't
I think that the controller is always going to be in struts. There
reason is this - the action will be obtaining some input, coordinating
with the back-end services, retrieving the model to be rendered and then
rendering the model into a view which could be HTML or XML/JSON which is
more "ajax
I've recently used AJAX in some existing Struts applications making use
of AjaxTags http://ajaxtags.sourceforge.net/. The Struts controller is
still very much applicable, in that the Ajax requests are made to struts
action urls, the action subclasses then delegate processing to business
objects
I have only a small knowledge of the Ajax frameworks out there and I am trying
to work out how much an Ajax app would depend on Struts.
I assume the view in an Ajax app is handled at the initial request by a JSP with HTML and that afterwards every request from the browser is XHR, ideally broken
5 matches
Mail list logo
