Saxon

This seems similar to problems we've seen before. The apply-templates select expression is a FilterExpression, and the streaming adjunct for a FilterExpression is an instance of TransmissionAdjunct. The ApplyTemplatesAdjunct therefore expects the ItemFeed for the expression to be a TransmissionFlow, but this is not the case here because the selected nodes have been grounded by calling copy-of.

In the case of a LetExpression we solved this by having two different Adjunct classes depending on whether the nodes were grounded or not. But I've always felt that was a rather ad-hoc solution and the problem was more general.

In the case of ForEachAdjunct, IterateAdjunct, and ForEachGroupAdjunct, the getWatchMaker() method does this:

    // If the select expression is grounded (but consuming), return null; so we end up with a Feed rather than a Watch.

    if (select.getPosture() == Posture.GROUNDED) {

        return null;

    }

but this is missing from ApplyTemplatesAdjunct. I'll give it a try.

The above change turned out to be necessary but not sufficient.

The code for handling apply-templates with a grounded (but consuming) selection isn't currently handling xsl:with-param, so this needed to be fixed as well.