On Mon, 2008-09-01 at 14:05 +0300, Sjur Moshagen wrote: > Den 22. aug. 2008 kl. 11.53 skrev Thorsten Scherler: > > > On Fri, 2008-08-22 at 11:44 +0300, Sjur Moshagen wrote: > >> Den 22. aug. 2008 kl. 11.29 skrev Sjur Moshagen: > >> > >>> But when I start up Forrest again, I get the following error: > >>> > >>> CAUSE: > >>> The entity "pdf-config-file" was referenced, but not declared. > >> > >> Forget about that, I didn't notice that Forrest had already copied in > >> an entity file in my $PROJECT_HOME folder, which of course did not > >> contain the entity declaration :/ > >> > > > > That is why I wrote in the other mail that best is to implement the > > default in the core. > > I did that now, but... > > >> Now it is working as a charm:) > > That was a little exaggerated. > > It does work as a charm IFF I add it manually in the $PROJECT_HOME/src/ > documentation/resources/schema/symbols-project-v10.ent > > 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. > > A possible workaround is to add it to the symbols-project-v10.ent file > in the seeded site - that way it will always be defined. It is still > somehow broken since it will break existing projects/sites until they > manually add the entity def. to their own symbols-project-v10.ent file. > That is not a viable solution in my eyes. salu2 > Suggestions? Ideas about the cause? > > Best regards, > Sjur > -- Thorsten Scherler thorsten.at.apache.org Open Source Java consulting, training and solutions
