Content

Application and Context

There are two base classes for the application framework:

• Application - binds the client and server code
• Context - this is a data holder

Application is an abstract superclass for each server application. It is created and managed by the running ApplicationContainer implementation (there is an implementation for Swing client called ApplicationServer).

The main task supported by the Application is to receive request from a client, find a controller to process it and to invoke that controller with request and current context as arguments.

Each instance of Application has its own id, which is used in talk with client. In your implementation you need override in you subclass only methods getStartControllerClassName() and getFile(String).

Context is a data holder for session and controller. Because all controllers are singletons, this is the only one place where can be stored data between the client requests.

ApplicationRequest is an application request from a client to the application server. It supports these properties:

• sessionId - an unique string identifier of the client / server session
• action - a name of the requested action
• parameters - a free (action-depended) map of parameters
• data - (changed) data from client to server

ApplicationResponse is an application response from an application server to a client. It supports these properties:

• sessionId - an unique string identifier of the client / server session
• instruction - an instruction for a client
• formId - a form identifier (a name of the form XML file to display)
• data - data from server to display on client
• parameters - a free (instruction-depended) map of parameters

Please, note there are some (by methods) supported parameters in Application Response to:

• hide component
• disable component
• transfer validation error