[MAGNOLIA-2577] Classloader related issues on JBoss 5.0 Created: 23/Jan/09 Updated: 02/Jun/17 Resolved: 27/Feb/09 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | build |
| Affects Version/s: | 4.0 |
| Fix Version/s: | 4.0 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Template: |
|
||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||||||
| Description |
|
From the exception (see attachment), it seems related to xerces - possibly because we ship with a version and jboss with another. Goes in the direction of my feeling we shouldn't bundle this at all. |
| Comments |
| Comment by Magnolia International [ 23/Jan/09 ] |
|
Seems to me 3.6.3 suffers from the same problem, needs double-check. |
| Comment by Magnolia International [ 27/Jan/09 ] |
|
Removing the xerces jar helps the deployment itself, but there is another issue, still related to classloading: module descriptors can't be found. |
| Comment by Magnolia International [ 27/Jan/09 ] |
|
Note that deployment on JBoss 4.2.2 still works like a breeze: adding the jaas config is sufficient; no need to remove xerces, and the current classloader as used in ClasspathResourcesUtil.findResources() behaves as expected (i.e returns URLs for the webapp's WEB-INF/lib jars and WEB-INF/classes folder) |
| Comment by Magnolia International [ 27/Jan/09 ] |
|
JBoss5 seems to behave differently, depending on how the webapp is deployed: as an exploded war directory, or as a war file Essentially, our code (ClasspathResourceUtil) is doing this: URLClassLoader cl = (URLClassLoader) Thread.currentThread().getContextClassLoader(); URL[] urls = cl.getURLs();
|
| Comment by Magnolia International [ 27/Jan/09 ] |
|
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=149391 |
| Comment by Magnolia International [ 17/Feb/09 ] |
|
Status so far:
|