Using Reference Framework

Owned by Xiaoyan Kong (Unlicensed)
Last updated: Oct 25, 2012 by Rob Gagne (Unlicensed)Version comment
2 min read

Requires Platform 4.5.33+

Reference Framework - Overview

The Nexaweb Reference Framework is a supported foundation for building mission critical enterprise class applications. Built on Nexaweb Platform, it provides navigation, screen management, data integration and enterprise ready components – enabling development efforts to focus on solving business problems and meeting business requirements.

Based on Nexaweb Platform

By leveraging Nexaweb Platform the Reference Framework is able to provide enterprise ready RIA “desktop in a browser”, integrated client/server messaging, real-time transactions and server push (IMB), clustering/failover and session management based on the industry standard Java  programming language.  

SLA Support

The Reference Framework is an upgradable and supported Nexaweb product offering.

Spring foundation for managing business logic objects and data integration

Spring is used to provide the middle tier glue to connect the application together, to manage requests without servlet programming and to manage server side business objects.  It also provides great extensibility for integrating with other solutions.

iBATIS XML based ORM persistence framework and data integration

iBATIS is bundled to provide declarative, transaction oriented, persistence layer.  Request handling and object marshalling is provided to enable very simple connections from the presentation layer to the data layer using Nexaweb XAL and declarative data binding.

Data management is provided for the full data lifecycle: query that populates a screen, screen modifications that are persisted back the database.  Data paging, or providing a view into a larger data set, will be easily possible with the exposed data management functionality.

With Spring as the foundation, other persistence options – such as Hibernate or TopLink – can also be utilized with minor customization.

Navigation System and Screen Management

Screen loading, caching and management are provided out of the box.  Each screen becomes a self contained object that the developer can focus their efforts on.  

Features include:

  1.  MDI screen management; select from tab based or window based window management.
  2.  Dynamic menu; select from drop down, pop-up or menu driven navigation.  The menu options can be populated at design time through XML or runtime through a simple interface.
  3. Status bar that can be used to indicate global or screen scoped status.


Each option is configured via a simple XML file.  Screen development will support both static (populated by data binding) and fully dynamic (JSP) screens.