United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-7131084 XMLDSig XPathFilter2Transform regression involving intersect filter
JDK-7131084 : XMLDSig XPathFilter2Transform regression involving intersect filter

Details
Type:
Bug
Submit Date:
2012-01-18
Status:
Closed
Updated Date:
2012-10-23
Project Name:
JDK
Resolved Date:
2012-09-12
Component:
security-libs
OS:
generic
Sub-Component:
javax.xml.crypto
CPU:
generic
Priority:
P3
Resolution:
Fixed
Affected Versions:
7
Fixed Versions:

Related Reports
Backport:

Sub Tasks

Description
A regression has been introduced in JDK 7 in the XMLDSig XPathFilter2 Transform involving the intersect filter. 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.

                                    

Comments
EVALUATION

This was initially fixed at Apache Santuario (in release 1.5): https://issues.apache.org/jira/browse/SANTUARIO-295

Fix ported to JDK 8.
                                     
2012-01-23



Hardware and Software, Engineered to Work Together