Browse Prior Art Database

Sequential screen order control framework for browser-based client under J2EE Architecture

IP.com Disclosure Number: IPCOM000016300D
Original Publication Date: 2002-Oct-26
Included in the Prior Art Database: 2003-Jun-21
Document File: 2 page(s) / 52K

Publishing Venue

IBM

Abstract

1. Outline It is important to ensure screen order on a browser in order to achieve reliable e-commerce on browser-based clients, and there're several ways to control screen order. This invention provides existent screen-order-control solutions with flexible behavior on browser-based application environment. Its main intension is to set screen-order-UOWs(Unit Of Work) which are groups of screens, and to ensure the order for them. The screen order not belonging to screen-order-UOW is out of scope. Users are enforced to observe screen order in screen-order-UOW, however, after they exit out of screen-order-UOW, they can wander around sites freely and also re-enter into screen-order-UOW. This invention, in other words, introduces concept of the abstract session group above session into screen order, and this concept of the abstract session group is uniqueness.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 1 of 2

  Sequential screen order control framework for browser-based client under J2EE Architecture

1. Outline It is important to ensure screen order on a browser in order to achieve reliable e-commerce on browser-based clients, and there're several ways to control screen order. This invention provides existent screen-order-control solutions with flexible behavior on browser-based application environment. Its main intension is to set screen-order-UOWs(Unit Of Work) which are groups of screens, and to ensure the order for them. The screen order not belonging to screen-order-UOW is out of scope. Users are enforced to observe screen order in screen-order-UOW, however, after they exit out of screen-order-UOW, they can wander around sites freely and also re-enter into screen-order-UOW. This invention, in other words, introduces concept of the abstract session group above session into screen order, and this concept of the abstract session group is uniqueness.

2. Behavior Suppose an example of this invention like that application consists of series of screens 1-6 and that screens 3-5 are defined as a screen-order-UOW. In this case, users are enforced to proceed in the order of the screen-order-UOW, like 3-4-5. So, following orders are allowed.
1-2-3-4-5-6

2-1-3-4-5-6

6-3-4-5-1-2

6-3-4-5-2-1

Below is not allowed.

 4-3-A 3-4-A A-4-A note:"A" is an arbitrary screen not belonging to the screen-order-UOW. In addition, users can exit out of the screen-order-UOW freely. Therefore next orders are valid.
3-4-A
3-A

3. Design Main intention of this invention is definition of screen-order-UOW. In order to achieve it, following components are required in J2EE.
1) Existent screen-order-control solution To observe the order of screens. Out of scope of this invention. Assume ID confrontation method.

  A servlet confront a unique ID sent by a client with an ID saved in HttpSession. If they are same, the servlet executes a process. Otherwise, the servlet suspends a process. This method is implemented in many solutions and products like Jakarta Struts
2) Scope flag Show that a screen is in a screen-order-UOW. Generated in a server-side, embedded into JSP as HIDDEN field, and sent to a client browser.

Sent to a server-side implicitly when a client requests an execution and used by a servlet to judge whether the request (screen) is in a screen-order-UOW.
3) Entrance flag Show the first screen of a screen-order-UOW.

1

Page 2 of 2

This flag is important because disagreement of ID between from-client and in-Httpsession must be allowed on the first screen. Generated in a server-side, embedded into JSP as HIDDEN field, and sent to a client browser.

Sent to a server-side implicitly when a client requests an executi...