[
https://issues.jboss.org/browse/JBAS-5900?page=com.atlassian.jira.plugin....
]
Ramesh Pitani commented on JBAS-5900:
-------------------------------------
we can resolved this problem by adding jboss-structure.xml with following content in SAR
file.
<?xml version="1.0" encoding="UTF-8"?>
<structure>
<context>
<path name=""/>
<metaDataPath>
<path name="META-INF"/>
</metaDataPath>
<classpath>
<path name=""/>
<path name="" suffixes=".jar" />
<path name="lib" suffixes=".jar" />
</classpath>
</context>
</structure>
jars are not loaded from the lib directory of a sar in JBoss AS 5
-----------------------------------------------------------------
Key: JBAS-5900
URL:
https://issues.jboss.org/browse/JBAS-5900
Project: Application Server 3 4 5 and 6
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.0.CR1
Reporter: Matt Wringe
Assignee: Ales Justin
Fix For: JBossAS-5.0.0.GA
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, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira