12 Jun
2015
12 Jun
'15
9:42 a.m.
Added some info in our top level POM:
http://git.io/vI7Ke
Thanks
-Vincent
On 11 Jun 2015 at 08:11:22, vincent(a)massol.net (vincent(a)massol.net) wrote:
On 10 Jun 2015 at 21:45:30, Sergiu Dumitriu (sergiu@xwiki.com(mailto:sergiu@xwiki.com))
wrote:
+1 for removing DOM4J, it's been dead for 10
years.
But why do we need a non w3c library at all? Why is JDOM better than DOM?
The main reason is that it is supposedly easier to use for Java
programmers, but is it that much easier to justify having different
APIs? The standard DOM is part of the Java language.
The DOM API was complex enough that several people created frameworks providing
alternatives. JDOM is one. That says a lot to me :)
And indeed I find it easy to use.
Ok so I’ changing the proposal from use JDOM2 to not using DOM4J.
If a dev in XWiki needs to manipulate an XML structure he should use one of:
* The W3C DOM API
* JDOM2
(or XStream, Stax, etc. Note that JDOM is not an XML parser, it uses available JAXP
parser)
Thanks
-Vincent
On 06/10/2015 11:07 AM, vincent(a)massol.net wrote:
Hi devs,
I’d like to propose that we agree about:
* using JDOM2 when needing to parse/output XML files
* moving away existing code gradually from DOM4J to JDOM2
Rationale:
* It would be nice to pick one fwk and have more consistency
* DOM4J seems not maintained anymore: https://sourceforge.net/projects/dom4j/files/
* JDOM2 seems maintained: http://jdom.org/news/
WDYT?
Thanks
-Vincent
--
Sergiu Dumitriu