The instructions for installing ColdFusion MX for J2EE on BEA WebLogic 7 contain two errors:

• To enable access to COM objects, you must move the jintegra.jar file from the cf_root\WEB-INF\cfusion\lib directory to the cf_root\WEB-INF\lib directory.
  
• You do not need to add the following line to wldomain_root/startWebLogic.cmd for COM support:
  SET PRE_CLASSPATH=%CF_SHARED_LIB_DIR%\jintegra.jar

ColdFusion MX for J2EE Application Servers uses the application server's default character encoding when it compiles ColdFusion pages into Java.

You can specify the character encoding to use for all pages by specifying the encoding in the JVM options for your application server. For example, the following application server JVM option specifies the Microsoft Windows Japanese character encoding:

-Dfile.encoding=MS932

However, you must force ColdFusion to recompile all pages before this switch will take effect. To force recompilation, stop ColdFusion, delete the contents of the cf_root\WEB-INF\cfclasses directory, and restart ColdFusion.

Note: You can also use the cfproccessingdirective tag to specify the character encoding for individual pages. This technique automatically causes ColdFusion to recompile the page.

<cfscript>
function getMultipartFormParameter(key, encoding)
{
	param = key.getBytes(encoding);
	value = evaluate(toString(param, "ISO-8859-1"));
	param = value.getBytes("ISO-8859-1");
	return toString(param, encoding);
}
</cfscript>

1. Start the ColdFusion MX ODBC Server and ColdFusion MX ODBC Agent services, if they are not already running.
2. In a command prompt, enter the following command:
   cf_root\db\slserver52\admin\setcp.bat OS
3. Stop the ColdFusion MX ODBC Server and ColdFusion MX ODBC Agent services.
4. Start the ColdFusion MX ODBC Server and ColdFusion MX ODBC Agent services.

The setcp.bat file sets the service code page for the ODBC server used by the Access and ODBC socket drivers. It takes one parameter. If you specify OS, the ODBC server uses the operating system code page. Specify OS for multi-byte character set operating systems like Japanese. If you specify value other than OS as the parameter, or omit a paramter, the ODBC service code page is set to the default state, no setting. The Default setting supports only 8-bit character sets.

• Access DSN –Select the Use Default Username option; OR show the Advanced Settings section and enter a username in the ColdFusion Username field.
• ODBC Socket DSN –Select the Use Trusted Connection option; OR show the Advanced Settings section and, in the Username field, accept the default username (system) or enter a username.

ColdFusion MX Administrator looks in the following JNDI locations for JDBC data sources configured at the application server level:

1: ""
2: "/"
3: "jdbc"
4: "java:comp/env/jdbc"

The ColdFusion MX Administrator does not list data sources that are configured at the application server level in other locations in the JNDI tree; however, you can use data sources that are listed elsewhere by specifying the data source's fully qualified JNDI name in any ColdFusion tag that takes a data source name, for example, cfquery.

The SQL statement [ select 1 ] caused an database query exception.

java.sql.SQLException: [Microsoft SQL Server] Login failed.
RAW_TRACE at coldfusion.tagext.lang.IncludeTag.doStartTag(Unknown Source)
PROBLEM java.lang.NumberFormatException: at coldfusion.tagext.lang.IncludeTag.doStartTag(Unknown Source)

CollectionID=default;packageName=<pkgname>;CreateDefaultPackage=false

[Macromedia][Oracle JDBC Driver]Connection reset by peer: socket write error

Connection verification failed for data source: exampleapps [MERANT][SequeLink JDBC Driver] [ODBC Socket][Microsoft][ODBC Microsoft Access 97 Driver] Can't open database '(unknown)'. It may not be a database that your application recognizes, or the file may be corrupt. The root cause was that: null

• Microsoft Jet 4 SP3
  http://www.microsoft.com/data/download_Jet4SP3.htm
• MDAC 2.7
  http://www.microsoft.com/data/download_270RTM.htm

• Use rpc as the SOAP binding style and use encoding as the encodingStyle
• Use document as the SOAP binding style and use literal as the encodingStyle

<binding name="BabelFishBinding" type="tns:BabelFishPortType">
  <soap:binding style="rpc" 
     transport="http://schemas.xmlsoap.org/soap/http"/>
  <operation name="BabelFish">
    <soap:operation soapAction="urn:xmethodsBabelFish#BabelFish" />
    <input>
      <soap:body use="encoded" namespace="urn:xmethodsBabelFish"
      encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
    </input>
    <output>
      <soap:body use="encoded" namespace="urn:xmethodsBabelFish"
      encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
    </output>
  </operation>
</binding>

<cfinclude template="/myvirtual/index.cfm">

48873
48863

48870
48867

• Collections on another server
• Collections created with mkvdk

On a system that is running JDK 1.4, you might encounter an exception that looks like the following when you run ColdFusion MX:

    class file has wrong version 48.0, should be 47.0
    Please remove or make sure it appears in the correct subdirectory of the classpath

If you get this message, replace the tools.jar file in cf_root\WEB-INF\cfusion\lib with the tools.jar that ships with JDK1.4.

To make this link work, download and install the complete ColdFusion MX documentation set. For more information on downloading ColdFusion MX documentation, see cf_root/cfdocs/dochome.htm.

java.lang.IllegalStateException: unexpected constant at coldfusion.compiler.ClassReader.readCpool(ClassReader.java:153)