Yes, I ack both of these. Removing dom4j from the bootclasspath requires removing it from the public api of all bootclasspath elements. The two evils are:

1. dropping the XMBean dom4j ctor. This is the lesser evil in my view.
2. Including dom4j in the bootclasspath and restricting all user apps to this version, as well as the jaxen xpath version. This is the bigger problem.

Adrian Brock wrote:

On Tue, 2006-09-19 at 07:48 -0700, Scott M Stark wrote:

Ok, but there are zero uses of that ctor in the codebase.


Which assumes that nobody else used it.

 Its going to 
be broken one way or another if you jarjar or revert to the jaxp apis.


For the XMBean class at least,
there already is an org.w3c.dom.Element version.