Actually it looks like quickbuild locates config.properties and productInfo.properties depending on the installation directory's location.
Having quickbuild checking into some predefined locations as well (like its document root of its WEB-INF) could ease the deployment of the only war archive (e.g.: unattended or via tomcat's manager). [Obviously it is assumed that the config files are correctly provided with the archive]
Description
Actually it looks like quickbuild locates config.properties and productInfo.properties depending on the installation directory's location.
Having quickbuild checking into some predefined locations as well (like its document root of its WEB-INF) could ease the deployment of the only war archive (e.g.: unattended or via tomcat's manager). [Obviously it is assumed that the config files are correctly provided with the archive]
Having the location of the config files explicitily configurable (and not depending on the installation directory) in web.xml would be probably better.
One could make the config files' directory point to a location like /etc/quickbuild thus avoiding to have to re-package the war if the configuration changes.
Cristiano Prisciandaro[22/Mar/07 01:56 AM]
Having the location of the config files explicitily configurable (and not depending on the installation directory) in web.xml would be probably better.
One could make the config files' directory point to a location like /etc/quickbuild thus avoiding to have to re-package the war if the configuration changes.
One could make the config files' directory point to a location like /etc/quickbuild thus avoiding to have to re-package the war if the configuration changes.