Developer

Application Customization

You can customize existing functions in the Web UI.

The Web UI, which runs outside the OSGi container, uses service client interfaces to access the container. Service clients provide the interface for all services.

Integrating a new service interface requires:
  • Spring bean configuration for the refreshable client interface
  • Spring bean configuration for the client logic, the service caller
  • Methods that access the new functions being used

Different service-client interfaces are provided for back-end authentication, via the built-in system user (client beans defined in the system-clients-context.xml file), or by using authentication for the currently logged in user (beans defined in the self-clients-context.xml file).  The application code determines which service-client interface bean to use, systemAuthTransactionClientLogic or selfAuthTransactionClientLogic.

You can also customize the application top menu (main navigation) items and left-menu items (context specific menu items) for existing portal applications, or provide new top-menu and left-menu items. To customize menu items:
  • Create new top-menu beans that identify text labels, target page Java classes, privileges required to view top-menu items, and whether the items are active.
  • Modify the existing topMenu Spring bean, by referencing new or modified top-menu item beanss
  • Modify existing or create new lists of left-menu beans, and identify text labels, target page Java classes, privileges required to view the left-menu items, and whether the items are active.  These java.util.List beans are injected into existing Wicket pages by references to the list bean names.