On 11/2/08, Florent André <[EMAIL PROTECTED]> wrote:
> Hello Solprovider,
> First : I would like to create a wiki page on this debugging discussion so
> : Can you allow me to copy paste your answer in the
> http://wiki.apache.org/lenya/DebuggingTips page for introduce the article ?
I am not certain that posts to mailing list become public domain, but...
1. Before I became a Committer, I posted that any of the Lenya-related
documentation from solprovider.com could be copied to the official
website. (A few articles were copied -- sometimes causing problems as
patches were added on my website and not the official one.)
2. As a Lenya Committer, all my personal contributions are for the
project's good.
This material is similar to information already on my website. Any
new text will eventually be posted there. You have my blessing to add
my text to the wiki.
> On Sun, 12 Oct 2008 13:27:19 -0400, [EMAIL PROTECTED] wrote:
> > With Lenya/Cocoon XMAP, debugging a complex process with multiple
> > pipelines in multiple XMAPs can be a challenge.
> >
> > When first creating an XMAP, I serialize after each generator,
> > aggregator, and transformer and save the XML from the browser to a
> > file.
>
> Second : My problem is that I don't see how to see the result XML in the
> browser (due to the construction of the site). Do you use a tips like that :
>
> On top of the publication-sitemap.xmap:
> <map:match pattern="**">
> <map:generate src="../../content/util/empty.xml"/>
> <map:mount uri-prefix="" src="{fallback:TheMapToTest.xmap}"
> check-reload="true" reload-method="synchron"/>
> <map:serialize type="html"/>
> </map:match>
Most of my work is on Lenya 1.3 with a different Module system.
publication-sitemap.xmap is no longer used. I rarely test within the
main Modules, preferring a "test" Module for testing snippets of XMAP
code -- sometimes using the empty Generator, sometimes using other
Generators and Aggregators.
> ==> I don't test that for now, I have this idea after read this mail :
> http://markmail.org/message/ljpvtd73fh6npmj2
>
> third :thank you for this good explanation
You are welcome.
> > Knowing the results of each process greatly helps with writing
> > the next stage. I often discover namespaces in element names that
> > need to be either dropped in the current process or handled by the
> > next process. The saved output provides reference for later
> > development.
> >
> > After an XMAP is completed, debugging is more difficult. The final
> > results are often combined from several XMAPs. Logging intermediate
> > results to a file is a very good solution.
> >
> > One difficult-to-notice mistake between processes can waste much time.
> > I often create a "test" XMAP to isolate portions of the problematic
> > XMAP -- copying pieces XMAPs, tweaking URLs, and controlling the input
> > by generating from XML files rather than depending on the full
> > process. Some tests work perfectly indicating the problem was earlier
> > in the pipeline -- difficult to determine without isolating each
> > process.
solprovider
