Am Mittwoch, 27. August 2003 17:21 schrieb Campano, Troy: I think Dan Wells already mentioned all the necessary aspects and though we're using Struts instead of Tapestry, there's nothing to object. Indeed, it's more kind of an architectural issue, as JSPs get compiled to servlets anyway. Following the MVC2 design idiom (among others), JSPs are best for the View role and should be as dumb as possible IMHO, while the Front Controller -> Service To Worker parts (which don't directly present anything on the client tier) are generally better suited for servlets. This part is more or less handled by Struts already, which allows for declarative configuration via an XML file and relieves some of the major pains of dealing with the HTTP protocol, too. Struts delegates the request to Struts Actions, which are basically normal Java classes forming the interface to the Model. 'Below' Struts and the web tier, there usually comes a lot of additional complexity plus several additional layers, and things should no longer be web-related in any kind at this stage. Note that the lifespan of Business Logic and Persistence in particular is much longer than that of the web tier which may be gone tomorrow and be replaced by something more powerful, who knows? Apart from that, calling Java classes direcly may lead to significant thread issues, bottlenecks or transaction problems, and I generally wouldn't recommend this approach. Same is true for 'direct-linking' the web tier to EJBs, I'm afraid.
HTH, -- Chris (SCPJ2) NB. Note that the existence of JSPs at all stems from the fact that pure servlets proved to be not too well-suited for visual output, but are powerful nonetheless when it comes to other tasks, such as delivering something other than just ordinary text (including HTML, WML and the like). > I'm curious as to what the reason is to use Servlets. > I write straight java class/methods and call them from my JSP. > My business logic goes into these classes. > > JSP handles the interface and handles request/response. > Usually I guess it's a Servlet that handles the request/response but > it seemed to me like an added extra step. > I didn't really see what I was gaining by using a Servlet. > > So I'm curious of what the point of Servlets are....is there > something they give you that JSP doesn't? > So I know I'm missing something....why use Servlets? > > Thank you for your responses! > > ~ t r o y ~ > > Troy Campano > IAS Database Management > Liberty Mutual > (603) 245 4092 > [EMAIL PROTECTED] > > > > ===================================================================== >====== To unsubscribe: mailto [EMAIL PROTECTED] with body: > "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with > body: "set JSP-INTEREST DIGEST". > > Some relevant archives, FAQs and Forums on JSPs can be found at: > > http://java.sun.com/products/jsp > http://archives.java.sun.com/jsp-interest.html > http://forums.java.sun.com > http://www.jspinsider.com =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant archives, FAQs and Forums on JSPs can be found at: http://java.sun.com/products/jsp http://archives.java.sun.com/jsp-interest.html http://forums.java.sun.com http://www.jspinsider.com
