Hi James, > I hope very little. JDOM is a totally different project with quite > different > goals. JDOM doesn't care much about performance or info-set compliance or > advanced features, its more focussed on making things easy. It wants to > protect uses from the complexities of using interfaces and flexible > implementation strategies and just have one core implementation of an XML > document in RAM.
Thats exactally what I have observed over the last month I'm dealing now with Java & XML. Although dom4j is a relative young project - and I know it currently from version 0.3 - I like it even more. JDOM is a pragmatic aproach - works fine, although it's unhandy. dom4j is well designed - I think its even better desingend than DOM itself - and I don't mean the collection API you use. I really like that you have formed such a pattern centric interface based desing. We can say now the API of dom4j is quite stable and relativly easy to extend. Every time I read the jdom mailing list I'm suprised how often they changed the standard API. Client Programmer there have often to change its code, which is a awful task. So I really hope JDOM gets stable one day, otherwise Sun wouldn't expect it as result of the JCP. I learnt much of design and xml using dom4j and I hope I can delegate that knowlege in the esperanto project. Bye Toby -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net _______________________________________________ dom4j-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dom4j-user
