[jboss-jira] [JBoss JIRA] (WFCORE-700) jboss deployment structure error when two deployments share the same dependency

[Enrique González Martínez (JIRA)]

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

Enrique González Martínez commented on WFCORE-700:
--------------------------------------------------

Hi [~stuartdouglas] 

The system was able to access external resource so I thought this was allowed. In any case if resource-root was designed to reference only within the deployment then I think this is still a bug because you can reference outside the deployment. 

> jboss deployment structure error when two deployments share the same dependency
> -------------------------------------------------------------------------------
>
>                 Key: WFCORE-700
>                 URL: https://issues.jboss.org/browse/WFCORE-700
>             Project: WildFly Core
>          Issue Type: Bug
>    Affects Versions: 2.0.0.Alpha2
>            Reporter: Enrique González Martínez
>            Assignee: Enrique González Martínez
>
> When two deployments depend on the same library it could throw and IOException.
> The problem is located in {code} org.jboss.as.server.deployment.module.descriptor.JBossDeploymentStructureParser12 {code}
> * When it is executed in sequence
> *# The first time is called with the argument "path", VFS is using RootFileSystem and it is considered a file.  
> *# Once it is called the second time, VFS is using JavaZipFileSystem (is mounted during the first call) and this time is not considered a file.
> * When is executed in parallel 
> *# both of them are using RootFileSystem. The second time VirtualFile.isFile is called throws an exception (Caused by: java.io.IOException: VFS000017: Filesystem already mounted at mount point)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)