Hi,
I encountered issues during a migration from Railo to Lucee.
Is there any way to migrate a railo-web.xml.cfm to a lucee-web.xml.cfm
without getting a lucee-web.1.buggy file?
Can I cleanup the system in a way, so the whole migration process starts
from the early beginning with the working /WEB-INF/railo/ files if I
restart Lucee?
Regards
Michael
Hmm, I thought you were just saying the Railo to Lucee migration was buggy,
but a quick search of the Lucee code base shows that, in some instances,
Lucee literally renames config files to have the word “buggy” in them.
Well, actually that line appears to be looking for such files-- I’m not
sure where they come from. I’m guessing you’ll have to wait for Micha to
pop in and explain how to troubleshoot that. I don’t know if the errors
get logged, but I’d check your standard out log to see.
You can try taking your old config and just doing a global file/replace to
change railo to lucee but I don’t know if that actually works.
Thanks!
~BradOn Friday, August 7, 2015 at 10:21:20 AM UTC-5, mich...@gmx.net wrote:
Hi,
I encountered issues during a migration from Railo to Lucee.
Is there any way to migrate a railo-web.xml.cfm to a lucee-web.xml.cfm
without getting a lucee-web.1.buggy file?
Can I cleanup the system in a way, so the whole migration process starts
from the early beginning with the working /WEB-INF/railo/ files if I
restart Lucee?Regards
Michael
Hi Brad,
I finally could re-start the migration by removing the lucee-server and
WEB-INF/lucee directories (which I tried about five times, and worked only
once).
Editing the files manually did not work and would also drop all scheduled
tasks, as they are not stored in the lucee-web.xml.cfm.
Regards
MichaelAm Sonntag, 9. August 2015 07:27:12 UTC+2 schrieb Brad Wood:
Hmm, I thought you were just saying the Railo to Lucee migration was
buggy, but a quick search of the Lucee code base shows that, in some
instances, Lucee literally renames config files to have the word “buggy” in
them.Well, actually that line appears to be looking for such files-- I’m not
sure where they come from. I’m guessing you’ll have to wait for Micha to
pop in and explain how to troubleshoot that. I don’t know if the errors
get logged, but I’d check your standard out log to see.You can try taking your old config and just doing a global file/replace to
change railo to lucee but I don’t know if that actually works.Thanks!
~Brad
On Friday, August 7, 2015 at 10:21:20 AM UTC-5, mich...@gmx.net wrote:
Hi,
I encountered issues during a migration from Railo to Lucee.
Is there any way to migrate a railo-web.xml.cfm to a lucee-web.xml.cfm
without getting a lucee-web.1.buggy file?
Can I cleanup the system in a way, so the whole migration process starts
from the early beginning with the working /WEB-INF/railo/ files if I
restart Lucee?Regards
Michael
seems that something goes wrong when converting the railo xml to the
lucee xml, what results in invalid xml file that then get renamed to
“.buggy” and replaced with a empty version of the file.
Lucee always stores the original Railo context in a zip file next to the
config folder, so revert the change is easy.
you can send me the railo-web.xml.cfm file in question (offlist if you
like), i will check what is causing the problem.
MichaOn Fri, Aug 7, 2015 at 5:21 PM, <@Michael_Forell> wrote:
Hi,
I encountered issues during a migration from Railo to Lucee.
Is there any way to migrate a railo-web.xml.cfm to a lucee-web.xml.cfm
without getting a lucee-web.1.buggy file?
Can I cleanup the system in a way, so the whole migration process starts
from the early beginning with the working /WEB-INF/railo/ files if I
restart Lucee?Regards
Michael–
See Lucee at CFCamp Oct 22 & 23 2015 @ Munich Airport, Germany - Get your
ticket NOW - http://www.cfcamp.org/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/bb002724-a507-4865-a1be-92b8dbf5dfc5%40googlegroups.com
https://groups.google.com/d/msgid/lucee/bb002724-a507-4865-a1be-92b8dbf5dfc5%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
Micha, I noticed the try/catch doesn’t actually do anything with the
trapped error which seems like a waste of a perfectly good exception object
How do you feel about adding some basic logging (even just
e.printStackTrace() ) so in cases like this, the developer can at least get
an idea of what the issue is by checking the logs instead of having to send
you the XML file?
Thanks!
~BradOn Monday, August 10, 2015 at 10:47:40 AM UTC-5, Micha wrote:
seems that something goes wrong when converting the railo xml to the
lucee xml, what results in invalid xml file that then get renamed to
“.buggy” and replaced with a empty version of the file.
Lucee always stores the original Railo context in a zip file next to the
config folder, so revert the change is easy.
you can send me the railo-web.xml.cfm file in question (offlist if you
like), i will check what is causing the problem.Micha
On Fri, Aug 7, 2015 at 5:21 PM, <mich...@gmx.net <javascript:>> wrote:
Hi,
I encountered issues during a migration from Railo to Lucee.
Is there any way to migrate a railo-web.xml.cfm to a lucee-web.xml.cfm
without getting a lucee-web.1.buggy file?
Can I cleanup the system in a way, so the whole migration process starts
from the early beginning with the working /WEB-INF/railo/ files if I
restart Lucee?Regards
Michael–
See Lucee at CFCamp Oct 22 & 23 2015 @ Munich Airport, Germany - Get your
ticket NOW - http://www.cfcamp.org/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/bb002724-a507-4865-a1be-92b8dbf5dfc5%40googlegroups.com
https://groups.google.com/d/msgid/lucee/bb002724-a507-4865-a1be-92b8dbf5dfc5%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.