Submitted a patch for getting rid of dom4j. One note thought - moving to JAXP might get rid of both dom4j and some generic warnings, but that's only because it uses its own special (non-)collection types such as NodeList; the fact it follows the cross-language w3c recommendation gives it "vintage" bouquet - I would still prefer to use a good XML processing library (or a wrapper) over both dom4j and JAXP. The only question remains - is there such a library, and can we use it?
p.s. Noticed that legal/NOTICE still contains a reference to Piccolo XML parser... -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Tuesday, August 5, 2014 00:09 To: [email protected] Subject: [Bug 56814] New: Investigate switching from Dom4J to Javax.XML https://issues.apache.org/bugzilla/show_bug.cgi?id=56814 Bug ID: 56814 Summary: Investigate switching from Dom4J to Javax.XML Product: POI Version: 3.11-dev Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: OPC Assignee: [email protected] Reporter: [email protected] When the OPC code was first added, it only required Java 1.4, so needed external XML jars in the form of stax-api and dom4j. Now that we're on Java 1.6, we've already been able to drop the stax-api jar. It may also be possible to drop the dom4j one too, with some minor package name changes. If so, that'd save us one dependency, and let us solve some generics warnings (dom4j 1.6.x is Java 1.4 compatible so no generics) Depending on exactly how major a change this turns out to be, it might be possible to do in 3.11, or might be better left for a 3.12 change -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
