LOVELY PROFESSIONAL UNIVERSITY

HOME WORK – I
DOA: 9/7/2012 DOS: 9/17/2012

-------------------------------------------------------------------------------------------------------------------

Assignment

COURSE- Modern Web Programming Tools and Techniques-I

COURSE CODE- CAP618T

SUBMITTED BY: SUBMITTED TO:

Anil Kumar MANDEEP KAUR

Roll-A11

Reg. - 11009839

Sec- D1R05

Q:1 Take a JavaBean Object named “Profession” with properties domain and expertise. Show the use of all 4 scope types on this object.

Ans:

Profession.jsp file

package pk;

public class profession

{

int domain;

int expertise;

public int getdomain()

{

return domain;

}

public void setdomain(int a)

{

this.domain=a;

}

public int getexpertise()

{

return expertise;

}

public void setexpertise(int b)

{

this.expertise=b;

}

}

1) Index.jsp file(for session Object)

2) Index.jsp file(for Page Object)

3) Index.jsp file(for Request Object)

4) Index.jsp file(for Application Object)

Q:2 Discuss and Demonstrate the use of all page directive attributes. Give minimum 2 separate types of examples for each attribute, to make it clear that how that attribute is effecting output.

Ans:

Page directive attributes are:

|Attribute |Purpose |
|buffer="none|size in kb" |This attribute determines whether the output stream is buffered. The default value is 8KB.|
|autoFlush="true|false" |This attribute determines whether the output buffer will be flushed automatically, or |
| |whether it will raise an exception when the buffer is full. The default is true, which |
| |states that the buffer should be flushed automatically. |
|contentType="ctinfo" |Defines the character encoding scheme. |
|errorPage="error_url" |This attribute represents the relative URL to the JSP page that will handle exceptions. |
|isErrorPage="true|false" |This attribute states whether or not the JSP page is an |
| |errorPage. The default is false. |
|Extends=” className" |This attribute defines the parent class that the JSP |
| |generated servlet will extend from. |
|Import=”importlist” |This attribute defines the list of packages that will be |
| |available to this JSP. It will be a comma-separated list of package names. |
|info="text" |This attribute represents information about the JSP pagethat can be accessed by the page's|
| |Servlet.getServlet Info() method. |
|isThreadSafe="true|false" |This attribute tells the JSP engine that this page can service more than one request at a |
| |time. By default this value is true; if false, the SingleThreadModel is used. |
|Language=”scriptinglanguage” |This attribute tells the server what language will be used to compile the JSP file. |
| |Currently Java is the only available language. |
|Session=”true|false” |This attribute determines whether the session data will be available to this page. The |
| |default is true. |
|isELIgnored |Specifies whether or not EL expression within the JSP page will be ignored. |
|isScriptingEnabled |Determines if scripting elements are allowed for use. |

Example:

The buffer Attribute:
The buffer attribute specifies buffering characteristics for the server output response object. We may code a value of "none" to specify no buffering so that all servlet output is immediately directed to the response object or we may code a maximum buffer size in kilobytes, which directs the servlet to write to the buffer before writing to the response object. 1) To direct the servlet to write output directly to the response output object, use the following:
| |

2) Use the following to direct the servlet to write output to a buffer of size not less than 8 kilobytes:
| |
| |
|The autoFlush Attribute: |
|The autoFlush attribute specifies whether buffered output should be flushed automatically when the buffer is filled, or whether|
|an exception should be raised to indicate buffer overflow. A value of true (default) indicates automatic buffer flushing and a |
|value of false throws an exception. The following directive causes the servlet to throw an exception when the servlet's output |
|buffer is full: |
| |
| |
| |
|This directive causes the servlet to flush the output buffer when full: |
| |
| |
|Usually, the buffer and autoFlush attributes are coded on a single page directive as follows: |
| |
| |
|The contentType Attribute: |
|The contentType attribute sets the character encoding for the JSP page and for the generated response page. The default content|
|type is text/html, which is the standard content type for HTML pages. If you want to write out XML from your JSP, use the |
|following page directive: |
| |
| |
|The following statement directs the browser to render the generated page as HTML: |
| |
| |
|The errorPage Attribute: |
|The errorPage attribute tells the JSP engine which page to display if there is an error while the current page runs. The value |
|of the errorPage attribute is a relative URL. The following directive displays MyErrorPage.jsp when all uncaught exceptions are|
|thrown: |
| |
| |
|The isErrorPage Attribute: |
|The isErrorPage attribute indicates that the current JSP can be used as the error page for another JSP. The value of |
|isErrorPage is either true or false. The default value of the isErrorPage attribute is false. |
| |
| |
|The extends Attribute: |
|The extends attribute specifies a superclass that the generated servlet must extend. |
| |
| |
|The import Attribute: |
|The import attribute serves the same function as, and behaves like, the Java import statement. The value for the import option |
|is the name of the package you want to import. |
|To import java.sql.*, use the following page directive: |
| |
| |
|To import multiple packages you can specify them separated by comma as follows: |
| |
| |
|The isThreadSafe Attribute: |
|The isThreadSafe option marks a page as being thread-safe. By default, all JSPs are considered thread-safe. If you set the |
|isThreadSafe option to false, the JSP engine makes sure that only one thread at a time is executing your JSP. |
|The following page directive sets the isThreadSafe option to false: |
| |
| |
|The language Attribute: |
|The language attribute indicates the programming language used in scripting the JSP page. |
|For example, because you usually use Java as the scripting language, your language option looks like this: |
| |
| |
|The session Attribute: |
|The session attribute indicates whether or not the JSP page uses HTTP sessions. A value of true means that the JSP page has |
|access to a builtin session object and a value of false means that the JSP page cannot access the builtin session object. |
|Following directive allows the JSP page to use any of the builtin object session methods such as session.getCreationTime() or |
|session.getLastAccessTime(): |
| |
| |
|The isScriptingEnabled Attribute: |
|The isScriptingEnabled attribute determines if scripting elements are allowed for use. The default value (true) enables |
|scriptlets, expressions, and declarations. If the attribute's value is set to false, a translation-time error will be raised if|
|the JSP uses any scriptlets: |
| |
| |
| |
| |

Q:3 Create a self description form with at least 5 detail fields. Write a program which handles an error of unfilled information in any of the text boxes. Also 2 out of these 5 fields have a minimum character limit. If user enters characters less than that of limit, then exception to be thrown and handled.

Ans:

1) Form.jsp

To create a form for processing..

JSP Page

Login form

First name:

Last name:

Age:  

Phone no:

Password:

Email_Id=

Output:

[pic]

Validation that are used are:

1) First Name –It is required field and it should not be empty.

2) Phone no- phone no should not be less than 10 digits.

3) Password - Password should not be less than 3 character.

2) Process.jsp

This form contain the processing part.

JSP Page

First Name:

Last Name:

Password:

Email_id:

Phone no:

3) Exception.jsp

This form is used to inform user about the exception that occurred in the program.

JSP Page

Error:

Q:4 Implement the subclass and superclass concept in JSP by taking a superclass “calculate”. The values of calculation are to be accepted from user using a form. Perform at least 6 calculations except plain arithmetic calculations. And use these methods in sub class.

Ans 4:

1) Servlet Code(Base class):

package anil;

import javax.servlet.*;

import java.io.IOException;

import java.io.PrintWriter;

import javax.servlet.ServletException;

import javax.servlet.annotation.WebServlet;

import javax.servlet.http.HttpServlet;

import javax.servlet.http.HttpServletRequest;

import javax.servlet.http.HttpServletResponse;

import javax.servlet.http.*;

import javax.servlet.jsp.HttpJspPage;

import java.io.*;

import java.util.*;

/**

*

* @author Anil-PC

*/

@WebServlet(name = "calculate", urlPatterns = {"/anil"})

public abstract class calculate extends HttpServlet implements HttpJspPage

{

private ServletConfig config;

int a,b,c;

final public void init(ServletConfig config)

throws ServletException {

this.config = config;

jspInit();

}

final public ServletConfig getServletConfig() {

return config;

}

final public void service(HttpServletRequest request, HttpServletResponse response)

throws ServletException, IOException {

_jspService(request, response);

}

abstract public void _jspService(HttpServletRequest request,

HttpServletResponse response)

throws ServletException, IOException;

final public void destroy() {

jspDestroy();

}

public int areasquare(HttpServletRequest request) {

a=Integer.parseInt(request.getParameter("t1"));

return a*a;

}

public int rectangle(HttpServletRequest request) {

b=Integer.parseInt(request.getParameter("t2"));

c=Integer.parseInt(request.getParameter("t3"));

int r;

r=1/2(b*c)

return b ;

}

public int circle(HttpServletRequest request) {

a=Integer.parseInt(request.getParameter("t1"));

int r;

r=3.14*a*a;

return a;

}

public double division(HttpServletRequest request) {

a=Integer.parseInt(request.getParameter("t1"));

b=Integer.parseInt(request.getParameter("t2"));

return a/b;

}

public double moduls(HttpServletRequest request) {

a=Integer.parseInt(request.getParameter("t1"));

b=Integer.parseInt(request.getParameter("t2"));

int d=a%b;

return d;

}

public String getServletInfo() {

return new String("Anil");

}

}

2) Form code:

[pic]

3) form process(Derived class):

Operation that are used :

1) Area of square

2) Area of rectangle

3) Area of circle

4) Division

5) Modulus

Q:5 Discuss Working, features, advantages and disadvantage of Tow-tier and Three Tier Database Access Models.

Working:

Two tier architecture means:
Client server application. Client acts as Front End and Server acts as Backend like databases.
The two-tier architecture is like client server application. The direct communication takes place between client and server. There is no intermediate between client and server.
Two tier architectures consist of three components distributed in two layers: client (requester of services) and server (provider of services). The three components are: 1) User System Interface (such as session, text input, dialog, and display management services) 2) Processing Management (such as process development, process enactment, process monitoring, and process resource services) 3) Database Management (such as data and file services)
So, in client application the client writes the program for saving the record in SQL Server and thereby saving the data in the database.

[pic]

Three tier Architecture Means:
Three tier architecure means N tier architecture like Yahoo , gmail, and or Web Applications. Having Number of Users or Customers or Clients.

[pic]

Three tier architecture having three layers. They are 1. Client layer 2. Business layer 3. Presentation layer
Client layer:
Here we design the form using textbox, label,button,etc.

Business layer:
Business tier provides the business services. This tier contains the business logic and the business data. All the business logic is centralised into this tier as opposed to 2-tier systems where the business logic is scattered between the front end and the backend. The benefit of having a centralised business tier is that same business logic can support different types of clients like browser, WAP, other stand-alone applications etc.
| |
| |

Presentation layer:
Presentation tier encapsulates the presentation logic required to serve clients. A Servlet or JSP in the presentation tier intercepts client requests, manages logons, sessions, accesses the business services, and finally constructs a response, which gets delivered to client.

Advantages and disadvantages of three-tier:

1) The three tier software architecture emerged to overcome the limitations of the two tier architecture.

2) The third tier is between the user interface and the data management components. This middle tier provides process management where business logic and rules are executed and can accommodate hundreds of users by providing functions such as queuing, application execution, and database staging.

3) The three tier architecture is used when an effective distributed client/server design is needed that provides increased performance, flexibility, maintainability, reusability, and scalability, while hiding the complexity of distributed processing from the user.

4) The three tier architecture is used when an effective distributed client/server design is needed that provides increased performance, flexibility, maintainability, reusability, and scalability, while hiding the complexity of distributed processing from the user.

5) A three tier distributed client/server architecture includes a user system interface top tier where user services reside.

Advantages and disadvantages of two-tier:

1) The application is expected to support a limited number of users (e.g. no more than a few hundred)

2) The application is networked and databases are "local" (i.e. not over WAN or Internet)

3) A normal level of security is required (data is not overly sensitive)

4) Data access from outside applications is minimal

5) The most important limitation of the two-tier architecture is that it is not scalable, because each client requires its own database session. The two tier design will scale-up to service 100 users on a network

6) Availability The assurance that a service/resource is always accessible. This aspect of a system is often coupled with measures of its performance. (time available) / (time possible) Example – 201 seconds down/week. 7) Capacity The ability to run a number of jobs per unit time. 8) Extensibility The ability to economically modify or add functionality. 9) Flexibility The ability to support architectural and hardware configuration changes.The ability to change architecture to meet new requirements in a cost-efficient manner.