[JIRA] Updated: (SC-175) NOT/AND/OR functors don't appear to support RuleReference children

[Chad La Joie (JIRA)]

     [ https://issues.shibboleth.net/jira/browse/SC-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chad La Joie updated SC-175:
----------------------------

    Fix Version/s: 1.3.6

> NOT/AND/OR functors don't appear to support RuleReference children
> ------------------------------------------------------------------
>
>                 Key: SC-175
>                 URL: https://issues.shibboleth.net/jira/browse/SC-175
>             Project: Shibboleth Common - Java
>          Issue Type: Bug
>          Components: Attribute Authority
>    Affects Versions: 1.3.5
>            Reporter: Scott Cantor
>            Assignee: Chad La Joie
>            Priority: Minor
>             Fix For: 1.3.6
>
>
> The schema for the AND/OR/NOT functors in the filter engine indicates that RuleReference elements can be used as children, but the bean parsers don't back that up. In particular, it's schema legal in the NOT case to include a single RuleReference child, but that crashes in the config parser because it assumes there's a Rule child:
> Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
> 	at java.util.ArrayList.RangeCheck(ArrayList.java:547)
> 	at java.util.ArrayList.get(ArrayList.java:322)
> 	at edu.internet2.middleware.shibboleth.common.config.attribute.filtering.match.basic.NotMatchFunctorBeanDefinitionParser.doParse(NotMatchFunctorBeanDefinitionParser.java:53)
> 	at org.springframework.beans.factory.xml.AbstractSingleBeanDefinitionParser.parseInternal(AbstractSingleBeanDefinitionParser.java:84)
> 	at org.springframework.beans.factory.xml.AbstractBeanDefinitionParser.parse(AbstractBeanDefinitionParser.java:56)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira