DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27213>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27213 Incorrect handling of isSupported() and getFeature() for DOM-3 Nodes? Summary: Incorrect handling of isSupported() and getFeature() for DOM-3 Nodes? Product: Xerces2-J Version: 2.6.2 Platform: All OS/Version: All Status: NEW Severity: Minor Priority: Other Component: DOM AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] In org.apache.xerces.dom.NodeImpl, the isSupported() function checks the DOMImplementation for the supported features. This is OK when the DOM implementations are used as is. However, a typical application is to extend them for build custom DOM implementations. The whole idea behing these functions for Nodes (as opposed to the DocumentImplementation) is to allow different nodes to support different features. DOM-3 tries to be able to mix various languages in a single document where the DOM Nodes will possible support various features. Now, if a custom DOM-3 implementation is based in the Xerces DOM-3 implementation, and the DOMImplementation is also extended, all the requests for org.apache.xerces.dom.NodeImpl features will return any additional features which are not generally supported. Whouldn't it be better for each node to know what features it has and respond accordingly without requesting the owner document? (easy solution: don't use the owner document, but use the document implementation class instead..maybe) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
