Re: some remnants of old JaxpParser

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

RE: some remnants of old JaxpParser

David Crossley wrote: OK now that is a non-issue, i can say that the Entity Resolver is still happy after the move to Excalibur JaxpParser. Great to hear this! Thanks David. Carsten - To unsubscribe, e-mail: [EMAIL

some remnants of old JaxpParser

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

RE: some remnants of old JaxpParser

David Crossley wrote: -Original Message- From: David Crossley [mailto:[EMAIL PROTECTED]] Sent: Friday, February 15, 2002 10:23 AM To: [EMAIL PROTECTED] Subject: some remnants of old JaxpParser Now that we are using the JaxpParser from Excalibur, i expected to see no mention

Re: some remnants of old JaxpParser

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.