[jboss-jira] [JBoss JIRA] Updated: (JBAS-5900) jars are not loaded from the lib directory of a sar in JBoss AS 5

[Adrian Brock (JIRA)]

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

Adrian Brock updated JBAS-5900:
-------------------------------

               Issue Type: Feature Request  (was: Bug)
    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=141581
        Affects Version/s: JBossAS-5.0.0.CR1
                               (was: JBossAS-5.0.0.CR2)
                 Assignee:     (was: Scott M Stark)


Changed to a feature request, since it was never documentated or tested to work this way
(in fact the opposite - see the forum thread).

Use the attached forum thread for discussions on how this behaviour might be "re-intriduced" .

For the workaround, an example jboss-structure.xml can be found in
server/[config]/deployers/jbossweb.deployer/META-INF/jboss-structure.xml


> jars are not loaded from the lib directory of a sar in JBoss AS 5
> -----------------------------------------------------------------
>
>                 Key: JBAS-5900
>                 URL: https://jira.jboss.org/jira/browse/JBAS-5900
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: ClassLoading
>    Affects Versions: JBossAS-5.0.0.CR1
>            Reporter: Matt Wringe
>         Attachments: testsar.tar.gz
>
>
> In JBoss AS 5, any jars placed in the lib directory of a sar are not loaded and results in a class not found exception. The classes are loaded if the jar is placed in the root directory of the sar.
> On previous versions of JBoss AS, the classes would be loaded from either location. This prevents sars that would have worked on JBoss AS 4 to fail on JBoss AS 5.
> Steps to reproduce:
> 1) take zip attached to this report.
> 2) deploy test-in-lib.sar to JBoss AS 5. The sar will not deploy and will fail with a classNotFoundException
> 3) deploy test-in-lib.sar to JBoss AS 4, the sar will deploy without issue.
> test-in-root.sar will work on both versions of JBoss. The only difference between these sars is the location of the jar.

-- 
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