> bit counter-intuitive? I mean, the whole purpose (in this
> case, at least) is to write the contents to a variable to
> pass back from my CFC. If I'm not writing anything to the
> output stream in cfsavecontent call itself, why do I need the
> cfoutputs? Just curious.
The CFSAVECONTENT tag is implemented as a custom tag, I think - if you look
in WEB-INF\cftags, there's a file there called savecontent.cfm. I suspect it
has something to do with that. If you were writing your own custom tag to do
the same thing, you'd typically have some line like this:
<cfset "Caller.#Attributes.Variable#" = ThisTag.GeneratedContent>
I suspect the first part of that might not work in a CFSETTING block with
output disabled.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
phone: 202-797-5496
fax: 202-797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
