[jboss-jira] [JBoss JIRA] (WFCORE-65) Filesystem deployment scanner deployment failure removes other scanners ' deployments

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13057113#comment-13057113 ] 

Brian Stansberry edited comment on WFCORE-65 at 4/8/15 2:21 PM:
----------------------------------------------------------------

A fix for WFCORE-65 will likely fix WFCORE-632 as well. If in a deployment resource in the model we store a non-persistent "owner" attribute (doesn't need to be persisted) with a value of type LIST of PROPERTY, the scanner can pass in its own address when adding deployments, and use that to ignore unrelated deployments.

Any "owner" attribute should be treated like the "persistent" attribute -- not part of the "add" API description for a resource, not modifiable, not persisted to xml.


was (Author: brian.stansberry):
A fix for WFCORE-65 will likely fix WFCORE-632 as well. If in a deployment resource in the model we store a non-persistent "owner" attribute (doesn't need to be persisted) with a value of type LIST of PROPERTY, the scanner can pass in its own address when adding deployments, and use that to ignore unrelated deployments.

> Filesystem deployment scanner deployment failure removes other scanners ' deployments
> -------------------------------------------------------------------------------------
>
>                 Key: WFCORE-65
>                 URL: https://issues.jboss.org/browse/WFCORE-65
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 1.0.0.Alpha5
>            Reporter: ehsavoie Hugonnet
>
> There is no way to associate a deployment to a specific scanner thus if one deployment fails for a scanner during startup all deployments not persistent will be removed 



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)