Compatibility / Migration with other CFML engines

Whilst Lucee is broadly compatible with Adobe ColdFusion, there are some differences.

Some are for performance reasons, others due to Adobe mis-adopting or adding features whch conflict with Lucee additions to the language. Sometimes it's a trade off between being compatible and respecting our existing users.

Our issue tracker has an acf-compat label which tracks all the known differences.

In addition, with Lucee 6, we decided to change some incompatible implementations and also change some older insecure defaults to be more secure, please refer to the following epic All Breaking changes in Lucee 6

Functions

  • ArrayContains() Returns the position of the first element in the array that matches the item that we are searching for, or 0 if the item is not found.
  • GetTimeZone() returns the timezone defined for the current request.

Guides

Guides

  • Lucee Language and Syntax Differences ## Architecture ## Adobe ColdFusion (ACF) is configured in a way that only one single web context is available for a server instance. This means that if you do not secure your single applications they might become vulnerable, you will have to use sandbox security, single instances, etc. This and the fact that you do not have the ability to configure individual CF settings for each virtual host are the major disadvantages of this setup
  • Migrating from Railo to Lucee Lucee 4.5 is forked from the Railo CFML Server (version 4.2) so you can easily migrate an existing Railo installation as follows.
  • Migrating to Lucee from ColdFusion How to migrate/port your code from Adobe ColdFusion to Lucee
  • Scopes local, arguments, query, variables, this, cgi, cffile, url, form, cookie, client, thread, caller, request

Tags

See also