MACROMEDIA COLFUSION MX 7-MIGRATING APPLICATIONS TO COLDFUSION MX 7 Manual page 27

•
The following new functions enable access to SOAP headers in CFML clients and
ColdFusion MX web services:
AddSOAPRequestHeader
AddSOAPResponseHeader
GetSOAPRequestHeader
GetSOAPResponseHeader
GetSOAPRequest
GetSOAPResponse
IsSOAPRequest
For more information, see CFML Reference and ColdFusion MX Developer's Guide.
ColdFusion components (CFCs)
You can now call super methods using named arguments.
CFCs can now return arrays of CFC instances.
Generating Java nulls
You can now generate Java nulls when calling a Java function. For more information, see the
function in CFML Reference.
JavaCast
Support for JNDI data sources under J2EE
When running the multiserver or J2EE configuration, the Data Sources page of the ColdFusion
MX Administrator lets you specify a J2EE Data Source (JNDI). After it is defined, you can
specify the data source name in the
source. Datasources found in this way cannot specify additional JNDI properties.
Changes to J2EE configuration requirements
The following changes have been made to configuration requirements when deploying
ColdFusion MX as an EAR or WAR:
Verity changes
longer need to add Verity binary file directories to your system path.
Classloader changes
ColdFusion MX 7 loads all JAR files in the cfusion/lib and cfusion/lib/update directories.
Additionally, ColdFusion MX 7 has its own classloader, for which you define the classpath using
the
cf.class.path
Tip: In the multiserver configuration, the installer creates a JRun user name admin, with the same
password as the ColdFusion Administrator password.
datasource
ColdFusion MX 7 uses Java interfaces to communicate with Verity. You no
You no longer need to add cfusion/lib to the system classpath.
element in the WEB-INF/web.xml file.
attribute of SQL tags to access the J2EE data
Other changes in ColdFusion MX 7 27