- Can you expound on the issue you’re solving by using a WAR deployment of Lucee as opposed to a “normal” installation? I just want to make sure we’re on the right road for the right reasons.
The end result, what I’m trying to achieve is deploying a web app, as an archive file, which has pre-compiled cfml code but not the source code. I used the Lucee installer as well, since I had issues with that, I attempted all the different modes of setting up Lucee. ie Lucee installer, Lucee.war in a tomcat container, using lucee.jar in a tomcat container.
- Have you installed just stock Tomcat and you’re trying to deploy a war on it? The subject of the post implies “yes”, but the file paths in the post imply “no”.
The method followed for my set up is this
Tomcat version is 8.5.40 and lucee-220.127.116.11.jar.
CATALINA_HOME is /opt/tomcat and CATALINA_BASE is /opt/lucee/lucee-server/
- Exactly how.where did you get/create your war file from?
The archive .lar is generated through the mapping in Lucee web admin and renamed it as ROOT.war to deploy it in the webapps directory.
- Is the issue that you can’t deploy a war that works at all, or specifically that you can’t deploy a war that provides all the CFML pre-compiled as a lar?
When archive-.lar ( built with the pre-compiled cfml alone without cfml source code) is deployed in /opt/lucee/webapps/ROOT/WEB-INF/lucee/deploy, it gets deployed successfully. And it takes me to the index.cfm, however the relative paths don’t get resolved correctly as the webroot is /opt/lucee/webaapps
But when I rename the same archive-.lar as ROOT.war, and on copy to /opt/lucee/lucee-server/webapps, it gets deployed, ie explodes the archive with all the pre-compiled cfml files. However it says, index.cfm is not found
However the same method works, if the ROOT.war has cfml source code in it and the application works as expected.
- Can you tell us more about the Lucee archive (lar)? How did you create it, how have you configured your war to use it, and what is it mapped as?
I created the Lucee archive following this https://docs.lucee.org/guides/cookbooks/filesystem-mapping/filesystem-mapping-define-mapping.html.
The mapping gets generated when its deployed as *.lar as expected. When deployed as ROOT.war, the mapping points to /opt/lucee/lucee-server/webapps/ROOT.
Hope this helps.