tion in the browser session), and finally to route the processed request to the appropriate JSP in the Presentation layer.

The Controller employs two packages to control the model and the view sections i.e. roseindia.web.struts.form (contains varous Action Forms) and roseindia.web.struts.action (contains varous Action Classes).

I The package roseindia.web.struts.form contains 10 Action Forms
II The package roseindia.web.struts.action contains 16
Action Classes

MODEL SECTION

The Business layer is responsible for processing the application’s business logic. The Business layer is responsible for managing a cart. It creates a representation of a new cart object needed to choose, remove and update the various items in the cart, and then communicate with the Data Access layer to store a representation of the cart in the database.

The Data Access layer is responsible for writing and retrieving data to and from the database, and returning the results to the Business layer.

The Model is organized into six packages where classes are devoted to interact with the database and to process business logic.

1 The roseIndia.dao package contains the ShoppingCartDAOImpl class implementing the ShoppingCartDAO interface. ShoppingCartDAOImpl class deals with all database related concern of administrator and customer sections of the application.

2. Package roseindia.dao.hibernate contains 7 java lasses
and 7 hibernate mapping xml documents (*.hbm.xml). hese
classes and xml documents does java-Object relational mapping with the underlying database.

3. The package roseindia.services contains a single class
ServiceFinder needed to retrieve various integrated services from Spring Application context.

4 The package roseindia.web.cart is the heart of the whole application. It contains 2 main classes which enable to add, update and remove items into a shopping cart.

5 The package roseindia.web.common contains various
helper and utility classes needed to process the business
logic.

The Presentation Layer

After the Web Controller layer routes the request to
the Business layer and retrieves the results of the processing, it then forwards the request to the Presentation layer, which is responsible for generating the HTML sent to the user’s browser.

Getting Shopping Cart Code

We are maintaining the code and documentation of the shopping cart at http://www.roseindia.net/shoppingcart/. Here, you can download the latest version of the shopping cart application.

Basically, a shopping cart is the interface between a company’s Web site and its deeper infrastructure. This allows customers to select merchandise; review their selection, make necessary modifications or additions; and finally purchase the merchandise.

Companies integrate shopping carts as these are sold as
independent pieces of software into their own unique online solution. There are number of shopping carts available like LaGarde, RomanCart, AgoraCart etc. For instance the PayPal Shopping Cart is a low-cost way for you to accept credit card and bank account payments, and can be fully integrated with your website in a few easy steps.

Features of a shopping cart:

I Easy-to-use store management tools, saves time and
money.
II Customizable for your business needs.
III Easy to implement - no CGI scripting necessary.
IV Improve buyer experience - with customizable buttons and secure payments happy customers becomes a frequent visitor.
V Customizable HTML store home page.
VI Order forms are in HTML for ease of customization.
VII Upload and store static html pages for product info,
store policies, etc.
VIII Dynamically generated product pages from store’s
database.

Developing a Shopping Cart Application

We are providing relevant details to develop an e- commerce application (a shopping cart) with Struts, Hibernate and Spring.
Features provided in the shopping cart

• Customers Registration: Existing user can login to the shopping cart by signing in using their username and password. Moreover they can update their profile suchas address, contact number, Email-id etc.