Thanks Joe, for the clarification. I've found that I
can side step the issue altogether if I call
getDocumentElement( ) rather than getChild( ).
-jason
--- Joseph Kesselman <[EMAIL PROTECTED]> wrote:
>
>
>
>
> Oracle is wrong. The XML Declaration is not a child
> in the DOM. Complain to
> them and see if they offer a mode which handles it
> properly.
>
> (The DOM had no standard API for the XML Declaration
> until DOM Level 3,
> which is part of why some parsers tried to cheat by
> turning it into a
> special node or -- erroneously -- calling it a
> Processing Instruction. But
> the DOM WG has said repeatedly that this kluge was,
> in fact, incorrect.)
>
> ______________________________________
> Joe Kesselman, IBM Next-Generation Web Technologies:
> XML, XSL and more.
> "The world changed profoundly and unpredictably the
> day Tim Berners Lee
> got bitten by a radioactive spider." -- Rafe Culpin,
> in r.m.filk
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
>
>
__________________________________
Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
http://promotions.yahoo.com/new_mail
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
