
Other changes
17
Other changes
This section describes other changes between ColdFusion 5 and ColdFusion MX.
Advanced security
ColdFusion MX provides a new and easy way for you to build user authentication and roles-based
security into your applications. However, it is based on a completely different security model than
ColdFusion 5. Also, ColdFusion MX no longer includes a licensed version of Netegrity
Siteminder. Therefore, any existing Advanced Security code—including the
cfauthenticate
and
cfimpersonate
tags, and the
authenticatedContext
,
authenticatedUser
,
isAuthenticated
,
isProtected
, and
isAuthorized
functions—no longer works in
ColdFusion MX. These tags and functions are obsolete in ColdFusion MX.
For more information, see
Configuring and Administering ColdFusion MX
and the “Application
Security” chapter in
ColdFusion MX Developer’s Guide
.
SNMP support
ColdFusion MX no longer supports Simple Network Management Protocol (SNMP) for
monitoring ColdFusion applications from enterprise management systems.
Variables
ColdFusion MX includes the following changes to variables:
•
You can no longer use a dot (.) in a variable name, because ColdFusion MX supports the dot
notation as a dot operator to create a struct. For example,
last.name
creates a struct called
last
with a key called
name
, instead of creating a simple variable with a period in the name.
To work around this, use underscores in variable names instead.
•
The following
cfcatch
variables have changed:
Message
,
NativeErrorCode
, and
SQLState
.
For more information, see
cfcatch
in
“New tags, attributes, values, and changes” on page 34
.
Operators
ColdFusion MX includes the following changes to operands:
•
Exponent results differ; for example, ColdFusion 5 returns an error for
0 ^ 3
, and
ColdFusion MX only returns 1.
•
ColdFusion MX supports the dot notation as a dot operator. For example, if your
ColdFusion 5 application has a variable called
last.name
, ColdFusion MX reads this code
and creates a struct called
last
with a key called
name
.
In addition, ColdFusion MX does not create keys with dots in them like ColdFusion 5 does,
but instead creates cascading structs with non-dotted names. For example, ColdFusion 5
interprets
a.b.c="foo"
to be
a["b.c"]="foo"
, whereas ColdFusion MX interprets it to be
a["b"]["c"]="foo"
.