mccorb101 wrote:in general, you don't need to do anything. java's class loading mechanism handles all this. classloaders chain together with parent/child references. most normal classloader implementations attempt to load a class from the parent before attempting to load it in the child. so, if you have a jdom jar available to both the parent and child classloader, it will only ever be loaded in the parent (and any classes in the child classloader will use these classes as well). you don't have to do anything.
Also, it's possible that some of the jars I have been given are the same as jars that my app needs. e.g. they may specify jdom and my app uses it. What is the proper way to handle this situation?