> From: Peter Donald [mailto:[EMAIL PROTECTED]]
>
> Hi,
>
> I was looking at the Parser interface and it seems very very
> unlikely that any
> implementation will ever not be threadsafe. So is it safe to
> assume that it
> always will be?
The XercesParser isn't
> Specifically there is a bunch of parser users that essentially do a
>
> final Parser parser = (Parser)m_manager.lookup( Parser.ROLE ); try {
> parser.doSOmeParsing();
> }
> finally
> {
> m_manager.release( parser );
> }
>
> Will anything break if the parser is aquired once in
> compose() method and
> never released. The reason is that all this lookup() +
> release() uses some
> serious CPU cycles, and these cycles completely and utterly
> wasted due to
> Parser interface definition. Not to mention, cluttering up
> oodles of classes
> with unecessary resource management.
As long as it is threadsafe, there will be no issue. The problem
comes when there is a non-threadsafe version.
> The question is will it break anything in cocoon if they are
> never released?
Not as long as they are using the JAXPParser
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
