[ http://issues.apache.org/jira/browse/FOR-796?page=comments#action_12364866 ]
Thorsten Scherler commented on FOR-796: --------------------------------------- HEADSUP: Before you can work with the dispatcher you *have to* patch the forrest.xconf with the patch (dispatcher-enabler.patch) attached to this issue!!! This is due to FOR-799 and the fact that people are using v2 and we should support them till we finish this issue. If you *do not* patch the core you may see something like the following: org.apache.cocoon.ProcessingException: Error during resolving of 'lm://resolve.structurer.index'. ... Caused by: org.apache.excalibur.source.SourceException: Could not resolve locationmap location. You should be able to answer "yes" to all of the following questions: 1) did you applied the attached patch? 2) are you on revision r373699 or higher (best HEAD)? 3) are you sure you did build.sh clean;./build.sh the forrest core (otherwise it will not work!) 4) did you deploy the new plugins? > Merge all view/dispatcher work into > org.apache.forrest.plugin.internal.dispatcher and > org.apache.forrest.themes.core > -------------------------------------------------------------------------------------------------------------------- > > Key: FOR-796 > URL: http://issues.apache.org/jira/browse/FOR-796 > Project: Forrest > Type: New Feature > Components: Dispatcher (aka views) > Versions: 0.8-dev > Reporter: Thorsten Scherler > Assignee: Thorsten Scherler > Priority: Blocker > Fix For: 0.8-dev > Attachments: dispatcher-enabler.patch > > This is the global issue to keep track on the merging effort -- 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
