That's exactly what I did, and it works, though in the general case an API could do something squirrelly like check on the class of the Reader object and do something different based on the derived class (e.g. FileReader) in which case the filter isn't going to be the same class as the class it's wrapping. Xerces doesn't do that, fortunately (and no respectable API should).
Thanks for the confirmation. Richard -----Original Message----- From: Joseph Kesselman [mailto:[EMAIL PROTECTED] Sent: Thursday, December 05, 2002 11:15 AM To: [EMAIL PROTECTED] Subject: Re: Closing the input stream One obvious workaround would be to write a stream "filter" object which passes most calls through to the stream it's wrapped around but ignores the close request, then use that between your stream and Xerces... ______________________________________ Joe Kesselman / IBM Research --------------------------------------------------------------------- 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]
