Code encapsulation Format for the Servlet+jdbc+javabean development system

I gave this architecture to replace the SSH architecture for project development

Some common classes are put in the common

There are some processing of the data in DAO

Entity is actually JavaBean

The service is put in some abstract class, simply speaking, abstract class is some interface, so-called interface is only " method name, plus a semicolon ".

1  PackageCom.ll.www.mis.service;2 3 Importjava.io.IOException;4 Importjava.util.List;5 6 Importjavax.servlet.ServletException;7 Importjavax.servlet.http.HttpServletRequest;8 ImportJavax.servlet.http.HttpServletResponse;9 Ten  Public InterfaceIOrderService { One      A     Public voidSelectAll (HttpServletRequest request, httpservletresponse response)throwsservletexception, IOException; -       -     Public voidSelectbypar (HttpServletRequest request, httpservletresponse response)throwsservletexception, IOException; the     -     Public voidSave (HttpServletRequest request, httpservletresponse response)throwsservletexception, IOException; -     -     Public voidUpdate (HttpServletRequest request, httpservletresponse response)throwsservletexception, IOException; +     -     Public voidDelete (HttpServletRequest request, httpservletresponse response)throwsservletexception, IOException; +  A}

View Code

Service.imp Implement these interfaces

The servlet is similar to the action of struts in SSH.

It feels good to encapsulate the code in this architecture.

Code encapsulation Format for the Servlet+jdbc+javabean development system