online_auctioning_system full.docx

8/19/2019 ONLINE_AUCTIONING_SYSTEM full.DOCX

1/205

ONLINE AUCTIONING SYSTEM

_______________

A Thesis Presented to the Faculty of

San Diego State University

_______________

In Partial Fulfillment

of the Requirements for the DegreeMaster of Science


2/205

in om!uter Science

_______________

"y Shanthi Potla Summer #$%%


3/205


4/205


5/205


6/205


7/205

iii


8/205

o!yright & #$%%

"y

Shanthi Potla

All Rights Reserved


9/205

iv

DEDICATION

To all'


10/205

v

ABSTRACT OF THE THESIS

(nline Autioning System

"y

Shanthi Potla

Master of Science in om!uter Science

San Diego State University) #$%%

The online auctioning system is a fle*i"le solution for su!!orting lot+ "ased online auctions'The thesis e*!lains the construction of an auction ,e"site' The system has "een designed to

"e highly+scala"le and ca!a"le of su!!orting large num"ers of "idders in an active auction'The online auction system lets you easily "ro,se lots and !lace "ids using a secure server'All cost of mailing lots ,ill "e !aid "y the "uyer' The o"-ective is to develo! a user+friendlyauctioning site ,here any .ind of !roduct can "e auctioned and !rovide value+added servicesto the "idders and the sellers' The !roducts ,ill "e authenticated and the site !rovides a safeenvironment for online users'


11/205

vi

TABLE OF CONTENTS

PA/0

A1STRAT v

2IST (F TA120S *

2IST (F FI/UR0S *i

3APT0R

% I4TR(DUTI(4 %

%'% (vervie, #

%'% 4o of Modules #

%'# Descri!tion for Modules 5

%'#'% Admin Module 5


12/205

%'#'# Seller Module 5

%'#'5 1uyer Module 5

%'#'6 7isitor Module 5

%'#'8 Security and Authentication 5

%'#'9 Re!orts 5

# R0S0AR3 : T034(2(/; 6

#'% Research 6

#'%'% 0*isting System 6

#'%'# Pro!osed System 6

#'%'5 Requirements 8

#'# Technology Descri!tion 8

#'#'% 3TM2 8

#'#'%'% 3y!er Te*t Mar.u! 2anguage 8


13/205

#'#'%'# Attri"utes 9

#'#'%'5 Advantages 9

#'#'#


14/205

vii

#'#'5

#'#'5'8 The 1yte ode >

#'#'5'9 om!ilation of ode

#'#'5' Sim!le%$

#'#'5'%$ ("-ect+(riented %$

#'#'5'%% Ro"ust %$

#'#'6


15/205

#'#'6'%


16/205

#'#'='5 Features of Servlets %6

#'#'='6 2oading Servlets %8

#'#'='8 2oading Remote Servlets %8

#'#'='9 Invo.ing Servlets %8

#'#'='=


17/205

viii

#'#'> Struts %=

#'#'>'% 0lements of a Ce" A!!lication %=

#'#'>'#

#'#'>'5 The M7 Model %

#'#'>'6 M7 7ie, %

#'#'>'8 M7 ontroller #$

#'#'>'9 Frame,or. #$

#'#'>'= reation of the Struts Frame,or. #%

#'#'>'> The Struts om!onent Pac.ages #%

#'#'>' Struts ontroller om!onents #%

#'#'>'%$ Struts ActionServlet #%

#'#'>'%% Struts Action lasses##

#'#'>'%# Ma!!ing the Actions##


18/205

#'#'>'%5 Determining the 4e*t 7ie, ##

#'#'>'%6 Struts Model om!onents ##

#'#'>'%8 Using the Struts ActionForm #5

#'#'>'%9 Using '%= Message Resource 1undles #6

#'#'>'%> Multi!le A!!lication Su!!ort #6

#'#'>'% onfiguring the Struts A!!lication #6

#'#'>'#$ ActionForms and Sco!e #8

5 M0T3(D #9

5'% The ActionForm validate?@ Method #9

5'%'% The ActionForm reset?@ Method #=

5'%'# Declaring ActionForms in the Struts onfiguration File #>

5'%'5 Declaring ActionForm Pro!erties as Strings #>


19/205

5'%'6 Using Action0rrors #>

5'%'8 Struts 1uilt+in Actions 5%

5'%'9 For,ard Action 5#

5'%'= Include Action 5#

5'%'> S,itch Action 5#

5'%' Dis!atch Action 5#


20/205

i*

5'%''%Ste!stouseDis!atchAction lass'''''''''''''''''''''''''''''''''''''''''''''''''

55

5'%''#reatingActionlass''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

55

5'%''5onfiguringActionMa!!ing'''''''''''''''''''''''''''''''''''''''''''''''''''''''''

55

5'#

Sco!eoftheDevelo!mentPro-ect'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

55

5'#'%0nvironment''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

56

5'#'#ProductFeatures''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''


21/205

56

5'5

DataFlo,'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

56

5'6

DataFlo,Diagrams''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

58

5'8

UnifiedModeling2anguage?UM2@ Diagrams ''''''''''''''''''''''''''''''''''''''''''''''

6$

5'8'%UserModel7ie,''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

6$

5'8'#StructuralModel7ie,''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

6$

5'8'51ehavioralModel7ie,''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

6%


22/205

5'8'6Im!lementationModel7ie, ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

6%

5'8'80nvironmentalModel7ie,''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

6%

5'8'9olla"orationDiagram''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

69

5'8'=(!eration2evelSequenceDiagrams''''''''''''''''''''''''''''''''''''''''''''''''''''''

6=

5'8'>(!erational2evelolla"oration Diagrams ''''''''''''''''''''''''''''''''''''''''''''

6=

5'8'ActivityDiagram''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

6=

6

T0STI4/ '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

8#

6'%


23/205

Soft,areTesting''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

8#

6'#

3istory''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

86

8

FUTUR0 043A40M04TS A4D(42USI(4'''''''''''''''''''''''''''''''''''''''''''''''''

8=

8'% 2imitations of the System ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

8=

8'#

Future0nhancements'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

8=

8'5 Cor. Done'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

8=

R0F0R040S ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

8

APP04DI

(D0

'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''


24/205

9$


25/205

*

LIST OF TABLES

PA/0

Ta"le 6'%' Performance Ta"le 86


26/205

*i

LIST OF FIGURES

PA/0

Figure #'%' ' 2evel # data flo, diagram for Admin' 5=


27/205

Figure 5'' 2evel 5 data flo, diagram for Admin' 5>

Figure 5'%$' 2evel 6 data flo, diagram for Admin' 5>

Figure 5'%%' 2evel % data flo, diagram for seller 5>

Figure 5'%#' 2evel # data flo, diagram for Seller' 5

Figure 5'%5' 2evel % data flo, diagram for 1uyer' 5

Figure 5'%6' 2evel # data flo, diagram' 5

Figure 5'%8' 0ntity+ Relationshi! flo, ,hich e*!lains the relationshi! in data 6$

Figure 5'%9' UM2 diagram of the ,or. 6#

Figure 5'%=' System use case diagram' 65

Figure 5'%>' Admin use case diagram65

Figure 5'%' 1uyerESeller ?ustomer@ use case diagram' 66

Figure 5'#$' 2ogin +7alidate 2ogin+7ie, ustomers+7ie, 1id Items+vie,

Auction items today and end day 66


28/205


29/205

*ii

Figure 5'#9' Administrator activity diagram 6

Figure 5'#=' Seller ?(,ner of the Article or customer@ activity diagram 8$

Figure 5'#>' 1uyer ?Registered 1idder or customer@ activity diagram 8%


30/205

%

CHAPTER 1

INTRODUCTION

An Auction is 2atin ,or. ,hich means augment' Auction is a "id) a !rocess of sellingG "uying and services offered ta.e !lace' There are several different ty!es of auctions andcertain rules e*ist for each auction' There are variations for an auction ,hich may includeminimum !rice limit) ma*imum !rice limit and time limitations etc' De!ending u!on theauction method "idder can !artici!ate remotely or in !erson' Remote auction include !artici!ating through tele!hone) mail) and internet' Sho!!ing online has ,idely gro,nGonline auction system is increasing ra!idly' (nline auction is "ecoming more and more !o!ular in electronic commerce and hence it should system must increase its quality and

security'

The online auction system is a model ,here ,e !artici!ate in a "id for !roducts and service'This auction is made easier "y using online soft,are ,hich can regulate !rocesses involved'There are several different auction methods or ty!es and one of the most !o!ular methods is0nglish auction system' This system has "een designed to "e highly+scala"le and ca!a"le ofsu!!orting large num"ers of "idders in an active auction'

(nline Auctioning System has several other names such as e+Auctions) electronic auction etc'The requirement for online auction or online "idding can "e more accurately s!ecified "y theclient' It should "e healthy and ,ill "e a good !ractice ,hen it is made more trans!arent as amatter of fact'


31/205

(nline 1idding has "ecome more ,ide s!read in all sorts of industrial usage' It not onlyincludes the !roduct or goods to "e sold) it also has services ,hich can "e !rovided' Due totheir lo, cost this e*!ansion made the system to gro,'

(nline "idding has "ecome a standard method for !rocurement !rocess' 1idders can "e

maintained in a single data"ase according to the !reference) and they can "e monitored'UserHs data can "e maintained in a confidential ,ay for validity and integrity of contractualdocumentation' 4eat re!orting reduces !a!er,or.) !ostage) !hotoco!ying and time


32/205

#

"eneficial' Multi!le "idders can "e communicated ,ith a great ease' This system allo,smulti!le "ids "y single users'

(nline "idding is "ased u!on lo,est or the highest !rice ,hich is initiated "ut not the "estvalue for the !roduct' Although there is a chance to fi* the criteria against the fact e*!ectedto have desired value "y the seller'

1.1 OVERVIEW

The ("-ective is to develo! a user+friendly auctioning site ,here any .ind of !roduct can "eauctioned and !rovide value+added services to the "idders and the sellers' The !roducts ,ill "e authenticated and the site !rovides a safe environment for online users

Secure registration of all users including a !ersonal !rofile Administrators ,ould authoriJethe !roduct to auction) set auction dates and Minimum auction amount for that !roduct'

Prior to each "id) the userHs "an. or credit account must "e authenticated for availa"le "alance required for the "id'

om!lete SearchESite Ma! of the entire site for easy access'

Discussion forums for users to interact ,ith other users to .no, a"out the !roductHs valueand originality'

(nline 2egal Documentation to avoid dis!utes' /uidance to the users a"out the same must "eavaila"le'

Rare articles may "e ,ithheld "y o,ner on the advice of the administrator to "e thro,n o!enin s!ecial auctions held "y the site so as to increase the "id+values'


33/205

1.1 NO OF MODULES

The system after careful analysis has "een identified to "e !resented ,ith the follo,ingmodules

Admin Module' Seller Module' 1uyer Module' 7isitor Module'

Security and authentication' Re!orts'


34/205

5

1.2 DESCRIPTION FOR MODULES

The follo,ing sections include the descri!tions for modules'

1.2.1 A!in Mou"#

This module !rovides the com!lete information related to !roducts for sale and the "uyerscan "id for the !roducts and can o,n them' All this has to "e !rovided and maintained "y theadmin "ecause the com!lete auction !rocess is to "e .e!t under control till the !roduct sale

gets confirmed'

1.2.2 S#""#$ Mou"#

Sellers ,ant a !lace ,here seller can sale their !roducts at a higher !rice and get ma*imum "enefit out of that' This is the !lace ,here seller can dis!lay all his !roducts and sell them'

1.2.% Bu$ Mou"#

The !eo!le al,ays ,ant different things to !urchase "ut in the local mar.et they can havelocal !roducts only' 1ut in this a!!lication "uyer can "uy any !roduct from any !art of the,orld at a very "est com!etitive !rice and o,n the !roduct'

1.2.' Vi(ito$ Mou"#

7isitor is nothing "ut all the !eo!le ,ho visits this a!!lication online' They can .no, theinformation of all the !roducts) ,hich are for sale under this a!!lication'


35/205

1.2.) S#cu$it& *n Aut+#ntic*tion

The security and authentication is as follo,s

2ogin as "uyer or seller or administrator' hange !ass,ord'

Forgot Pass,ord'

Registration for "uyer E seller'

R#,o$t(

In this module) different actors can generate the different ty!es of re!orts according to theiraccess'


36/205

6

CHAPTER 2

RESEARCH - TECHNOLOGY

The on"in# *uctionin (&(t#! is a fle*i"le solution for su!!orting lot+ "ased online auctions'The system has "een designed to "e highly+scala"le and ca!a"le of su!!orting large num"ersof "idders in an active auction' To hel! "usiness ,ith financeHs and !urchases in on"in#*uctionin (&(t#!'

2.1 R ESEARCH

Research includes ,hat e*isting system is and the !ur!ose of the system'

2.1.1 E/i(tin S&(t#!

From a recent study ma.e "y scientists at arnegie Mellon University) found many fraudschemes from the historical auction data using data mining techniques and otheraccom!liances K5)%#L(ne of the most currently fraud schemes is that the "idders are mas.ingfalse identity or accounts in order to increase the sale !rice K%#)%5L'

urrently there are t,o a!!roaches mostly "eing im!lemented such as !olicy+"ased andre!utation+"ased trust management K#L) ,hich also lag certain security issues'


37/205

There ,as a recently !ro!osed system "y /aneri,al and Srivastava) ,hich ,as a re!utation "ased model for sensor net,or.s' This system ,or.s ,ell in maintain the re!utation for thenodes and also in evaluating trust,orthiness K=L' 1ut the main dra,"ac. is that there is noeffective and !articular method to !revent the users from giving false identity and hence thesystem fails in !roviding a secured environment'

2.1.2 P$o,o(# S&(t#!

The develo!ment of this ne, system contains the follo,ing activities) ,hich try to develo!the ,e"+a!!lication entire !rocess .ee!ing in the vie, of data"ase integration a!!roach

This system ,ill generate team !rogress and also !rovides secure registration and !rofile

management of the users'


38/205

8

Administrators ,ould authoriJe the !roduct to auction) set auction dates : minimum auctionamount for that !roduct'

Prior to each "id) the userHs "an. or credit account must "e authenticated for availa"le "alance required for the "id'

Users can select their interested fields for "idding and !eriodic Mail alerts must "e sent incase an article in that field goes on auction'


2.1.% R#0ui$#!#nt(

The ("-ective is to develo! a user+friendly auctioning site ,here any .ind of !roduct can "eauctioned and !rovide value+added services to the "idders and the sellers' The !roducts ,ill "e authenticated and the site !rovides a safe environment for online users

Secure registration of all users including a !ersonal !rofile'

Prior to each "id) the userHs "an. or credit account must "e authenticated for' Availa"le "alance required for the "id'


2.2 TECHNOLOGY DESCRIPTION


39/205

The !ro!osal has to "e descri"ed in a detailed form to get an overvie, and an understandingof the functionalities of the technical a!!roach' This !rovides the technical descri!tion of thecharacteristics of a !ro!osal'

2.2.1 HTML

3TM2) an initialiJe of 3y!erte*t Mar.u! 2anguage) is the !redominant mar.u! language for ,e" !ages' It !rovides a means to descri"e the structure of te*t+"ased information in adocument "y denoting certain te*t as headings) !aragra!hs) lists) and so on and tosu!!lement that te*t ,ith interactive forms) em"edded images) and other o"-ects'

2.2.1.1 HYPER TET MARUP LANGUAGE

3y!erte*t Mar.u! 2anguage ?3TM2@) the languages of the Corld Cide Ce" ?CCC@)allo,s users to !roduces Ce" !ages that include te*t) gra!hics and !ointer to other Ce" !ages ?3y!erlin.s@'


40/205

9

3TM2 can "e used to dis!lay any ty!e of document on the host com!uter) ,hich can "egeogra!hically at a different location' It is a versatile language and can "e used on any !latform or des.to!'

3TM2 !rovides tags ?s!ecial codes@ to ma.e the document loo. attractive' 3TM2 tags arenot case+sensitive' Using gra!hics) fonts) different siJes) color) etc') can enhance the !resentation of the document' Anything that is not a tag is !art of the document itself'

2.2.1.2 ATTRIBUTES

The attri"utes of an element are name+value !airs) se!arated "y NON) and ,ritten ,ithin the startla"el of an element) after the elements name' The value should "e enclosed in single or dou"lequotes) although values consisting of certain characters can "e left unquoted in 3TM2 ?"ut not3TM2@'2eaving attri"ute values unquoted is considered unsafe'

Most elements ta.e any of several common attri"utes id) class) style and title' Most also ta.elanguage+related attri"utes language and dir'

2.2.1.% ADVANTAGES

The advantages include

A 3TM2 document is small and hence easy to send over the net' It is small "ecause it doesnot include formatted information'

3TM2 is !latform inde!endent'

3TM2 tags are not case+sensitive'


41/205

2.2.2 3*4*Sc$i,t


42/205

=

2.2.2.1 3AVASCRIPT VS 3AVA


43/205

Initially the language ,as called as Qoa. "ut it ,as renamed as Q


44/205

>

information and Dynamic active !rograms' The Dynamic) Self+e*ecuting !rograms causeserious !ro"lems in the areas of Security and !ro"a"ility K=L'

2.2.%.2 3AVA CAN BE USED TO CREATE TWO

TYPES OF PROGRAMS

A!!lications and A!!lets An a!!lication is a !rogram that runs on our om!uter under theo!erating system of that com!uter' It is more or less li.e one creating using or '


45/205

The .ey that allo,s the


46/205

com!iles "yte code into e*ecuta"le code in real time) on a !iece+"y+!iece) demand "asis' It isnot !ossi"le to com!ile an entire


47/205

%$

2.2.%.: SIMPLE


48/205

0sta"lish a connection ,ith a data"ase' Send SB2 statements'

Process the results'

2.2.'.1 3DBC VER . ODBC AND OTHER API

At this !oint) Microsofts (D1 ?(!en Data"ase onnectivity@ API is that !ro"a"ly the most,idely used !rogramming interface for accessing relational data"ases' It offers the a"ility toconnect to almost all data"ases on almost all !latforms'


49/205

%%

So ,hy not -ust use (D1 from


50/205

In the t,o+tier model) a


51/205

%#

4ative+API !artly+


52/205

A data"ase management system ?D1MS@ is com!uter soft,are designed for the !ur!ose ofmanaging data"ases) a large set of structured data) and run o!erations on the data requested "y numerous users' Ty!ical e*am!les of D1MSs include (racle) D1#) Microsoft Access)Microsoft SB2 Server) Fire"ird) PostgreSB2) MySB2) SB2ite) FileMa.er and Sy"aseAda!tive Server 0nter!rise' D1MSs are ty!ically used "y Data"ase administrators in thecreation of Data"ase systems' Ty!ical e*am!les of D1MS use include accounting) human

resources and customer su!!ort systems'

2.2.).2 DESCRIPTION

A D1MS is a com!le* set of soft,are !rograms that controls the organiJation) storage)management and retrieval of data in a data"ase' A D1MS includes


53/205

%5

A modeling language to define the schema of each data"ase hosted in the D1MS) accordingto the D1MS data model'

The four most common ty!es of organiJations are the hierarchical) net,or.) relational ando"-ect models' Inverted lists and other methods are also used' A given data"ase managementsystem may !rovide one or more of the four models' The o!timal structure de!ends on thenatural organiJation of the a!!lications data) and on the a!!lications requirements ?,hichinclude transaction rate ?s!eed@) relia"ility) maintaina"ility) scala"ility) and cost@'

2.2.5 S>L

Structured Buery 2anguage ?SB2@ is the language used to mani!ulate relational data"ases' SB2is tied very closely ,ith the relational model' In the relational model) data is stored in structurescalled relations or ta"les. SB2 statements are issued for the !ur!ose of

D*t* #?inition Defining ta"les and structures in the data"ase ?DD2 used to create) alter anddro! schema o"-ects such as ta"les and inde*es@'

D*t* !*ni,u"*tion Used to mani!ulate the data ,ithin those schema o"-ects ?DM2 Inserting) U!dating) Deleting the data) and Buerying the Data"ase@'

2.2.5.1 DATA

Defining ta"les and structures in the data"ase ?DD2 used to create) alter and dro! schemao"-ects such as ta"les and inde*es@'

2.2.5.2 DATA MANIPULATION


54/205

Used to mani!ulate the data ,ithin those schema o"-ects ?DM2 Inserting) U!dating) Deletingthe data) and Buerying the Data"ase@' A schema is a collection of data"ase o"-ects that caninclude ta"les) vie,s) inde*es and sequences'

2.2.8 S#$4"#t(

The


55/205

%6

Servlets are o"-ects that conform to a s!ecific interface that can "e !lugged into a


56/205

nothing a"out

The !rotocol "eing used to transmit on the net' 3o, it is loaded'

The server environment it ,ill "e running in'

These qualities are im!ortant) "ecause it allo,s the Servlet API to "e em"edded in

many different .inds of servers' There are other advantages to the Servlet API as ,ell' These

include

ItHs e*tensi"le + you can inherit all your functionality from the "ase classes made availa"le toyou'

ItHs sim!le) small) and easy to use'

2.2.8.% FEATURES OF SERVLETS

Features of Servlets include

Servlets are !ersistent' Servlet are loaded only "y the ,e" server and can maintain services

"et,een requests'

Servlets are fast' Since Servlets only need to "e loaded once) they offer much "etter !erformance over their /I counter!arts'


57/205

%8

Servlets are !latform inde!endent'

Servlets are e*tensi"le'


58/205

A Servlet invo.er is a Servlet that invo.es the NserviceN method on a named Servlet' If theServlet is not loaded in the server) then the invo.er first loads the Servlet ?either from localdis. or from the net,or.@ and the then invo.es the NserviceN method' Also li.e a!!lets) localServlets in the server can "e identified "y -ust the class name' In other ,ords) if a Servletname is not a"solute) it is treated as local'

A client can invo.e Servlets in the follo,ing ,ays@

The client can as. for a document that is served "y the Servlet'

The client ?"ro,ser@ can invo.e the Servlet directly using a UR2) once it has "een ma!!ed

using the Servlet Aliases section of the admin /UI'

The Servlet can "e invo.ed through server side include tags'

The Servlet can "e invo.ed "y !lacing it in the ServletsE directory' The Servlet can "einvo.ed "y using it in a filter chain'


59/205

%9

2.2.8.8 3AVA SERVER PAGES 63SP7


60/205

Ste!s in the e*ecution of a


61/205

%=

The client sends a request to the ,e" server for a


62/205


63/205

%>

2.2.9.2 3SP MODEL 1 AND MODEL 2

ARCHITECTURES

The early


64/205

Fiu$# 2.1. 3SP !o#" *$c+it#ctu$#.

As you can see) the main difference "et,een the t,o a!!roaches is that the Model # architectureintroduces a controller servlet that !rovides a single !oint of entry and also encourages morereuse and e*tensi"ility than Model %' Cith the Model # architecture) there is also a clearse!aration of the "usiness logic) !resentation out!ut) and request !rocessing' This se!aration isoften referred to as a Model+7ie,+ontroller ?M7@ !attern' Chile the


65/205

%

Model # architecture might seem overly com!licated) it can actually sim!lify an a!!licationgreatly' Ce" a!!lications "uilt using the Model # a!!roach are generally easier to maintainand can "e more e*tensi"le than com!ara"le a!!lications "uilt around the Model %

architecture'

T+# Mo#" Co!,on#nt@ Res!onsi"le for the "usiness domain state .no,ledge'

T+# Vi# Co!,on#nt@ Res!onsi"le for a !resentation vie, of the "usiness domain'

T+# Cont$o""#$ Co!,on#nt@ Res!onsi"le for controlling flo, and state of the user in!utnormally ,ith the M7 !attern) thereHs a form of event notification that ta.es !lace to notifythe vie, ,hen some !ortion of the model changes' 3o,ever) since a "ro,ser in a ty!ical,e" a!!lication has a stateless connection) the notification from the model to the vie, canHteasily occur' (f course) an a!!lication could !erform some ty!e of !ush action to !ush datachanges all the ,ay to a clientG "ut this doesnHt and !ro"a"ly shouldnHt ha!!en in most ,e"a!!lications' A user can close at a "ro,ser anytime and there isnHt ,arning or notificationsent to the server' ThereHs a great deal of overhead necessary to management remote clientsfrom the server side' This ty!e of "ehavior is over.ill for ty!ical 1# and 1#1 ,e"a!!lications'

2.2.9.% THE MVC MODEL

De!ending on the ty!e of architecture of your a!!lication) the model !ortion of the M7 !attern can ta.e many different forms' In a t,o+tier a!!lication) ,here the ,e" tier interactsdirectly ,ith a data store li.e a data"ase) the model classes may "e a set of regular


66/205

The vie,s ,ithin the ,e" tier M7 !attern ty!ically consist of 3TM2 and


67/205

#$

session data for a user or even store data ,ithin the "ro,ser on "ehalf of the user' Somea!!lications may require the need for client+side


68/205

I have "een thro,ing the ,ord frame,or. around in this cha!ter ,ithout having reallydefined ,hat e*actly it is or ho, it adds value in soft,are develo!ment' In its sim!lest form)a frame,or. is a set of classes and interfaces that coo!erate to solve a s!ecific ty!e ofsoft,are !ro"lem' A frame,or. has the follo,ing characteristics

A frame,or. is made u! of multi!le classes or com!onents) each of ,hich may Provide ana"straction of some !articular conce!t'

The frame,or. defines ho, these a"stractions ,or. together to solve a !ro"lem' Theframe,or. com!onents are reusa"le'

A good frame,or. should !rovide generic "ehavior that can "e utiliJed across many

different ty!es of a!!lications' There are many inter!retations of ,hat constitutes a


69/205

#%

frame,or.' Some might consider the classes and interfaces !rovided "y the


70/205

coordinating the vie, to return "ac. to the client' (f course) there are many other functionsthat the controller may !erform) "ut these are a fe, of the !rimary ones'

2.2.9.1; STRUTS ACTIONSERVLET

The ActionServlet e*tends the -ava*'servlet'htt!'3tt!Servlet class and is res!onsi"le for !ac.aging and routing 3TTP traffic to the a!!ro!riate handler in the frame,or.' TheActionServlet class is not a"stract and therefore can "e used as a concrete controller "y youra!!lications' Prior to version %'% of the Struts frame,or.) the ActionServlet ,as solelyres!onsi"le for receiving the request and !rocessing it "y calling the a!!ro!riate handler' Inversion %'%) a ne, class called org'a!ache'struts'action'RequestProcessor has "een introducedto !rocess the request for the controller'


71/205

##

2.2.9.11 STRUTS ACTION CLASSES

An org'a!ache'struts'action'Action class in the Struts frame,or. is an e*tension of thecontroller com!onent' It acts as an Adaptor "et,een a user action and a "usiness o!eration'The Action class decou!les the client request from the "usiness model' This decou!lingallo,s for more than a one+to+one ma!!ing "et,een the user request and an Action class' TheAction class can !erform other functions) such as authoriJation) logging) and sessionvalidation) "efore invo.ing the "usiness o!eration'

2.2.9.12 MAPPING THE ACTIONS

At this !oint) you might "e as.ing yourself) Q3o, does the controller .no, ,hich Actioninstance to invo.e ,hen it receives a request The ans,er is "y ins!ecting the requestinformation and utiliJing a set of action ma!!ings' Action ma!!ings are !art of the Strutsconfiguration information that is configured in a s!ecial M2 file' This configurationinformation is loaded into memory at startu! and made availa"le to the frame,or. atruntime'

2.2.9.1% DETERMINING THE NET VIEW

CeHve tal.ed a"out ho, the controller receives the request and ho, the action ma!!ings andrequest information are used to determine the correct action instance to invo.e and !ass therequest to' Chat hasnHt "een discussed is ho, or ,hat determines the vie, to return "ac. tothe client' If you loo.ed closely at the e*ecute?@ method signature in the Action class fromthe !revious section) you might have noticed that the return ty!e for the method is anorg'a!ache'struts'action'ActionFor,ard class' The ActionFor,ard class re!resents a

destination to ,hich the controller may send control once an Action has com!leted' Insteadof s!ecifying an actual


72/205

2.2.9.1' STRUTS MODEL COMPONENTS

There are several different ,ays to loo. at ,hat constitutes a model for Struts' The lines "et,een "usiness and !resentation o"-ects can get quite "lurry ,hen dealing ,ith ,e"


73/205

#5

a!!lications' (ne a!!licationHs "usiness o"-ects are anotherHs value o"-ects' ItHs im!ortant to.ee! the "usiness o"-ects se!arate from the !resentation) so that the a!!lication is not tightlycou!led to one ty!e of !resentation'

2.2.9.1) USING THE STRUTS ACTIONFORM

Struts ActionForm o"-ects are used in the frame,or. to !ass client in!ut data "ac. and forth "et,een the user and the "usiness layer' The frame,or. ,ill automatically collect the in!utfrom the request and !ass this data onto an Action using a form "ean) ,hich then can "e !assed along to the "usiness layer' To .ee! the !resentation layer decou!led from the

"usiness layer) you should not !ass the action form itself to the "usiness layer) "ut rathercreate the a!!ro!riate value o"-ects using the data from the form and !ass these o"-ects asargument to the "usiness layer' The follo,ing ste!s illustrate ho, the frame,or. !rocessesan ActionForm for every request

hec. the ma!!ing for the action and see if a form "ean has "een configured for it' If so) usethe name attri"ute to loo.u! the form "ean configuration information'

De!ending on the sco!e configured for the form "ean for the action) chec. to see if thereHsalready an instance of the form "ean at the a!!ro!riate sco!e'

If an ActionForm instance is !resent in the a!!ro!riate sco!e and itHs the same ty!e as neededfor this ne, request) reuse it'

(ther,ise) create a ne, instance of the required form "ean and store it into the a!!ro!riate

sco!e that is set "y the sco!e attri"ute for the action ma!!ing'

The reset?@ method is called on the ActionForm instance'


74/205

Iterate through the request !arameters and for every !arameter name that has a corres!ondingset method name on the ActionForm) !o!ulate it ,ith the value for that !arameter'

Finally) if the validate attri"ute is set to true) then invo.e the validate?@ method on theActionForm instance and return any errors'

2.2.9.15 USING 3AVASERVER PAGES FOR

PRESENTATION


75/205

#6

the Struts frame,or. and S2T and "eans serialiJed from the value o"-ects to render the

vie,s' Many develo!ers feel that


76/205

Struts a!!lication ,as limited to having a single configuration file' The single instance of thefile) ,hich is normally called struts-config.xml ) ,as s!ecified in the ,e" a!!licationde!loyment descri!tor' It ,as the sole !rovider of the configuration information for the Strutsa!!lication' The fact that there ,as only a single !lace to !ut configuration information madeit very difficult for larger !ro-ects "ecause it often "ecame a "ottlenec. and causedcontentions to use and modify this file' Pro"lem has "een alleviated ,ith the advent of multi

a!!lication su!!ort' ;ou can no, define multi!le configuration files and allo, develo!ers to,or. "etter in !arallel'

2.2.9.1: CONFIGURING THE STRUTS

APPLICATION

The Struts frame,or. uses t,o se!arate) "ut some,hat related ty!es of configuration files) ,hichmust "e !ro!erly configured "efore an a!!lication ,ill function !ro!erly' Due to


77/205

#8

the !o!ularity and fle*i"ility of the self+descri"ing nature of M2) "oth of theseconfiguration files are "ased on M2' The ,e" a!!lication de!loyment descri!tor web.xml isdescri"ed fully in the


78/205

#9

CHAPTER %

METHOD

The ActionForm class !rovided "y the Struts frame,or. is a"stract' ;ou need to createsu"classes of it to ca!ture your a!!lication s!ecific form data' Cithin your su"class) you shoulddefine a !ro!erty for each field that you ,ish to ca!ture from the 3TM2 form'

The ActionForm is !o!ulated from request !arameters) not request attri"utes' If you arefor,arding from one action to another) you canHt add a request attri"ute and e*!ect that theActionForm ,ill "e !o!ulated from it' Request !arameters and request attri"utes are t,ose!arate resources'

%.1 THE ACTIONFORM VALIDATE67 METHOD

The validate?@ method may "e called "y the Request Processor for every request' Chether itHscalled or not de!ends on t,o things' First) an ActionForm must "e configured for an actionma!!ing' This means that the name attri"ute for an action element must corres!ond to thename attri"ute of one of the form+"ean elements in the configuration file' The secondcondition that must "e met "efore the RequestProcessor ,ill invo.e the validate?@ method isthat the validate attri"ute must have a value of Qtrue'


79/205

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

name="loginForm"

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

Chen the signin action is invo.ed) the frame,or. ,ill !o!ulate an instance of a 2oginFormusing values it finds in the request' 1ecause the validate attri"ute has a value of Qtrue) thevalidate?@ method in the 2oginForm ,ill "e called' 0ven if the validate attri"ute is


80/205

#=

set to Qfalse) the ActionForm ,ill still "e !o!ulated from the request if an ActionForm isconfigured for the action'

The validate?@ method in the "ase ActionForm class sim!ly returns null' If you ,ant to !erform validation on the data that is su"mitted ,ith the request) youHll need to override thevalidate?@ method in your ActionForm su"classes'

The validate?@ method may return an Action0rrors o"-ect) de!ending on ,hether or not anyvalidation errors ,ere detected' ;ou also can return null if there are no errorsG the frame,or.,ill chec. for "oth null and an em!ty Action0rrors o"-ect' This saves you from having tocreate an instance of Action0rrors ,hen there are no errors'

%.1.1 T+# ActionFo$! $#(#t67 M#t+o

The reset?@ method has "een a "ane for much of the Struts user community at one time oranother' 0*actly ,hen the reset?@ method is called and ,hat should "e done ,ithin it isalmost al,ays misinter!reted' This doesnHt mean that one im!lementation is more correctthan another) "ut there are misconce!tions that many ne, Struts develo!ers !ic. u! and thenhave a hard time sha.ing regarding the reset?@'

ItHs called "efore the ActionForm has "een !o!ulated from the request' The method ,asadded to the ActionForm class originally to hel! facilitate resetting "oolean !ro!erties "ac.to their defaults' To understand ,hy they need to "e reset) itHs hel!ful to .no, ho, the "ro,ser and the 3TM2 form su"mit o!eration !rocesses chec."o*es' Chen an 3TM2 formcontains chec."o*es) only the values for the chec."o*es that are chec.ed are sent in therequest' Those that are not chec.ed are not included as a request !arameter' Therefore) thereset?@ method ,as added to allo, a!!lications to reset the "oolean !ro!erties in theActionForm "ac. to false) since false ,asnHt included in the request and the "oolean values,ould !ossi"ly "e stuc. in the Qtrue state' The reset?@ method in the "ase ActionFormcontains no default "ehavior) since no !ro!erties are defined in this a"stract class'A!!lications that e*tend the ActionForm class are allo,ed to override this method and resetthe ActionForm !ro!erties to ,hatever state they ,ish' This may include setting "oolean !ro!erties to true or false) setting String values to null or some initialiJed value) or eveninstantiating instances of other o"-ects that the ActionForm holds on to' For an ActionFormthat has "een configured ,ith request sco!e) the frame,or. ,ill essentially create a ne,


81/205

#>

instance for each ne, request' Since a ne, instance is created) thereHs not much need toreset?@ the values "ac. to any default state' ActionForms that are configured ,ith sessionsco!e are different ho,ever' This is the time that the reset?@ method comes in handy'

%.1.2 D#c"*$in ActionFo$!( in

t+# St$ut( Con?iu$*tion Fi"#

(nce you have created a class that e*tends ActionForm) you need to configure the class in

the Struts configuration file' The first ste! is to add a ne, form+"ean element to the form+ "eans section of the file

The value for the ty!e field must "e a fully qualified


82/205

String' The reason for this is to su!!ort dis!laying the data "ac. out in its original form to theuser) ,hen there is an error' For e*am!le) if a user ty!es in Q%#X for a !ro!erty e*!ecting to "e an Integer) thereHs no ,ay to store Q%#X into an int or Integer !ro!erty' 3o,ever) you canstore it into a String until it can "e validated' This same value) ,hich is stored in a String) can "e used to render the in!ut field ,ith the value) so the user can see their mista.e' This isfunctionality that even the most ine*!erienced users have come to e*!ect and loo. for'

%.1.' U(in ActionE$$o$(

0arlier in the cha!ter) you sa, that the validate?@ method returned an Action0rrors o"-ect'The Action0rrors class enca!sulates one or more errors that have "een discovered "y


83/205

#

the a!!lication' 0ach !ro"lem discovered is re!resented "y an instance oforg'a!ache'struts'action'Action0rror' An Action0rrors o"-ect has request sco!e' (nce aninstance is created and !o!ulated "y the validate?@ method) it is stored into the request' 2ater)

the


84/205

same and you have no need to retrieve them individually) you can use the constantAction0rrors'/2(1A2_0RR(R similar to this

errors.add(ActionErrors.GLOBAL_ERROR,

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

Using the ActionForm class has many advantages over !erforming the functionality yourselfin the Action class or some set of hel!er utility classes' Since the "ehavior that theActionForm class !rovides is needed in nearly every ,e" a!!lication) as ,ell as many times


85/205

5$

in the same a!!lication) using the frame,or. to !erform the ,or. can really reduce thedevelo!ment time and your frustration level' 3aving stated the "enefits of usingActionForms) there are a fe, very im!ortant do,nsides to using them'

The first and foremost !ro"lem ,ith using ActionForms is the sheer num"er of classes that itcan add to a !ro-ect' 0ven if you share ActionForm definitions across many !ages) theadditional classes ma.e it more difficult to manage a !ro-ect and !rovide maintenance' Thisis ,hy some develo!ers might create a single ActionForm and im!lement the !ro!erties forall of the 3TM2 forms ,ithin these' The !ro"lem ,ith this of course) is that com"ining thefields into this one class ma.es it a !oint of contention on a !ro-ect that has more than -ust afe, develo!ers' Another ma-or lia"ility is the requirement to define the !ro!erties in theActionForm that need to "e ca!tured from the 3TM2 form' If a !ro!erty is added or removed

from the 3TM2 form) the ActionForm class may need to "e modified and recom!iled' Forthese reasons) a ne, ty!e of ActionForm ,as added to the frame,or.) ,hich is dynamic innature and allo,s you to avoid having to create concrete ActionForm classes for youra!!lication' The dynamic ActionForm is im!lemented "y the "ase classorg'a!ache'struts'action'DynaActionForm) ,hich e*tends the ActionForm class'

The !ro!erties that the ActionForm defines

The validate?@ method' The reset?@ method'

The !ro!erties for a DynaActionForm are configured in the Struts configuration file) ,hichyouHll see ho, to do in the ne*t section' The reset?@ method is called at e*actly the same timeduring request !rocessing as it is for a standard ActionForm' The one difference is that youhave a little less control over ,hat you do during the method' 3o,ever) you can al,ayssu"class the DynaActionForm to override the reset "ehavior'

The validation of the !resentation data is a little more com!licated) "ecause ,eHll need to,ait until ,e tal. a"out the Struts validate com!onents "efore tal.ing a"out ho, validationoccurs in a dynamic form'


86/205

To use the DynaActionForm in your Struts a!!lication) the first ste! is to add a form+"eanelement to the configuration file' There are t,o very im!ortant differences "et,een a form+ "ean element for a regular ActionForm and one that is dynamic' First) a form+"ean elementfor a dynamic ActionForm is required to have an attri"ute called dynamic) ,hich


87/205

5%

must have a value of Qtrue' This is necessary for the frame,or. to understand that it shouldhandle this ActionForm differently' The second difference is that you must include one ormore form+!ro!erty elements in order for the dynamic form to have !ro!erties' The

DynaActionForm uses a -ava'util'Ma! internally to store .eyEvalue !airs' The form+!ro!ertyelements are loaded into the Ma! and "ecome the !ro!erties that get !o!ulated "y theframe,or.'

The declarative !ro!erties are ,hat ma.e the ActionForm dynamic' At runtime) theframe,or. creates an instance of the DynaActionForm class and ma.es it !ossi"le to set andget the configured !ro!erty values' To add ne, !ro!erties) you only need to modify theconfiguration file' 4o source code needs to "e changed' The !o,er and fle*i"ility that this !rovides for you is immense'

The form+"eam element also allo,s you to s!ecify the initial value for each !ro!erty' Theframe,or. ,ill set the !ro!erty to that value ,hen the a!!lication is started' The initial valueis also used ,hen the reset?@ method is called to reset the values "ac. to their original state' If you donHt include the initial attri"ute) then !ro!erties ,ill "e assigned default values "ased onthe


88/205

Dis!atchAction'


89/205

5#

%.1.5 Fo$*$ Action

The org'a!ache'struts'actions'For,ardAction dis!atches the request to the given !ath ,ithout !erforming any action' The For,ardAction is configured if ,e ,ant our request to "efor,arded to the given !ath may "e a


90/205

the need to create se!arate action classes for each of the action' This class !rovides amechanism for modulariJing a set of related actions into a single Action'

The org'a!ache'struts'actions'Dis!atchAction class is an a"stract class ,ith no a"stractmethods and is a su" ty!e of 1aseAction class) ,hich e*tends org'a!ache'struts'action'Actionclass' The e*ecute?@ method of Dis!atchAction dis!atches the request to a !u"lic method thatis named "y the request !arameter value) the !arameter name is s!ecified through !arameter

attri"ute of Waction tag in struts+config'*ml file'


91/205

55

%.1.:.1 STEPS TO USE DISPATCHACTION

CLASS

There are t,o ste!s

reate an action class'

onfigure action ma!!ing'

%.1.:.2 CREATING ACTION CLASS

Su"class the Action class ,ith Dis!atchAction class and !rovides a set of methods that ,ill "e called "y the e*ecute?@ method of Dis!atchAction'

4ote that this class should not override e*ecute?@ method li.e other actions'

%.1.:.% CONFIGURING ACTION MAPPING

onfiguring Action ma!!ing is as follo,s


92/205


93/205

56

%.2.1 En4i$on!#nt


94/205

for dra,ing the systemHs structure charts' The 1asic 4otation used to create a DFDHs are asfollo,s

D*t*?"o@ Data move in a s!ecific direction from an origin to a destination ?see Figure 5'%@'

Fiu$# %.1. F"o ,$oc#((.


95/205

58

P$oc#(( Peo!le) !rocedures) or devices that use or !roduce ?Transform@ Data' The !hysicalcom!onent is not identified ?see Figure 5'#@'

Fiu$# %.2. P$oc#((.

Sou$c#@ 0*ternal sources or destination of data) ,hich may "e Peo!le) !rograms) organiJations or other entities ?see Figure 5'5@'

Fiu$# %.%. Sou$c# o? *t*.


96/205

D*t* Sto$#@ 3ere data are stored or referenced "y a !rocess in the System ?see Figure

5'6@'

Fiu$# %.'. D*t* (to$*# i*$*! inic*to$.

%.' DATA

FLOW

DIAGRAMS

The data flo, diagram sho,n in Figure 5'8 illustrates the entire flo, in the !rocess'


97/205

59


98/205

Fiu$# %.). D*t* ?"o i*$*! +ic+ i""u(t$*t#( #nti$# ?"o in t+# ,$oc#((.

In the 2ogin Screen the entered username and !ass,ord ,ill "e su!!lied to the authenticationserver and if the login credentials are valid the user ,ill "e directed to the home screen and if

they are invalid the user ,ill "e ta.en "ac. to the login screen ?see Figure 5'9@'After logging in Admin ,ill "e redirected to the User Interface ,hich dis!lays all theavaila"le admin tas.s that are to "e !erformed' These tas.s include reatingEModifyingategories) reatingEModifying Items and 1idding Information ?see Figure 5'=@'

From the UI Interface Admin adds a ne, ategory ,hich ,ill "e stored in the data"ase u!onsuccessful creation ?see Figure 5'>@'


99/205

5=

Fiu$# %.5. Aut+#ntic*tion *t* ?"o i*$*!.


100/205

Fiu$# %.8. L#4#" 1 *t* ?"o i*$*! ?o$ A!in.

Fiu$# %.9. L#4#" 2 *t* ?"o i*$*! ?o$ A!in.


101/205

5>

7ie, ategories ,ill fetch the categories information from the data"ase and dis!lays on theuser interface ?see Figure 5'@'

Fiu$# %.:. L#4#" % *t* ?"o i*$*! ?o$ A!in.

In the ategories form category name can "e entered and it ,ill "e stored in the data"ase ?seeFigure 5'%$@'

Fiu$# %.1;. L#4#" ' *t* ?"o i*$*! ?o$ A!in.

For Seller the first ste! is registration and u!on successful login the seller ,ill "e ta.en to theUI dis!laying the set of o!erations' The o!erations include 7ie, Items) 7ie, ategories)

7ie, 1idding Information and sale at higher !rice ?see Figure 5'%%@'


102/205

Fiu$# %.11. L#4#" 1 *t* ?"o i*$*! ?o$ (#""#$.

From the User Interface clic.ing the items ,ill fetch the items from the data"ase and ,ill "e

dis!layed to the seller ?see Figure 5'%#@'


103/205

5

Fiu$# %.12. L#4#" 2 *t* ?"o i*$*! ?o$ S#""#$.

For "uyer the first ste! is registration and u!on successful login the UI is dis!layed ,ith a setof o!erations' (!erations include 7ie, Items) 7ie, ategories) 7ie, 1iding Informationand "uying all !ossi"le items ?see Figure 5'%5@'


104/205

Fiu$# %.1%. L#4#" 1 *t* ?"o i*$*! ?o$ Bu$.

Items ,ill "e fetched from the data"ase and dis!layed on the User Interface ?see Figure5'%6@'

Fiu$# %.1'. L#4#" 2 *t* ?"o i*$*!.

Figure 5'%8 sho,s the 0+R diagram'


105/205

6$

QUESTIONBASE

CATEGORYMASTER

QUESTIONID

CATEGORYNAME

QUESTIONDETAIL

CATEGORYABBR

CATEGORYDESC


106/205

ITEMMASTER

ITEMNAME

CATEGORYNAME (FK)

ITEMDESC

SUMMARY


107/205

STARTPRICE

INCRPRICE

STDATE

ENDDATE

LOGINNAME (FK)

LOGINPROFILE

BIDCOUNT


108/205

LOGINID (FK)

BIRTHDATE

HNO

LOGINDETAILS

STREET

CITY

LOGINNAME

STATE


109/205

COUNTRY

PASSWORD

LOGINAUDIT

PINCODE

FIRSTNAME

CONTACTNO

LASTNAME


110/205

EMAIL

LOGINTYPE

LOGINID (FK)

LOCALE

BIDDINGINFORMATION

LOGINSTATUS

PROFILEMODIFIEDDATE

LOGINDATE

REGDATE


111/205

LOGINDESC

BIDDERID

SQUESTIONID

LOGINNAME (FK)

SANSWER

FIRSTLOGIN

BAMOUNT

PASSMODIFIEDDATE


112/205

ITEMNAME (FK)

BIDDERDATE

STATUS

Fiu$# %.1). Entit&< R#"*tion(+i, ?"o +ic+ #/,"*in( t+# $#"*tion(+i, in *t*.

%.) UNIFIED MODELING

LANGUAGE 6UML7 DIAGRAMS

The Unified Modeling 2anguage allo,s the soft,are engineer to e*!ress an analysis modelusing the modeling notation that is governed "y a set of syntactic semantic and !ragmatic

rules' A UM2 system is re!resented using five different vie,s that descri"e the system fromdistinctly different !ers!ective' 0ach vie, is defined "y a set of diagram) ,hich is as follo,s'

%.).1 U(#$ Mo#" Vi#


113/205

This vie, re!resents the system from the users !ers!ective' The analysis re!resentationdescri"es a usage scenario from the end+users !ers!ective'

%.).2 St$uctu$*" Mo#" Vi#

In this model the data and functionality are arrived from inside the system' This model vie,models the static structures'


114/205

6%

%.).% B#+*4io$*" Mo#" Vi#

It re!resents the dynamic of "ehavioral as !arts of the system) de!icting the interactions ofcollection "et,een various structural elements descri"ed in the user model and structuralmodel vie,'

%.).' I!,"#!#nt*tion Mo#" Vi#

In this the structural and "ehavioral as !arts of the system are re!resented as they are to "e

"uilt'

%.).) En4i$on!#nt*" Mo#" Vi#

In this the structural and "ehavioral as!ects of the environment in ,hich the system is to "eim!lemented are re!resented'

UML i( (,#ci?ic*""& con(t$uct# t+$ou+ to i??#$#nt o!*in( t+#& *$#@

UM2 Analysis modeling) this focuses on the user model and structural model vie,s of thesystem'

UM2 design modeling) ,hich focuses on the "ehavioral modeling) im!lementation modeling

and environmental model vie,s'

U(# c*(# Di*$*!( re!resent the functionality of the system from a userHs !oint of


115/205

vie,' Use cases are used during requirements elicitation and analysis to re!resent thefunctionality of the system' Use cases focus on the "ehavior of the system from e*ternal !oint of vie,' ?See Figure 5'%9@'

Acto$( are e*ternal entities that interact ,ith the system' 0*am!les of actors include users

li.e administrator) "uyer) seller[etc') or another system li.e central data"ase'

System here refers to the (nline Auctioning system and the actors that are using the systemare Admin and ustomer ?see Figure 5'%=@'

Admin can vie, all the customers) vie, the "id items) vie, today and end day auction itemsand vie, the !rofiles of the customers ?see Figure 5'%>@'

ustomer registers) and u!on successful login can "uy or sell the items) can vie, his !rofile)

can vie, the ne, auction items today and end day ?see Figure 5'%@'Figure 5'#$ sho,s an Admin sequence diagram'

After !roviding login details for admin login the details ,ill "e validated and after successfulvalidation it ,ill "e redirected to the admin home !age'

BidderDAO

+register(aform Bi""erForm# $oo%ea&

+'ieBi""i&gI&formatio&(%ogi&&ame Stri&g#

CoreList +)*"ateStat)s(item&ame Stri&g#

$oo%ea& +'ieBi""i&gs(%ogi&&ame Stri&g#

CoreList +'ieA%%Bi""i&gs(# CoreList

+'ieA%%Bi""i&gsI&formatio&(item&ame

Stri&g# CoreList

+)*"atStat)sDetai%s(item&ame Stri&g#

$oo%ea&

SellItemDAO

+register(amo"e% ItemMo"e%# $oo%ea&

+'ieItems(%ogi&&ame Stri&g# CoreList

+'ieItem$O&e(item&ame Stri&g# CoreList

+)*"ateItems(amo"e% ItemMo"e%# $oo%ea&

+"e%eteItems()ser&ame Stri&g# $oo%ea&

+'ieItem$Detai%s(item&ame Stri&g, -ategor&ame

Stri&g# ItemMo"e% +'ieItemsBDetai%s(%ogi&&ame

Stri&g# CoreList +a)-tio&ItemDetai%s(%ogi&&ame Stri&g#

CoreList +a)-tio&ItemE&"Da(%ogi&&ame Stri&g# CoreList

+'ieA%%Items(# CoreList


116/205

CategoryDAO

AbstractDataAccessObject

+register(amo"e% CategorMo"e%# $oo%ea&

.-o& Co&&e-tio&

.*ro*s Pro*erties

+'ieCategors(# CoreList

+'ieCategors(-ategor&ame Stri&g# CategorMo"e%


117/205

+getPro*erties(# Pro*erties

+)*"ate(amo"e% CategorMo"e%# $oo%ea&

+setPro*erties(*ro*s Pro*erties#

+"e%ete(-ategor&ame Stri&g# $oo%ea&

+getCo&&e-tio&(# Co&&e-tio&

+getSe/)e&-eID(ta$%eName Stri&g, *0i" Stri&g# i&t

SecurityDAO


118/205

.-o& Co&&e-tio&

1"es- Stri&g

1f%ag $oo%ea&

22-reate33+Se-)ritDAO(#

ProfileDAO

+-4e-0Passor"(reg$ea& Profi%e# $oo%ea&

+-o& Co&&e-tio&

+-4e-0FirstLogi&(%ogi&&ame Stri&g# i&t

1f%ag $oo%ea&

+%ogi&C4e-0(%ogi&i" Stri&g, *assor" Stri&g# Stri&g

22-reate33+Profi%eDAO(#

+%ogi&a)"it(%ogi&i" Stri&g, "es- Stri&g#


119/205

+registratio&(reg$ea& Profi%e# $oo%ea&

+-4a&gePassor"(reg$ea& Profi%e# $oo%ea&

+getProfi%e(%ogi&&ame Stri&g# Profi%e

+-4a&geQ)estio&(reg$ea& Profi%e# $oo%ea&

+mo"ifProfi%e(reg$ea& Profi%e# $oo%ea&

+re-o'erPassor"BE5istQ)estio&(reg$ea& Profi%e# Stri&g


120/205

+-4a&geA--o)&tStat)s(%ogi&i" Stri&g, stat)s i&t# $oo%ea&

+re-o'erPassor"BO6NQ)estio&(reg$ea& Profi%e# Stri&g

+getProfi%e(# CoreList

Fiu$# %.15. UML i*$*! o? t+# o$.

6#


121/205

65

System

Admin

OnLine Auctioning System

Customer

Fiu$# %.18. S&(t#! u(# c*(# i*$*!.


122/205

View Customers

View Bid Items

New Auction Items Today

Admin

Auction Items Endday

ViewProfle

Fiu$# %.19. A!in u(# c*(# i*$*!.


123/205

66

Registration

Login

Buy

Items

Customer

Sell

ViewProfle

New Auction Items today


124/205

New Auction Items Enday

Fiu$# %.1:. Bu$S#""#$ 6Cu(to!#$7 u(# c*(# i*$*!.

Cst!me"s

B#$Items

A$m#%

L!%

A't#!%Items


125/205


126/205

*!%()

+ ,-*#$-te()

A$m#%H!me()

/ ,#e0Cst!me"s()

1 ,#e0B#$Items()

2 ,#e0A't#!%ItemsT!$-y()

3 ,#e0A't#!%ItemsE%$D-y()


127/205

Fiu$# %.2;. Loin


128/205

68

From the admin home the follo,ing are the tas.s that admin can !erform ?see

Figure 5'#%@

7ie, ustomers Admin can vie, information of all the registered customers from this !age'

7ie, 1id Items Admin can vie, all the items that are u! for "idding through this !age'

7ie, Auction Items Today Admin can vie, all the items that are u! for auction for that !articular day'

7ie, Auction Items 0nd Day Admin can vie, all the auction items ,hose auction date endsthat day'

C)stomer

Logi&


129/205

B)Item

Se%%Item

A)-tio& Items To"a

A)-tio& Item E&"To"a


130/205

7 e&terLogi&(#


131/205

8 'a%i"ate(#

9 %ogi&S)--ess(#


132/205

: $i"T4eItem(#

; se%%T4eItem(#

< 'ieA)-tio&ItemsTo"a(#

= 'ieA)-tio&ItemsE&"To"a(#

Fiu$# %.21. Bu$(#""#$ 6Cu(to!#$7 S#0u#nc# Di*$*!. Loin


133/205

69

%.).5 Co""*=o$*tion Di*$*!

Figure 5'## sho,s an Admin colla"oration diagram'

+ ,-*#$-te()

Cst!me"s

B#$Items

A't#!%Items

L!%

3 ,#e0A't#!%ItemsE%$D-y() 1 ,#e0B#$Items() *!%()


134/205

A$m#%H!me()

/ ,#e0Cst!me"s() 2 ,#e0A't#!%ItemsT!$-y()

A$m#%

Fiu$# %.22. A!in co""*=o$*tion i*$*!.

Admin after validating login information ,ill "e ta.en to the admin home !age and from thehome !age he can vie, the customers info) "id items) auction items today and end day ?seeFigure 5'#5@'

+ ,-*#$-te()

L!%

A't#!% Items T!$-y

*!%S''ess()

e%te"L!%()

Se**Item2 ,#e0A't#!%ItemsT!$-y() 3 ,#e0A't#!%ItemsE%$T!$-y()

1 se**T4eItem()

A't#!% Item E%$T!$-y


135/205

ByItem

/ 5#$T4eItem() Cst!me"

Fiu$# %.2%. Cu(to!#$ 6=u$S#""#$7 co""*=o$*tion i*$*!.


136/205

6=

ustomer after login validation ,ill "e ta.en to the customer home !age and from the home !age he can "id for items) sell items) vie, auction items today and end day'

%.).8 O,#$*tion L#4#" S#0u#nc# Di*$*!(

Admin after !roviding the login credentials and u!on successful validation ,ill "e ta.en tothe login !age ,here he can !erform the !rovided o!erations' If the validation isunsuccessful it ,ill "e redirected "ac. to the login !age ?see Figure 5'#6@'

%.).9 O,#$*tion*" L#4#" Co""*=o$*tion Di*$*!(

Admin or customer u!on successful validation of login credentials ,ill "e ta.en to adminhome !age and customer home !age res!ectively and if the validation is unsuccessful ,ill "eta.en "ac. to the login !age ?see Figure 5'#8@'

%.).: Acti4it& Di*$*!

After successful validation of login credentials Admin ,ill "e redirected to the home !ageand from the home !age he can add items for auction) vie, items that are u! for auction) addcategories) vie, categories) add "idding info and vie, "idding info ?see Figure 5'#9@'

After successful validation of login credentials sellerEo,ner ,ill "e redirected to the home !ageand from the home !age he can vie, items) u!date or delete items) vie, categories) vie, "iddinginfo) u!date "idding info and delete "idding info ?see Figure 5'#=@'

After successful validation of login credentials registered "idder ,ill "e redirected to thehome !age and from the home !age he can vie, items) vie, categories and vie, "iddinginfo ?see Figure 5'#>@'


137/205

6>


138/205

Admin

Login

Owner Of The

Registered


139/205

System

Bidders


140/205

Login


141/205

Validate


142/205


143/205


144/205


145/205


146/205


147/205


148/205

ValidLogin

Login

validate

ValidLogin

Login

validate

validLogin

Fiu$# %.2'. Loin (#0u#nc# i*$*!.


149/205

Owner Of The

System

6: ValidLogin 4: Login

Admin

Registered

Bidders

1: Login

2: Validate

: validLogin

!: validate


150/205

": validate

#: ValidLogin

$: Login

Login

Fiu$# %.2). Loin co""*=o$*tion i*$*!.


151/205

A$m#%

L!%

E%te" Use"%-me67-ss0!"$

F-#*

S''ess


152/205

H!me Item C-te&!"#es B#$$#%&I%8! L !&Ot

A$$ Items

9#e0 Items

A$$ C-te&!"#es

9#e0 C-te&!"#es

A$$ B#$$#%&I%8!

9#e0 B#$$#%&I%8!


153/205

Fiu$# %.25. A!ini(t$*to$ *cti4it& i*$*!.


154/205

6


155/205

O0%e"O8 A"t#'*e

L!%


F-#*

S''ess


156/205

H!me Item C-te&!"#es B#$$#%&I%8! L!&Ot

9#e0 Items

9#e0 C-te&!"#es

9#e0 B#$$#%&I%8!


157/205

U7$-te Items

$e*ete Items

U7$-te B#$$#%& I%8!

De*ete B#$$#%& I%8!


158/205

Fiu$# %.28. S#""#$ 6On#$ o? t+# A$tic"# o$ cu(to!#$7 *cti4it& i*$*!.

8$


159/205

Reste"e$ B#$$e"

L!%


F-#*

S''ess


160/205

H!me Item C-te&!"#es B#$$#%&I%8! L!&Ot

9#e0 Items

9#e0 C-te&!"#es

9#e0 B#$$#%&I%8!


161/205

Fiu$# %.29. Bu$ 6R#i(t#$# Bi#$ o$ cu(to!#$7 *cti4it& i*$*!.

8%


162/205

8#

CHAPTER '

TESTING

'.1 SOFTWARE TESTING

Soft,are Testing is the !rocess used to hel! identify the correctness) com!leteness) security)and quality of develo!ed com!uter soft,are' Testing is a !rocess of technical investigation) !erformed on "ehalf of sta.eholders) that is intended to reveal quality+related informationa"out the !roduct ,ith res!ect to the conte*t in ,hich it is intended to o!erate' This includes) "ut is not limited to) the !rocess of e*ecuting a !rogram or a!!lication ,ith the intent offinding errors' Buality is not an a"soluteG it is value to some !erson' Cith that in mind)

testing can never com!letely esta"lish the correctness of ar"itrary com!uter soft,areG testingfurnishes a criticism or com!arison that com!ares the state and "ehavior of the !roductagainst a s!ecification' An im!ortant !oint is that soft,are testing should "e distinguishedfrom the se!arate disci!line of Soft,are Buality Assurance ?SBA@) ,hich encom!asses all "usiness !rocess areas) not -ust testing'

There are many a!!roaches to soft,are testing) "ut effective testing of com!le* !roducts isessentially a !rocess of investigation) not merely a matter of creating and follo,ing routine !rocedure' (ne definition of testing is Nthe !rocess of questioning a !roduct in order to

evaluate itN) ,here the NquestionsN are o!erations the tester attem!ts to e*ecute ,ith the !roduct) and the !roduct ans,ers ,ith its "ehavior in reaction to the !ro"ing of the tester K8L'Although most of the intellectual !rocesses of testing are nearly identical to that of revie, orins!ection) the ,ord testing is connoted to mean the dynamic analysis of the !roduct !utting the !roduct through its !aces' Some of the common quality attri"utes includeca!a"ility) relia"ility) efficiency) !orta"ility) maintaina"ility) com!ati"ility and usa"ility' Agood test is sometimes descri"ed as one ,hich reveals an errorG ho,ever) more recent


163/205

thin.ing suggests that a good test is one ,hich reveals information of interest to someone,ho matters ,ithin the !ro-ect community'

In general) soft,are engineers distinguish soft,are faults from soft,are failures' In case of afailure) the soft,are does not do ,hat the user e*!ects' A fault is a !rogramming


164/205

85

error that may or may not actually manifest as a failure' A fault can also "e descri"ed as anerror in the correctness of the semantic of a com!uter !rogram' A fault ,ill "ecome a failureif the e*act com!utation conditions are met) one of them "eing that the faulty !ortion of

com!uter soft,are e*ecutes on the PU' A fault can also turn into a failure ,hen thesoft,are is !orted to a different hard,are !latform or a different com!iler) or ,hen thesoft,are gets e*tended' Soft,are testing is the technical investigation of the !roduct undertest to !rovide sta.eholders ,ith quality related information'

Soft,are testing may "e vie,ed as a su"+field of Soft,are Buality Assurance "ut ty!icallye*ists inde!endently ?and there may "e no SBA areas in some com!anies@' In SBA) soft,are !rocess s!ecialists and auditors ta.e a "roader vie, on soft,are and its develo!ment' Theye*amine and change the soft,are engineering !rocess itself to reduce the amount of faults

that end u! in the code or deliver faster'

Regardless of the methods used or level of formality involved the desired result of testing is alevel of confidence in the soft,are so that the organiJation is confident that the soft,are hasan acce!ta"le defect rate' Chat constitutes an acce!ta"le defect rate de!ends on the nature ofthe soft,are' An arcade video game designed to simulate flying an air!lane ,ould !resuma"ly have a much higher tolerance for defects than soft,are used to control an actualairliner'

A !ro"lem ,ith soft,are testing is that the num"er of defects in a soft,are !roduct can "every large) and the num"er of configurations of the !roduct larger still' 1ugs that occurinfrequently are difficult to find in testing' A rule of thum" is that a system that is e*!ected tofunction ,ithout faults for a certain length of time must have already "een tested for at leastthat length of time' This has severe consequences for !ro-ects to ,rite long+lived relia"lesoft,are'

A common !ractice of soft,are testing is that it is !erformed "y an inde!endent grou! oftesters after the functionality is develo!ed "ut "efore it is shi!!ed to the customer' This !ractice often results in the testing !hase "eing used as !ro-ect "uffer to com!ensate for !ro-ect delays' Another !ractice is to start soft,are testing at the same moment the !ro-ectstarts and it is a continuous !rocess until the !ro-ect finishes'

Another common !ractice is for test suites to "e develo!ed during technical su!!ortescalation !rocedures' Such tests are then maintained in regression testing suites to ensure


165/205

86

that future u!dates to the soft,are dont re!eat any of the .no,n mista.es ?see Ta"le 6'%@' It iscommonly "elieved that the earlier a defect is found the chea!er it is to fi* it'

T*="# '.1. P#$?o$!*nc# T*="#

Ti!# D#t#ct#


166/205

Time

Requirements

Architecture

onstruction

System

Post+

Introduced


167/205

Test

Release


168/205

Requirements

%

5

8+%$

%$

%$+%$$


169/205


170/205

onstruction

+

+

%

%$

%$+#8

In counter!oint) some emerging soft,are disci!lines such as e*treme !rogramming and theagile soft,are develo!ment movement) adhere to a Ntest+driven soft,are develo!mentN

model' In this !rocess unit tests are ,ritten first) "y the !rogrammers ?often ,ith !air !rogramming in the e*treme !rogramming methodology@' (f course these tests fail initiallyGas they are e*!ected to' Then as code is ,ritten it !asses incrementally larger !ortions of thetest suites' The test suites are continuously u!dated as ne, failure conditions and corner casesare discovered) and they are integrated ,ith any regression tests that are develo!ed'


171/205


172/205

88

follo,s until %89 it ,as the de"ugging oriented !eriod) ,here testing ,as often associatedto de"ugging there ,as no clear difference "et,een testing and de"ugging' From %8=+%=>there ,as the demonstration oriented !eriod ,here de"ugging and testing ,as distinguished

no, + in this !eriod it ,as sho,n) that soft,are satisfies the requirements' The time "et,een%=+%># is announced as the destruction oriented !eriod) ,here the goal ,as to find errors'%>5+%>= is classified as the evaluation oriented !eriod intention here is that during thesoft,are lifecycle a !roduct evaluation is !rovided and measuring quality' From %>> on it,as seen as !revention oriented !eriod ,here tests ,ere to demonstrate that soft,aresatisfies its s!ecification) to detect faults and to !revent faults' Dr' /el!erin chaired the I000>#+%>> ?Test Documentation Standard@ ,ith Dr' 3etJel ,riting the "oo. NThe om!lete/uide of Soft,are TestingN' 1oth ,or.s ,ere !ivotal in to todays testing culture and remaina consistent source of reference' Dr' /el!erin and


173/205

Admin ,ill "e res!onsi"le for all the actions done "y the users' Admin can "loc. the usersand can change the !rivileges of the selected user'

Admin can delete the categories and can delete the items that are u! for the auction'


174/205

89

U(#$ Mou"#@ User module is the !lace ,here users can register themselves so that they can "id for the items availa"le and can add items for auction' The follo,ing are the featuresavaila"le for the user

User can add items to the categories availa"le so that the items can "e availa"le for auction'

User can vie, all the items that are u! for the auction and can "id for any item availa"le'

User can remove the items o,ned "y him from the auction and can fi* an end date for the

auction'

(nline auction is an effort to,ards ma.ing the auction !rocess trans!arent and easy

to users' Users can "id for the items availa"le and can add the items for the auction'


175/205

8=

CHAPTER )

FUTURE ENHANCEMENTS ANDCONCLUSION

).1 LIMITATIONS OF THE SYSTEM

The limitations of the system are

(nly the !ermanent em!loyees can access the system'

System ,or.s in all !latforms and its com!ati"le environments' Advanced techniques are notused to chec. the authoriJation'

).2 FUTURE ENHANCEMENTS

It is not !ossi"le to develo! a system that ma.es all the requirements of the user' Userrequirements .ee! changing as the system is "eing used' Some of the future enhancements

that can "e done to this system are

As the technology emerges) it is !ossi"le to u!grade the system and can "e ada!ta"le todesired environment'


176/205

1ecause it is "ased on o"-ect+oriented design) any further changes can "e easily ada!ta"le'

1ased on the future security issues) security can "e im!roved using emerging technologies'

su" admin module can "e added'

An in+"uilt ,e" "ro,ser can "e added'

).% WOR DONE

The On"in# Auctionin S&(t#! ,as successfully designed and is tested for accuracy andquality'

During this !ro-ect ,e have accom!lished all the o"-ectives and this !ro-ect meets the needsof the organiJation' The develo!ed ,ill "e used in searching) retrieving and generatinginformation for the concerned requests'

Go*"(@

Reduced entry ,or.'

0asy retrieval of information'


177/205

8>

Reduced errors due to human intervention' User friendly screens to enter the data'

Porta"le and fle*i"le for further enhancement' Ce" ena"led'

Fast finding of information requested'


178/205

8

REFERENCES


179/205

' S' 3(RTSMA44 A4D /' (R4022) )ore Java /olume 00–Advanced &eatures) Prentice 3all)U!!er Saddle River) 4e, '

F' MAR3I(4I) J1oss A* 2 #evelopment ) Pac.t Pu"lishing) 1irmingham) 0ngland) #$$'

3' MART;) (ore *ervlets and Java*erver Pages) Pearson 0ducation) U!!er Saddle River) 4e,


180/205

9$


181/205

APPENDI

CODE


182/205

9%

JSP


183/205


184/205

9#


185/205


186/205

95


187/205


188/205

96


189/205

Ha$e


190/205

98

##Dou sou+d create te *a+idator on+y ater te deinition o

te :'L or$

*ar r$*a+idator ! new Ka+idator("re0ister");

r$*a+idator.addKa+idation("cate0oryna$e","req","Q+ease enter

ate0ory Ha$e");

r$*a+idator.addKa+idation("cate0oryar","req","Q+ease enter

ate0ory Ar");

r$*a+idator.addKa+idation("cate0orydesc","req","Q+ease enter

ate0ory esc");


191/205


192/205

99


193/205


194/205

9=

"=ust RsT55#3


195/205


196/205

9>

+osin0 1te$s


197/205

@

oo+ean +a0!a+se; onnection con!nu++; try@

con!0etonnection();

Qrepared2tate$ent pst!con.prepare2tate$ent("insert into

cate0ory$aster *a+ues(Y,Y,Y)");

pst.set2trin0(7,a$ode+.0etate0oryna$e());

pst.set2trin0(P,a$ode+.0etate0oryar());

pst.set2trin0(>,a$ode+.0etate0orydesc()); int

n!pst.e9ecuteJpdate();

i(n)


198/205

9

@

+a0!true;

C

Ccatc (E9ception e) @ e.print2tac&race();

## OO8 and+e e9ception

C

return +a0;

C

pu+ic oreList *iewate0orys()

@

oreList acore+ist!new oreList();

onnection con!nu++;


199/205

ate0ory'ode+ a$ode+!nu++;

try@

con!0etonnection(); Qrepared2tate$ent

pst!con.prepare2tate$ent("se+ect X ro$ cate0ory$aster");

Resu+t2et rs!pst.e9ecuteVuery(); wi+e(rs.ne9t())

@

a$ode+!new ate0ory'ode+();

a$ode+.setate0oryna$e(rs.0et2trin0(7));

a$ode+.setate0oryar(rs.0et2trin0(P));

a$ode+.setate0orydesc(rs.0et2trin0(>));

acore+ist.add(a$ode+);

Ccon.c+ose();

Ccatc (E9ception e) @

e.print2tac&race();



200/205

=$

C

return acore+ist;

C

pu+ic ate0ory'ode+ *iewate0orys(2trin0 cate0oryna$e)

@

oreList acore+ist!new oreList();

onnection con!nu++;

ate0ory'ode+ a$ode+!nu++;

try@

con!0etonnection(); Qrepared2tate$ent

pst!con.prepare2tate$ent("se+ect X ro$ cate0ory$aster were

ate0oryna$e!Y");

pst.set2trin0(7,cate0oryna$e); Resu+t2et rs!pst.e9ecuteVuery();

wi+e(rs.ne9t())

@


201/205

a$ode+!new ate0ory'ode+();

a$ode+.setate0oryna$e(rs.0et2trin0(7));

a$ode+.setate0oryar(rs.0et2trin0(P));

a$ode+.setate0orydesc(rs.0et2trin0(>));

Ccon.c+ose(); Ccatc (E9ception e) @

e.print2tac&race();


C

return a$ode+;

C

pu+ic oo+ean update(ate0ory'ode+ a$ode+)

@


202/205

=%


con!0etonnection();

Qrepared2tate$ent pst!con.prepare2tate$ent("update

cate0ory$aster set ate0oryar!Y,ate0orydesc!Y were

ate0oryna$e!Y");

pst.set2trin0(7,a$ode+.0etate0oryar());

pst.set2trin0(P,a$ode+.0etate0orydesc());

pst.set2trin0(>,a$ode+.0etate0oryna$e());

int n!pst.e9ecuteJpdate(); i(n)

@

+a0!true;

C



203/205


C

return +a0;

C

pu+ic oo+ean de+ete(2trin0 cate0oryna$e)

@


con!0etonnection();


204/205

=#

Qrepared2tate$ent pst!con.prepare2tate$ent("de+ete ro$

cate0ory$aster were ate0oryna$e!Y");

pst.set2trin0(7,cate0oryna$e);

int n!pst.e9ecuteJpdate(); i(n)

@

+a0!true;

C



C

return +a0;

C


205/205

C

online_auctioning_system full.docx

Documents