The Controller represents a behavioural component that lives throughout\n the entire lifecycle of an WebApplication or WebSite. Generally, it manages the Presenters\n and Views that are displayed, but may also provide behind the scenes management of things\n like communications, security, menu structure etc. Controllers do not implement Presenter\n interfaces i.e. they do not interact directly with Views; that is the role of Presenters.\n
\n Because of their implied lifetime, Controllers are made part of the overall RunContext for\n an application and are constructed during initialization of the application. There is no\n need to instantiate Controllers separately. The RunContextItem created for a controller\n has the same name as the Controller itself with RCI appended. You may specify an itemOrder\n for the Controller to control when it is instantiated in the RunContext; use this option\n only if you know what you're doing! The default itemOrder is 50, most base related functionality\n starts in itemOrder 20 or lower.\n
\n Controllers should not communicate with other Controllers directly; this type of communication\n should be performed using events. So, although it is possible to get the handle to another\n Controller via the RunContext, it is discouraged.\n
Generated from the mvw schema at version 0.1
This code was auto-generated by the dmogenerator utility and shouldn't be alterred manually! Generated from: org.dmd.dms.util.DmoFormatter.dumpDMO(DmoFormatter.java:133)