Ross Gardler wrote:
Ferdinand Soethe wrote:
In trying to track down the processing of html-files (to fix the
problems with attributes disappearing and other unwanted ones
reappearing) I have gone through my own documentation
And found that it is broken as soon as we move from sitemap.xmap to
forrest.xmap.
Open the file 'forrest.xmap' and continue the search for a matching
pattern.
Could somebody pls check and correct the following analysis of what
currently
happens in forrest.xmap?
1. We go through forrest.xmap looking for a match for **.xml
2. First match is
<map:match type="wildcard" pattern="**.xml">
<map:select type="exists">
<map:when test="{project:temp-dir}/input.xmap">
<map:mount uri-prefix=""
src="{project:temp-dir}/input.xmap"
check-reload="yes"
pass-through="true"/>
</map:when> </map:select>
This will load and process input.xmap normally in build\tmp
and process it if it exists.
I guess this is to allow the input-plugins to intercept processing
by defining their own matchers in there?
Yes, the 'pass-through="true"' attribute indicates that if no match is
found within the mounted sitemap then we should continue checking the
mounting sitemap from this point.
In other words, we will only continue processing in this sitemap if
there is a map:generate that is processed in input.xmap.
That last sentence should be:
In other words, we will only continue processing in this sitemap if
there is *not* a map:generate that is processed in input.xmap.
Sorry,
Ross
