[jboss-jira] [JBoss JIRA] Updated: (JBAS-6266) DeploymentInfo.getManifest() doesn't close the JarFile it uses to read the Manifest of a jarred deployment

[Ian Springer (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ian Springer updated JBAS-6266:
-------------------------------

    Summary: DeploymentInfo.getManifest() doesn't close the JarFile it uses to read the Manifest of a jarred deployment  (was: DeploymentInfo.getManifest() does close the JarFile it uses to read the Manifest of a jarred deployment)


> DeploymentInfo.getManifest() doesn't close the JarFile it uses to read the Manifest of a jarred deployment
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-6266
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6266
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.3.GA
>            Reporter: Ian Springer
>            Priority: Minor
>         Attachments: JBAS-6266.patch
>
>
> This is bad because if getManifest() is called on a Windows system, the deployment jarfile will end up locked. A patch to fix this is attached.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira