<?xml version="1.0" encoding="utf-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc = "http://purl.org/dc/elements/1.1/" xmlns="http://purl.org/rss/1.0/">
	<channel rdf:about="http://livedocs.adobe.com/">
	<title>LiveDocs Comments - coldfusion - 7 - htmldocs - 00000244.htm</title>	
		<link>http://livedocs.adobe.com/</link>
		<description>Macromedia LiveDocs - online documentation with user feedback.</description>
		<copyright>Copyright 2009, Macromedia, Inc.</copyright>
		<dc:date>2009-11-26T06:36:34</dc:date>
		<dc:language>en-us</dc:language>
		<items>
			<rdf:Seq>
				<rdf:li rdf:resource="http://livedocs.adobe.com/coldfusion/7/htmldocs/00000244.htm#66281" />
				<rdf:li rdf:resource="http://livedocs.adobe.com/coldfusion/7/htmldocs/00000244.htm#42869" />
			</rdf:Seq>
		</items>
	</channel>
	
	<item rdf:about="http://livedocs.adobe.com/coldfusion/7/htmldocs/00000244.htm#66281">
		<title>coldfusion/7/htmldocs/00000244.htm</title>
		<link>http://livedocs.adobe.com/coldfusion/7/htmldocs/00000244.htm#66281</link>
		<description>&quot;If this tag is encountered outside the context of a custom tag, for example in the base page or an included page, it executes in the same way as cfabort.&quot;&lt;br /&gt;Not quite true. cfabort will quit all processing, and not run code inside the onRequest method of Application.cfc, while cfexit within a normal cfml page will return from that template, and still run the onRequest code.&lt;br /&gt;This behavior is very useful for situations where templating is applied inside onRequest.</description>
		<dc:creator>SamCurren</dc:creator>
		<dc:type>0 0</dc:type>
		<dc:date>2007-05-03T05:35:12</dc:date>
	</item>
	<item rdf:about="http://livedocs.adobe.com/coldfusion/7/htmldocs/00000244.htm#42869">
		<title>coldfusion/7/htmldocs/00000244.htm</title>
		<link>http://livedocs.adobe.com/coldfusion/7/htmldocs/00000244.htm#42869</link>
		<description>I don't think it's correct that cfexit aborts all processing when called from a cfincluded file. My tests (cf7) show that it stops processing of the included file that contains the cfexit call, but processing of the calling page continues after the cfinclude. This is the same behavior as when called from a cfmoduled file.</description>
		<dc:creator></dc:creator>
		<dc:type>0 0</dc:type>
		<dc:date>2005-12-01T06:24:21</dc:date>
	</item>
	</rdf:RDF>

