-
Bug
-
Resolution: Fixed
-
P2
-
6
-
b92
-
generic
-
generic
deployment.config contains two properties:
- deployment.system.config
- deployment.system.config.mandatory.
deployment.system.config is the file URL to the system (enterprise-wide) deployment.properties file while deployment.system.config.mandatory is a boolean value.
As per documentation "If deployment.system.config.mandatory is set to true, there will be an attempt to load the system deployment.properties file pointed to by the deployment.system.config URL. If the URL can be found and loaded, it will be used; but if it cannot be found or loaded, then nothing will be allowed to run."
But that's not happening in reality if URL specified inside the deployment.system.config
is invalid then running deployment applications fallback to deployment_user_home(default settings) and run using the user settings. Either we should change the behavior mentioned inside the docs or change the documentation to specify the exact/actaul behavior.
- deployment.system.config
- deployment.system.config.mandatory.
deployment.system.config is the file URL to the system (enterprise-wide) deployment.properties file while deployment.system.config.mandatory is a boolean value.
As per documentation "If deployment.system.config.mandatory is set to true, there will be an attempt to load the system deployment.properties file pointed to by the deployment.system.config URL. If the URL can be found and loaded, it will be used; but if it cannot be found or loaded, then nothing will be allowed to run."
But that's not happening in reality if URL specified inside the deployment.system.config
is invalid then running deployment applications fallback to deployment_user_home(default settings) and run using the user settings. Either we should change the behavior mentioned inside the docs or change the documentation to specify the exact/actaul behavior.