Heads-up: bug introduced into CFABORT & CFLOCATION in CF9
G'day
This is just a heads-up about a not-insignificant bug Ben Nadel has spotted with CFABORT (and the same thing applies to CFLOCATION) in CF9.
The blog entry is here:
The short version is that prior to CF9, CFABORT meant "abort processing". In CF9, it now only kinda aborts processing, as whilst it halts "mainline" code from running, it still executes onRequestEnd().
It seems that this change came about from a "bug" raised with Adobe here:
http://cfbugs.adobe.com/cfbugreport/flexbugui/cfbugtracker/main.html#bugId=80798
This is not a bug (Mark's raised it as a bug, not an enhancement request), as it's been the way CFABORT had always previously worked. I can see an argument as to how Mark's suggestion could be handy, but monkeying with CFABORT's default behaviour was not the solution here.
We've just upgraded our CF servers to CF9, and now we need to recode certain parts of our app to work around this. So we're not overly happy about this.
I've raised a bug report suggesting this change is backed out and delivered as a hotfix:
http://cfbugs.adobe.com/cfbugreport/flexbugui/cfbugtracker/main.html#bugId=86960
If it's the sort of thing that would affect you - or if you're just as annoyed as I am about Adobe changing the default behaviour of its really really fundamental tags for no good (/well-thought-out ~) reason, then pls vote for it.
Cheers.
--
Adam
AdChoices