Changes between Version 2 and Version 3 of controller-gui

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

--

Legend:

Unmodified
Added
Removed
Modified
  • controller-gui

    v2 v3  
    99 * In the factory for the controller, you need to specify the  portal plugin class that goes with it. The portal plugin class has a method getMainTemplate() that returns the path to the controller's main web template. In the context of the interdomain controller it is /interdomain/main.xml. This is so because of the way we package the controller, evertything under resources/web is copied in the package and then put under the webapp dir in tomcat. So if you make a copy of these files under resources/web/xmlrpc/, your portal plugin should return /xmlrpc/main.vm.  (See !InterDomainControllerPortalPlugin.java and !InterDomainControllerFactory.java). 
    1010 
    11  * In addition to the portal plugin class you will need to define a ManagerObject, a proxy interface to the manager object and an implementation of this interface using local communication. The interdomain controller does all this. 
     11 * In addition to the portal plugin class you will need to define a !ManagerObject, a proxy interface to the manager object and an implementation of this interface using local communication. The interdomain controller does all this. 
    1212 
    1313 * Once these are in place, the templates will be able to acquire the proxy object and can talk with the manager object. 
    1414 
    15 InterdomainController is a good source of examples on how it is done. 
     15BEN !InterdomainController (orca.controllers.ben is a good source of examples on how it is done.