4.4.4.2.How DataService works: Extracts from ItsBaseServlet
Similar to the Dispatcher in the Spring framework, ItsBaseServlet extends HttpServlet and via the doPost() method passes control to a proper service-action class.

ItsBaseServlet also implements ServletContextListener and HttpSessionListener interfaces, which makes this class responsible for initialization of application parameters, when application starts and for handling events of creation and destroy of a user session.


/**

 * This class inits configuration parameters defined in web.xml (ServletContext)

 * Must implement contextInitialized() and contextDestroyed() as beginning and ending of the application

 * Must implement sessionCreated() and sessionDestroyed() as beginning and ending of a user session

 * Overrides doGet() and doPost() of the servlet and via the doPost()

 * Reads request parameters, including action, and calls a proper the action class - service

 * @author Jeff Zhuk

 */

public class ItsBaseServlet extends HttpServlet implements ServletContextListener, HttpSessionListener {

	public static String appName; // the name of the project

	public static String pathToDeploy; // path to the directory where the project is deployed

	// protected to allow creation sub-classes that will inherit 

	// these hard-coded values can be instead defined in the web.xml

	protected String actionPackageName = "com.its.webactions."; // the name of the package for actions

	protected String jspPath = "/jsp"; // the path to the folder with Java Server Pages called from actions

	protected String urlPattern = "Lookup"; // url pattern provided in the web.xml for servlets

	// more parameters

	

	/**

	 * contextInitialized() is called automatically by a Servlet container (Tomcat) on application start

	 * @param ServletContextEvent - passed automatically to the method

	 */

	@Override

	public void contextInitialized(ServletContextEvent sce) {

		ServletContext context = sce.getServletContext(); // context is a map with web.xml parameters

		appName = context.getInitParameter("appName");

		pathToDeploy = context.getInitParameter("pathToDeploy");

		// retrieve more parameters

		

		

	}

	/**

	 * The contextDestroyed() method is called on application exit

	 * @param ServletContextEvent - passed automatically to the method

	 */

	@Override

	public void contextDestroyed(ServletContextEvent sce) {

		// usually closing DB pool and other cleaning actions

	}

	/**

	 * The sessionCreated() method is called by a Servlet container when a user starts a session

	 * @param HttpSessionEvent - passed automatically to the method

	 */

	@Override

	public void sessionCreated(HttpSessionEvent arg0) {

		// TODO: usually store user data

		

	}

	/**

	 * The sessiontDestroyed() method is called when session expired (timeout) or session.invalidate() is called

	 * @param HttpSessionEvent - passed automatically to the method

	 */

	@Override

	public void sessionDestroyed(HttpSessionEvent hse) {

		// TODO: usually storing session data to a DB

	}

The major part of the work done by this class is getting a request and passing control to a proper service-action class.
How this is done?

The request can come as a URL or link, which means via the HTTP GET method.
The request can also be sent as a web form, via the HTTP POST method.
Anyway, the program should parse the request, find parameters and pass control to a service.
This happen in the doPost() method.
If the request comes to the doGet() method as a URL, it will be directed still to the doPost() method for processing.


	/**

	 * @see HttpServlet#doGet(HttpServletRequest request, HttpServletResponse

	 *      response)

	 */

	protected void doGet(HttpServletRequest request,

			HttpServletResponse response) throws ServletException, IOException {

             doPost();

        }

Was it clear so far? Highlight the text in question Or

In the doPost() method, the program is looking for the action parameter.
This is the naming agreement in the Data Service framework.
The action parameter defines the service to be called.
For example, in the URL http://itofthefuture.com/BASE/Lookup?action=content, the action value is content and according to the naming agreement, the name of the service class is ContentAction.

All action classes must implement the BaseAction interface.
This implementation allows us to use polymorphism and call any service universally with two lines:
BaseAction service = (BaseAction) Class.forName(actionPackageName + serviceName).newInstance();
// each service-action must implement the BaseAction with the run method
// run the service, which usually generates important data and returns the name of a jsp
String[] serviceResults = service.run(request, response);

The service will return the name of the JSP page to present the data generated by the service.


	/**

	 * @see HttpServlet#doPost(HttpServletRequest request, HttpServletResponse

	 *      response)

	 */

	protected void doPost(HttpServletRequest request,

			HttpServletResponse response) throws ServletException, IOException {

		HttpSession session = request.getSession();

		// reading parameters

		String action = request.getParameter("action"); // the first part of the service name

		if (action != null) {

// the name of the service class, for example, for the "content" action must be ContentAction

			String serviceName = action + "Action"; 

			// make sure that it starts with the upper case

			serviceName = serviceName.substring(0,1).toUpperCase() + serviceName.substring(1);

			try {

				// create a new service object

				BaseAction service = (BaseAction) Class.forName(actionPackageName + serviceName).newInstance();

				// each service-action must implement the BaseAction with the run method

				// run the service, which usually generates important data and returns the name of a jsp

				String[] serviceResults = service.run(request, response);

				// check if the first String is the name of a JSP

				String pageName = serviceResults[0];

				if(pageName != null && pageName.endsWith(".jsp")) {

					RequestDispatcher rd = request.getRequestDispatcher(jspPath + "/" + pageName);

					rd.forward(request, response);	

				}

			} catch (Exception e) {

				System.out.println("ERROR: service="+serviceName+" e=" + e);

			}	

		}

	}

}

One pre-requisite is to create all service-classes as implementations of the BaseAction interface with the names that consist of the action name and the �Action� word at the end. So, the name of the service class, for example, for the "content" action, must be ContentAction.
Here is a very simple BaseAction interface, which requires to implement the run() method.


public interface BaseAction {

	public String[] run(HttpServletRequest request, HttpServletResponse response) throws Exception;

}

Assignments:
1. In Eclipse create a new Dynamic Web project 4.4.4.2.ItsBaseServlet
2. In the project WebContent/WEB-INF � create the web.xml file
3. Add to the file context-param sections with the parameters that are listed in the source above.
4. Add to the file the listener and servlet sections, check the sample from the previous lesson.
5. In the project Java Resource � src add the package com.its.util
6. Add to the package the BaseAction interface.
7. Add to the package the class ItsBaseServlet and provide (copy/paste or better type) the content above, including doGet(), doPost() and other methods, (you might need to fix red lines if any)
8. Reminder: to import necessary libraries just press CTRL-SHIFT-O (character o, not zero)
9. Make sure that necessary jar files are in the WebContent/WEB-INF/lib (check in the previous projects)
10. Make sure that the project works locally and send the project sources as a zip file (src and WebContent with web.xml, jsp, js, css, and whatever sources needed) to dean@ituniversity.us.
11. Create 4 QnA and send to dean@ituniversity.us

/** * This class inits configuration parameters defined in web.xml (ServletContext) * Must implement contextInitialized() and contextDestroyed() as beginning and ending of the application * Must implement sessionCreated() and sessionDestroyed() as beginning and ending of a user session * Overrides doGet() and doPost() of the servlet and via the doPost() * Reads request parameters, including action, and calls a proper the action class - service * @author Jeff Zhuk */ public class ItsBaseServlet extends HttpServlet implements ServletContextListener, HttpSessionListener { public static String appName; // the name of the project public static String pathToDeploy; // path to the directory where the project is deployed // protected to allow creation sub-classes that will inherit // these hard-coded values can be instead defined in the web.xml protected String actionPackageName = "com.its.webactions."; // the name of the package for actions protected String jspPath = "/jsp"; // the path to the folder with Java Server Pages called from actions protected String urlPattern = "Lookup"; // url pattern provided in the web.xml for servlets // more parameters /** * contextInitialized() is called automatically by a Servlet container (Tomcat) on application start * @param ServletContextEvent - passed automatically to the method */ @Override public void contextInitialized(ServletContextEvent sce) { ServletContext context = sce.getServletContext(); // context is a map with web.xml parameters appName = context.getInitParameter("appName"); pathToDeploy = context.getInitParameter("pathToDeploy"); // retrieve more parameters } /** * The contextDestroyed() method is called on application exit * @param ServletContextEvent - passed automatically to the method */ @Override public void contextDestroyed(ServletContextEvent sce) { // usually closing DB pool and other cleaning actions } /** * The sessionCreated() method is called by a Servlet container when a user starts a session * @param HttpSessionEvent - passed automatically to the method */ @Override public void sessionCreated(HttpSessionEvent arg0) { // TODO: usually store user data } /** * The sessiontDestroyed() method is called when session expired (timeout) or session.invalidate() is called * @param HttpSessionEvent - passed automatically to the method */ @Override public void sessionDestroyed(HttpSessionEvent hse) { // TODO: usually storing session data to a DB }

/** * @see HttpServlet#doGet(HttpServletRequest request, HttpServletResponse * response) */ protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { doPost(); }

/** * @see HttpServlet#doPost(HttpServletRequest request, HttpServletResponse * response) */ protected void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { HttpSession session = request.getSession(); // reading parameters String action = request.getParameter("action"); // the first part of the service name if (action != null) { // the name of the service class, for example, for the "content" action must be ContentAction String serviceName = action + "Action"; // make sure that it starts with the upper case serviceName = serviceName.substring(0,1).toUpperCase() + serviceName.substring(1); try { // create a new service object BaseAction service = (BaseAction) Class.forName(actionPackageName + serviceName).newInstance(); // each service-action must implement the BaseAction with the run method // run the service, which usually generates important data and returns the name of a jsp String[] serviceResults = service.run(request, response); // check if the first String is the name of a JSP String pageName = serviceResults[0]; if(pageName != null && pageName.endsWith(".jsp")) { RequestDispatcher rd = request.getRequestDispatcher(jspPath + "/" + pageName); rd.forward(request, response); } } catch (Exception e) { System.out.println("ERROR: service="+serviceName+" e=" + e); } } } }