The event object is the object that will let you set the views that you want to render, so please explore its API in the CFC Docs. To quickly set a view to render, do the following:
1
event.setView('view');
Copied!
The view name is the name of the template in the views directory without appending the .cfm. If the view is inside another directory, you would do this:
1
event.setView('mydirectory/myView');
Copied!
The views you set will use the default layout defined in your configuration file which by default is the layouts/Main.cfm
We recommend that you set your views following the naming convention of your event. If your event is users.index, your view should be users/index. This will go a long way with maintainability and consistency and also will activate implicit views where you don't even have to use the set view method call.
View With Custom Layouts
You can also use the setView(), setLayout() methods to tell the framework which view and layout combination to use:
* @view The name of the view to set. If a layout has been defined it will assign it,elseif will assign the default layout. No extension please
2
* @args An optional setof arguments that will be available when the view is rendered
3
* @layout You can override the rendering layout ofthissetView() call if you want to. Else it defaults to implicit resolution or another override.
4
* @module The explicit module view
5
* @noLayout Boolean flag, wether the view sent in will be using a layout or not. Default is false. Uses a pre set layout or the default layout.
6
* @cache True if you want to cache the rendered view.
7
* @cacheTimeout The cache timeout in minutes
8
* @cacheLastAccessTimeout The last access timeout in minutes
9
* @cacheSuffix Add a cache suffix to the view cache entry. Great for multi-domain caching or i18n caching.
10
* @cacheProvider The cache provider you want to use for storing the rendered view. By default we use the 'template' cache provider
11
* @name This triggers a rendering region. This will be the unique name in the request for specifying a rendering region, you can then render it by passing the unique name to renderView();
Copied!
Cached Views
You can leverage the caching arguments in the setView() method in order to render and cache the output of the views once the framework renders it. These cached views will be stored in the template cache region, which you can retrieve or purge by talking to it: getCache( 'template' ).
1
// Cache in the template cache for the default amount of time
2
event.setView( view='myView', cache=true);
3
// Cache in the template cache for up to 60 minutes, or 20 minutes after the last time it's been used
Data can be passed from your handler to the view via rc or prc. If you want to pass data to a view without polluting rc and prc, you can pass it directly via the args parameter, much like a method call.
1
var viewData ={
2
data1 = service.getData1(),
3
data2 = service.getData2()
4
};
5
​
6
event.setView( view='myView', args=viewData );
Copied!
Access the data in the view like so:
1
<cfoutput>
2
Data 1: #args.data1#<br>
3
Data 2: #args.data2#
4
</cfoutput>
Copied!
No Rendering
If you don't want to, you don't have to. The framework gives you a method in the event object that you can use if this specific request should just terminate gracefully and not render anything at all. All you need to do is use the event object to call on the noRender() method and it will present to the user a lovely white page of death.