[
https://issues.jboss.org/browse/AS7-4383?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-4383:
---------------------------------------
Another option is to have the switch trigger storing the files in the data/ dir, so they
are usable by the scanner code but are not visible to the user. This would add quite a bit
of complexity to the scanning logic though.
Mode to disable writing deployment outcome files to deployment
scanner dir
--------------------------------------------------------------------------
Key: AS7-4383
URL:
https://issues.jboss.org/browse/AS7-4383
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 7.2.0.Alpha1
Investigate adding a config option that disables writing the .isdeploying, .deployed,
.isundeploying, .undeployed files to the deployment scanner dir.
Idea is to make it possible to have multiple scanners on different nodes sharing the
deployment directory, without having the markers from one interfere with another.
This may not be practical at all in reality; needs investigation.
Marker files created by the user to control deployment should still be supported.
The .failed and .pending files are a bit of a gray area that need investigation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira