Quoting Joe Germuska <[EMAIL PROTECTED]>: > I don't think I'm going to articulate this question very clearly, but > hopefully my drift will be gotten, so to speak. > > If we're talking about making Struts independent of Servlets, then > what part of Struts would depend on either Servlet 2.3 or Servlet 2.4? >
Even if the core framework is independent of the presentation tier APIs, you still need an adapter layer (often called a binding) between the particular presentation API in use and the fundamental controller capabilities. As I pointed out in a previous message, I can see three very obvious bindings (to servlets, to portlets, and to SOAP) that we'd undoubtedly want to include in the basic package -- but we know we've succeeded when you can use the same actions in each of those three environments (to perform the same transaction). > Rather, how will we partition Struts so that we know our boundaries? > Presumably in a chain-like world, you could have Servlet 2.3 > pre-processing chains and Servlet 2.4 pre-processing chains, and of > course we're going to have view post-processors for XSLT, Velocity... > so why shouldn't there be JSP 1.2 and JSP 2.0 post-processors? > For servlet 2.3 versus 2.4, one approach to building frameworks would be to architect the controller as a filter (or set of cooperating filters) rather than as a servlet. That is not a practical reality in servlet 2.3 because you can't interpose filters on a RequestDispatcher call. It's probably feasible to have a decomposed request processor that can be implemented as either a set of filters (which, after all, is sort of the CoR pattern again, just with different APIs) or as a servlet. In practical terms, though, it's easier to abstract the layers if we stick with a servlet as the basic adapatation gadget. The main reason I'm interested in J2EE 1.4 as the base platform is for JSP 2.0. But the choice between JSP 1.2 and JSP 2.0 should have zero impact on the organization of the request processor -- it should be as totally an independent decision as possible. However, if you choose JSP 2.0 for the minimum platform for JSP-based presentation stuff, you get servlet 2.4 for free to use in the controller tier if you want. > I suppose we ought to draft a glossary to make sure we all agree on > these various concepts... > > Joe > Craig --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
