[ http://issues.apache.org/jira/browse/FOR-932?page=comments#action_12436181 ] Thorsten Scherler commented on FOR-932: ---------------------------------------
I started my tomcat (5.x) in debugging mode (sh bin/catalina.sh jpda start) and set a breakpoint in the ForrestConfModule.java#getAttribute(...) and t seems that the lookup for above variable never happens (neither for project:resources). It seems that it is not directly related to the dispatcher but more to the lm. > forrest war error: Cannot get variable 'dispatcher.theme-ext' > ------------------------------------------------------------- > > Key: FOR-932 > URL: http://issues.apache.org/jira/browse/FOR-932 > Project: Forrest > Issue Type: Bug > Components: Launch servlet WAR, Dispatcher (aka views) > Affects Versions: 0.8-dev > Reporter: David Crossley > Attachments: error.log > > > A dispatcher-enabled site does work okay with 'forrest run'. However, not > with 'forrest war' deploying to a servlet container. It seems that Dispatcher > is missing the setup of properties. Yes i do have forrest.properties.xml > settings. > The Forrest error.log has this ... > ERROR (2006-09-20) 10:53.57:909 [core.modules.mapper.lm] > (/varietee/index.html) http-8080-Processor5/MountNode: Failure processing > LocationMap. > org.apache.cocoon.sitemap.PatternException: Cannot get variable > 'dispatcher.theme-ext' in expression > '{properties:resources}/structurer/url/{1}{properties:dispatcher.theme-ext}' > at > org.apache.cocoon.components.treeprocessor.variables.PreparedVariableResolver.processModule(PreparedVariableResolver.java:250) > at > org.apache.cocoon.components.treeprocessor.variables.PreparedVariableResolver.resolve(PreparedVariableResolver.java:197) > at > org.apache.forrest.locationmap.lm.LocationNode.locate(LocationNode.java:65) > at > org.apache.forrest.locationmap.lm.SelectNode.locate(SelectNode.java:110) > at > org.apache.forrest.locationmap.lm.MatchNode.locate(MatchNode.java:131) > ... > ... [snip] ... see attachment error.log -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
