RE: JSP and MVC (newbie question)

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

Well, in my case I don't actually write servlets anymore.  I have a
standard servlet that looks something like this (depending on the
application):

import java.io.*;
import javax.servlet.*;
import javax.servlet.http.*;

public class CSServlet extends HttpServlet implements CSConstants {

  public void doGet(HttpServletRequest req, HttpServletResponse res)
    throws ServletException, IOException
  {
    CSSession.createSession(this, req, res);
  }
  
  public void doPost(HttpServletRequest req, HttpServletResponse res)
    throws ServletException, IOException
  {
    CSSession.process(req, res);
  }
}

A GET invokes CSSession.createSession (this happens to be an example
taken from my standard Client/Server architecture).  This static method
creates a non-multi-threaded object which extends CSSession and acts as
a servlet proxy.  From that point on, every input from the user is a
POST.  CSSession.process is a convenience method which passes the POST
request through to the appropriate session object.

With this architecture, all of my application work is done in subclasses
using standard Java programming techniques.  Doing everything in a JSP
is sort of counter-productive, since most IDEs don't treat a JSP as a
class.  Instead, I want to take advantage of all the goodies a Java IDE
like WDSC is going to give me, such as refactoring.

Joe


> From: Kelly Cookson
> 
> But why would reuse and deployment be an issue? How
> could a servlet be reused in a way that a JSP with
> pure JSP tags and Java code could not? How would using
> JSPs as a controll cause problems with deployment?