Changes between Initial Version and Version 1 of controller-gui

Show
Ignore:
Timestamp:
03/13/11 13:47:23 (8 years ago)
Author:
ibaldin (IP: 108.65.61.102)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • controller-gui

    v1 v1  
     1= Adding a web GUI to the controller = 
     2 
     3== Overview == 
     4 
     5Orca uses Velocity template engine to drive the GUI. Adding a GUI to the controller involves writing template files that will present the different views for the controller and connecting it to the controller logic. 
     6 
     7== Connecting controller to the GUI == 
     8 
     9 * In the factory for the controller, you need to specify the  portal 
     10plugin class that goes with it. The portal plugin class has a method 
     11getMainTemplate() that returns the path to the controller's main web 
     12template. In the context of the interdomain controller it is 
     13/interdomain/main.xml. This is so because of the way we package the 
     14controller, evertything under resources/web is copied in the package 
     15and then put under the webapp dir in tomcat. So if you make a copy of 
     16these files under resources/web/xmlrpc/, your portal plugin should 
     17return /xmlrpc/main.vm.  (See InterDomainControllerPortalPlugin.java 
     18and InterDomainControllerFactory.java). 
     19 
     20 * In addition to the portal plugin class you will need to define a 
     21ManagerObject, a proxy interface to the manager object and an 
     22implementation of this interface using local communication. The 
     23interdomain controller does all this. 
     24 
     25 * Once these are in place, the templates will be able to acquire the 
     26proxy object and can talk with the manager object. 
     27 
     28InterdomainController is a good source of examples on how it is done.