cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <cross...@indexgeo.com.au>
Subject Re: some remnants of old JaxpParser
Date Tue, 19 Feb 2002 10:24:40 GMT
Carsten Ziegeler wrote:
> > David Crossley wrote:
> > 
> >  <snip/>
> > Perhaps i did not express myself clearly. I am trying to
> > verify that the Catalog Entity Resolver is still functioning
> > properly after the move to Excalibur JaxpParser.
> > 
> > When i look at the startup logs, then there is one mention
> > of the old role "shorthand resolver" (which then uses the
> > old parser role "shorthand parser"). This entry is then
> > followed by two mentions of the new resolver role
> > "shorthand entity-resolver" (which use the new parser
> > role "shorthand xml-parser").
> > 
> > I cannot find where the first entry (using the old resolver
> > and old parser) are coming from, and so why there is
> > a mixture of old and new.
> 
> The old roles (resolver and parser) are still in the cocoon.roles
> for compatibility , so when this roles file is parsed by the component
> manager, it immediately creates a pool for the old components as
> they are poolable. So, the messages will still appear in the logs - 
> the only solution to avoid them is to remove the Poolable marker
> from the components.
> 
> Carsten

Thanks for explaining that Carsten. You would not believe
how long i have pondered over the meaning of those startup
log messages.

OK now that is a non-issue, i can say that the Entity Resolver
is still happy after the move to Excalibur JaxpParser.
--David


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message