[
https://issues.jboss.org/browse/WFCORE-1333?page=com.atlassian.jira.plugi...
]
David Lloyd commented on WFCORE-1333:
-------------------------------------
While I agree that the server should not crash in this case, validating the attribute is
the wrong answer.
Here are a few ways in which it could fail:
* The directory might be moved or deleted while the server is running
* The directory's permissions might be modified while the server is running
* The user might expect to be able to start the server and add the directory after the
fact
The reason this fails is that a transient condition is being checked for in the
configuration, but the configuration has no way to enforce the ongoing conformence to the
constraint.
The right answer is for the deployment scanner to dynamically be able to handle the
directory appearing and disappearing. The user should be allowed to set a non-existent
{{path}} component, which causes the deployment scanner to find no files until the path is
created. The {{relative-to}} component, however, should be validated as that is a model
integrity check.
Editing of default deployment scanner's relative-to attribute can
cause server crash
------------------------------------------------------------------------------------
Key: WFCORE-1333
URL:
https://issues.jboss.org/browse/WFCORE-1333
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 2.0.7.Final
Reporter: Chao Wang
Assignee: Chao Wang
Priority: Critical
Setting value of {{relative-to}} attribute of default deployment scanner on standalone
server to a path which does not exists in file system causes server crash.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)