There are also methods of getting the pageContext in the onRequestEnd and cleaning the whitespace out there.
With all these tho, there can be unexpected consequences. I'd do the output=false and enablewhitespacemanagement stuff, if possible. :D On 6/5/06, Rob Wilkerson <[EMAIL PROTECTED]> wrote: > > I've used this with a reasonable degree of success. Is there a reason > for not using the obvious? I glanced at the URL and it appears to be > a CFM page, but I certainly may have missed something. > > <cfprocessingdirective suppresswhitespace="Yes"> > ... your code ... > </cfprocessingdirective> > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:242472 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
