[SANTUARIO-295] XMLDSig XPathFilter2Transform bug involving intersect filter

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Java 1.4.6, Java 1.5
• Fix Version/s: Java 1.5, Java 1.4.7
• Component/s: Java
• Security Level: Public (Public issues, viewable by everyone)
• Assignee: sean.mullan
• Reporter: sean.mullan
• Created: 19/Jan/12 13:43
• Updated: 23/Jan/12 10:24
• Resolved: 19/Jan/12 18:10

Description

If the intersect filter is present, but the result of the XPath expression is an empty node-set, it ignores the filter rather than properly performing an intersection with an empty node-set, the result of which should always be an empty node-set. The problem is that the code does not distinguish between filters that are not included in the Transform and those that produce an empty node-set.

This is a fairly obscure case and should occur infrequently in practice, as it would signify that the Transform was probably created incorrectly if the intersect filter didn't select any nodes at all.

However, this used to work in a previous version of Santuario, thus it is a regression.