You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@santuario.apache.org by "Colm O hEigeartaigh (Closed) (JIRA)" <ji...@apache.org> on 2012/01/23 11:26:41 UTC
[jira] [Closed] (SANTUARIO-295) XMLDSig XPathFilter2Transform bug
involving intersect filter
[ https://issues.apache.org/jira/browse/SANTUARIO-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh closed SANTUARIO-295.
-----------------------------------------
> XMLDSig XPathFilter2Transform bug involving intersect filter
> ------------------------------------------------------------
>
> Key: SANTUARIO-295
> URL: https://issues.apache.org/jira/browse/SANTUARIO-295
> Project: Santuario
> Issue Type: Bug
> Components: Java
> Affects Versions: Java 1.4.6, Java 1.5
> Reporter: sean.mullan
> Assignee: sean.mullan
> Fix For: Java 1.5, Java 1.4.7
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira