Sjur Moshagen wrote: > Thorsten Scherler: > >> > >>But it does NOT work if I DON'T add it manually there, even though > >>the > >>entity is now defined both in core and in project within > >>$FORREST_HOME. > > > >Hmm that is weird. I have to admit unless like David I am not the > >expert > >in the entity config, but it should work in editing > > > >vim main/webapp/resources/schema/entity/symbols-core-v10.ent > > > >and then in your sitemap like in the dispatcher plugin: > > > >vim > >whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/ > >internal.xmap > > > ><!DOCTYPE map:sitemap [ > ><!ENTITY % symbols-project > >PUBLIC "-//Apache Forrest//ENTITIES Symbols Project v1.0//EN" > >"symbols-project-v10.ent"> > >%symbols-project; > ><!ENTITY % symbols-core > >PUBLIC "-//Apache Forrest//ENTITIES Symbols Core v1.0//EN" > >"symbols-core-v10.ent"> > >%symbols-core; > >]> > > > >>It *should* work, AFAICU. > > > >it should work as described above, it is hard to comment on it > >without a > >commit. > > Thanks for the patience. For some reason I had forgot to add the > symbols-core entity def. in the output.xmap file in the pdf plugin. > > That made all the difference:)
Glad that it works. There is another configuration mechanism. See example main/webapp/WEB-INF/properties/dev/core.properties That is a demo of getting a configurable value into the cocoon.xconf system. I gather that the same will work in sitemaps, but haven't tried yet. Also see explanation in Ralph's commit message when that ability added to Cocoon (see link from FOR-1091 on 2008-08-22). I gather that the forrest developer's site config (and perhaps a plugin too) can provide properties via local properties files, or via the "forrest.jvmargs=-D..." in forrest.properties* files. I have not yet done enough testing with that. Note that the "running modes" ability (i.e. the files in the "dev|prod|etc." directories) is not present in Cocoon-2.1 (unless someone wants to backport that). The "properties system" is present. You would add your config to the top-level main/webapp/WEB-INF/properties/core.properties anyway, so no upgrade issues. -David
