1. A system for constructing a controller and a model component of a web application, comprising: a plurality of business logic objects stored on a computer readable medium, wherein each of the plurality of business logic objects represents a corresponding table of a data store, and wherein attributes of each of the plurality of business logic objects represent columns in the corresponding table of the data store; a table extensible markup language file stored on a computer readable medium that provides extensible markup language definitions of tables of the data store, wherein the extensible markup language definition of each table includes text identifying a table of the data store, text identifying columns of the identified table, and text defining an accessor method of one of the plurality of business logic objects that represent the identified table; an object extensible markup language file stored on a computer readable medium that provides extensible markup language definitions of classes persisted in the data store that correspond with the plurality of business logic objects, wherein the extensible markup language definition of each of the classes associates the class with the text identifying the table of the data store which is included in one of the extensible markup language definitions of tables of the data store in the table extensible markup language file; wherein the model component comprises the table extensible markup language file, the object extensible markup language file, and at least some of the plurality of business logic objects stored in a session memory allocated to a specific web session of the web application, and wherein the model component, when the web application is executed on a web server, provides local access to data stored in the data store through the at least some of the plurality of business logic objects; a site flow file template stored on a computer readable medium, wherein the site flow file template is configured to serve as a baseline for deriving a site flow file that defines a site flow sequence, and a servlet template stored on a computer readable medium, wherein the servlet template is configured to serve as a baseline for deriving a servlet; wherein the controller component comprises the site flow file and the servlet, and wherein the servlet, when the web application is executed on the web server, parses the table extensible markup language file and the object extensible markup language file, and establishes associations between the at least some of the plurality of business logic objects and corresponding objects persisted in the data store, wherein the servlet further receives a request from a client application, processes the request based on the site flow file, and accesses data through the model component to generate a response to the request, and when accessing the corresponding objects persisted in the data store, the servlet dynamically generates SQL commands based on the associations.
1. A system for constructing a controller and a model component of a web application, comprising: a plurality of business logic objects stored on a computer readable medium, wherein each of the plurality of business logic objects represents a corresponding table of a data store, and wherein attributes of each of the plurality of business logic objects represent columns in the corresponding table of the data store; a table extensible markup language file stored on a computer readable medium that provides extensible markup language definitions of tables of the data store, wherein the extensible markup language definition of each table includes text identifying a table of the data store, text identifying columns of the identified table, and text defining an accessor method of one of the plurality of business logic objects that represent the identified table; an object extensible markup language file stored on a computer readable medium that provides extensible markup language definitions of classes persisted in the data store that correspond with the plurality of business logic objects, wherein the extensible markup language definition of each of the classes associates the class with the text identifying the table of the data store which is included in one of the extensible markup language definitions of tables of the data store in the table extensible markup language file; wherein the model component comprises the table extensible markup language file, the object extensible markup language file, and at least some of the plurality of business logic objects stored in a session memory allocated to a specific web session of the web application, and wherein the model component, when the web application is executed on a web server, provides local access to data stored in the data store through the at least some of the plurality of business logic objects; a site flow file template stored on a computer readable medium, wherein the site flow file template is configured to serve as a baseline for deriving a site flow file that defines a site flow sequence, and a servlet template stored on a computer readable medium, wherein the servlet template is configured to serve as a baseline for deriving a servlet; wherein the controller component comprises the site flow file and the servlet, and wherein the servlet, when the web application is executed on the web server, parses the table extensible markup language file and the object extensible markup language file, and establishes associations between the at least some of the plurality of business logic objects and corresponding objects persisted in the data store, wherein the servlet further receives a request from a client application, processes the request based on the site flow file, and accesses data through the model component to generate a response to the request, and when accessing the corresponding objects persisted in the data store, the servlet dynamically generates SQL commands based on the associations. 18. The system of claim 1 , wherein the servlet is further configured to receive a first input and a first universal reference locator to a secure web site via a client, store the first input and the first universal reference locator, display, via the client, a first secure page of the secure web site in response to the first input and the first universal reference locator, navigate to a second secure page, display, via the client, the second secure page, provide the first input and the first universal reference locator to the secure web site in response to selecting, via the client, to return to the first secure page, and display the first secure page in accordance with the first input via the client.