Bernhard Huber wrote: > SAXESS - Hussayn Dabbous wrote: > > I wonder, why the Catalog.properties must reside > > in the classes directory. For me it would be > > more natural to put it either into WEB-INF, or > > WEB-INF/conf instead. > > > com.sun.resolver.CatalogManager reads this property file > from the classpath, so its not any Cocoon component > responsible for that behaviour,
That is correct the Entity Resolver code expects it to be there. Actually, we have not being using the com.sun.resolver for a while now. Norm now has the code and documentation at Apache XML Commons http://xml.apache.org/commons/ Cocoon and Forrest use the latest resolver.jar pre-release. Evidently, there is a change in this version that allows the entity resolver to ignore missing CatalogManager.properties The next steps for Cocoon, are to take advantage of the upgraded resolver and refine our implementation of it. If you could help, please see the new "resolver-article.html" via the draft XML Commons website: http://marc.theaimsgroup.com/?l=xml-commons-dev&m=104037450832414 --David > for a detailed explanantin, see userdocs/concepts entity catalogs > (catalog.html) > > regards bernhard --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
