- it only applies to Unix systems not 100% true, Robin.
I remember on a win2k + :8500webserver one dumb-ass error I made (about 18+ months ago) was where I had an Application.cfm file that I renamed as "application.cfm". Because the classes had already been compiled, the file system saw application.cfm fine but I kept getting strange errors. Clearing the \WEB-INF\cfclasses folder fixed the issue. dunno what was actually happening but it all started with me changing "App.." to "app..." (unfortunatly I can't find the cfaussie post detailing this) exceptions prove the rule perhaps? cheers barry.b -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robin Hilliard Sent: Wednesday, 22 September 2004 7:15 AM To: CFAussie Mailing List Subject: [cfaussie] Re: Include application.cfm Not up to Macromedia - it only applies to Unix systems, where filenames are case sensitive. See http://livedocs.macromedia.com/coldfusion/6/Developing_ColdFusion_MX_App lications_with_CFML/appFramework4.htm Robin http://www.rocketboots.com.au Peter Tilbrook wrote: > Just remember it should always be called "Application.cfm", not > application.cfm - same goes with OnRequestEnd.cfm. Why MM have stuck to this > after nine years is beyond me but that's the way it is. --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/ --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
