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 Fri, 15 Feb 2002 23:23:05 GMT
Carsten Ziegeler wrote:
> > David Crossley wrote:
> > 
> > Now that we are using the JaxpParser from Excalibur,
> > i expected to see no mention of the old parser in the
> > logfiles upon Cocoon startup.
> >  grep "shorthand xml-parser" core.log
> > reveals some log entries as expected from the new role.
> > However
> >  grep "shorthand parser" core.log
> > also reveals some entries from the old role, which i did
> > not expect.
> > 
> The cocoon parser is deprecated but still available. Don't forget
> all the users currently developing their own components for
> 2.0 or 2.0.1. They use/need the Cocoon parser, so I think we
> cannot remove it in the next release but only deprecate it.
> In a later release we can remove it.
> 
> Carsten

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.
--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