Home

System Architecture

Architecture of GWT/GWTP MVP on client and Spring MVC on the server side

Client side

• View

  The View is based on Ui-Binder, the pages are defined in xml files which primary contain html code, combined with GWT-Widgets and layouted with CSS. The UI-Binder xml file contains no logik. A corresponding Java file connects the widgets with the program, all gui specific logic gets in there (switch on/off elements, show or hide elements, ...), but no business logic. The binding to the Model is done by the editor framework.

• Presenter

  All client side logic is implemented in the Presenter layer. There is now direct communication with gui elements, this is delegated to View. The communication with the server is done in thes Layer using gwtp rest dispatcher.

More details you can find on the Client-Implementation page.

Shared part

• Model

  The Model contains data and validation rules added as JSR-303 bean validation. It's used as exchange object between Client and Server using REST communication.

Server part

• Web Layer

  In the Web Layer contains controllers, exception handlers and filters. The communication with the client is done by REST controllers using the Model to exchange data.

• Service Layer

  Contains application services and infastructure services. It's only used at login implementation in the example, because we don't do anything with the given data.

• Repository Layer

  Repository interfaces and their implementations. Part of this is the communication with the database.

More details you can find on the Server-Implementation page.