If one of the true signs of a vibrant developer community is an active blogosphere surrounding a technology, then ColdFusion certainly passes that test with flying colors. Here's a more or less random selection of what's being talked about in the community's blogs recently.

ColdFusion MX 7.01 Just Released
By Stephen Erat
from www.talkingtree.com/blog/

In these last 10 minutes the CFMX Updates page on Macromedia.com was modified to include the latest revision of ColdFusion MX, 7.01. This free update for CFMX 7 provides support for Network Deploy on WebSphere, support for Oracle 10g, support for Red Hat Enterprise Linux 4 and SUSE 9 Enterprise Linux, a Mac OS X clickable and user friendly installation GUI for the familiar Server Configuration of ColdFusion MX, as well as a bundle of bug fixes.

Sandboxing with Multiple Instances
By Andy Allan
from www.creative-restraint.co.uk/blog

A while back, John Beynon and I were having an issue with getting multiple instances to use their own JVM when enabling Sandboxing. This is when creating them using the new Enterprise Manager.

The problem we had was that for the new instances, we had to point the security manager JVM arguments to the default "cfusion" instance.

Any time we tried to have them point to the new instance, we got a security exception.

Well, as it turns out, it's a real doddle to fix, but very very easy to miss.

The default server instance "cfusion" lives under:
<jrun>/servers/cfusion/cfusion-ear/cfusion-war

When you create a new instance, it gets deployed to:
<jrun>/servers/<instance>/cfusion.ear/cfusion.war

Note the difference - a dot instead of a dash.

Now, I need to step back a bit and explain the issue.

When trying to run the new instance with it's own JVM, we took a copy of the original jvm.config file and simply replaced all "cfusion" entries for "newinstance".

What we didn't notice was that the dashes were also being replaced by dots ... hence the security warning.

So, when setting up your new instances to use their own JVM, remember to not only change the instance name but also that cfusion-ear needs to become cfusion.ear and cfusion-war needs to become cfusion.war.