Coldfusion VS Lucee

[Mehdi B]

Is there a way of updating more a page like we had on railo?

http://www.getrailo.org/railoorg/index.cfm/documentation/compatibility/cfml-compatibility/

https://github.com/getrailo/railo/wiki/Language_And_Syntax_Differences

As a developper I would like to work more on lucee but still keep apps running well on CF11. 

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.


M B

[Daniel Short]

I was just looking for this myself. Is the Railo documentation applicable to Lucee at this point?

Dan

[Nando Breiter]

Mehdi,

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:

https://dnando.github.io/blog/2014/12/04/change-location-of-cf11-webroot/

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. 

M B

--
You received this message because you are subscribed to the Google Groups "Lucee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/c6619fb8-f30d-4a95-9015-150647377e81%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mehdi B]

Hi,

No need for different browser as all you have to do is setup different host names for testings.

cf.localhost in your hosts 

and

lucee.localhost 

as cookies are tied to domains and thus will trigger any cookies conflicts ;-).

I'm well aware for setting them side by side and adding jetty to the stack, it helps a lot but if you we try to log issues and try to build a kb over errors we face. I noticed some nasty bugs in the past that would pop up as the engines ground are a bit different.

Mehdi

[Paul Kukiel]

Just use this:

http://readme.localtest.me/

for any local testing.  lucee.localtest.me cf.localtest.me can't be easier.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/4058ce72-0875-4dcd-aa29-d2c676faaa22%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Paul Kukiel

[Andrew Dixon]

These links will apply to Lucee for the time being however I have raised an enhancement request against the documentation project to add in this information for Lucee, however like Nando says, this will probably never be 100% so if you need your code working on ACF and Lucee you need to run your test suite against both ACF and Lucee.

Ticket here: https://luceeserver.atlassian.net/browse/LD-22

Kind regards,

Andrew

about.me - mso - Lucee Member

--

You received this message because you are subscribed to the Google Groups "Lucee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/3190d79f-19a0-4c4b-a19d-723fbbfbf434%40googlegroups.com.