Implementation Type - This option enables you to specify whether you wish to use an XML or Java implementation of the Controller logic on the server. This provides flexibility and choice on the server, enabling you to better adapt MVC to your server architecture. If you use the XML option you will have access to all the native XML processing instructions, including SQL access and SOAP and REST support for remote Web Service access. Selecting the Java option means you will have access to the request and response objects from the web interface and you can process this information in your choice of technology framework. Please note: that the XML option still enables you to use Java Controllers for specific situations. Additional information on Java Controllers, including example code can be found within the MVC Overview document.
View Controller Rules - When clicked, this opens a new window showing the RuleMaker screen for the selected controller, enabling its rules to be easily customised. Please see the RuleMaker User Guide for more information.
Used Services - This shows the Web Services currently used by the controller. For new controllers, no services will be present initially. When used services are present, a Remove Link to Service button will appear below the text area. Selecting a service and clicking this button will remove the selected service from the list, and it will appear in the list below it.
Available Services - If Web Services have been defined for this application, a list of these services will be present in this dropdown. Selecting one of these services, and clicking on Use Service, will transfer the service from this list to the text area above, to show that a link now exists between the controller and that service. The easiest way to add new entries to this list, is to use the Import WSDL function described within the XDE User Guide. This will process a given WSDL file and create the required entries within the
The Save button saves all server-side component manipulation to do with the Controller.
modellayer of the MVC application, which would then appear in this list.
In exceptional circumstances it may be necessary to make the controller replicate the functionality of a different controller, Generally, this will not be necessary, but the advanced options make this possible.
Create New Controller - If a controller has already been created on the application map it has a set of rules/logic associated with it. However, you can associate a new set of rules/logic to the controller without creating a new controller on the application map using this feature.
Select Existing Controller - It is possible to easily replicate the functionality of a different controller by selecting an already existing controller in this dropdown list.