...
User Interface | What users see - in Nexaweb specified with XAL markup. |
Behavior | What the application does - in Nexaweb you can locate business logic on the server, usually as Java coded event handlers, but is not limited to this; and you locate it on the client in the form of MCOs. |
Data | What data the application uses. You can now manage data through the data framework, rather than having to embed data into your user interface XML or business logic application code. Note: The data framework is not a part of the NFC model/view/controller framework; applications written using NFC cannot access the data framework directly. |
The Data Framework is a declarative –XML only– and programmatic framework for getting data into the display. This framework allows you to:
...
Component | Description |
Data sources | Java objects that serve data to the user interface. Data sources define access points into query capable data stores. See Data Sources for more information on accessing and creating data sources. |
Formatters | A scriptable means of formatting the data for display. Formatters define data manipulation and transformation steps used to modify data for presentation purposes. See Formatters for more information on accessing and creating formatters. |
Bindings | Declarative XML markup for associating user interface components with the data sources. A binding defines a query to be made to a data source to retrieve a data object. See Binding and Iterator Tags for more information on declaring a binding. |
Iterator | Allows iterative binding of user interface objects to display complex items such as listboxs and tables. In addition, you can nest iterators to build even more complex user interface elements such as trees and tree tables. See Binding and Iterator Tags for more information on using iterators. |
...
See the API documentation for the DataService interface and the Data Service - bind syntax section of this documentation for more information.