I have to apologize for this one. I was contacted by Macromedia's QA team some time ago about this issue, which at the time appeared to be a bug in the updater. I wasn't on the Merrimack beta at the time, so they had to get me in the program first. By the time they got me in a few days later, it was the very end of July and we were engaged on a new project. I truly thought this was a simple problem with the updater and that they would resolve it. Because of the NDA, I couldn't relay such problems with a Beta to anyone (you know the rules).
I don't display the "To" column in my mailboxes, and I set up filters to route discussion list messages to their respective folders. I just re-searched the contents of my email for anything related to this issue and a message that was sent directly to me as a forward back on August 8th was filtered to my Merrimack folder, but I didn't recognize it as relevant because the subject line as "FW: [merrimack_general] Welcome to the ColdFusion MX 7 Updater Release Candidate Program". The message clearly stated the problem, which was that the updater is now more sensitive to using reserved words in the code. It was line 191 that I mentioned earlier. The reason for this line of code is that in an earlier version of ColdFusion MX 6.1 there was a bug that would allow the CFCATCH scope to be shared between multiple components persisted in the Application scope, and this line of code was necessary to work around the bug. Updater 7.01 is now more sensitive to using reserved words in code, so this line of code now throws an exception. If I had seen that message then I would have posted it to the rest of the Merrimack list and created a KnowledgeBase article describing the fix that would have remained unpublished until the release of the Updater. I've created the KnowledgeBase article and published it: http://www.productivityenhancement.com/support/DisplayKBArticle.cfm?id=9F837982-D32F-10C8-5477-6E19E31B1274&Page=1 Below is the message I missed from Macromedia. Respectfully, Adam Phillip Churvis Member of Team Macromedia Certified Advanced ColdFusion MX 7 Developer http://www.ProductivityEnhancement.com Download Plum and other cool development tools, and get advanced intensive Master-level training: * C# & ASP.NET for ColdFusion Developers * ColdFusion MX Master Class * Advanced Development with CFMX and SQL Server 2000 ==================================================== Adam, I think we found the source of the incompatibility with your plum software. We tightened up some checking for reserved words and caught a variable called 'CFCATCH' in your code. Stephen Dupre Macromedia QA -----Original Message----- From: Thomas Donovan [mailto:[EMAIL PROTECTED] Sent: Monday, August 08, 2005 7:44 AM To: merrimack_general Subject: RE: [merrimack_general] Welcome to the ColdFusion MX 7 Updater Release Candidate Program The stylesheet component seems to define, but never use, a variable named CFCATCH. {Plum_application}/components/StylesheetAPI.cfc line 191 var CFCATCH = 0; This variable is reserved to the <cftry><cfcatch> tags, which StylesheetAPI does use. ref: http://livedocs.macromedia.com/coldfusion/7/htmldocs/00000192.htm Merrimack catches this error. If I remove this line it runs OK for me on merrimack. -tom- ********************************************************************** You can subscribe to and unsubscribe from lists, and you can change your subscriptions between normal and digest modes here: http://www.productivityenhancement.com/support/DiscussionListsForm.cfm **********************************************************************
