Luca brought up something that I've been meaning to bring up on the list but kept on forgetting about it. He said: ...snip", especially since DOM4J claims to offer full support for the standards, such as W3C DOM."
Does dom4j at its core really need to be w3c DOM compliant? The w3c DOM is a good idea gone horribly wrong (I'm sure I can find support for this argument on the XML-DEV mailing list) and IMHO dom4j should not conform to (duplicate) the w3c DOM's mistakes. Granted, I'm using hindsight to (gently) bash the w3c's DOM but that's the benefit of hindsight. It allows you see what when wrong in the past and therefore take steps to prevent it from happening again in the present or future. I think for interoperability purposes having something in the util package to covert a dom4j DOM to a w3c DOM is a good idea (I think we have this already somewhere) but forcing the dom4j document model to reflect the w3c's is an accident waiting to happen. Just my 2 cents. Dane Foster Equity Technology Group, Inc http://www.equitytg.com. 954.360.9800 _______________________________________________ dom4j-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dom4j-user
