DO NOT REPLY [Bug 22611] - better error handling when attempting to serialize a null text node

[bu...@apache.org]

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

better error handling when attempting to serialize a null text node

keshlam@us.ibm.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|Minor                       |Enhancement



------- Additional Comments From keshlam@us.ibm.com  2003-08-21 19:37 -------
Since the current code is correct (just not maximally helpful), I'm
reclassifying this as Enhancement rather than minior bug. 

I'm not entirely sure we should be making much effort to help diagnose
mis-constructed DOMs. Not sure we should't be either.

Assuming we decide to work on this, the proposed solution isn't quite right.
Remember, we're talking about a text node. Its node name and local name are
#text, by definition. Knowing its implementation class might be useful. Knowing
its parent might be but remember that the DOM does not define the toString
operation on nodes and we probably shouldn't count on it. 

Also note that if we're going to add another exception message, we need to do so
 via our internationalization tables rather than by hardcoding the text into the
throw statement.