been fixed in this release. [14563]
l
When you attempted to send an email that was undeliverable with the CFMAIL tag, empty email messages
were created. This behavior has been fixed in this release. [14580]
CORBA
l
On NT and HP-UX, CORBA support now uses the VisiBroker 3.3/C++ libraries for the orb and naming
service.
l
On Solaris, ColdFusion uses VisiBroker 4.0/C++ libraries for the orb and naming service. Please note that
the interface repostiories created by the VisiBroker 4.0 and previous versions are incompatible. There is
currently a bug in the VisiBroker libraries that prevents objects (TypeCode : tk_objref) to be passed in/out
or returned as arguments on method or attribute calls. ColdFusion will report an unhandled or
TypeMismatch exception if an attempt is made to call such a method.
Other
l
An extra character in the HTTP header returned by CF can upset some browsers, most notably on
Macintosh computers. This problem was introduced in CF 4.5 but has been fixed in 4.5.1. [14533]
l
Debugging ColdFusion templates on Unix using ColdFusion Studio now works correctly. [13507]
Upgrading to ColdFusion 4.5.1
Note the following when upgrading to ColdFusion 4.5.1 from previous releases of ColdFusion:
Whitespace handling
l
ColdFusion Server version 4.5.1 ships with the Administrator setting, "Suppress whitespace by default,"
enabled. Some CFML applications have depended on CFML' s pre-4.5 behavior, which was to leave all
whitespace present in the template. Such applications can be fixed in one of two ways:
1. Disable the "Suppress whitespace by default" feature in the Administrator. Note that the server must
be restarted for this change to take effect.
2. Use <CFPROCESSINGDIRECTIVE SUPPRESSWHITESPACE="NO"> tags to guard the code that
depends on the pre-4.5 whitespace preserving behavior. This is similar to using an HTML <PRE>
tag around preformatted data.
Error handling
l
CFCATCH.EXTENDEDINFO is now available for all structured exception types. Certain unstructured
exceptions, caught by CFCATCH or CFERROR with TYPE="ANY", may not contain an EXTENDEDINFO
variable. All such exceptions can be distinguished by their type, which will be "UNKNOWN."
l
CFCATCH selection logic in ColdFusion 4.5.1 differs slightly from ColdFusion 4.0.x In ColdFusion 4.0.x,
the first matching CFCATCH block encountered would be selected to handle an exception. ColdFusion 4.5
scans a CFTRY tag's entire list of CFCATCH blocks to find the closest match. For example, if a CFTRY tag
has a CFCATCH TYPE=TEMPLATE block, followed by a CFCATCH TYPE=MISSINGINCLUDE block,
ColdFusion 4.0.x will select the TEMPLATE block to handle a MISSINGINCLUDE exception, while
ColdFusion 4.5.1 will select the MISSINGINCLUDE block. ColdFusion 4.5.1 can be reset to handle a
template using ColdFusion 4.0.x rules by setting the compatibility setting, <cfsetting
catchexceptionsbypattern=no>
ColumnList function
l
In releases prior to ColdFusion Server 4.5, the ColumnList function would return columns added by
QueryNew in random order. Now ColdFusion returns columns in the same order in which they were added.
Page 6 of 26Release Notes - ColdFusion Server 4.5.1
08/22/2000file://C:\TEMP\cfserver451_release_notes.htm
(36 Seiten)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Kommentare zu diesen Handbüchern