http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2530 *** shadow/2530 Tue Jul 10 06:42:35 2001 --- shadow/2530.tmp.26470 Tue Jul 10 10:32:31 2001 *************** *** 34,37 **** Looks like it was broken in 1.4.0 and nobody noticed. You mentioned that you could provide fix in your application by implementing processingInstructionIO. Or do you prefer it being fixed in Xerces? As you know ! it is an internal API, so in general you can't really depend on it.. --- 34,49 ---- Looks like it was broken in 1.4.0 and nobody noticed. You mentioned that you could provide fix in your application by implementing processingInstructionIO. Or do you prefer it being fixed in Xerces? As you know ! it is an internal API, so in general you can't really depend on it.. ! ! ------- Additional Comments From [EMAIL PROTECTED] 2001-07-10 10:32 ------- ! Hm, is there a more "offical" way to modify an HTMLSerializer? At least, both ! the class and the method in question are public. ! ! I'm not sure how you could fix this in the Xerces code, because I see no good ! way to know whether a derived class implements one method or the other, so ! there's no way to know which one to call in a class that uses only a generic ! BaseMarkupSerializer. You could make the old method (processingInstruction) ! private or remove it entirely -- that way, there will at least be a compile- ! time error for applications that use the old interface. (That's probably better ! than breaking existing code silently.) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
