Is there a way of updating more a page like we had on railo?
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
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:
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+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/c6619fb8-f30d-4a95-9015-150647377e81%40googlegroups.com
https://groups.google.com/d/msgid/lucee/c6619fb8-f30d-4a95-9015-150647377e81%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
Just use this:
for any local testing. lucee.localtest.me cf.localtest.me can’t be easier.On Thu, May 14, 2015 at 8:10 PM, Mehdi B <@Mehdi_B> wrote:
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
On Thursday, May 14, 2015 at 11:50:17 AM UTC+2, Nando Breiter wrote:
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:Change Location of ColdFusion Webroot - Nando @ Aria Media
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
https://groups.google.com/d/msgid/lucee/c6619fb8-f30d-4a95-9015-150647377e81%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.–
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+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/4058ce72-0875-4dcd-aa29-d2c676faaa22%40googlegroups.com
https://groups.google.com/d/msgid/lucee/4058ce72-0875-4dcd-aa29-d2c676faaa22%40googlegroups.com?utm_medium=email&utm_source=footer
.For more options, visit https://groups.google.com/d/optout.
–
Paul Kukiel
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.
MehdiOn Thursday, May 14, 2015 at 11:50:17 AM UTC+2, Nando Breiter wrote:
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:Change Location of ColdFusion Webroot - Nando @ Aria Media
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 <javascript:>.
To post to this group, send email to lu...@googlegroups.com <javascript:>
.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/c6619fb8-f30d-4a95-9015-150647377e81%40googlegroups.com
https://groups.google.com/d/msgid/lucee/c6619fb8-f30d-4a95-9015-150647377e81%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
I was just looking for this myself. Is the Railo documentation applicable
to Lucee at this point?
DanOn Wednesday, May 13, 2015 at 12:41:41 PM UTC-5, Mehdi B wrote:
Is there a way of updating more a page like we had on railo?
Top 10 Best Bitcoin Slots Sites | Best Online Casino 2022
Language_And_Syntax_Differences · getrailo/railo Wiki · GitHub
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