forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <cross...@apache.org>
Subject Re: [jira] Commented: (FOR-680) The jspwiki parser renders nested lists invalid
Date Thu, 27 Oct 2005 02:51:54 GMT
Ross Gardler wrote:
> David Crossley wrote:
> >Gav.... wrote:
> >>David Crossley wrote:
> >>| Gav.... wrote:
> >>| > | >
> >>| > | > Anywhere else I should be looking ?
> >>| > |
> >>| > | Don't forget the sitemaps too. They build a parser
> >>| > | out of the grammar and then apply it to the text.
> >>| > | plugins/...input.wiki/input.xmap lines 55 and 56
> >>| > | and then either
> >>| > | plugins/...input.wiki/input.xmap line 93
> >>| > | or
> >>| > | webapp/sitemap.xmap line 326
> >>| > | (i am not sure which).
> >>| > |
> >>| > | Change the wiki/input.xmap at line 91 to let
> >>| > | the pipeline be external, then view
> >>| > | localhost:8888/wiki.xlex
> >>| >
> >>| > I did that but resource not found.
> >>|
> >>| Oh, i just tried it too. It seems that setting
> >>| <map:pipeline type="caching" internal-only="false">
> >>| has no effect when used in a plugin. It does work when
> >>| used in the main/webapp sitemaps.
> >
> >This new bug is a problem for you. That would have
> >enabled you to see the xml output from building the
> >dynamic Chaperon "lexer" and "parser" at step 5 below.
> >Using the Cocoon Profiler as described below might be
> >the only way that you can see the xml stream (for debugging
> >purposes) at the points where wiki.xlex and wiki.xgrm
> >are built from the wiki.grm file.
> 
> As a temporary workaround for debugging purposes you could comment out 
> the matchers in the plugin xmap and add them into the core sitemap.xmap.

But this would mean adding back the chaperon resources
to the core. We really need to separate those into a
new plugin as suggested in:
http://issues.apache.org/jira/browse/FOR-718

-David

Mime
View raw message