activation condition WARN in v3.3

[Andrew Morgan]

I'm using an activation condition on my persistent NameID generator, like 
so:

   <bean parent="shibboleth.SAML2PersistentGenerator">
       <property name="activationCondition">
           <bean parent="shibboleth.Conditions.NOT">
               <constructor-arg>
                   <bean parent="shibboleth.Conditions.RelyingPartyId" c:_0="#{{'https://oregonstate-staff.webex.com', 'https://oregonstate-students.webex.com'}}" />
               </constructor-arg>
           </bean>
       </property>
   </bean>


This worked fine in v3.2.0.  I have upgraded one of my nodes to v3.3 for 
testing, and now I get the following warning during startup:

2017-02-01 16:09:45,236 - INFO [net.shibboleth.ext.spring.context.FilesystemGenericApplicationContext:581] - Refreshing ApplicationContext:shibboleth.NameIdentifierGenerationService: startup date [Wed Feb 01 16:09:45 PST 2017]; parent: Root WebApplicationContext
2017-02-01 16:09:45,386 - WARN [net.shibboleth.ext.spring.config.StringBooleanToPredicateConverter:51] - Unrecognized value 'https://oregonstate-staff.webex.com' converted to false; if intentional, explicitly use 'false'
2017-02-01 16:09:45,404 - WARN [net.shibboleth.ext.spring.config.StringBooleanToPredicateConverter:51] - Unrecognized value 'https://oregonstate-staff.webex.com' converted to false; if intentional, explicitly use 'false'
2017-02-01 16:09:45,472 - INFO [net.shibboleth.ext.spring.service.ReloadableSpringService:380] - Service 'shibboleth.NameIdentifierGenerationService': Completed reload and swapped in latest configuration for service 'shibboleth.NameIdentifierGenerationService'

I tried using a different constructor format:

   <bean parent="shibboleth.Conditions.RelyingPartyId">
      <constructor-arg>
         <list>
            <value>https://oregonstate-staff.webex.com</value>
            <value>https://oregonstate-students.webex.com</value>
         </list>
      </constructor-arg>
   </bean>

Same WARN though.

Is there some new way to specify this in v3.3?  The only issue in the v3.3 
release notes that I could find related to this problem is:

   https://issues.shibboleth.net/jira/browse/JSE-17


Thanks,
 	Andy