Allow webConfigDir, serverConfigDir & webXML to be relative
Description
The webXML parameter can be stored in server.json as relative, however Runwar will fail to start if you specify a web.xml outside of a war right now, so it's disabled. I have a ticket in for Runwar on this. https://github.com/cfmlprojects/runwar/issues/54
webConfigDir and serverConfigDir are ignored for Adobe servers. They are used for Railo and Lucee servers. Note your serverConfigDir path will have the folder "lucee-server" appended to it This appears to come from Lucee and I don't think we have any control over it. These two settings override the location that the server and web context are expanded into. If you want to know the root of the expanded WAR for the server (where the WEB-INF lives), then you want the serverHome property.
Gliffy Diagrams
Activity
Show:
Fixed
Pinned fields
Click on the next to a field label to start pinning.
The webXML parameter can be stored in server.json as relative, however Runwar will fail to start if you specify a web.xml outside of a war right now, so it's disabled. I have a ticket in for Runwar on this. https://github.com/cfmlprojects/runwar/issues/54
webConfigDir and serverConfigDir are ignored for Adobe servers. They are used for Railo and Lucee servers. Note your serverConfigDir path will have the folder "lucee-server" appended to it This appears to come from Lucee and I don't think we have any control over it. These two settings override the location that the server and web context are expanded into. If you want to know the root of the expanded WAR for the server (where the WEB-INF lives), then you want the serverHome property.