wow this has dragged on a bit. I think perhaps the point is being missed, so let me have a go for you.
The pdf file is never normally executed, so therefore you believe it should never be compiled either, which is a correct assumption if you are just delivering the file with with CFCONTENT, as it should never be touched with the cfcompiler. However i'm sure you said earlier that the reason for the problem was because someone was directly trying to access the file, in which case CF will of course try to compile and execute it as this is how cf works, and this is the only reason you have not had this problem before is because no-one has previously tried to link to the .pdf.cfm file. As Andrew has explained to you, JRUN will try to compile all the files within a request first before it executes anything, as it cannot execute CFML, only class files, regardless of whether the application.cfm is executed first or not. So the only way to avoid this is to make sure the .pdf.cfm file cannot be linked to directly, and you have been given several ways to achieve this. Russ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:345592 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
