Klaus Bertram wrote:Yes I had the same idea and checked both, same result
Hi Joerg
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.
Some questions to help us track the problem :
- do you use a caching pipeline - if yes, does it still happen if you use a non-caching pipeline ?
Oh, the called map:part match is in different pipeline than the map:aggregation
and I checked
<map:pipeline internal-only="true">
and
<map:pipeline>
but I tryed not the match in the same pipeline
I check it in the afternoon
- can you provide us the two stack trace when you hit the breakpoint ?I will do my best
Klaus
Thanks, Sylvain
