PATIENT BILLING SYSTEM

INDEX

1. Introduction

2. System Analysis

a. Existing System

b. proposed System

3. Feasibility Report

a. Technical Feasibility

b. Operational Feasibility

c. Economical Feasibility

4. System Requirement Specification Document

a. Overview

b. Modules Description

c. Process Flow

d. SDLC Methodology

e. Software Requirements

f. Hardware Requirements

5. System Design

a. DFD

b. E-R diagram

c. UML

d. Data Dictionary

6. Technology Description

7. Coding

8. Testing & Debugging Techniques

9. Output Screens
10. Reports

11. Future Enhancements

12. Conclusion

13. Bibliography
INTRODUCTION
This project is aimed at developing a patient billing software system that is of
importance to a hospital. The PBS is a local software system. This system can
be used to maintain the location (bed no.) of each patient either in the ward
or the ICU. Information about the patient and the charges to be paid is also
stored.

NEED FOR AUTOMATION

The development of this new system contains the following activities, which
try to automate the entire process keeping in the view of database
integration approach.

• The existing system needs to save patients information in the

form of excels sheet.

• The manual system gives us very less security for saving data;
some data may be lost due to mismanagement.

• Searching of particular room vacancy information is very critical

where it takes lot of time.

• This system is not having the facility of tracking transfers of

patients from the general ward to the ICU and vice versa.
SYSTEM ANALYSIS
PURPOSE OF THE SYSTEM

This project is aimed at developing a patient billing software system

that is of importance to a hospital. The PBS is a local software system.
This system can be used to maintain the location (bed no.) of each
patient either in the ward or the ICU. Information about the patient
and the charges to be paid is also stored.

EXISTING SYSTEM

• The existing system needs to save patients information in the

form of excels sheets.

• The manual system gives us very less security for saving

data; some data may be lost due to mismanagement.

• Searching of particular room vacancy information is very

critical where it takes lot of time.

• This system is not having the facility of tracking transfers

of patients from the general ward to the ICU and vice versa.

LIMITATIONS IN EXISTING SYSTEM

• The current system is not completely complete computerized and

manual system in entering students and staff data and handling
it.
• There is no centralized database maintenance
• There is no easy access to the particular employee record
• The administrator and employee cannot easily navigate through
the database
PROPOSED SYSTEM

The development of this new system contains the following activities, which
try to automate the entire process keeping in the view of database
integration approach.

• This system can provide the information about the patient based
on the ward number whether the patient is either in the general
ward or the ICU.

• By using this system we can prepare all bills pending to be paid

by a patient before the patient’s discharge.

• We can keep a track of all beds occupied / free in both the ward
and the ICU by using this system.

• We can keep track of all transfers of patients from the general

ward to the ICU and vice versa.

• This system is providing the facility of viewing all information

about patients details, their admit time and the amount to be
paid based on the treatment given and the ward selected.

• We can register all the patient details like the amount to be

paid / any balance remaining, the ward number, the bed
number, the registration number, case number etc. as soon as a
new patient is joined in the hospital.

• Authentication is provided for this application only registered

employees can access.
FEASIBILITY STUDY
TECHNICAL FEASIBILITY:
Evaluating the technical feasibility is the trickiest part of a feasibility
study. This is because, at this point in time, not too many detailed
design of the system, making it difficult to access issues like
performance, costs on (on account of the kind of technology to be
deployed) etc. A number of issues have to be considered while doing a
technical analysis.

i) Understand the different technologies involved in the

proposed system:
Before commencing the project, we have to be very clear about
what are the technologies that are to be required for the
development of the new system.

ii) Find out whether the organization currently possesses the

required technologies:

o Is the required technology available with the

organization?

o If so is the capacity sufficient?

For instance –
“Will the current printer be able to handle the new reports and
forms required for the new system?”
OPERATIONAL FEASIBILITY:
Proposed projects are beneficial only if they can be turned into
information systems that will meet the organizations operating
requirements. Simply stated, this test of feasibility asks if the system
will work when it is developed and installed. Are there major barriers
to Implementation? Here are questions that will help test the
operational feasibility of a project:
  Is there sufficient support for the project from management from
users? If the current system is well liked and used to the extent
that persons will not be able to see reasons for change, there
may be resistance.

 Are the current business methods acceptable to the user? If they

are not, Users may welcome a change that will bring about a
more operational and useful systems.

 Have the user been involved in the planning and development of

the project?

 Early involvement reduces the chances of resistance to the

system and in

 General and increases the likelihood of successful project.

Since the proposed system was to help reduce the hardships

encountered. In the existing manual system, the new system was
considered to be operational feasible.

ECONOMIC FEASIBILITY:

Economic feasibility attempts 2 weigh the costs of developing and

implementing a new system, against the benefits that would accrue
from having the new system in place. This feasibility study gives the
top management the economic justification for the new system.

A simple economic analysis which gives the actual comparison of costs

and benefits are much more meaningful in this case. In addition, this
proves to be a useful point of reference to compare actual costs as the
project progresses. There could be various types of intangible benefits
on account of automation. These could include increased customer
satisfaction, improvement in product quality better decision making
timeliness of information, expediting activities, improved accuracy of
operations, better documentation and record keeping, faster retrieval
of information, better employee morale.
SYSTEM REQUIREMENT SPECIFICATION
STUDY OF THE SYSTEM

NUMBER OF MODULES

1. Administrator

2. Employee (Receptionist)

3. Payment Module

4. Security and authentication

5. Reports

MODULES DESCRIPTION

Administrator:

This module is having the facility of adding/deleting the branches

details of the hospital. He maintains all the employee’s details. He also
can view all the details of patients and billing generation regarding the
patients. He maintains the records of doctor’s movement from one
branch to another branch.

Employee:

This module is dealing with the details of all patients details, their
admit time and the amount to be paid based on the treatment given
and the ward selected. We can also view the patient details like
amount to be paid / any balance remaining, the ward number, the bed
number, the registration number, case number etc. Keep a track of all
beds occupied / free in both the ward and the ICU. Keep a track of all
transfers of patients from the general ward to the ICU and vice versa.

Payment Module :

This module is dealing with the patient bill generation as well as

payment through the credit card or cash.

Security and Authentication:

1. Login as Receptionist or administrator

2. Change password

3. Forgot Password

Reports:

In this Module, Different actors can generate the different types of

Reports according to their access.
PROCESS FLOW
 The Model 2 architecture for designing JSP pages is in reality,
Model View Controller (MVC) applied to web applications. Hence the
two terms can be used interchangeably in the web world. MVC
originated in SmallTalk and has since made its way into Java
community. Model 2 architecure and its derivatives are the
cornerstones for all serious and industrial strength web applications
designed in the real world. Hence it is essential for you understand
this paradigm thoroughly.

The main difference between Model 1 and Model 2 is that in

Model 2, a controller handles the user request instead of another
JSP. The controller is implemented as a Servlet. The following steps
are executed when the user submits the request.

1. The Controller Servlet handles the user’s request. (This

means the hyperlink in the JSP should point to the controller
servlet).
2. The Controller Servlet then instantiates appropriate
JavaBeans based on the request parameters (and optionally
also based on session attributes).
3. The Controller Servlet then by itself or through a controller
helper communicates with the middle tier or directly to the
database to fetch the required data.
4. The Controller sets the resultant JavaBeans (either same or a
new one) in one of the following contexts – request, session or
application.
5. The controller then dispatches the request to the next view
based on the request URL.
6. The View uses the resultant JavaBeans from Step 4 to
display data. Note that there is no presentation logic in the JSP.
The sole function of the JSP in Model 2 architecture is to display
the data from the JavaBeans set in the request, session or
application scopes.

Model-2 Architecture.
SDLC METHDOLOGIES
SDLC METHDOLOGIES

This document play a vital role in the development of life cycle (SDLC) as it
describes the complete requirement of the system. It means for use by
developers and will be the basic during testing phase. Any changes made to
the requirements in the future will have to go through formal change
approval process.

SPIRAL MODEL was defined by Barry Boehm in his 1988 article, “A spiral
Model of Software Development and Enhancement. This model was not the
first model to discuss iterative development, but it was the first model to
explain why the iteration models.

As originally envisioned, the iterations were typically 6 months to 2 years

long. Each phase starts with a design goal and ends with a client reviewing
the progress thus far. Analysis and engineering efforts are applied at each
phase of the project, with an eye toward the end goal of the project.

The steps for Spiral Model can be generalized as follows:

• The new system requirements are defined in as much details as

possible. This usually involves interviewing a number of users
representing all the external or internal users and other aspects of
the existing system.

• A preliminary design is created for the new system.

• A first prototype of the new system is constructed from the

preliminary design. This is usually a scaled-down system, and
 represents an approximation of the characteristics of the final
product.

• A second prototype is evolved by a fourfold procedure:

1. Evaluating the first prototype in terms of its strengths,

weakness, and risks.

2. Defining the requirements of the second prototype.

3. Planning an designing the second prototype.

4. Constructing and testing the second prototype.

• At the customer option, the entire project can be aborted if the risk
is deemed too great. Risk factors might involve development cost
overruns, operating-cost miscalculation, or any other factor that
could, in the customer’s judgment, result in a less-than-satisfactory
final product.

• The existing prototype is evaluated in the same manner as was the

previous prototype, and if necessary, another prototype is
developed from it according to the fourfold procedure outlined
above.

• The preceding steps are iterated until the customer is satisfied that
the refined prototype represents the final product desired.

• The final system is constructed, based on the refined prototype.

• The final system is thoroughly evaluated and tested. Routine

maintenance is carried on a continuing basis to prevent large scale
failures and to minimize down time.
The following diagram shows how a spiral model acts like:
Fig 1.0-Spiral Model
ADVANTAGES

• Estimates(i.e. budget, schedule etc .) become more relistic as work

progresses, because important issues discoved earlier.

• It is more able to cope with the changes that are software

development generally entails.

• Software engineers can get their hands in and start woring on the
core of a project earlier.
SOFTWARE REQUIREMENT & HARDWARE
REQUIREMENT
Software Requirements :

Operating System : Windows XP/2003 or Linux

User Interface : HTML, CSS
Client-side Scripting : JavaScript
Programming Language : Java
Web Applications : JDBC, Servlets, JSP
IDE/Workbench : My Eclipse 6.0
Database : Oracle 10g
Server Deployment : Tomcat 5.x
Frame Work : Struts 1.x

Hardware Requirements:

Processor : Pentium IV

Hard Disk : 40GB

RAM : 512MB or more

SYSTEM DESIGN
DATA FLOW DIAGRAM
DATA FLOW DIAGRAMS:

A graphical tool used to describe and analyze the moment of data through a

system manual or automated including the process, stores of data, and

delays in the system. Data Flow Diagrams are the central tool and the basis

from which other components are developed. The transformation of data

from input to output, through processes, may be described logically and

independently of the physical components associated with the system. The

DFD is also know as a data flow graph or a bubble chart.

DFDs are the model of the proposed system. They clearly should show the

requirements on which the new system should be built. Later during design

activity this is taken as the basis for drawing the system’s structure charts.

The Basic Notation used to create a DFD’s are as follows:

1. Dataflow: Data move in a specific direction from an origin to a

destination.

2. Process: People, procedures, or devices that use or produce (Transform)

Data. The physical component is not identified.

3. Source: External sources or destination of data, which may be People,

programs, organizations or other entities.

4. Data Store: Here data are stored or referenced by a process in the

System.
AUTHENTICATION DFD:

U I In terface U sern ame

,Passwo rd Au th en ticatio n Server

Au th en ticatio n Server A u th en ticatio n U I In terface

NO
Context Level :-

Physician

Data Output Stage

Data base
Physician
Specialization

Data Input Stage

Administrator
Data Output Stage
Treatment GUI Interface

Data Input Stage

Employee
Pathology
Test

Data Output Stage

Reports

Data Input Stage

Patient Employee

Wards

Patients

DFD for Administrator:-

 Adding
Physician

Data Output Stage

Data base
Adding
Physician
Specialization

Data Input Stage

Administrator
Data Output Stage
Adding
GUI Interface
Treatment

Adding
Pathology
Test

Data Output Stage

Reports

Adding
Employee

Adding Wards

DFD for employee:-

 View Profile

Data Output Stage

Data base
Adding in-
patient

Data Input Stage

Employee
Data Output Stage
Adding Out-
GUI Interface
Patient

Treatment
Details

Data Output Stage

Reports

Operation
Details

Patient
Movement

DFD For Patient:-

 View Profile

Data Input Stage

Patient
View Data Output Stage
Physician GUI Interface

View
Employees

Data Output Stage

Reports

View Bill

ADMIN:-

Level 1 DFD for Administrator:-

 Add Physician

Add Physician
Specialization

Add Medical
Area

Add Medical
Area
Specialization

UI displaying set
Admin Login
Of Operations

Add
Treatments

General
Information Add
Pathology
Test

Add
Employees

Add
Employee
Types

Level2 Data Flow Diagram:

Add
UI Interface InputStage OutputStage Data Store
Employee

Level3 Data Flow Diagram:

Add
UI Interface InputStage OutputStage Data Store
Treatment
EMPLOYEE:-

Level1 Data Flow Diagram for Employee:

Register Out
Patient

Register In
Patient

UI displaying set
Employee Login
Of Operations

Add
Treatment
Details

Add Patient
Operation

Level2 Data Flow Diagram:

Register Out
UI Interface Input Stage OutoutStage Data Store
Patient

Level3 Data Flow Diagram:

Register In
UI Interface Input Stage Output Stage Data Store
Patient

PATIENT:-

Level1 Data Flow Diagram for Patient:

 View
Employees

View Patients

UI displaying set
Patient Login
Of Operations

View Bill
Details

View Profile
E-R DIAGRAM
 UML DIAGRAMS

UNIFIED MODELING LANGUAGE DIAGRAMS

The unified modeling language allows the software engineer to express an

analysis model using the modeling notation that is governed by a set of
syntactic semantic and pragmatic rules.
A UML system is represented using five different views that describe the
system from distinctly different perspective. Each view is defined by a set of
diagram, which is as follows.

USER MODEL VIEW

This view represents the system from the users perspective.

The analysis representation describes a usage scenario from the end-users

perspective.

STRUCTURAL MODEL VIEW

In this model the data and functionality are arrived from inside the system.
This model view models the static structures.

BEHAVIORAL MODEL VIEW

It represents the dynamic of behavioral as parts of the system, depicting the

interactions of collection between various structural elements described in
the user model and structural model view.

IMPLEMENTATION MODEL VIEW

In this the structural and behavioral as parts of the system are represented
as they are to be built.

ENVIRONMENTAL MODEL VIEW

In this the structural and behavioral aspects of the environment in which the
system is to be implemented are represented.
UML is specifically constructed through two different domains they are:

UML Analysis modeling, which focuses on the user model and

structural model views of the system.

UML design modeling, which focuses on the behavioral modeling,

implementation modeling and environmental model views.

Use case Diagrams represent the functionality of the system from a

user’s point of view. Use cases are used during requirements elicitation
and analysis to represent the functionality of the system. Use cases
focus on the behavior of the system from external point of view.

Actors are external entities that interact with the system. Examples of
actors include users like administrator, bank customer …etc., or
another system like central database.
CLASS COLLABORATIVE DIAGRAME
 AddTreatm entDAO GetBedNum ber BedsDA O

~flag: boolean ~stmt: java.sql. Statement = null ~flag: boolean

~con: Connection = null ~con: java. sql. Connection = null ~con: Connection = null
~stmt: java. sql.PreparedStatement = null ~sno: int ~stmt: java.sql. PreparedStatement = null

+addTreatment(treatmentform: AddTreatmentForm): boolean+getNames(): CoreHash +addBeds(bedsform: com.dts. patient.form. BedsForm): boolean

I nPatientDAO
~flag: boolean Em ployeeDAO
~con: Connection = null A bstractDataAccessObject
~flag: boolean
~stmt: java. sql.CallableStatement = null
-mCon: Connection = null ~con: Connection = null
-mProps: Properties
+addI nPatient(inpatientform: com.dts. patient. form.I npatientForm): boolean ~stmt: java.sql. CallableStatement = null
+getProperties(): Properties +addEmployee(employeetype: EmployeeModelForm): boolean
OutPatientDAO +setProperties(aProps: Properties)
+getConnection(): Connection
~flag: boolean +getSequenceI D(tableName: String, pkid: String): int
~con: Connection = null
~stmt: java. sql.PreparedStatement = null

+addOutPatient(outpatientform: OutPatientForm): boolean

Em ployeeTypeDAO
~flag: boolean
PathologyTestDAO
~con: Connection = null
~flag: boolean ~stmt: java. sql.PreparedStatement = null
~con: Connection = null
+addEmployeeType(employeetype: EmployeeTypeFormForm): boolean
~stmt: java. sql.PreparedStatement = null

+addPathologyTest(pathologyform: PathologyTestForm): boolean

 USECASE DIAGRAM

Context Level Diagram for On-line Patient Billing Sysem:-

 System

Employee

On-line Patient Billing System

Administrator

Usecase for Administrator:-

 System

Adding Of Physician

Adding Physician Specialization

Adding Treatment On-line Patient Billing System

Administrator

Adding Pathology Test

Adding Employees

Adding Wards

Usecase for Employee:-

 System

View Profile

Adding In Patient

Adding Out Patient On-line Patient Billing System

Employee

Treatment Details

Operation Details

Patient Movement
 SEQUENCE DIAGRAMS

Sequence Diagrams For Administrator Activites:-

Logincheck:-
 Administrator Login AdminHome Validate Database Logout

1 : LoginDetails()

2 : Validate()

3 : Check Details()

5 : Login_Check()
4 : Fail()

6 : Check Details()

7 : Forward If Sucess() 8 : Logout If fail()

Collobaration Diagram for Logincheck:-

 AdminHome

7 : Forward If Sucess()
8 : Logout If fail()

6 : Check Details()
Logout
Database

5 : Login_Check()

3 : Check Details()

Validate

4 : Fail() 2 : Validate()

1 : LoginDetails()
Administrator Login

Sequence Diagram for Employee Activites:-

 Employee Login EmployeeHome Validate Database Logout

1 : LoginDetails()

2 : Validate()

3 : Check Details()

5 : Login_Check()
4 : Fail()

6 : Check Details()

7 : Forward If Sucess() 8 : Logout If fail()

Collobaration diagram for employee logincheck:-

 Logout

8 : Logout If fail() EmployeeHome

7 : Forward If Sucess()

6 : Check Details()
Database

5 : Login_Check()
3 : Check Details()

Validate

4 : Fail()
Employee

2 : Validate()
1 : LoginDetails()

Login
ACTIVITY DIAGRAM
Activity Diagram For Administrator:-

Login

Validate

If data is not valid

AdminHome

Add Physician Add Physician Specialization Adding treatment Add Pathology Test Add Employee Adding Wards

Logout

Activity Diagram for Employee:-

 Login

Validate

If data is not valid

Employee Home

View Profile Adding in patient Adding out patient Treament Details operation details Patient Movement

Logout

COMPONENT DIAGRAM:
DEPLOYMENT DIAGRAM:
 DATA DICTIONARY

ADDRESS MASTER:-
BEDSMASTER

DIAGNOSIS DETAILS

EMPLOYEEMASTER

EMPLOYEE TYPE MASTER

INPATIENT MASTER

MEDICAL AREA MASTER

MEDICAL AREA SPECIALIZATION

OPERATION DOCTOR MASTER

OPERATION ROLE MASTER

OUTPATIENT MASTER

PATHOLOGY TEST MASTER

PATIENT MOVEMENT MASTER

PATIENT OPERATION MASTER

PHONE MASTER

PHYSICIAN SPECIALIZATION MASTER

PHYSICIAN CONSULTATION MASTER

PHYSICIAN MASTER
ROOM MASTER

SPECIALIZATION MASTER

TREATMENT DETAILS

TREATMENT MASTER

USER AUTH DETAILS

WARDS MASTER
TECHNOLOGY DESCRIPTION
HTML

HTML, an initialism of Hypertext Markup Language, is the predominant

markup language for web pages. It provides a means to describe the
structure of text-based information in a document — by denoting certain text
as headings, paragraphs, lists, and so on — and to supplement that text with
interactive forms, embedded images, and other objects. HTML is written in
the form of labels (known as tags), surrounded by angle brackets. HTML can
also describe, to some degree, the appearance and semantics of a document,
and can include embedded scripting language code which can affect the
behavior of web browsers and other HTML processors.

HTML is also often used to refer to content of the MIME type text/html or
even more broadly as a generic term for HTML whether in its XML-descended
form (such as XHTML 1.0 and later) or its form descended directly from
SGML

Hyper Text Markup Language

Hypertext Markup Language (HTML), the languages of the World Wide

Web (WWW), allows users to produces Web pages that include text,
graphics and pointer to other Web pages (Hyperlinks).

HTML is not a programming language but it is an application of ISO

Standard 8879, SGML (Standard Generalized Markup Language), but
specialized to hypertext and adapted to the Web. The idea behind
Hypertext is that instead of reading text in rigid linear structure, we
can easily jump from one point to another point. We can navigate
through the information based on our interest and preference. A
markup language is simply a series of elements, each delimited with
special characters that define how text or other items enclosed within
the elements should be displayed. Hyperlinks are underlined or
emphasized works that load to other documents or some portions of
the same document.

HTML can be used to display any type of document on the host

computer, which can be geographically at a different location. It is a
versatile language and can be used on any platform or desktop.

HTML provides tags (special codes) to make the document look

attractive. HTML tags are not case-sensitive. Using graphics, fonts,
different sizes, color, etc., can enhance the presentation of the
document. Anything that is not a tag is part of the document itself.

Basic HTML Tags:

<! -- --> specifies comments

<A>……….</A> Creates hypertext links

<B>……….</B> Formats text as bold

<BIG>……….</BIG> Formats text in large font.

<BODY>…</BODY> Contains all tags and text in the HTML

document

<CENTER>...</CENTER> Creates text

<DD>…</DD> Definition of a term

<DL>...</DL> Creates definition list

<FONT>…</FONT> Formats text with a particular font

<FORM>...</FORM> Encloses a fill-out form

<FRAME>...</FRAME> Defines a particular frame in a set of frames

<H#>…</H#> Creates headings of different levels(1–6 )

<HEAD>...</HEAD> Contains tags that specify information about

a document

<HR>...</HR> Creates a horizontal rule

<HTML>…</HTML> Contains all other HTML tags

<META>...</META> Provides meta-information about a document

<SCRIPT>…</SCRIPT> Contains client-side or server-side script

<TABLE>…</TABLE> Creates a table

<TD>…</TD> Indicates table data in a table

<TR>…</TR> Designates a table row

<TH>…</TH> Creates a heading in a table

Attributes

The attributes of an element are name-value pairs, separated by "=", and

written within the start label of an element, after the element's name. The
value should be enclosed in single or double quotes, although values
consisting of certain characters can be left unquoted in HTML (but not
XHTML).Leaving attribute values unquoted is considered unsafe.

Most elements take any of several common attributes: id, class, style and
title. Most also take language-related attributes: lang and dir.

The id attribute provides a document-wide unique identifier for an element.

This can be used by stylesheets to provide presentational properties, by
browsers to focus attention on the specific element or by scripts to alter the
contents or presentation of an element. The class attribute provides a way of
classifying similar elements for presentation purposes. For example, an HTML
document (or a set of documents) may use the designation class="notation"
to indicate that all elements with this class value are all subordinate to the
main text of the document (or documents). Such notation classes of
elements might be gathered together and presented as footnotes on a page,
rather than appearing in the place where they appear in the source HTML.

An author may use the style non-attributal codes presentational properties to

a particular element. It is considered better practice to use an element’s son-
id page and select the element with a stylesheet, though sometimes this can
be too cumbersome for a simple ad hoc application of styled properties. The
title is used to attach subtextual explanation to an element. In most
browsers this title attribute is displayed as what is often referred to as a
tooltip. The generic inline span element can be used to demonstrate these
various non-attributes.

The preceding displays as HTML (pointing the cursor at the abbreviation

should display the title text in most browsers).

Advantages

 A HTML document is small and hence easy to send over the net.
It is small because it does not include formatted information.
 HTML is platform independent.
 HTML tags are not case-sensitive.
JavaScript

JavaScript is a script-based programming language that was developed by

Netscape Communication Corporation. JavaScript was originally called Live
Script and renamed as JavaScript to indicate its relationship with Java.
JavaScript supports the development of both client and server components of
Web-based applications. On the client side, it can be used to write programs
that are executed by a Web browser within the context of a Web page. On
the server side, it can be used to write Web server programs that can
process information submitted by a Web browser and then update the
browser’s display accordingly

Even though JavaScript supports both client and server Web programming,
we prefer JavaScript at Client side programming since most of the browsers
supports it. JavaScript is almost as easy to learn as HTML, and JavaScript
statements can be included in HTML documents by enclosing the statements
between a pair of scripting tags

<SCRIPTS>.. </SCRIPT>.

<SCRIPT LANGUAGE = “JavaScript”>

JavaScript statements

</SCRIPT>

Here are a few things we can do with JavaScript:

 Validate the contents of a form and make calculations.

 Add scrolling or changing messages to the Browser’s status line.
 Animate images or rotate images that change when we move
the mouse over them.
 Detect the browser in use and display different content for
different browsers.
  Detect installed plug-ins and notify the user if a plug-in is
required.
We can do much more with JavaScript, including creating entire
application.

JavaScript Vs Java

JavaScript and Java are entirely different languages. A few of the most
glaring differences are:

• Java applets are generally displayed in a box within the web

document; JavaScript can affect any part of the Web document itself.
• While JavaScript is best suited to simple applications and adding
interactive features to Web pages; Java can be used for incredibly
complex applications.

There are many other differences but the important thing to remember is
that JavaScript and Java are separate languages. They are both useful for
different things; in fact they can be used together to combine their
advantages.

Advantages

 JavaScript can be used for Sever-side and Client-side scripting.

 It is more flexible than VBScript.
 JavaScript is the default scripting languages at Client-side since
all the browsers supports it.
Java Technology

Initially the language was called as “oak” but it was renamed as “Java” in
1995. The primary motivation of this language was the need for a platform-
independent (i.e., architecture neutral) language that could be used to create
software to be embedded in various consumer electronic devices.

• Java is a programmer’s language.

• Java is cohesive and consistent.
• Except for those constraints imposed by the Internet environment,
Java gives the programmer, full control.
• Finally, Java is to Internet programming where C was to system
programming.

Importance of Java to the Internet

Java has had a profound effect on the Internet. This is because; Java
expands the Universe of objects that can move about freely in
Cyberspace. In a network, two categories of objects are transmitted
between the Server and the Personal computer. They are: Passive
information and Dynamic active programs. The Dynamic, Self-
executing programs cause serious problems in the areas of Security
and probability. But, Java addresses those concerns and by doing so,
has opened the door to an exciting new form of program called the
Applet.

Java can be used to create two types of programs

Applications and Applets: An application is a program that runs on

our Computer under the operating system of that computer. It is more
or less like one creating using C or C++. Java’s ability to create
Applets makes it important. An Applet is an application designed to be
transmitted over the Internet and executed by a Java –compatible web
browser. An applet is actually a tiny Java program, dynamically
downloaded across the network, just like an image. But the difference
is, it is an intelligent program, not just a media file. It can react to the
user input and dynamically change.

Features of Java Security

Every time you that you download a “normal” program, you are risking a
viral infection. Prior to Java, most users did not download executable
programs frequently, and those who did scan them for viruses prior to
execution. Most users still worried about the possibility of infecting their
systems with a virus. In addition, another type of malicious program exists
that must be guarded against. This type of program can gather private
information, such as credit card numbers, bank account balances, and
passwords. Java answers both these concerns by providing a “firewall”
between a network application and your computer.

When you use a Java-compatible Web browser, you can safely download Java
applets without fear of virus infection or malicious intent.

Portability

For programs to be dynamically downloaded to all the various types of

platforms connected to the Internet, some means of generating portable
executable code is needed .As you will see, the same mechanism that helps
ensure security also helps create portability. Indeed, Java’s solution to these
two problems is both elegant and efficient.

The Byte code

The key that allows the Java to solve the security and portability problems is
that the output of Java compiler is Byte code. Byte code is a highly optimized
set of instructions designed to be executed by the Java run-time system,
which is called the Java Virtual Machine (JVM). That is, in its standard form,
the JVM is an interpreter for byte code.

Translating a Java program into byte code helps makes it much easier to run
a program in a wide variety of environments. The reason is, once the run-
time package exists for a given system, any Java program can run on it.

Although Java was designed for interpretation, there is technically nothing

about Java that prevents on-the-fly compilation of byte code into native
code. Sun has just completed its Just In Time (JIT) compiler for byte code.
When the JIT compiler is a part of JVM, it compiles byte code into executable
code in real time, on a piece-by-piece, demand basis. It is not possible to
compile an entire Java program into executable code all at once, because
Java performs various run-time checks that can be done only at run time.
The JIT compiles code, as it is needed, during execution.

Java Virtual Machine (JVM)

Beyond the language, there is the Java virtual machine. The Java virtual
machine is an important element of the Java technology. The virtual machine
can be embedded within a web browser or an operating system. Once a piece
of Java code is loaded onto a machine, it is verified. As part of the loading
process, a class loader is invoked and does byte code verification makes sure
that the code that’s has been generated by the compiler will not corrupt the
machine that it’s loaded on. Byte code verification takes place at the end of
the compilation process to make sure that is all accurate and correct. So byte
code verification is integral to the compiling and executing of Java code.

Overall Description

Java Java byte

JavaVM
Source code

Java .Class
Picture showing the development process of JAVA Program

Java programming uses to produce byte codes and executes them.

The first box indicates that the Java source code is located in a. Java
file that is processed with a Java compiler called javac. The Java
compiler produces a file called a. class file, which contains the byte
code. The .Class file is then loaded across the network or loaded
locally on your machine into the execution environment is the Java
virtual machine, which interprets and executes the byte code.

Java Architecture

Java architecture provides a portable, robust, high performing

environment for development. Java provides portability by compiling
the byte codes for the Java Virtual Machine, which is then interpreted
on each platform by the run-time environment. Java is a dynamic
system, able to load code when needed from a machine in the same
room or across the planet.

Compilation of code

When you compile the code, the Java compiler creates machine code
(called byte code) for a hypothetical machine called Java Virtual
Machine (JVM). The JVM is supposed to execute the byte code. The
JVM is created for overcoming the issue of portability. The code is
written and compiled for one machine and interpreted on all machines.
This machine is called Java Virtual Machine.

Compiling and interpreting Java Source Code

 Source

Code
Java
Java
……….. PC Compiler Interpreter
Java
……….. (PC)
Byte code Interpreter
Macintosh Java
(Spare)
……….. Compiler Interpreter

(Macintosh)
SPARC (Platform

Compiler Independ
………… ent)

During run-time the Java interpreter tricks the byte code file into
thinking that it is running on a Java Virtual Machine. In reality this

could be a Intel Pentium Windows 95 or SunSARC station running

Solaris or Apple Macintosh running system and all could receive code
from any computer through Internet and run the Applets.

Simple

Java was designed to be easy for the Professional programmer to learn

and to use effectively. If you are an experienced C++ programmer,
learning Java will be even easier. Because Java inherits the C/C++
syntax and many of the object oriented features of C++. Most of the
confusing concepts from C++ are either left out of Java or
implemented in a cleaner, more approachable manner. In Java there
are a small number of clearly defined ways to accomplish a given task.

Object-Oriented
Java was not designed to be source-code compatible with any other
language. This allowed the Java team the freedom to design with a
blank slate. One outcome of this was a clean usable, pragmatic
approach to objects. The object model in Java is simple and easy to
extend, while simple types, such as integers, are kept as high-
performance non-objects.

Robust

The multi-platform environment of the Web places extraordinary

demands on a program, because the program must execute reliably in
a variety of systems. The ability to create robust programs was given
a high priority in the design of Java. Java is strictly typed language; it
checks your code at compile time and run time.

Java virtually eliminates the problems of memory management and

de-allocation, which is completely automatic. In a well-written Java
program, all run time errors can –and should –be managed by your
program.
Java Database Connectivity

What Is JDBC?

JDBC is a Java API for executing SQL statements. (As a point of interest,
JDBC is a trademarked name and is not an acronym; nevertheless, JDBC is
often thought of as standing for Java Database Connectivity. It consists of a
set of classes and interfaces written in the Java programming language.
JDBC provides a standard API for tool/database developers and makes it
possible to write database applications using a pure Java API.

Using JDBC, it is easy to send SQL statements to virtually any relational

database. One can write a single program using the JDBC API, and the
program will be able to send SQL statements to the appropriate database.
The combinations of Java and JDBC lets a programmer write it once and run
it anywhere.

What Does JDBC Do?

Simply put, JDBC makes it possible to do three things:

 Establish a connection with a database
 Send SQL statements
 Process the results.

JDBC versus ODBC and other APIs

At this point, Microsoft's ODBC (Open Database Connectivity) API is that

probably the most widely used programming interface for accessing relational
databases. It offers the ability to connect to almost all databases on almost
all platforms.

So why not just use ODBC from Java? The answer is that you can use
ODBC from Java, but this is best done with the help of JDBC in the
form of the JDBC-ODBC Bridge, which we will cover shortly. The
question now becomes "Why do you need JDBC?" There are several
answers to this question:

1. ODBC is not appropriate for direct use from Java because it uses a C
interface. Calls from Java to native C code have a number of
drawbacks in the security, implementation, robustness, and automatic
portability of applications.
2. A literal translation of the ODBC C API into a Java API would not be
desirable. For example, Java has no pointers, and ODBC makes
copious use of them, including the notoriously error-prone generic
pointer "void *". You can think of JDBC as ODBC translated into an
object-oriented interface that is natural for Java programmers.
3. ODBC is hard to learn. It mixes simple and advanced features
together, and it has complex options even for simple queries. JDBC, on
the other hand, was designed to keep simple things simple while
allowing more advanced capabilities where required.
4. A Java API like JDBC is needed in order to enable a "pure Java"
solution. When ODBC is used, the ODBC driver manager and drivers
must be manually installed on every client machine. When the JDBC
driver is written completely in Java, however, JDBC code is
automatically installable, portable, and secure on all Java platforms
from network computers to mainframes.
Two-tier and Three-tier Models

The JDBC API supports both two-tier and three-tier models for
database access.

In the two-tier model, a Java applet or application talks directly to the database. This
requires a JDBC driver that can communicate with the particular database management
system being accessed. A user's SQL statements are delivered to the database, and the
results of those statements are sent back to the user. The database may be located on
another machine to which the user is connected via a network. This is referred to as a
client/server configuration, with the user's machine as the client, and the machine housing
the database as the server. The network can be an Intranet, which, for example, connects
employees within a corporation, or it can be the Internet.

JAVA
Client machine
Application

JDBC
DBMS-proprietary protocol

Database
server
DBMS

Java applet or
Client machine (GUI)
Html browser

HTTP, RMI, or CORBA calls

Application Server machine (business

Server (Java)

JDBC Logic)
DBMS-proprietary protocol

Database server
In the three-tier model, commands are sent to a "middle tier" of services,
which then send SQL statements to the database. The database processes
DBMS
the SQL statements and sends the results back to the middle tier, which then
sends them to the user. MIS directors find the three-tier model very
attractive because the middle tier makes it possible to maintain control over
access and the kinds of updates that can be made to corporate data. Another
advantage is that when there is a middle tier, the user can employ an easy-
to-use higher-level API which is translated by the middle tier into the
appropriate low-level calls. Finally, in many cases the three-tier architecture
can provide performance advantages.

Until now the middle tier has typically been written in languages such
as C or C++, which offer fast performance. However, with the
introduction of optimizing compilers that translate Java byte code into
efficient machine-specific code, it is becoming practical to implement
the middle tier in Java. This is a big plus, making it possible to take
advantage of Java's robustness, multithreading, and security features.
JDBC is important to allow database access from a Java middle tier.
JDBC Driver Types

The JDBC drivers that we are aware of at this time fit into one of
four categories:

 JDBC-ODBC bridge plus ODBC driver

 Native-API partly-Java driver
 JDBC-Net pure Java driver
 Native-protocol pure Java driver

JDBC-ODBC Bridge

If possible, use a Pure Java JDBC driver instead of the Bridge and an
ODBC driver. This completely eliminates the client configuration
required by ODBC. It also eliminates the potential that the Java VM
could be corrupted by an error in the native code brought in by the
Bridge (that is, the Bridge native library, the ODBC driver manager
library, the ODBC driver library, and the database client library).

What Is the JDBC- ODBC Bridge?

The JDBC-ODBC Bridge is a JDBC driver, which implements JDBC

operations by translating them into ODBC operations. To ODBC it
appears as a normal application program. The Bridge implements
JDBC for any database for which an ODBC driver is available. The
Bridge is implemented as the

Sun.jdbc.odbc Java package and contains a native library used to

access ODBC. The Bridge is a joint development of Innersole and
Java Soft.
JDBC connectivity

The JDBC provides database-independent connectivity between the

J2EE platform and a wide range of tabular data sources. JDBC
technology allows an Application Component Provider to:

 Perform connection and authentication to a database server

 Manager transactions
 Move SQL statements to a database engine for preprocessing
and execution
 Execute stored procedures
 Inspect and modify the results from Select statements
Database:

A database management system (DBMS) is computer software designed for

the purpose of managing databases, a large set of structured data, and run
operations on the data requested by numerous users. Typical examples of
DBMSs include Oracle, DB2, Microsoft Access, Microsoft SQL Server, Firebird,
PostgreSQL, MySQL, SQLite, FileMaker and Sybase Adaptive Server
Enterprise. DBMSs are typically used by Database administrators in the
creation of Database systems. Typical examples of DBMS use include
accounting, human resources and customer support systems.

Originally found only in large companies with the computer hardware needed
to support large data sets, DBMSs have more recently emerged as a fairly
standard part of any company back office.

Description

A DBMS is a complex set of software programs that controls the organization,

storage, management, and retrieval of data in a database. A DBMS includes:

 A modeling language to define the schema of each database hosted in

the DBMS, according to the DBMS data model.

• The four most common types of organizations are the hierarchical,

network, relational and object models. Inverted lists and other
methods are also used. A given database management system may
provide one or more of the four models. The optimal structure
depends on the natural organization of the application's data, and
on the application's requirements (which include transaction rate
(speed), reliability, maintainability, scalability, and cost).

• The dominant model in use today is the ad hoc one embedded in

SQL, despite the objections of purists who believe this model is a
 corruption of the relational model, since it violates several of its
fundamental principles for the sake of practicality and performance.
Many DBMSs also support the Open Database Connectivity API that
supports a standard way for programmers to access the DBMS.

 Data structures (fields, records, files and objects) optimized to deal

with very large amounts of data stored on a permanent data storage
device (which implies relatively slow access compared to volatile main
memory).

 A database query language and report writer to allow users to

interactively interrogate the database, analyze its data and update it
according to the users privileges on data.

• It also controls the security of the database.

• Data security prevents unauthorized users from viewing or

updating the database. Using passwords, users are allowed access
to the entire database or subsets of it called subschemas. For
example, an employee database can contain all the data about an
individual employee, but one group of users may be authorized to
view only payroll data, while others are allowed access to only work
history and medical data.

• If the DBMS provides a way to interactively enter and update the

database, as well as interrogate it, this capability allows for
managing personal databases. However, it may not leave an audit
trail of actions or provide the kinds of controls necessary in a multi-
user organization. These controls are only available when a set of
application programs are customized for each data entry and
updating function.
  A transaction mechanism, that ideally would guarantee the ACID
properties, in order to ensure data integrity, despite concurrent user
accesses (concurrency control), and faults (fault tolerance).

• It also maintains the integrity of the data in the database.

• The DBMS can maintain the integrity of the database by not

allowing more than one user to update the same record at the
same time. The DBMS can help prevent duplicate records via
unique index constraints; for example, no two customers with the
same customer numbers (key fields) can be entered into the
database. See ACID properties for more information (Redundancy
avoidance).

The DBMS accepts requests for data from the application program and
instructs the operating system to transfer the appropriate data.

When a DBMS is used, information systems can be changed much more

easily as the organization's information requirements change. New categories
of data can be added to the database without disruption to the existing
system.

Organizations may use one kind of DBMS for daily transaction processing and
then move the detail onto another computer that uses another DBMS better
suited for random inquiries and analysis. Overall systems design decisions
are performed by data administrators and systems analysts. Detailed
database design is performed by database administrators.

Database servers are specially designed computers that hold the actual
databases and run only the DBMS and related software. Database servers are
usually multiprocessor computers, with RAID disk arrays used for stable
storage. Connected to one or more servers via a high-speed channel,
hardware database accelerators are also used in large volume transaction
processing environments.
DBMSs are found at the heart of most database applications. Sometimes
DBMSs are built around a private multitasking kernel with built-in networking
support although nowadays these functions are left to the operating system.
SQL

Structured Query Language (SQL) is the language used to manipulate

relational databases. SQL is tied very closely with the relational model.

In the relational model, data is stored in structures called relations or tables.

SQL statements are issued for the purpose of:

Data definition: Defining tables and structures in the database (DDL used
to create, alter and drop schema objects such as tables and indexes).

Data manipulation: Used to manipulate the data within those schema

objects (DML Inserting, Updating, Deleting the data, and Querying the
Database).

A schema is a collection of database objects that can include: tables, views,

indexes and sequences

List of SQL statements that can be issued against an Oracle database schema
are:

• ALTER - Change an existing table, view or index definition

(DDL)
• AUDIT - Track the changes made to a table (DDL)
• COMMENT - Add a comment to a table or column in a table
(DDL)
• COMMIT - Make all recent changes permanent (DML -
transactional)
• CREATE - Create new database objects such as tables or views
(DDL)
• DELETE - Delete rows from a database table (DML)
• DROP - Drop a database object such as a table, view or index
(DDL)
• GRANT - Allow another user to access database objects such as
tables or views (DDL)
• INSERT - Insert new data into a database table (DML)
• No AUDIT - Turn off the auditing function (DDL)
• REVOKE - Disallow a user access to database objects such as
tables and views (DDL)
• ROLLBACK - Undo any recent changes to the database (DML -
Transactional)
• SELECT - Retrieve data from a database table (DML)
• TRUNCATE - Delete all rows from a database table (can not be
rolled back) (DML)
• UPDATE - Change the values of some data items in a database
table (DML)
SERVLETS

Introduction

The Java web server is JavaSoft's own web Server. The Java web
server is just a part of a larger framework, intended to provide you not
just with a web server, but also with tools. To build customized
network servers for any Internet or Intranet client/server system.
Servlets are to a web server, how applets are to the browser.

About Servlets

Servlets provide a Java-based solution used to address the problems

currently associated with doing server-side programming, including
inextensible scripting solutions, platform-specific APIs, and incomplete
interfaces.

Servlets are objects that conform to a specific interface that can be plugged
into a Java-based server. Servlets are to the server-side what applets are to
the client-side - object byte codes that can be dynamically loaded off the net.
They differ from applets in that they are faceless objects (without graphics or
a GUI component). They serve as platform independent, dynamically
loadable, pluggable helper byte code objects on the server side that can be
used to dynamically extend server-side functionality.

For example, an HTTP Servlets can be used to generate dynamic HTML

content. When you use Servlets to do dynamic content you get the
following advantages:

 They’re faster and cleaner than CGI scripts

 They use a standard API (the Servlets API)
  They provide all the advantages of Java (run on a variety of
servers without needing to be rewritten).

Attractiveness of Servlets

There are many features of Servlets that make them easy and attractive to
use. These include:

 Easily configured using the GUI-based Admin tool

 Can be loaded and invoked from a local disk or remotely across
the network.
 Can be linked together, or chained, so that one Servlets can call
another Servlets, or several Servlets in sequence.
 Can be called dynamically from within HTML pages, using
server-side include tags.
 Are secure - even when downloading across the network, the
Servlets security model and Servlets sandbox protect your
system from unfriendly behavior.

Advantages of the Servlet API

One of the great advantages of the Servlet API is protocol independence. It
assumes nothing about:

• The protocol being used to transmit on the net

• How it is loaded
• The server environment it will be running in
These qualities are important, because it allows the Servlet API to be
embedded in many different kinds of servers. There are other advantages to
the Servlet API as well. These include:

• It’s extensible - you can inherit all your functionality from the base
classes made available to you.
• It’s simple, small, and easy to use.

Features of Servlets:

• Servlets are persistent. Servlet are loaded only by the web server
and can maintain services between requests.
• Servlets are fast. Since Servlets only need to be loaded once, they
offer much better performance over their CGI counterparts.
• Servlets are platform independent.
• Servlets are extensible. Java is a robust, object-oriented
programming language, which easily can be extended to suit your
needs
• Servlets are secure.
• Servlets can be used with a variety of clients.
Loading Servlets:

Servlets can be loaded from three places

From a directory that is on the CLASSPATH. The CLASSPATH of the

JavaWebServer includes service root/classes/ which is where the system
classes reside.

From the <SERVICE_ROOT /Servlets/ directory. This is *not* in the server’s

class path. A class loader is used to create Servlets from this directory. New
Servlets can be added - existing Servlets can be recompiled and the server
will notice these changes.

From a remote location, for this a code base like http: // nine.eng / classes /
foo / is required in addition to the Servlets class name. Refer to the admin
GUI docs on Servlet section to see how to set this up.

Loading Remote Servlets

Remote Servlets can be loaded by:

1. Configuring the Admin Tool to setup automatic loading of remote

Servlets
2. Setting up server side include tags in. shtml files
3. Defining a filter chain configuration

Invoking Servlets

A Servlet invoker is a Servlet that invokes the "service" method on a named

Servlet. If the Servlet is not loaded in the server, then the invoker first loads
the Servlet (either from local disk or from the network) and the then invokes
the "service" method. Also like applets, local Servlets in the server can be
identified by just the class name. In other words, if a Servlet name is not
absolute, it is treated as local.

A client can invoke Servlets in the following ways:

 • The client can ask for a document that is served by the Servlet.
• The client (browser) can invoke the Servlet directly using a URL, once
it has been mapped using the Servlet Aliases section of the admin GUI.
• The Servlet can be invoked through server side include tags.
• The Servlet can be invoked by placing it in the Servlets/ directory.
• The Servlet can be invoked by using it in a filter chain.

Java Server Pages (JSP)

Java server Pages is a simple, yet powerful technology for creating

and maintaining dynamic-content web pages. Based on the Java
programming language, Java Server Pages offers proven portability,
open standards, and a mature re-usable component model .The
Java Server Pages architecture enables the separation of content
generation from content presentation. This separation not eases
maintenance headaches; it also allows web team members to focus
on their areas of expertise. Now, web page designer can
concentrate on layout, and web application designers on
programming, with minimal concern about impacting each other’s
work.

Features of JSP

Portability:

Java Server Pages files can be run on any web server or web-
enabled application server that provides support for them. Dubbed
the JSP engine, this support involves recognition, translation, and
management of the Java Server Page lifecycle and its interaction
components.

Components
 It was mentioned earlier that the Java Server Pages architecture
can include reusable Java components. The architecture also allows
for the embedding of a scripting language directly into the Java
Server Pages file. The components current supported include Java
Beans, and Servlets.

Processing

A Java Server Pages file is essentially an HTML document with JSP

scripting or tags. The Java Server Pages file has a JSP extension to
the server as a Java Server Pages file. Before the page is served,
the Java Server Pages syntax is parsed and processed into a Servlet
on the server side. The Servlet that is generated outputs real
content in straight HTML for responding to the client.

Access Models:

A Java Server Pages file may be accessed in at least two different

ways. A client’s request comes directly into a Java Server Page. In
this scenario, suppose the page accesses reusable Java Bean
components that perform particular well-defined computations like
accessing a database. The result of the Beans computations, called
result sets is stored within the Bean as properties. The page uses
such Beans to generate dynamic content and present it back to the
client.

In both of the above cases, the page could also contain any valid
Java code. Java Server Pages architecture encourages separation of
content from presentation.
Steps in the execution of a JSP Application:

1. The client sends a request to the web server for a JSP file by
giving the name of the JSP file within the form tag of a HTML
page.

2. This request is transferred to the JavaWebServer. At the server side

JavaWebServer receives the request and if it is a request for a jsp file
server gives this request to the JSP engine.
3. JSP engine is program which can under stands the tags of the

jsp and then it converts those tags into a Servlet program and it

is stored at the server side. This Servlet is loaded in the memory

and then it is executed and the result is given back to the

JavaWebServer and then it is transferred back to the result is

 given back to the JavaWebServer and then it is transferred back

to the client.

About Stuts:

What is a Web Application?

Applications built using the Struts framework are at their core, web
applications. A web application is a collection of individual components
that once bound together, form a complete application that can be
installed and executed by a web container. The components are tied
together due to the fact that they reside in the same web context and
in many cases, may refer to one another, directly or indirectly.

Elements of a Web Application

Obviously, not all web applications are created equal. They will not
have the same functional and non-functional requirements across
organizations, departments, or even the same vertical markets.
Therefore, not all web applications will contain the same types of
resources. In general however, web applications can consist of one or
more of the following types of components:

 Servlets

 JSP Pages

 Standard JavaBeans and Utility Classes

 HTML Documents

 Multimedia Files (Images, Audio and Video Files, CAD Drawings,

etc… )
  Client side Applets, Stylesheets, and JavaScript Files

 Text Documents

Meta information that ties all of the above components together

JSP Model 1 and Model 2 Architectures:

The early JSP specifications presented two approaches for building web
applications using JSP technology. These two approaches were
described in the specification as JSP Model 1 and Model 2
architectures. Although the terms are no longer used in the JSP
specification, their usage throughout the web tier development
community is still widely used and referenced.

The two JSP architectures differed in several key areas. The major
difference was how and by which component the processing of a
request was handled. With the Model 1architecture, the JSP page
handles all of the processing of the request and is also responsible for
displaying the output to the client.

In direct comparison to the Model 1 approach, in the Model 2

architecture, the client request is first intercepted by a servlet, most
often referred to as a Controller servlet. The servlet handles the initial
processing of the request and also determines which JSP page to
display next.
As you can see from the above figure, in the Model 2 architecture, a
client never sends a request directly to a JSP page. The controller
servlet acts as sort of a traffic cop. This allows the servlet to perform
front-end processing like authentication and authorization, centralized
logging, and possibly help with Internationalization. Once processing of
the request has finished, the servlet directs the request to the
appropriate JSP page. How exactly the next page is determined can
vary widely across different applications. For example, in simpler
applications, the next JSP page to display may be hard coded in the
servlet based on the request, parameters, and current application
state. In other more sophisticated web applications, a workflow/rules
engine may be used.

As you can see, the main difference between the two approaches is
that the Model 2 architecture introduces a controller servlet that
provides a single point of entry and also encourages more reuse and
extensibility than Model 1. With the Model 2 architecture, there is also
a clear separation of the business logic, presentation output, and
request processing. This separation is often referred to as a Model-
View-Controller (MVC) pattern. While the Model 2 architecture might
seem overly complicated, it can actually simplify an application
greatly. Web applications built using the Model 2 approach are
generally easier to maintain and can be more extensible than
comparable applications built around the Model 1 architecture.
All of this doesn’t mean that applications built using the Model 1
approach are incorrectly designed. The Model 1 architecture might be
the best decision for smaller applications that have simple page
navigation, no need for centralized features, and are fairly static.
However, for more larger enterprise-size web applications, it would be
more advantageous to utilize the Model 2 approach.

Why is Model-View-Controller So Important?

Model-View-Controller is an architectural pattern that by it self has

nothing to do with web applications directly. As we saw from the
previous section, the JSP Model 2 approach is clearly about separating
responsibilities in a web application built using Servlet and JSP
technologies. Allowing a JSP page to handle the responsibilities of
receiving the request, executing some business logic, and then
determining the next view to display can really make for an
unattractive JSP page, not to mention the problems this entanglement
causes for maintenance and extensibility. By having components
within a web application that have very clear and distinct
responsibilities, the development and maintenance on an application
can be made more efficient. This is also true for software development
as a whole. The MVC pattern is categorized as a design pattern in
many software design books. Although there is usually much
disagreement on the precise definition of the pattern, there are some
fundamental ideas.

The MVC pattern has three key components:

The Model Component

Responsible for the business domain state knowledge

The View Component

Responsible for a presentation view of the business domain

The Controller Component

Responsible for controlling flow and state of the user input

Normally with the MVC pattern, there’s a form of event notification

that takes place to notify the view when some portion of the model
changes. However, since a browser in a typical web application has a
stateless connection, the notification from the model to the view can’t
easily occur. Of course, an application could perform some type of
push action to push data changes all the way to a client; but this
doesn’t and probably shouldn’t happen in most web applications. A
user can close at a browser anytime and there isn’t warning or
notification sent to the server. There’s a great deal of overhead
necessary to management remote clients from the server side. This
type of behavior is overkill for typical B2C and B2B web applications.

The MVC Model

Depending on the type of architecture of your application, the model

portion of the MVC pattern can take many different forms. In a two-
tier application, where the web tier interacts directly with a data store
like a database, the model classes may be a set of regular Java
objects. These objects may be populated manually from a result set
returned by a database query or they can even be instantiated and
populated automatically by an Object-to-Relational Mapping (ORM)
framework.

In a more complex enterprise application where the web tier

communicates with an EJB server for example, the model portion of
the MVC pattern might be Enterprise JavaBeans. Although the EJB 2.0
Specification made some improvements in performance through the
use of local interfaces, there can still be a significant performance
impact if the web tier attempted to use entity beans directly as the
model portion of the application. In many cases, JavaBeans are
returned from Session beans and used within the web tier. These
JavaBeans are commonly referred to as value objects and are used
within the views to build the dynamic content.
The MVC View

The views within the web tier MVC pattern typically consist of HTML
and JSP pages. HTML pages are used to serve static content, while JSP
pages can be used to serve both static and dynamic content. Most
dynamic content is generated in the web tier. However, Web
applications are considered stateless because the browser doesn’t
typically maintain an open socket to the web server. However, a web
application may still maintain session data for a user or even store
data within the browser on behalf of the user. some applications may
require the need for client-side JavaScript. This does not interface or
infringe upon the MVC concept.

The MVC Controller

The controller portion of the web tier MVC design is generally a Java
servlet. The controller in a web tier application performs the following
duties:

1. Intercepts HTTP requests from a client.

2. Translates the request into a specific business operation to perform.

3. Either invokes the business operation itself or delegates to a

handler.

4. Helps to select the next view to display to the client.

5. Returns the view to the client.

The Front Controller pattern, which is part of the J2EE Design Patterns,
describes how a web tier controller should be implemented. Since all
client requests and responses go through the controller, there is a
centralized point of control for the web application. This aides in
maintenance and when adding new functionality. Code that would
normally need to be put in every JSP page can be put in the controller
servlet, since it processes all requests. The controller also helps to
decouple the presentation components (views) from the business
operations, which also aids development.

What is a Framework?

I have been throwing the word framework around in this chapter

without having really defined what exactly it is or how it adds value in
software development. In its simplest form, a framework is a set of
classes and interfaces that cooperate to solve a specific type of
software problem. A framework has the following characteristics:

 A framework is made up of multiple classes or components, each

of which may Provide an abstraction of some particular concept.

 The framework defines how these abstractions work together to

solve a problem.

 The framework components are reusable

A good framework should provide generic behavior that can be utilized

across many different types of applications. There are many
interpretations of what constitutes a framework. Some might consider
the classes and interfaces provided by the Java language a framework,
but it’s really a library. There’s a subtle, but very distinct difference
between a software library and a framework. With a software library,
your application is the main code that executes and it invokes routines
on the library. With a framework, it contains the executing routines
and invokes operations onto your extensions through inheritance and
other means. The places where the framework can be extended are
known as extension points. A framework is commonly referred to an
“upside-down” library because of the alternate manner in which it
operates.

Creation of the Struts Framework

By now you should have a foundation for JSP and Servlet technology
and you should also understand the benefits that the Web MVC design
and JSP Model 2 architecture adds to a web application. This section
provides a little background and history on the Struts framework,
which is an implementation of all of these ideas.

High-level Diagram of Struts Framework:

Typical Diagram of Struts Framework:

The Struts Component Packages

The Struts framework is made up of approximately 200 Java classes,

divided into 15 Java packages. Approximately is an appropriate term
because the framework is continuously growing and being shaped.

Struts Controller Components

The controller component in a MVC application has several

Responsibilities. Those responsibilities include receiving input from a
client, invoking a business operation, and coordinating the view to
return back to the client. Of course, there are many other functions
that the controller may perform, but these are a few of the primary
ones.

You also learned that, with the JSP Model 2 architecture, on which
Struts was fashioned the controller was implemented by a Java
servlet. This servlet becomes the centralized point of control for the
web application. The controller servlet maps user actions into business
operations and then helps to select the view to return to the client
based on the request and other state information.

In the Struts framework however, the controller responsibilities are

implemented by several different components, one of which is an
instance of the org.apache.struts.action.ActionServlet class.

The Struts ActionServlet

The ActionServlet extends the javax.servlet.http.HttpServlet class and

is responsible for packaging and routing HTTP traffic to the appropriate
handler in the framework. The ActionServlet class is not abstract and
therefore can be used as a concrete controller by your applications.
Prior to version 1.1 of the Struts framework, the ActionServlet was
solely responsible for receiving the request and processing it by calling
the appropriate handler. In version 1.1, a new class called
org.apache.struts.action.RequestProcessor has been introduced to
process the request for the controller. The main reason for decoupling
the request processing from the ActionServlet is to provide you with
the flexibility to subclass the RequestProcessor with your own version
and modify how the request is processed. For the banking application
example, we are going to keep it simple and utilize the default
ActionServlet and RequestProcessor classes provided by the
framework.
Once the controller receives a client request, it delegates the handling
of the request to a helper class. This helper knows how to execute the
business operation that is associated with the requested action. In the
Struts framework, this helper class is a descendant of the
org.apache.struts.action.Action class.

Struts Action Classes

An org.apache.struts.action.Action class in the Struts framework is an

extension of the controller component. It acts as an Adaptor between
a user action and a business operation. The Action class decouples the
client request from the business model. This decoupling allows for
more than a one-to-one mapping between the user request and an
Action class. The Action class can perform other functions, such as

authorization, logging, and session validation, before invoking the

business operation.

The Struts Action class contains several methods, but the most
important is the execute() method. Here is the method signature:

public ActionForward execute(ActionMapping mapping,

ActionForm form, HttpServletRequest request,

HttpServletResponse response) throws IOException, ServletException;

The execute() method is called on an instance of an Action class by the

controller when a request is received from a client. The controller will
create an instance of the Action class if one doesn’t already exist. The
Struts framework will only create a single instance of each Action class
in your application. Since there is only one instance for all users, you
must ensure that all of your Action classes operate properly in a multi-
threaded
Environment Although the execute() method is not abstract, the
default implementation just returns null so you will need to create your
own Action class implementations and override this method.

Mapping the Actions

At this point, you might be asking yourself, “How does the controller
know which Action instance to invoke when it receives a request?” The
answer is by inspecting the request information and utilizing a set of
action mappings. Action mappings are part of the Struts configuration
information that is configured in a special XML file. This configuration
information is loaded into memory at startup and made available to
the framework at runtime. Each <action> element is represented in
memory by an instance of the org.apache.struts.action.ActionMapping
class. The ActionMapping object contains a path attribute that is
matched against a portion of the URI of the incoming request.

Whenever the controller receives a request where the path in the URI
contains the string “/login”, the execute() method of the LoginAction
instance will be invoked. The Struts framework also uses the mappings
to identify the resource to forward the user to once the action has
completed.

Determining the Next View

We’ve talked about how the controller receives the request and how
the action mappings and request information are used to determine
the correct action instance to invoke and pass the request to. What
hasn’t been discussed is how or what determines the view to return
back to the client. If you looked closely at the execute() method
signature in the Action class from the previous section, you might have
noticed that the return type for the method is an
org.apache.struts.action.ActionForward class. The ActionForward class
represents a destination to which the controller may send control once
an Action has completed. Instead of specifying an actual JSP page in
the code, you can declaratively associate an action forward mapping
with the JSP and then use that ActionForwardthroughout your
application. The action forwards are specified in the configuration file,
similar to action mappings.
The logout action declares a <forward> element that is named
“Success”, which forwards to a resource of “/login.jsp”. Notice in this
case, a redirect attribute is set to “true”. Instead of performing a
forward using a RequestDispatcher, the request that invokes the
logout action mapping will be redirected instead.

The action forward mappings can also be specified in a global section

independent of any specific action mapping. In the previous case, only
the logout action mapping could reference the action forward named
“Success”. In the case of forwards declared in the global forwards
section, all action mappings can reference them. Here is an example
global forwards section from the configuration file:

<global-forwards>

<forward name="SystemFailure" path="/systemerror.jsp" />

<forward name="SessionTimeOut" path="/sessiontimeout.jsp" />

</global-forwards>

The forwards defined in the global section are more general and don’t
apply to a specific action. Notice that every forward must have a name
and path, but the redirect flag is optional. If you don’t specify a
redirect attribute, its default value is false and thus performs a
forward. The path attribute in an ActionForward can also specify
another Struts Action.

Struts Model Components

There are several different ways to look at what constitutes a model

for Struts. The lines between business and presentation objects can
get quite blurry when dealing with web applications. One application’s
business objects are another’s value objects. It’s important to keep the
business objects separate from the presentation, so that the
application is not tightly coupled to one type of presentation. It’s very
likely that the look and feel of a web site will change over time.
Studies show that the freshness of a web
site’s appearance helps to attract new customers and also keep
existing customers coming back. This may not be as true in the
Business-to-Business (B2B) world, but it’s definitely true for Business-
to-Consumer (B2C) applications, which make up the majority of the
web applications used today.

The Struts View Components

The last of the MVC components to discuss are the Struts View
components. Arguably, it’s the easiest to understand. The view
components that are typically employed in a Struts application are:

JavaServer Pages

Custom Tags

HTML

Java Resource Bundles

Struts Action Forms

Value Objects

Using the Struts ActionForm

Struts ActionForm objects are used in the framework to pass client

input data back and forth between the user and the business layer.
The framework will automatically collect the input from the request
and pass this data onto an Action using a form bean, which then can
be passed along to the business layer. To keep the presentation layer
decoupled from the business layer, you should not pass the action
form itself to the business layer, but rather create the appropriate
value objects using the data from the form and pass these objects as
argument to the business layer. The following steps
illustrate how the framework processes an ActionForm for every
request.

1. Check the mapping for the action and see if a form bean has been
configured for it.

2. If so, use the name attribute to lookup the form bean configuration
information.

3. Depending on the scope configured for the form bean for the action,
check to see if there’s already an instance of the form bean at the
appropriate scope.

4. If an ActionForm instance is present in the appropriate scope and

it’s the same type as needed for this new request, reuse it.

5. Otherwise, create a new instance of the required form bean and

store it into the appropriate scope that is set by the scope attribute for
the action mapping.

6. The reset() method is called on the ActionForm instance.

7. Iterate through the request parameters and for every parameter

name that has a corresponding set method name on the ActionForm,
populate it with the value for that parameter.

8. Finally, if the validate attribute is set to true, then invoke the

validate() method on the ActionForm instance and return any errors.

Using JavaServer Pages for Presentation

JavaServer Pages make up the majority of what has to be built for the
Struts view components. Combined with custom tag libraries and
HTML, it becomes easy to provide a set of views for an application.
Although JavaServer Pages make up the majority of what
organizations and developers are using to display the dynamic content,
it’s not the only technology. There are other forms of presentation
technologies that can be combined with the Struts framework. One
very popular one is the XML/XSLT combination. This alternate model is
being referred to as Model 2X, which is a combination of the controller
servlet from the Struts framework and XSLT and beans serialized from
the value objects to render the views. Many developers feel that JSP
has the following problems:

 Developers are free to embed application logic into the JSP

pages. This can lead to an application that is difficult to
maintain.

 JSP syntax is not currently XML compliant, which may cause the
XML or HTML that gets generated, not to be “well formed”.

 Developers must learn the JSP syntax and how to program

custom tags.

 Developing a processing pipeline where each node in the pipeline

may modify the data or layout is not possible with JSP pages.
This makes it difficult to separate layout and style.

A recompile of the JSP page is necessary for each change made to the
page.

Custom Tag Libraries

The Struts framework provides five core tag libraries that can be used
by your applications. Each one has a different purpose and can be
used individually or along side the others. You may also create your
own custom tags and can even extend the Struts tags if you need
them to perform extra functionality. The custom tag libraries that are
included with the framework are:

1) HTML Tag Library

2) Bean Tag Library

3) Logic Tag Library

4) Template Tag Library

5) Nested Tag Library

Unless you are planning on using templates as part of your application,
the Template Tag library might not be necessary, but the others are
invaluable to making your application easy to develop and maintain.

To use the libraries in your application, you need to first register them
with the web application. To do this, you should add the following lines
to the deployment descriptor for each web application that you wish to
use Struts for.

<web-app>

<taglib>

<taglib-uri>/WEB-INF/struts-html.tld</taglib-uri>

<taglib-location>/WEB-INF/struts-html.tld</taglib-location>

</taglib>

<taglib>

<taglib-uri>/WEB-INF/struts-bean.tld</taglib-uri>

<taglib-location>/WEB-INF/struts-bean.tld</taglib-location>

</taglib>

<taglib>

<taglib-uri>/WEB-INF/struts-logic.tld</taglib-uri>

<taglib-location>/WEB-INF/struts-logic.tld</taglib-location>

</taglib>

<taglib>

<taglib-uri>/WEB-INF/struts-template.tld</taglib-uri>

<taglib-location>/WEB-INF/struts-template.tld</taglib-location>

</taglib>

<taglib>

<taglib-uri>/WEB-INF/struts-nested.tld</taglib-uri>
<taglib-location>/WEB-INF/struts-nested.tld</taglib-location>

</taglib>

</web-app>

The next step is to create your JSP pages and include the following
lines.

<%@ taglib uri="/WEB-INF/struts-bean.tld" prefix="bean" %>

<%@ taglib uri="/WEB-INF/struts-html.tld" prefix="html" %>

<%@ taglib uri="/WEB-INF/struts-logic.tld" prefix="logic" %>

<%@ taglib uri="/WEB-INF/struts-nested.tld" prefix="nested" %>

Once this is done and the Struts JAR file is in the web application’s
CLASSPATH, you are then able to use the custom tags in your JSP
pages.

Message Resource Bundles

The Java library includes a set of classes to support reading message

resources from either a Java class or a properties file. The core class in
this set is the java.util.ResourceBundle. The Struts framework provides
a similar set of classes, based around the
org.apache.struts.util.MessageResources class

that provides similar functionality, but provides for a little more

flexibility that the framework requires.

The standard Java support for Internationalization has grown with the
past several releases and the Struts framework could probably use
what’s included with 1.2 and newer, but since Struts was created
before 1.2, they had to build in their own support for several key
pieces. With a Struts application, you must provide a Java message
bundle for each language that
you wish to support A message resource bundle is used for reasons
other than just for localization. It can also save time during application
maintenance. For example, if you use the same text messages or
labels throughout various parts of your web site or application, when
one or more of these values need to change, you only need to make
the change in a single location. Even if you don’t have requirements
for Internationalization, you should still utilize resource bundles.

With Struts 1.1, you now have the ability to define multiple
MessageResources for an application. This allows you isolate certain
types of resources, into separate bundles. For example, you might
want to store the image resources for an application into one bundle
and the rest of the resources into another. How you organize your
application’s resources is up to you, but you now have the flexibility to
separate them based on some criteria. Some applications choose to
separate along components lines

Multiple Application Support

Prior to version 1.1, each Struts application was limited to having a

single configuration file. The single instance of the file, which is
normally called struts-config.xml, was specified in the web application
deployment descriptor. It was the sole provider of the configuration
information for the Struts application. The fact that there was only a
single place to put configuration information made it very difficult for
larger projects because it

often became a bottleneck and caused contentions to use and modify

this file. With the creation of 1.1, this problem has been alleviated with
the advent of multi application support. You can now define multiple
configuration files and allow developers to work better in parallel.

Configuring the Struts Application

The Struts framework uses two separate, but somewhat related types
of configuration files, which must be properly configured before an
application will function properly. Due to the popularity and flexibility
of the self-describing nature of XML, both of these configuration files
are based on XML.
The web application deployment descriptor web.xml is described fully
in the Java Servlet specification. This configuration file is necessary for
all web applications, not just those built with the Struts framework.
There is however, Struts specific deployment information that must be
configured within it when building web applications using Struts.

The second configuration file is the Struts configuration file, commonly

named struts-config.xml. As you’ll see however, the name can be just
about anything that you want it to. The Struts configuration file makes
it possible for you to declaratively configure many of your application’s
settings. You can think of the Struts configuration file as the rules for
the web application.

Template for struts-config.xml file:

<struts-config>

<data-sources>

<form-beans>

<global-exceptions>

<global-forwards>

<action-mappings>

<controller>

<message-resources>

<plug-in>

</struts-config>

Note that we have to follow the above order strictly, otherwise it will
throw exceptions.
What are ActionForms?

Almost every web application has a requirement to accept input from

users. Some examples of user input are credit card information, billing
and shipping address information, or even something as small as a
username and password. The HTML language provides the necessary
components to render the input fields in a browser, including text
boxes, radio buttons, check boxes, buttons, and many more. When
building these types of pages, the input components must be nested
inside of an HTML form

Elements. The Struts framework relies on the

org.apache.struts.action.ActionForm class as the key component for

handling these tasks.

The ActionForm class is used to capture input data from an HTML

form and transfer it to the Action class. Since the HTML input
components don’t natively include an input buffer and users quite
often enter invalid data, web applications need a way to store the
input data temporarily, so that it can be redisplayed when an error
occurs. In this sense, the ActionForm class acts as a buffer to hold the
state of what the user entered while it is being validated. The
ActionForm also acts as a “firewall” for your application in that it helps
to keep suspect or invalid input out of your business tier until it can be
scrutinized by the validation rules. Finally, the ActionForm is also used
to transfer data from the Action class back to the HTML form. This
allows more consistency for your HTML forms, because they are
always pulling data from the ActionForm. When the user input data
does pass input validation, the ActionForm is passed into the execute()
method of the Action class. From there, the data can be retrieved from
the ActionForm and passed on to the business tier. Because the
ActionForm imports packages from the Servlet API, you shouldn’t pass
the ActionForm to the business tier. Doing so would couple the
business methods to the Servlet API and make it more difficult to
reuse the business tier components. Instead, the data within the
ActionForm should be transferred to an object from the domain model
instead of being passed as an argument to the business tier. A
common approach is to create a data transfer object and populate it
with the data from the ActionForm. You don’t have to declare an
ActionForm for every HTML form in your application. The same
ActionForm can be associated with one or more action mappings. This
means that they can be shared across multiple HTML forms. For
example, if you had a wizard interface, where a set of data was
entered and posted across multiple pages, a single ActionForm can be
used to capture all of this data, a few fields at a time.

ActionForms and Scope

ActionForms can have two different levels of scope, request and

session. If request scope is used, an ActionForm will only be available
until the end of the request/response cycle. Once the response has
been returned to the client, the ActionForm and the data within it is no
longer accessible.

If you need to keep the form data around longer than the request,
you can configure an ActionForm to have session scope. This might be
necessary if your application captures data across multiple pages,
similar to a wizard dialog. An ActionForm that has been configured
with session scope will remain in the session until it’s removed,
replaced with another object, or until the session times out. The
framework doesn’t have a built-in facility for cleaning up session
scoped ActionForm objects automatically. Like any other object placed
into the HttpSession, it’s up to the application to routinely perform
clean up on the resources stored there. This is slightly different from
objects placed into the request, because once the request is finished,
they can be reclaimed by the garbage collector since they can no
longer be referenced. Unless you need to specifically hold the form
data across multiple requests, you should use request scope for your
ActionForm objects.

When the controller receives a request, it will attempt to recycle an

ActionForm instance from either the request or the session, depending
on the scope that the ActionForm has in the action element. If no
instance is found, a new instance will be created.

Creating an ActionForm

The ActionForm class provided by the Struts framework is abstract.

You need to create subclasses of it to capture your application specific
form data. Within your subclass, you should define a property for each
field that you wish to capture from the HTML form.

The ActionForm is populated from request parameters, not request

attributes. If you are forwarding from one action to anther, you
can’tadd a request attribute and expect that the ActionForm will be
populated from it. Request parameters and request attributes are two
separate resources.

The ActionForm validate() Method

The validate() method may be called by the RequestProcessor for

every request. Whether it’s called or not depends on two things. First,
an ActionForm must be configured for an action mapping. This means
that the name attribute for an action element must correspond to the
name attribute of one of the form-bean elements in the configuration
file.

The second condition that must be met before the RequestProcessor

will invoke the validate() method is that the validate attribute must
have a value of “true”.

<action

path="/signin" type=" LoginAction" scope="request"

name="loginForm"

validate="true" input="/security/signin.jsp">

<forward name="Success" path="/index.jsp" redirect="true"/>

<forward name="Failure" path="/security/signin.jsp"

redirect="true"/>

</action>

When the signin action is invoked, the framework will populate an

instance of a LoginForm using values it finds in the request. Because
the validate attribute has a value of “true”, the validate() method in
the LoginForm will be called. Even if the validate attribute is set to
“false”, the ActionForm will still be populated from the request if an
ActionForm is configured for the action.

The validate() method in the base ActionForm class simply returns

null. If you want to perform validation on the data that is submitted
with the request, you’ll need to override the validate() method in your
ActionForm subclasses.

The validate() method may return an ActionErrors object,

depending on whether or not any validation errors were detected. You
also can return null if there are no errors; the framework will check for
both null and an empty ActionErrors object. This saves you from
having to create an instance of ActionErrors when there are no errors.

The ActionForm reset() Method

The reset() method has been a bane for much of the Struts user
community at one time or another. Exactly when the reset() method is
called and what should be done within it is almost always
misinterpreted. This doesn’t mean that one implementation is more
correct than another, but there are misconceptions that many new
Struts developers pick up and then have a hard time shaking regarding
the reset().

It’s called before the ActionForm has been populated from the
request. The method was added to the ActionForm class originally to
help facilitate resetting boolean properties back to their defaults. To
understand why they need to be reset, it’s helpful to know how the
browser and the HTML form submit operation processes checkboxes.
When an HTML form contains checkboxes, only the values for the
checkboxes that are checked are sent in the request. Those that are
not checked are not included as a request

parameter. Therefore, the reset() method was added to allow

applications to reset the boolean properties in the ActionForm back to
false, since false wasn’t included in the request and the boolean values
would possibly be stuck in the “true” state. The reset() method in the
base ActionForm contains no default behavior, since no properties are
defined in this abstract class. Applications that extend the ActionForm
class are allowed to override this method and reset the ActionForm
properties to whatever state they wish. This may include setting
boolean properties to true or false, setting String values to null or
some initialized value, or even instantiating instances of other objects
that the ActionForm holds on to. For an ActionForm that has been
configured with request scope, the framework will essentially create a
new instance for each new request. Since a new instance is created,
there’s not much need to reset() the values back to any default state.
ActionForms that are configured with session scope are different
however. This is the time that the reset() method comes in handy.

Declaring ActionForms in the Struts Configuration File

Once you have created a class that extends ActionForm, you need
to configure the class in the Struts configuration file. The first step is
to add a new form-bean element to the form-beans section of the file:

<form-beans>

<form-bean name="loginForm" type=" LoginForm"/>

</form-beans>

The value for the type field must be a fully qualified Java class name
that is a descendant of ActionForm. Once you have defined your form-
bean, you can now use it in one or more action elements. It’s very
common to share one ActionForm across several actions.

Declaring ActionForm Properties as Strings

All request parameters that are sent by the browser are Strings. This
is true regardless of the type that the value will eventually map to in
Java. For example, dates, times, Booleans, and other values are all
strings when they are pulled out of the request. They will also be
converted into strings when they are written back out to the HTML
page.Therefore, it makes sense that all of the ActionForm properties
where the input may be invalid, should be of type String. The reason
for this is to support displaying the data back out in its original form to
the user, when there is an error. For example, if a user types in “12Z”
for a property expecting to be an Integer, there’s no way to store
“12Z” into an int or Integer property. However, you can store it into a
String until it can be validated. This same value, which is stored in a
String, can be used to render the input field with the value, so the user
can see their mistake. This is functionality that even the most
inexperienced users have come to expect and look for.

Using ActionErrors

Earlier in the chapter, you saw that the validate() method returned an
ActionErrors object. The ActionErrors class encapsulates one or more
errors that have been discovered by the application. Each problem
discovered is represented by an instance of
org.apache.struts.action.ActionError. An ActionErrors object has
request scope. Once an instance is created and populated by the
validate() method, it is stored into the request. Later, the JSP page
can retrieve the object from the request and use the ActionError
objects contained within it to display errors messages to the user.

An instance of ActionErrors can be instantiated in the validate()

method and populated by adding instances of the ActionError class to
it.

public ActionErrors validate(ActionMapping mapping,

HttpServletRequest request){

ActionErrors errors = new ActionErrors();

if( getEmail() == null || getEmail().length() < 1 ){

errors.add("email", new ActionError("security.error.email.required"));

if( getPassword() == null || getPassword().length() < 1 ){

errors.add("password",new
ActionError("security.error.password.required"));

return errors;

}
 The validate() method in this fragment checks to make sure that the
email and password fields have been set with values other than an
empty string. If not, ActionError objects are added to the ActionErrors
instance.

The ActionError class contains several useful constructors.

Several are listed here:

public ActionError(String key);

public ActionError(String key, Object value0);

public ActionError(String key, Object value0, Object value1);

public ActionError(String key, Object[] values);

The key argument is a String value that corresponds to a key from one
of the application’s resource bundles. The custom tag ErrorsTag uses
this value to lookup the message to display to the user. The remaining
arguments are used as parametric replacement values for the
message. For example, if you had a bundle message defined like this:

global.error.login.requiredfield=The {0} field is required for login

then we could create an instance of an ActionError like this:

ActionError error = new ActionError("global.error.login.requiredfield",

“Email” );

The message displayed to the user after substituting in the “Email”

string would be:

The Email field is required for login

When adding instances of the ActionError class to the ActionErrors
object, the first argument in the add() method is a property that can
be used to retrieve a specific ActionError instance. If all of your
ActionError instances can be treated the same and you have no need
to retrieve them individually, you can use the constant
ActionErrors.GLOBAL_ERROR similar to this:

errors.add(ActionErrors.GLOBAL_ERROR,

new ActionError("security.error.password.required"));

Using Dynamic ActionForms

Using the ActionForm class has many advantages over performing

the functionality yourself in the Action class or some set of helper
utility classes. Since the behavior that the ActionForm class provides is
needed in nearly every web application, as well as many times in the
same application, using the framework to perform the work can really
reduce the development time and your frustration level. Having stated
the benefits of using ActionForms, there are a few very important
downsides to using them.

The first and foremost problem with using ActionForms is the sheer
number of classes that it can add to a project. Even if you share
ActionForm definitions across many pages, the additional classes make
it more difficult to manage a project and provide maintenance. This is
why some developers might create a single ActionForm and implement
the properties for all of the HTML forms within these. The problem with
this of course, is that combining the fields into this one class makes it
a point of contention on

a project that has more than just a few developers. Another major
liability is the requirement to define the properties in the ActionForm
that need to be captured from the HTML form. If a property is added
or removed from the

HTML form, the ActionForm class may need to be modified and

recompiled. For these reasons, a new type of ActionForm was added to
the framework, which is dynamic in nature and allows you to avoid
having to create concrete ActionForm classes for your application. The
dynamic ActionForm is implemented by the base class
org.apache.struts.action.DynaActionForm, which extends the
ActionForm class.

The properties that the ActionForm defines:

1. The validate() method

2. The reset() method

The properties for a DynaActionForm are configured in the Struts

configuration file, which you’ll see how to do in the next section. The
reset() method is called at exactly the same time during request
processing as it is for a standard ActionForm. The one difference is
that you have a little less control over what you do during the method.
However, you can always subclass the DynaActionForm to override the
reset behavior.

The validation of the presentation data is a little more complicated,

because we’ll need to wait until we talk about the Struts Validator
components before talking about how validation occurs in a dynamic
form.

Configuring Dynamic ActionForm

To use the DynaActionForm in your Struts application, the first step is

to add a form-bean element to the configuration file. There are two
very important differences between a form-bean element for a regular
ActionForm and one that is dynamic. First, a form-bean element for a
dynamic ActionForm is required to have an attribute called dynamic,
which must have a value of “true”. This is necessary for the framework
to understand that it should handle this ActionForm differently. The
second difference is that you must include one or more form-property
elements in order for the dynamic form to have properties. The
DynaActionForm uses a java.util.Map internally to store key/value
pairs. The form-property elements are loaded into the Map and
become the properties that get populated by the framework.

<form-beans>
<form-bean name="loginForm" dynamic="true"

type="org.apache.struts.action.DynaActionForm">

<!-- Specify the dynamic properties of the form -->

<form-property name="email" type="java.lang.String "/>

<form-property name="password" type="java.lang.String "/>

<!-- You can also set the initial value of a property -->

<form-property initial=”false”

name="rememberMe" type="java.lang.Boolean "/>

</form-bean>

<form-beans>

The declarative properties are what make the ActionForm dynamic.

At runtime, the framework creates an instance of the DynaActionForm
class and makes it possible to set and get the configured property
values. To add new properties, you only need to modify the
configuration file. No source code needs to be changed. The power and
flexibility that this provides for you is immense.

The form-beam element also allows you to specify the initial value for
each property. The framework will set the property to that value when
the application is started. The initial value is also used when the
reset() method is called to reset the values back to their original state.
If you don’t include the initial attribute, then properties will be
assigned default values based on the Java programming language;
numbers to zero (0) and properties of type Object will be assigned a
null value by the framework.

Performing Validation using Dynamic ActionForms

 Since the DynaActionForm is used for every dynamic ActionForm and
you don’tprovide subclasses of ActionForm, there’s no way to override
the validate() method. Fortunately, the framework comes to your aid
again with a feature called the Struts Validator. The Struts Validator
was created by David Winterfeldt and is now in the main Struts
distribution. The validator is a framework that was intended to work
with Struts from the beginning. It supports basic validation rules like
checking for required fields, email, date and time fields, and many
others.

Struts Built-in Actions:

The following are the built-in actions given under the struts
framework:

 ForwardAction
 IncludeAction
 SwitchAction
 DispatchAction

ForwardAction:

The org.apache.struts.actions.ForwardAction dispatches the request

to the given path without performing any action. The ForwardAction is
configured if we want our request to be forwarded to the given path
may be a JSP, Servlet or any other resource. The ForwardAction must
be configured in struts-config.xml.

Syntax:

<action path=“/mypath”

type=“org.apache.struts.actions.ForwardAction”
parameter=“/MyPage.jsp”/>

(OR)

<action path=“/mypath” forward=“/MyPage.jsp”/>

This is the recommended approach.

IncludeAction:

The org.apache.struts.actions.IncludeAction dispatches the request

to the given path using the include option of RequestDispatcher.
IncludeAction is same as of ForwardAction but this uses
RequestDispatcher include method to dispatch the request to the given
path instead of returning ActionForward to the RequestProcessor. The
IncludeAction must be configured in struts-config.xml.

Syntax:

<action path=“/mypath”

type=“org.apache.struts.actions.IncludeAction”
parameter=“/MyPage.jsp”/>

(OR)

<action path=“/mypath” include=“/MyPage.jsp”/>

This is the recommended approach.

SwitchAction:

The org.apache.struts.actions.SwitchAction is used to switch the

request from one module to other. The SwitchAction is configured as a
normal action;SwitchAction accepts parameters named page and
prefix. The page parameter takes the module relative URI beginning
with “/” character to which page the request should be forwarded after
switching the module.

The prefix parameter takes module name beginning with “/”, i.e, to
which module the request should be switched.
Configuration in struts-config.xml:

<action path=“/changeModule”

type=“org.apache.struts.actions.SwitchAction”prefix=“/admin”
page=“/home.jsp”/>

DispatchAction:

The org.apache.struts.actions.DispatchAction class allows us to

combine set

of similar actions into a single Action class, in order to simplify the

application design by eliminating the need to create separate action

classes

for each of the action. This class provides a mechanism for

modularizing a

set of related actions into a single Action.

The org.apache.struts.actions.DispatchAction class is an abstract class

with no abstract methods and is a sub type of BaseAction class, which
extends org.apache.struts.action.Action class. The execute() method
of DispatchAction dispatches the request to a public method that is
named by the request parameter value, the parameter name is
specified through parameter attribute of <action> tag in struts-
config.xml file.

Steps to use DispatchAction class:

 Create an action class

  Configure action mapping

Creating action class:

Subclass the Action class with DispatchAction class and provides a set
of methods that will be called by the execute() method of
DispatchAction.

Note that this class should not override execute() method like other
actions.

Configuring action mapping:

<action path=“/mypath” type=“com.mk.struts.MyAction”

name=“myform” parameter=“submit” validate=“false”>

<forward name=“success” path=“/home.jsp”/>

</action>
Eclipse IDE:
Eclipse is an open-source software framework written primarily in
Java. In its default form it is an Integrated Development Environment
(IDE) for Java developers, consisting of the Java Development Tools
(JDT) and the Eclipse Compiler for Java (ECJ). Users can extend its
capabilities by installing plug-ins written for the Eclipse software
framework, such as development toolkits for other programming
languages, and can write and contribute their own plug-in modules.
Language packs are available for over a dozen languages.

Architecture:
The basis for Eclipse is the Rich Client Platform (RCP). The following
components constitute the rich client platform:

 OSGi - a standard bundling framework

 Core platform - boot Eclipse, run plug-ins

 the Standard Widget Toolkit (SWT) - a portable widget toolkit

 JFace - viewer classes to bring model view controller

programming to SWT, file buffers, text handling, text editors

 the Eclipse Workbench - views, editors, perspectives, wizards

Eclipse's widgets are implemented by a widget toolkit for Java called

SWT, unlike most Java applications, which use the Java standard
Abstract Window Toolkit (AWT) or Swing. Eclipse's user interface also
leverages an intermediate GUI layer called JFace, which simplifies the
construction of applications based on SWT.

Eclipse employs plug-ins in order to provide all of its functionality on

top of (and including) the rich client platform, in contrast to some
other applications where functionality is typically hard coded. This
plug-in mechanism is a lightweight software componentry framework.
In addition to allowing Eclipse to be extended using other
programming languages such as C and Python, the plug-in framework
allows Eclipse to work with typesetting languages like LaTeX,
networking applications such as telnet, and database management
systems. The plug-in architecture supports writing any desired
extension to the environment, such as for configuration management.
Java and CVS support is provided in the Eclipse SDK.

The key to the seamless integration of tools with Eclipse is the plug-in.
With the exception of a small run-time kernel, everything in Eclipse is
a plug-in. This means that a plug-in you develop integrates with
Eclipse in exactly the same way as other plug-ins; in this respect, all
features are created equal.

The Eclipse SDK includes the Eclipse Java Development Tools, offering
an IDE with a built-in incremental Java compiler and a full model of
the Java source files. This allows for advanced refactoring techniques
and code analysis. The IDE also makes use of a workspace, in this
case a set of metadata over a flat file space allowing external file
modifications as long as the corresponding workspace "resource" is
refreshed afterwards. The Visual Editor project allows interfaces to be
created interactively, hence allowing Eclipse to be used as a RAD tool.

The following is a list of notable projects and plug-in for the

Eclipse IDE.

These projects are maintained by the Eclipse community and hosted

by the Eclipse Foundation.

1. Core projects:
Rich Client Platform (Platform) is the core framework that all other
Eclipse projects are built on.

Java Development Tools (JDT) provides support for core Java SE. This
includes a standalone fast incremental compiler.

2. Tools projects:

C/C++ Development Tools (CDT) adds support for C/C++ syntax

highlighting, code formatting, and debugger integration and project
structures. Unlike the JDT project, the CDT project does not add a
compiler and relies on an external tool chain.

Graphical Editing Framework (GEF) allows developers to build

standalone graphical tools. Example use includes circuit diagram
design tools, activity diagram editors and WYSIWYG document editors.

3. Web projects:

J2EE Standard Tools (JST) extends the core JDT to include support for
Java EE projects. This includes EJBs, JSPs and Servlets.

PHP Development Tools (PDT)

Web Standard Tools (WST) adds standards compliant web

development tools. These tools include editors for XML, HTML and
CSS.

4. Modeling projects:
Eclipse Modeling Framework (EMF) a modeling framework and code
generation facility for building tools and other applications based on a
structured data model, from a model specification described in XMI.

Graphical Modeling Framework (GMF) is a generative component and

runtime infrastructure for developing graphical editors based on EMF
and GEF.

5. Other projects:

Test and Performance Tools Platform (TPTP) which provides a platform

that allows software developers to build test and performance tools,
such as debuggers, profilers and benchmarking applications.

Business Intelligence and Reporting Tools Project (BIRT), an Eclipse-

based open source reporting system for web applications, especially
those based on Java EE.

WebServer/Application Server:

An application server is a software engine that delivers applications to

client computers or devices, typically through the Internet and using
the Hypertext Transfer Protocol. Application servers are distinguished
from web servers by the extensive use of server-side dynamic content
and frequent integration with database engines.

Common features:

Application server products typically bundle middleware to enable

applications to intercommunicate with dependent applications, like web
servers, database management systems, and chart programs. Some
application servers also provide an API, making them operating system
independent. Portals are a common application server mechanism by
which a single point of entry is provided to multiple devices.

Java application servers:

Java EE Servers:

Following the success of the Java platform, the term application server
sometimes refers to a Java Platform--Enterprise Edition (J2EE) or Java
EE 5 application server. Among the better known Java Enterprise
Edition application servers are WebLogic Server (BEA), JBoss (Red
Hat), WebSphere (IBM), JRun (Adobe), Apache Geronimo (Apache
Foundation, based on IBM WebSphere), Oracle OC4J (Oracle
Corporation), Sun Java System Application Server (Sun Microsystems)
and Glassfish Application Server (based on Sun Java System
Application Server).

Java application server was the first open source application server to
have achieved official compliance with the Java Enterprise
Specification. BEA delivered the first Java EE 5 certified application
server followed by Sun Microsystems' reference implementation
Glassfish.

The Web modules are servlets and Java Server Pages, and business
logic is built into Enterprise JavaBeans (EJB-3 and later). The
Hibernate project offers an EJB-3 container implementation for the
JBoss Application server. Tomcat from Apache and JOnAS from
ObjectWeb are typical of containers into which these modules can be
put.

A Java Server Page (JSP) is a servlet from Java that executes in a Web
container—the Java equivalent of CGI scripts. JSPs are a way to create
HTML pages by embedding references to the server logic within the
page. HTML coders and Java programmers can work side by side by
referencing each other's code from within their own. JavaBeans are the
independent class components of the Java architecture from Sun
Microsystems.

The application servers mentioned above mainly serve Web

applications. Some application servers target networks other than the
Web: Session Initiation Protocol servers, for instance, target telephony
networks.

Scope of The Development Project

Database Tier: The concentration is applied by adopting the Oracle
8.1 Enterprise versions. SQL is taken as the standard query language.
The overall business rules are designed by using the power of PL/SQL
components like stored procedures stored functions and database
triggers.

User Tier: The use interface is developed is a browser specific

environment to have centralized architecture. The components are
designed using Dreamweaver and Java server pages power the
dynamic of the page design.

Data Base Connectivity Tier

The communication architecture is designed by concentrated on the

standards of struts and Java Beans. The database connectivity is
established using the Java Database connectivity.

JBOSS

JBoss Application Server (or JBoss AS) is a free software / open source
Java EE-based application server. Because it is Java-based, JBoss AS is
cross-platform, usable on any operating system that Java supports.

Environment

JBoss AS 4.0 is a J2EE 1.4 application server, with embedded Tomcat

5.5. Any JVM between 1.4 and 1.5 is supported. JBoss can run on
numerous operating systems including Windows, Mac OS X, many
POSIX platforms, and others, as long as a suitable JVM is present.

JBoss AS 4.2 is also a J2EE 1.4 application server, but EJB 3 is

deployed by default. It requires JDK 5. Tomcat 6 is bundled with it.
Next JBoss AS 5 will be Java EE 5 application server.
Product features

 Failover (including sessions)

 Load balancing

 Distributed caching (using JBoss Cache, a standalone product)

 Distributed deployment (farming)

 Enterprise JavaBeans version 3

SAMPLE CODING
<%@ page
import="com.dts.project.dao.GetAdAlDeDAO,com.dts.core.util.CoreHash,java.
util.*,com.dts.project.model.GetAdAlDeModel" %>

<%@page import="com.dts.project.model.AdvanceModel"%>

<%@page import="com.dts.dae.model.Profile"%>

<%@page import="com.dts.project.model.AllowanceModel"%>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">

<!-- DW6 -->

<head>

<script language="JavaScript" src="scripts/gen_validatorv31.js"

type="text/javascript"></script>

<script language="JavaScript" type="text/javascript"

src="scripts/ts_picker.js"></script>

<script language="JavaScript1.1" src="scripts/pass.js">

</script> <script type="text/javascript" src="scripts/image.js"> </script>

<script type="text/javascript" src="scripts/general.js"> </script>

<script type="text/javascript" src="scripts/adi.js"> </script>

<script type="text/javascript" src="scripts/form_validation.js"> </script>

<script>

//var x_win = window.self;

<script>

//var x_win = window.self;

function GetThose(){

alert('Called');

var form = document.register;

var selectWidget = document.forms.register.elements["aname"];

var myValue = selectWidget.options[selectWidget.selectedIndex].value;

var myName = selectWidget.options[selectWidget.selectedIndex].name;

alert(myName);

window.location.href="http://localhost:8081/NewPayRoll1/CheckAdvanceActi
on?AdvanceName="+myName+"&AdvanceId="+myValue;

function inDate(){

var date=new Date();

document.register.aDate.value=date.getDate()+"-"+(date.getMonth()
+1)+"-"+date.getYear();

function check(){

var min=document.register.aMinValue.value;

var max=document.register.aMaxValue.value;

if(min<max){}

else

alert ('Maximum Must Be Greater Than Minimum Value');

document.getElementById("max").focus();
 }

</script>

<STYLE type=text/css>

input {

width: 125px;

font-family: Verdana;

font-size: 8pt;

</style>

<!-- Copyright 2005 Macromedia, Inc. All rights reserved. -->

<title>Lodging - Home Page</title>

<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-

1" />

<link rel="stylesheet" href="css/mm_lodging1.css" type="text/css" />

<style type="text/css">

<!--

.style1 {color: #FFFFFF}

body {

background-color: #FFFFFF;

}
-->

</style>

</head>

<body>

<table border="0" align="center" cellpadding="0" cellspacing="0">

<tr>

<td height="139" colspan="6" align="left" valign="top"

nowrap="nowrap"><img src="images/mm_spacer.gif" alt="" width="15"
height="1" border="0" /><br />

<table width="100%" border="0">

<tr>

<td bgcolor="#0F615D"><img src="images/Distributed Payroll

System.jpg" alt="ds" width="800" height="139" /></td>

</tr>

</table></td>

</tr>

<tr bgcolor="#ffffff">

<td colspan="6"><img src="images/mm_spacer.gif" alt="" width="1"

height="1" border="0" /></td>

</tr>

<tr bgcolor="#a4c2c2">

<td width="229" nowrap="nowrap"

bgcolor="#16B3AA">&nbsp;</td>

<td height="36" colspan="3" bgcolor="#16B3AA" class="navText"

id="navigation">

<jsp:include page="GeneralOptions.html"/>

</td>
 <td width="125" bgcolor="#16B3AA">&nbsp;</td>

<td width="61" bgcolor="#16B3AA">&nbsp;</td>

</tr>

<tr bgcolor="#ffffff">

<td colspan="6"><img src="images/mm_spacer.gif" alt="" width="1"

height="1" border="0" /></td>

</tr>

<tr bgcolor="#ffffff">

<td colspan="2" valign="top" bgcolor="#16B3AA"><table

border="0" cellspacing="0" cellpadding="0" width="230">

<tr>

<td width="15">&nbsp;</td>

<td width="200" height="100%" class="sidebarText"

id="padding"><br />

&nbsp;<br /> </td>

<td width="15">&nbsp;</td>

</tr>

</table> </td>

<td width="50" valign="top"><img src="images/mm_spacer.gif"

alt="" width="50" height="1" border="0" /></td>

<td width="529" valign="top"><br />

<form action="./LoginAction" method="post" name="register"

onSubmit="return validate()">
 <center> <% if(request.getParameter("status")!=null)

{%>

<strong><font color=red><
%=request.getParameter("status")%></font></strong>

<%}%></center>

<table cellpadding="2px" cellspacing="1px" bgcolor="#F4F5F7"

width="400px" class="tableBorder" align="center">

<tr>

<td colspan="2" bgcolor="#16B3AA">&nbsp;</td>

</tr>

<tr>

<td colspan="2" class="label">&nbsp;</td>

</tr>

<tr>

<td align="center" colspan="2">

<img src="images/arrow.png" border="0"

align="absbottom"/>&nbsp;

<span class="message">Login to the Panel</span>

</td>

</tr>

<tr>

<td colspan="2" class="label">&nbsp;</td>

</tr>

<tr>
 <td class="label" align="right" width="40%">Username:</td>

<td align="left" width="60%"><input type="text" name="username"

maxlength="30"/></td>

</tr>

<tr>

<td class="label" align="right">Password:</td>

<td align="left"><input type="password" name="password"

maxlength="30" /></td>

</tr>

<tr>

<td class="label" align="right"></td>

<td align="left"><input type="submit" value="Login" /></td>

</tr>

<tr>

<td colspan="2" class="label">&nbsp;</td>

</tr>

</table>

</form>

<script>

var frmvalidator = new Validator("register");

frmvalidator.addValidation("username","req","Please Enter Username");

 frmvalidator.addValidation("password","req","Please Enter Password");

</script>

<td width="108">&nbsp;</td>

<td width="61">&nbsp;</td>

</tr>

<tr bgcolor="#ffffff">

<td colspan="6">`</td>

</tr>

<tr>

<td height="20" colspan="6" bgcolor="#0F615D"><div

align="center"><span class="style2 style1"><jsp:include
page="footer.html"/> </span></div></td>

</tr>

</body>

</html>
TESTING
Testing Concepts

• Testing

• Testing Methodologies

 Black box Testing:

 White box Testing.
 Gray Box Testing.

• Levels of Testing

 Unit Testing.
 Module Testing.
 Integration Testing.
 System Testing.
 User Acceptance Testing.

• Types Of Testing

 Smoke Testing.
 Sanitary Testing.
 Regression Testing.
 Re-Testing.
 Static Testing.
 Dynamic Testing.
 Alpha-Testing.
  Beta-Testing.
 Monkey Testing.
 Compatibility Testing.
 Installation Testing.
 Adhoc Testing.
 Ext….

TCD (Test Case Documentation)

• STLC
 Test Planning.
 Test Development.
 Test Execution.
 Result Analysis.
 Bug-Tracing.
 Reporting.

• Microsoft Windows – Standards

• Manual Testing
• Automation Testing (Tools)
 Win Runner.
 Test Director.
Testing:

• The process of executing a system with the intent of finding an error.

• Testing is defined as the process in which defects are identified,
isolated, subjected for rectification and ensured that product is defect
free in order to produce the quality product and hence customer
satisfaction.
• Quality is defined as justification of the requirements
• Defect is nothing but deviation from the requirements
• Defect is nothing but bug.
• Testing --- The presence of bugs
• Testing can demonstrate the presence of bugs, but not their absence
• Debugging and Testing are not the same thing!
• Testing is a systematic attempt to break a program or the AUT
• Debugging is the art or method of uncovering why the script /program
did not execute properly.
Testing Methodologies:

• Black box Testing: is the testing process in which tester can

perform testing on an application without having any internal
structural knowledge of application.
Usually Test Engineers are involved in the black box testing.

• White box Testing: is the testing process in which tester can

perform testing on an application with having internal structural
knowledge.
Usually The Developers are involved in white box testing.
 • Gray Box Testing: is the process in which the combination of black
box and white box tonics’ are used.

Levels of Testing:

Module1 Module2 Module3

Units Units Units

i/p Integration o/p i/p Integration

o/p

System Testing: Presentation + business +Databases

 UAT: user acceptance testing

STLC (SOFTWARE TESTING LIFE CYCLE)

Test Planning:
 1.Test Plan is defined as a strategic document which
describes the procedure how to perform various testing on the
total application in the most efficient way.

2.This document involves the scope of testing,

3. Objective of testing,

4. Areas that need to be tested,

5. Areas that should not be tested,

6. Scheduling Resource Planning,

7. Areas to be automated, various testing tools

Used….

Test Development:

1. Test case Development (check list)

2. Test Procedure preparation. (Description of the Test cases).

1. Implementation of test cases. Observing the result.

Result Analysis:

1. Expected value: is nothing but expected behavior Of application.

2. Actual value: is nothing but actual behavior of application

Bug Tracing: Collect all the failed cases, prepare documents.

Reporting : Prepare document (status of the application)

Types Of Testing:

> Smoke Testing: is the process of initial testing in which tester looks for
the availability of all the functionality of the application in order to perform
detailed testing on them. (Main check is for available forms)

> Sanity Testing: is a type of testing that is conducted on an application

initially to check for the proper behavior of an application that is to check all
the functionality are available before the detailed testing is conducted by on
them.

> Regression Testing: is one of the best and important testing.

Regression testing is the process in which the functionality, which is already
tested before, is once again tested whenever some new change is added in
order to check whether the existing functionality remains same.

>Re-Testing: is the process in which testing is performed on some

functionality which is already tested before to make sure that the defects are
reproducible and to rule out the environments issues if at all any defects are
there.

Static Testing: is the testing, which is performed on an application when

it is not been executed.ex: GUI, Document Testing
Dynamic Testing: is the testing which is performed on an application
when it is being executed.ex: Functional testing.

Alpha Testing: it is a type of user acceptance testing, which is conducted

on an application when it is just before released to the customer.

 Beta-Testing: it is a type of UAT that is conducted on an application

when it is released to the customer, when deployed in to the real time
environment and being accessed by the real time users.

 Monkey Testing: is the process in which abnormal operations, beyond

capacity operations are done on the application to check the stability of it in
spite of the users abnormal behavior.

Compatibility testing: it is the testing process in which usually the

products are tested on the environments with different combinations of
databases (application servers, browsers…etc) In order to check how far the
product is compatible with all these environments platform combination.

Installation Testing: it is the process of testing in which the tester try to

install or try to deploy the module into the corresponding environment by
following the guidelines produced in the deployment document and check
whether the installation is successful or not.
Adhoc Testing: Adhoc Testing is the process of testing in which unlike the
formal testing where in test case document is used, with out that test case
document testing can be done of an application, to cover that testing of the
future which are not covered in that test case document. Also it is intended
to perform GUI testing which may involve the cosmotic issues.

TCD (Test Case Document):

Test Case Document Contains

• Test Scope (or) Test objective

• Test Scenario
• Test Procedure
• Test case
This is the sample test case document for the advertise details of Blazon
Agency project:
 Test scope:

• Test coverage is provided for the screen “ Login check” form of a

Administration module of Blazon Agency application
• Areas of the application to be tested

Test Scenario:

• When the office personals use this screen for the payment, tariff and
company registration and web advertisements on basis of
requirements and quit the form.

Test Procedure:

• The procedure for testing this screen is planned in such a way that the
data entry, status calculation functionality, saving and quitting
operations are tested in terms of GUI testing, Positive testing,
Negative testing using the corresponding GUI test cases, Positive test
cases, Negative test cases respectively

Test Cases:

• Template for Test Case

T.C.No Description Exp Act Result

1 Login With Home page Home page ok

Username and

password

Guidelines for Test Cases:

1. GUI Test Cases:

• Total no of features that need to be check

• Look & Feel
• Look for Default values if at all any (date & Time, if at all any require)
• Look for spell check

Example for Gui Test cases:

T.C.No Description Expected Actual value Result

value

Check for all the The

features in the screen
1
screen must
 contain all
the
features

Check for the The

alignment of the alignment
2
objects as per the should be
validations in proper
way

2. Positive Test Cases:

• The positive flow of the functionality must be considered

• Valid inputs must be used for testing
• Must have the positive perception to verify whether the requirements
are justified.

Example for Positive Test cases:

T.C.No Description Expected Actual value Result

value

1
2

3. Negative Test Cases:

• Must have negative perception.

• Invalid inputs must be used for test.

Example for Negative Test cases:

T.C.No Description Expected Actual value Result

value

1 Try to modify Modification

The information should not be
in date and allow
time

2
SCREENS
REPORTS
 FUTURE ENHANCEMENTS

Future Enhancements:
 It is not possible to develop a system that makes all the requirements of

the user. User requirements keep changing as the system is being used.

Some of the future enhancements that can be done to this system are:

• As the technology emerges, it is possible to upgrade the system and

can be adaptable to desired environment.

• Because it is based on object-oriented design, any further changes can

be easily adaptable.

• Based on the future security issues, security can be improved using

emerging technologies.

• sub admin module can be added

 CONCLUSION

This application software has been computed successfully and was also

tested successfully by taking “test cases”. It is user friendly, and has

required options, which can be utilized by the user to perform the

desired operations.

The software is developed using Java as front end and Oracle as back end in

Windows environment. The goals that are achieved by the software are:

 Optimum utilization of resources.

 Efficient management of records.

 Simplification of the operations.

 Less processing time and getting required information.

 User friendly.

 Portable and flexible for further enhancement.

 BIBLIOGRAPHY

Core Java™ 2 Volume I – Fundamentals 7th Cay S. Hortsman

Edition
Pearson Education – Sun Microsystems Gary Cornell

Core Java™ 2 Volume II – Advanced Cay S. Hortsman

Pearson Education – Sun Microsystems Gary Cornell

Head First Servlets & JSP Eric Freeman

O’Reilly – SPD Elisabeth Freeman

The Book of JavaScript 2nd Edition thau

SPD

Effective Java – Programming Language Guide Joshua Bloch

Pearson Education – Sun Microsystems

Java Database Best Practices George Reese

O’Reilly – SPD

JBoss – A Developers Notebook Norman Richards

O’Reilly – SPD Sam Griffith