Joseph Kesselman wrote: > (a) Enable the new way in parallel with the old way, if you haven't > already done so.
It is already implemented in CVS. > (b) Post (here and on website) a good illustration of old way/new way to > simplify code conversion Yes, we need to add an FAQ entry. > (c) Deprecate the old call, making sure the javadoc is updated to explain > why it's deprecated and, preferably, to include or point to the > illustration. > (d) Give people a release cycle or two to notice and to correct their code > before you remove the methods. Sure, we can deprecate this method for the release next month and removed it in the next Xerces release. > And even if we agreed that it was worth the > damage, your change then requires all parser > configurations to have a NamespaceContext object > in their configuration. Here begins the slippery > slope... Well, this is what we do for SymbolTable. The basic parser configuration always sets SymbolTable and NamespaceContext properties so a configuration that extends the basic one does not need to do anything specific. Thanks, -- Elena Litani / IBM Toronto --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
