Skip to main content

Implementing MVC from scratch

For simple and moderately complex applications,  implementing MVC from scratch with RequestDispatcher is straightforward and flexible.

The most important point about MVC is the idea of separating the business logic and data access layers from the presentation layer.  Here is a quick summary of the required steps:
1. Define beans to represent the data.
Beans are just Java objects that follow a few simple conventions. Your first step is define beans to represent the results that will be presented to the user
2. Use a servlet to handle requests.
In most cases, the servlet reads request parameters(shorthand using BeanUtils.populateBean)
e.g.
3. Populate the beans. The servlet invokes business logic(application-specific code) or data-access code to obtain the results. The results are placed in the beans that were defined in step 1.

e.g.
ValueObject value = new ValueObject(...);
HttpSession session = request.getSession();
session.setAttribute("key", value);

Next, the servlet would forward to a JSP page that uses the following
to retrieve the data:
<jsp:useBean id="key" type="somePackage.ValueObject"
scope="session" />

4. Store the bean in the request, session , or servlet context. The servlet calls setAttribute on the request , session , or servlet context objects to store a reference to the beans that represent the results of the request.

5. Forward the request to a JSP page. The servlet determines which JSP page is appropriate to the situation and uses the forward method of RequestDispatcher to transfer control to that page.
e.g.

String operation = request.getParameter("operation");
if (operation == null) {
operation = "unknown";
}
String address;
if (operation.equals("order")) {
address = "/WEB-INF/Order.jsp";
} else if (operation.equals("cancel")) {
address = "/WEB-INF/Cancel.jsp";
} else {
address = "/WEB-INF/UnknownOperation.jsp";
}
//RequestDispatcher: Defines an object that receives requests from the clicent and sends them to any //resource(such as a servlet, HTML file , or JSP file) on the server. The servlet container creates the //RequestDispatcher object, which is used as a wrapper around a server resource located at a particular //path or given by a particular name.
RequestDispatcher dispatcher =
request.getRequestDispatcher(address);
dispatcher.forward(request, response);
// in JSp, you can use <jsp:forward page="<%= destination %>" />


6. Extract the data from the beans. the JSP page accesses beans with jsp:useBean and a scope matching the location of Step 4. The page then uses jsp:getProperty to output the bean properties. The JSP page does not create or modify the bean; it merely extracts and displays data that the servlet created.
e.g.

<jsp:useBean id="key" type="somePackage.SomeBeanClass"
scope="session" />

Comments

Popular posts from this blog

Stretch a row if data overflows in jasper reports

It is very common that some columns of the report need to stretch to show all the content in that column. But  if you just specify the property " stretch with overflow' to that column(we called text field in jasper report world) , it will just stretch that column and won't change other columns, so the row could be ridiculous. Haven't find the solution from internet yet. So I just review the properties in iReport one by one and find two useful properties(the bold highlighted in example below) which resolve the problems.   example:
<band height="20" splitType="Stretch"> <textField isStretchWithOverflow="true" pattern="" isBlankWhenNull="true"> <reportElement stretchType="RelativeToTallestObject" mode="Opaque" x="192" y="0" width="183" height="20"/> <box leftPadding="2"> <pen lineWidth="0.25"/> …

JasperReports - Configuration Reference

Live - solving the jasper report out of memory and high cpu usage problems

I still can not find the solution. So I summary all the things and tell my boss about it. If any one knows the solution, please let me know.


Symptom: 1.The JVM became Out of memory when creating big consumption report 2.Those JRTemplateElement-instances is still there occupied even if I logged out the system
Reason:         1. There is a large number of JRTemplateElement-instances cached in the memory 2.The clearobjects() method in ReportThread class has not been triggered when logging out
Action I tried:      About the Virtualizer: 1.Replacing the JRSwapFileVirtualizer with JRFileVirtualizer 2.Not use any FileVirtualizer for cache the report in the hard disk Result: The japserreport still creating the a large number of JRTemplateElement-instances in the memory     About the work around below,      I tried: item 3(in below work around list) – result: it helps to reduce  the size of the JRTemplateElement Object                Item 4,5 – result : it helps a lot to reduce the number of  JRTemplateE…