Please note that Allaire will phase-out this tag in future releases, and recommends that you simply convert
it to a Java Custom tag.
For example, if you currently use the CFX_J tag that has the CLASS attribute set to "Foo", then to use a
Java CFX, you would do the following:
1. Rename your custom tag to something like "CFX_Foo".
2. Add the "java" custom tag using the ColdFusion Administrator. Specify the classname as
"Foo" (case sensitive) in the appropriate field.
3. Call you custom tag from your template using CFX_Foo instead of CFX_J. You should omit the
"CLASS" attribute in the tag.
Tags
l
The CFIMPERSONATE tag, using the TYPE=OS attribute won't work if the account under which
ColdFusion is running does not have rights to logon the user.[12544]
l
Using an ODBC driver, CFUPDATE does not update datetime fields correctly for SQL Server 6.5 or
Sybase System 11. It inputs a time portion of 00:00:00 no matter what time you provide. This does not
happen with CFQUERY or CFGRIDUPDATE. [7162]
l
When using CFGRIDUPDATE with the Sybase native driver, you can only delete one row. If you try to
delete more than one row, a Sybase DB error will occur.
l
CFINSERT and CFUPDATE fail for datetime fields when you use the IBM DB2 ODBC driver. To avoid this
behavior, either use the DB2 native driver, or, if you must use the IBM DB2 ODBC driver, use the
CFQUERY tag to update the row.
COM and CORBA
l
The behavior for COM objects that return a VT_NULL has been changed. In previous versions the return
values was "TRUE". In the current version, the return value is an empty string (""). This was implemented
to be consistent with other scripting languages, and given that the current version of ColdFusion does not
have a concept of NULL values.
l
ColdFusion 4.5.1 now supports calling property put methods that have arguments. For example to set the
following property:
[id(200), propput] HRESULT Value([in] BSTR x, [in] VARIANT y);
use the
following CFM syntax:
<cfset foo.Value("name", "bubu")>
l
COM/DCOM support for Intel platforms is available only under NT 4.0 or greater, and DCOM enabled
Windows 95. An error message with the following text will be displayed when running under platforms that
do not support it:
This OS does not support COM/DCOM. Please verify that you
are running NT 4.0 or DCOM enabled Windows 95.
CoInitialize has not been called
A patch for Windows 95 can be found at http://www.microsoft.com/msdn. (DCOM for Windows Version
1.1).
There could still be some problems reported when using objects that do not have a threading model, and
potentially have not been made thread-safe. Some of these objects have been generated using older
versions of Delphi (3.0), and VB.
To work around these issues, change the threading model to "Free" by using "OleView", or have the
vendor of the object/development tool provide you with an updated conforming object.
l
The "LOCALE" attribute can be used to set arguments for the call to init_orb(..). This is specific to
VisiBroker orbs, and has only been tested with the 3.2 C++ version.
The value should be of the form (note that each type-value pair has to start with a leading "-"):
<CFOBJECT TYPE=CORBA
Page 11 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