forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thorsten Scherler (JIRA)" <>
Subject [jira] Commented: (FOR-932) forrest war error: Cannot get variable 'dispatcher.theme-ext'
Date Wed, 20 Sep 2006 09:08:25 GMT
    [ ] 
Thorsten Scherler commented on FOR-932:

I started my tomcat (5.x) in debugging mode (sh bin/ jpda start) and set a breakpoint
in the 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:
>             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 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(
>         at org.apache.cocoon.components.treeprocessor.variables.PreparedVariableResolver.resolve(
>         at org.apache.forrest.locationmap.lm.LocationNode.locate(
>         at org.apache.forrest.locationmap.lm.SelectNode.locate(
>         at org.apache.forrest.locationmap.lm.MatchNode.locate(
> ...
> ... [snip] ... see attachment error.log

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message