The following diagrams show the relationship between the various UI reference implementation modules. The diagrams are broken into the four primary modules for Java and .NET.
Java module maps
The controller.jsp (Java) module is the entry point into the UI reference implementation. It receives the browser request from the application server, formulates the MDEX Engine query, establishes a connection with the MDEX Engine and sends the query. Based on the contents of the query results, the controller module determines whether the request was a navigation, a record, or an aggregated record request. For navigation requests, controller forwards the request to the nav module.
The following diagram shows the controller module map:
The nav.jsp (Java), using other included nav modules, renders the main navigation page, including the navigation controls, navigation descriptors, and a record set.
The following diagram shows the nav module map:
For record requests, controller forwards the request to the rec.jsp (Java) module which, along with its child rec_* modules, is responsible for rendering a record page for a single record.
The following diagram shows the rec module map:
For aggregated record requests, controller forwards the request to the agg_rec.jsp (Java) module which, again, along with its child agg_rec_* modules, renders a page for an aggregated Endeca record.
The following diagram shows the agg_rec module map:
.NET module maps
The following diagram shows the controller module map:
The following diagram shows the nav module map:
The following diagram shows the rec module map:
The following diagram shows the agg_rec module map:
