I did not know that the non-NS API were at one point considered for deprecation. Given that - there is no question on which one I will use.
My problems with the NS API are minor : 'xmlns' attributes can only belong to one explicit namespace, but I still have to mention which one it happens to be. And if I get it wrong, the API will raise an exception. Also, when I create an element within a namespace and a prefix, there is no option to autocreate the appropriate 'xmlns' attribute. Thanks, Keyur ----- Original Message ----- From: "Joseph Kesselman/CAM/Lotus" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, February 21, 2002 12:17 PM Subject: Re: xerces DOM API: to NS or not to NS? > > For new code, use the DOM's -NS calls. Period. > > (The DOM WG would have deprecated the old calls, if we could. > Unfortunately, it's sometimes desirable to pass a Level 2 document to old > Level 1 code, eg using a modern parser with a pre-existing application. But > they were retained _ONLY_ for this purpose; all new code should be written > using the namespace aware calls... and once a DOM has been operated on > using the old calls it is _NOT_ guaranteed safe to go back to viewing it as > a Level 2 DOM.) > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
