I would also like to do the exact same thing, but JBoss is loading the older version instead :(
jdom is used only for parsing xmbean descriptors. If the server starts with the newer jdom then there will be no problems.
Thanks for the reply Scott. I updated the jdom.jar in server/lib and the server booted fine.
I'm working with a webapp deployed inside of a .ear. This webapp uses Cocoon/Avalon which has its own JDOM nested in a couple levels deep. This JDOM version is rather old, and at runtime I'm getting method invocation errors because I believe it is trying to use the version of JDOM in server/lib.
I've seen a couple posts about using class loader repositories for different WARs and what have you. If I wanted to isolate parts of a WAR and/or EAR to use different version of JDOM, is this the way to go?