Source-derived document; reported behaviour, inference and evidence gaps are identified in the text.
Return to: C07 — System Context and Components — topic detail
runtime and user interface
In this document
System: runtime and user interface
The target application is a Java desktop application using the com.ais.fc.ix framework for UI, input handling, and application lifecycle management, with AWT event handling and Swing-like form components. Custform, Orderform, Stock_Sel, and State_List provide evidence of generated forms and screen records. Orderform includes customer, order, item, stock, form-only total, and s_items records. E0011 E0012
The repository describes the project as an Informix 4GL-to-Java migration example for the stores demo. The Java launcher invokes com.ais.demo.D4_Main and uses libraries including SwingX, the Informix JDBC driver, jfclix, and iText. A Gitpod workspace installs Informix components, and the documented database setup uses the ibmcom/informix-developer-database image. These facts describe the development and execution prerequisites, not a verified assignment of application components to particular hosts. E0014
The configuration sets the application date format to mm-dd-yyyy and the number format to use a dollar sign, comma, period, and asterisk. It also sets exception throwing and exception logging to false by default. These settings help explain why error-status handling and visible error messages are important, but the runtime semantics of all framework error paths remain unresolved. E0013
Harten documentation of the Informix 4GL and Java source repository, from the retained 17 October 2026 export. The exact upstream revision analysed is not established. Source findings do not establish runtime behaviour or equivalence between the implementations.
Evidence identifiers are retained for traceability. The underlying analysis records are not included in this public edition; credential values are redacted. About this case study.