http://coldfusion.com logo
Join Slack
Powered by
I'm probably looking in the wrong spots, but are t...
# lucee
d
I'm probably looking in the wrong spots, but are there any guides on getting Lucee 6.2.1.122+ manually up and running using Tomcat 11? I see that Lucee 6 installer has recently switched to installing Tomcat 11 for new versions, so I'm using that as a blue print, but not being familiar with all of the installer following the source is slow for me. Is cfml_mod still required? It looks like it, but it looks like you need v2, which I do not see an official release for on https://viviotech.github.io/mod_cfml/download.html.
z
use lucee express if you don't want to use the installer, both are 99.943% indentical
d
I'm wanting to use the raw JAR for various reasons.
z
d
I saw it in the install, but it looked like maybe Tomcat 11 didn't need it (but Tomcat 9 and 10 do)
z
that's fine but take the lucee express as a template
d
But I could be misreading the installer
Yes, thank for the suggestion for Express. I'm looking through that and grabbed out the JARs required.
z
it's super generic tomcat with only the mods required to run lucee
i'm interested to know why you don't want to just use that?
d
There's multiple reasons, but we already have a bunch of provisioning scripts in place to manage spinning up new servers. And have some Tomcat customizations in place. I also want to be able to independently update Tomcat to keep up with security patches.
z
just diff the generic tomcat distribution with express to see what we changed, there's only about 5 files changed and 6 jars added from memory
you can always grab the latest tomcat express templates from here, minus the lucee far jar https://update.lucee.org/rest/update/provider/expressTemplates
i have finally managed to get all our build automation in place
I'm excited to hear your getting into 6.2 🙂
d
@zackster While going through all these config files, I've noticed a few issues: 1. The Tomcat web.xml still has Flex Gateway references. They are commented out, but it seems like there's no need for them given that Flash is long dead. 2. It looks like the base "express" configs are getting a bit behind based on the default Tomcat configs. I'm noticing a lot of line differences in things I do not are supposed to be different. I'm seeing a lot of differences in the XML comment text (which obviously isn't important, but indicates things are not quite in sync), but there's also configuration things missing in the current files that are in the current Tomcat 11 release (like mime-mappings in the 
web.xml
file). I really wish Tomcat had a way to customize the default configuration like this w/out modifying the base templates (or at least had a tool to script the changes). Would simplify things!
Here's a side-by-side comparison between a fresh Tomcat 11 web.xml and the Lucee express version. The differences might not be important now, but I could see where things like the missing 
request-character-encoding
and 
response-character-encoding
could cause issues in some cases (maybe only in the future).
web_xml_compare.html
z
i think lucee may override 
request-character-encoding
and 
response-character-encoding
as per the server admin charset
the flex stuff is commented out, but it's fine to remove it too
d
It's probably nothing major. Like I said, I wish there was a better way of overriding Tomcat. It's one of the issues I've found in trying to keep our provisioning scripts updated. Some releases tweak the default configs.
z
atm we are monkey patching the 9x file for 10 and 11
d
I know the Flex stuff is commented out, just seemed like it could be completely gutted to simplify things. I can't imagine anyone is using it.
z
yeah, PR's are welcome, as we just released 6.2.1 we are in beta and snapshot stage, so we can FAFO a bit 🙂
d
I appreciate all the hard work you guys. I know how time consuming it is.
z
the utf-8 stuff might solve this https://luceeserver.atlassian.net/browse/LDEV-5545 ?
d
It's possible. I'm not sure, but that's why I was mentioning it.
z
it's nice to have other eyes on this stuff, i've spent ages gettting it all working, the whole test suite was a pain in the arse
d
It would seem like those are important, since Tomcat added them to the default template.
I just responded to the post in the forum.
z
just tried that utf-8 stuff, works with 11 local and 7
for that ticket
d
Niceness!
Glad I had something useful to contribute today!
z
doesn't seem to be in 9 tho
but it supported
dropped the v11 original files in there for easy comparison https://github.com/lucee/lucee-installer/commit/9a8433d8981485b3d6089c6abc79931d835c7ccf
d
Awesome!
I wonder if you can end up using a "patch" file with the install. That's the approach I'm using to make sure that changes survive updates.
z
xml with formatted comments don't help! but they seems pretty stable between versions
this update code sometimes doesn't work, i'm just redeploying the update server to make sure the next express versions include all these changes https://github.com/lucee/lucee-data-provider/blob/main/apps/updateserver/services/legacy/expressTemplates.cfc#L53 maybe it needs a date check, of course it works on my machine, sigh
ahhh, it's probably cloudflare caching...
i can see the changes in the express templates!
image.png
d
@zackster : It looks like this page is outdated for Lucee 6+: https://docs.lucee.org/guides/Various/configuration-web-xml.html
z
It's not exactly relevant for 6 is it? If you want to file PR to add a disclaimer I'd really appreciate the contribution!
d
Well, I think the page is still relevant, but the servlet classes have changed in 6. They've changed from 
lucee.loader.servlet.CFMLServlet
(Lucee 5) to 
lucee.loader.servlet.jakarta.CFMLServlet
(Lucee 6). Correct?
z
Jarkata for 6.2 onwards yes, sorry I saw XML and thought it was pre cfconfig! 6.2 needs both javax and Jakarta libs, 7 is pure Jakarta
d
@zackster FYI - Getting ready to release a Tomcat 10+ filter to replace the functionality of https://github.com/cfmlprojects/regexpathinfofilter. The Github page is: https://github.com/dswitzer/PathInfoParserFilter
I'm just finalizing testing of the filter.
It's a lot lighter weight than using something like UrlRewriteFilter to support path info with Lucee.
Open in Slack
PreviousNext
Powered by