David Crossley wrote: > Thorsten Scherler wrote: > > No. What the above means is that i configured the core > to have a project symbols file. If they over-ride that in > their project's xml catalog they can supply their own file.
See other reply. It does work, just poor configuration in 'forrest seed-basic'. > > Makes me think > > whether "cocoon://entity/symbols-project-v10.ent" would not work? > > The catalog system above should work properly. Not sure if our > entity resolver would understand the "cocoon:" protocol. > Also the xml catalogs could not then be used in other tools > such as xml editors. > > Your idea might work instead of using the resolver to locate > those entities in the declaration of the main sitemaps: > main/webapp/sitemap.xmap > whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/internal.xmap No, i tried and it does not. That gives "unknown protocol: cocoon" too. > Another solution would be to put an empty symbols-project-v10.ent file > directly > at the "main/webapp" directory. When the catalog resolver cannot find > a particular resource, then the default place to look is alongside > the file that tried to include this resource, e.g. main/webapp/sitemap.xmap > However that is not an elegant solution. > > Anyway, i will revert now and investigate this FOR-1071. I reverted at r633330. -David
