As a developper I would like to work more on lucee but still keep apps
running well on CF11.
I think the only way to reliably do this is to continually test against
both engines while developing. Documentation is hard to get right, and
documenting differences even more difficult, especially in that some
differences will be bugs, in either engine, which might be fixed. Each
developer will likely run across their own subset of differences, depending
on the CFML features they use.
So I think the primary documentation needed is how to setup ACF and Lucee
side by side for rapid, easy testing of the the same codebase against both
engines. This might be helpful:
Similar instructions, but not exactly the same, will be applicable for
Lucee and can be easily found. Essentially, you need to modify the docBase
in Tomcat to be the same for both engines, and of course ensure each engine
runs on a different port.
There is one issue I’ve run across that you may need to work around: the
engines tend to step on each other’s cookies, which is only a problem if
both engines run from the same domain, which will be “localhost” while you
are developing. I use separate browsers, one for ACF and one for Lucee, to
work around this. Your other option is to clear cookies for localhost if
you find that you suddenly can’t login anymore locally.
So to summarize: use the same docBase for each engine installed locally for
development, but test in different browsers.
I noticed some tweaks in DSN on the fly configs and more in scripting. If
we know the features that would trigger issues we would either try to avoid
them or at least comment them as lucee/railo specific and equivalent
solution in CF11.
You will only really know which “features trigger issues” in your codebase
if you test. Once you are setup, testing an existing codebase can be
accomplished very quickly.>
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an
email to email@example.com.
To post to this group, send email to firstname.lastname@example.org.
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.