Content deleted Content added
DenaDweller (talk | contribs) replaced previous content, which had been marked as to be removed |
No edit summary |
||
Line 14:
The most complex "Jar hell" problems arise in circumstances that take advantage of the full complexity of the classloading system. A Java program is not required to use only a single "flat" classloader, but instead may be composed of several (an indefinite number, in fact) nested, cooperating classloaders. This is not as uncommon as one might think: so-called "servlet containers" are typically implemented in terms of multiple classloaders. The interactions between classloaders is too complex to be fully described here. It is sufficient to say that classes loaded by different classloaders interact in ways which may not be fully comprehended by the developer, leading to inexplicable errors or bugs.
== See also ==
*[[Apache Maven]], automated software build tool with dependency management
*http://www.jayasoft.org/ivy, Dependency manager, now at Apache incubator: http://incubator.apache.org/projects/ivy.html
[[Category:Anti-patterns]]
| |||