Luca wrote: >Just like to point out that the DOM4J list of features, on the DOM4J home >page, includes this item: > > * full support for JAXP, TrAX, SAX, DOM and XSLT. > >The DOM in this list is a hyper-link to the W3C DOM specification. > >I guess the question comes down to what 'full support' really means...
The key thing to keep in mind in regard to w3c DOM compliance is the default dom4j DOM does not and will not be w3c compliant but the dom4j API may provide facilities to accept a w3c DOM object and covert it to its dom4j representation so you get all the benefits (ease of use and XPath for starters) of the dom4j document model. Also dom4j may provide facilities to convert a dom4j DOM to a w3c compliant DOM. The converted w3c DOM (should) fall(s) outside of the dom4j API, therefore you can no longer use the dom4j interfaces to manipulate the DOM once its been converted to a w3c DOM. In other words, dom4j may provide w3c import and export functionality and that should basically sum up full w3c DOM support (correct me if I'm wrong on this last sentence James). Dane Foster Equity Technology Group, Inc http://www.equitytg.com. 954.360.9800 ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, November 26, 2001 1:38 PM Subject: Re: [dom4j-user] dom4j and standards compliant Just like to point out that the DOM4J list of features, on the DOM4J home page, includes this item: * full support for JAXP, TrAX, SAX, DOM and XSLT. The DOM in this list is a hyper-link to the W3C DOM specification. I guess the question comes down to what 'full support' really means... Let me point out also that the class org.dom4j.dom.DOMDocument includes the following method: public org.w3c.dom.DocumentFragment createDocumentFragment() { DOMNodeHelper.notSupported(); return null; } And here is the code for DOMDocumentHelper.notSupported() : /** Called when a method has not been implemented yet */ public static void notSupported() { throw new DOMException( DOMException.NOT_SUPPORTED_ERR, "Not supported yet"); } I guess that at some point in the past there was an intention to support DocumentFragments... I agree that the DOM is a good idea that went wrong, and that the designers of DOM4J have done a much better job. This is why I have decided to switch to DOM4J on a project that was initially started using W3C DOM. Nevertheless W3C DOM deserves some credit for laying out good concepts, and among those the DocumentFragment. The DOM4J concept of Branch is very similar. But why is it not possible to instanciate a Branch? Would'nt DocumentFragment be a perfect candidate to be a concrete sub-class of Branch? Luca -- DISCLAIMER: This e-mail contains proprietary information some or all of which may be legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the author by replying to this e-mail. If you are not the intended recipient you must not use, disclose, distribute, copy, print, or rely on this e-mail. _______________________________________________ dom4j-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dom4j-user _______________________________________________ dom4j-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dom4j-user
