On Tue, 9 Jul 2002 23:08, Berin Loritsch wrote: > > In which case can I make it thread safe via some primitive > > pooling of the > > SAXParser. > > If you do, have it catch exceptions so that the parser can be removed > from the pool when an exception is caught (it's a real issue).
I am thinking about not pooling at all (or just pooling a single instance) as the old version was SingleThreaded and thus was recreated all the time. If I do pool it will only be a single instance (assuming that isntance does not generate an exception). Any preference? > > BTW it seems that the XercesParser is a little buggy. The > > lexical handler is > > never reset to null between subsequent runs even if null is passed in. > > True. Most support has gone into the more robust JAXPParser. > > The XercesParser is needed in environments with broken classloaders > or JAXP 1.0 environments like BEA WebLogic 6.0. Since most current > products supply JAXP 1.1 (including JDK 1.4) the XercesParser can > be slowly phased out. Want me to get it to print out a warning message? Or maybe deprecated the java file? -- Cheers, Peter Donald ------------------------------------------------------------ militant agnostic: i don't know, and you don't know either. ------------------------------------------------------------ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
