On 6/16/06, Chris Scott <[EMAIL PROTECTED]> wrote:
So this brings up a conundrum. 'Fixing' this may very well bring up more problems that solutions. ColdSpring does some magic on cfc metaData, which evidently does not work on CF 6.1 versions prior to CF 6,1,0,83762 (which is still available on Adobe's site).
No. Make people patch to 83762 to use ColdSpring. Sorry, but hot fixes and updaters are created for a reason and it's ridiculous to saddle today's frameworks with problem that got fixed ages ago. CFMX 7 has been out about eighteen months now and has already had several hot fixes and an updater (7.0.1) with Mystic "coming soon". CFMX 6.1 itself came out in August 2003 - THREE YEARS AGO - and has had a steady stream of hot fixes etc to support folks who, for whatever reason, can't yet upgrade. We just hit a similar issue with Fusebox 5: in order to increase performance when generating parsed/ files, we switched from CF's built-in string to Java's StringBuffer (we do a huge amount of string concatenation!). This works fine on CFMX 6.1, CFMX 7, Railo 1.0 and BlueDragon 6.2.1 Server / JX and J2EE on JDK 1.4.2. It doesn't work on BlueDragon.NET 6.2.1 or BlueDragon J2EE 6.2.1 on JDK 1.5. New Atlanta know about the bug and between them and myself we feel comfortable about *not* including a patch in Fusebox 5 to workaround this issue. BD621 J2EE users should use 1.4.2 if they need Fusebox 5, otherwise BD621 J2EE and BD621 .NET users should wait for BD 7. I think it's reasonable that frameworks have a baseline for systems they support and systems they don't. -- Sean A Corfield -- http://corfield.org/ Got frameworks? "If you're not annoying somebody, you're not really alive." -- Margaret Atwood
