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=22440>.
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=22440

DTMNodeProxy has a number of unimplemented methods

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |DUPLICATE



------- Additional Comments From [EMAIL PROTECTED]  2003-08-18 16:55 -------
It does look like these two gripes should be merged.

Meanwhile, one possible workaround is to process from a DOMSource. If you hand
us a DOM, we will try to hand back the original DOM Nodes are responses to XPath
or as nodes for Extensions to look at, rather than generating proxy objects.
That obviously introduces some risks, but it also means you aren't depending on
our proxy layer and thus dodge this issue.

*** This bug has been marked as a duplicate of 17128 ***

Reply via email to