[jboss-jira] [JBoss JIRA] (AS7-6068) jar file system is broken again (regression)

[Stuart Douglas (JIRA)]

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

Stuart Douglas edited comment on AS7-6068 at 12/19/12 8:38 PM:
---------------------------------------------------------------

There is a flag in jboss-deployment-structure.xml that allows you to change the code base from a vfs:// URL to the physical URL, via the use-physical-code-source attribute. For bouncycastle bundled in a war the code would look something like:

{code}
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.1">
    <deployment>
        <resources>
            <resource-root path="WEB-INF/lib/bouncycastle.jar"  use-physical-code-source="true"/>
        </resources>
    </deployment>
</jboss-deployment-structure>
{code}

Does this resolve the problem?
                
      was (Author: swd847):
    There is a flag in jboss-deployment-structure.xml that allows you to change the code base from a vfs:// URL to the physical URL, via the use-physical-code-source attribute. For bouncycastle bundled in a war the code would look something like:

[code]
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.1">
    <deployment>
        <resources>
            <resource-root path="WEB-INF/lib/bouncycastle.jar"  use-physical-code-source="true"/>
        </resources>
    </deployment>
</jboss-deployment-structure>
[code]

Does this resolve the problem?
                  
> jar file system is broken again (regression)
> --------------------------------------------
>
>                 Key: AS7-6068
>                 URL: https://issues.jboss.org/browse/AS7-6068
>             Project: Application Server 7
>          Issue Type: Bug
>    Affects Versions: 7.1.1.Final
>            Reporter: Alvin Thompson
>            Assignee: JBoss SET
>            Priority: Critical
>
> Similar to issue JBAS-7882, you cannot bundle a security provider in a WAR/EAR, because JBOSS's jar file system becomes confused when there are JARs nested in other JARs/WARs/EARs, which is pretty much always.
> This was supposedly fixed in previous versions, but it's back in 7.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira