FENIX Modules Architecture

From Giews

According to July 10th meeting the client's has been restructured with a modular architecture. Each "bubble" in the schema is a FENIX GWT module. There is a CORE module which contains the client entry point class (Fenix.java) and a reference to all the modules by means of Fenix.gwt.xml configuration file. There is also a SHARED module containing resources and utilities used by all the other ones, e.g. windows.

[edit] FENIX Module's Structure

Each module is divided in a client side, which contains all the code to be traslated by GWT, and in a server side. Client side itself is divided in a view part, containing all the user interface classes and definitioins, and in a control part, which holds all listeners implementations. A simple tree schema follows:

• Module
  • client: all Java code to be traslated by GWT must be in this package
    • control: listeners implementations
      • services: GWT services interfaces
    • view: all UI code and definitions
      • lang: multilanguage package
      • vo: value objects
    • module.gwt.xml: GWT configuration file for the module
  • server: server side code
    • utils: server side utilities

[edit] Modules List

• Core
  • BIRT
  • CCBS
  • Communication
  • FPI
  • Map
  • RE
  • Shared
    • Window
  • Table
  • Text