yes I found it by debugging an action where the breakpoint was stoped twice.
So I wrote a small test sidemap with an xsp side and database actions
By request the map:aggregation match, an action in map:part add a row to the databse and then the xsp read the table entrys.
The browser show the insertred row, but the database had 2 new rows
The sitemap.log shows the complete match handling twice
After that I test the match form the part direkt with a request and it works. (1 row added)
When needed I can send you my test sides.
Klaus
Joerg Heinicke wrote:
Do you mean each map:part in an aggregation? Where do you take this from (debug?)?
Joerg
Klaus Bertram wrote:
Hi all,
the treeprocessor call an map:part src twice at one request. The first generated map:part are used from the browser (both Mozilla and IE6.0) The sitemap log file show both generation processes
excuse but at the source i don't find the bug :(
Klaus
