java.lang.IllegalArgumentException: Failed to parse a valid name/value pair from /xx=

Spring JIRA | Peter Thomas | 1 decade ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    SEC-320: FilterChainProxy not supporting URL paths mapped to nothing from RC2 onwards

    GitHub | 1 decade ago | spring-issuemaster
    java.lang.IllegalArgumentException: Failed to parse a valid name/value pair from /xx=
  2. 0

    I used to have my filterChainProxy as follows <bean id="filterChainProxy" class="org.acegisecurity.util.FilterChainProxy"> <property name="filterInvocationDefinitionSource"> <value> PATTERN_TYPE_APACHE_ANT /resources/*= /calendar/**= /index.jsp= /login.htm*= ogout.htm= /**=httpSessionFilter,authenticationFilter,rememberMeFilter,anonFilter,exceptionTranslationFilter,authorizationFilter </value> </property> </bean> My thinking was that this might give better performance so that the filter chain is not fired at all for images and css files and even the login / logout pages - rather than setting a ROLE_ANONYMOUS mapping in the FilterSecurityInterceptor. So I reduced the number of mapping entries in FilterSecurityInterceptor. This was working fine ever since I started using Acegi. But since Acegi RC2, a mapping of URL=[blank] in FilterChainProxy is not possible anymore. I get the following error: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'filterChainProxy' defined in ServletContext resource [/WEB-INF/import-acegi.xml]: Error setting property values; nested exception is PropertyAccessExceptionsException (1 errors) Caused by: PropertyAccessExceptionsException (1 errors) org.springframework.beans.TypeMismatchException: Failed to convert property value of type [java.lang.String] to required type [org.acegisecurity.intercept.web.FilterInvocationDefinitionSource] for property 'filterInvocationDefinitionSource'; nested exception is java.lang.IllegalArgumentException: Failed to parse a valid name/value pair from /xx= Caused by: java.lang.IllegalArgumentException: Failed to parse a valid name/value pair from /xx= at org.acegisecurity.intercept.web.FilterInvocationDefinitionSourceEditor.setAsText(FilterInvocationDefinitionSourceEditor.java:136) at org.springframework.beans.PropertyTypeConverter.convertValue(PropertyTypeConverter.java:250) at org.springframework.beans.PropertyTypeConverter.convertIfNecessary(PropertyTypeConverter.java:174) at org.springframework.beans.PropertyTypeConverter.convertIfNecessary(PropertyTypeConverter.java:108) at org.springframework.beans.BeanWrapperImpl.setPropertyValue(BeanWrapperImpl.java:723) at org.springframework.beans.BeanWrapperImpl.setPropertyValue(BeanWrapperImpl.java:575) at org.springframework.beans.AbstractPropertyAccessor.setPropertyValue(AbstractPropertyAccessor.java:49) at org.springframework.beans.AbstractPropertyAccessor.setPropertyValues(AbstractPropertyAccessor.java:68) at org.springframework.beans.AbstractPropertyAccessor.setPropertyValues(AbstractPropertyAccessor.java:57) Please advise. Also do you think that it is okay to avoid the filter chain as far as possible.

    Spring JIRA | 1 decade ago | Peter Thomas
    java.lang.IllegalArgumentException: Failed to parse a valid name/value pair from /xx=
  3. 0

    I used to have my filterChainProxy as follows <bean id="filterChainProxy" class="org.acegisecurity.util.FilterChainProxy"> <property name="filterInvocationDefinitionSource"> <value> PATTERN_TYPE_APACHE_ANT /resources/*= /calendar/**= /index.jsp= /login.htm*= ogout.htm= /**=httpSessionFilter,authenticationFilter,rememberMeFilter,anonFilter,exceptionTranslationFilter,authorizationFilter </value> </property> </bean> My thinking was that this might give better performance so that the filter chain is not fired at all for images and css files and even the login / logout pages - rather than setting a ROLE_ANONYMOUS mapping in the FilterSecurityInterceptor. So I reduced the number of mapping entries in FilterSecurityInterceptor. This was working fine ever since I started using Acegi. But since Acegi RC2, a mapping of URL=[blank] in FilterChainProxy is not possible anymore. I get the following error: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'filterChainProxy' defined in ServletContext resource [/WEB-INF/import-acegi.xml]: Error setting property values; nested exception is PropertyAccessExceptionsException (1 errors) Caused by: PropertyAccessExceptionsException (1 errors) org.springframework.beans.TypeMismatchException: Failed to convert property value of type [java.lang.String] to required type [org.acegisecurity.intercept.web.FilterInvocationDefinitionSource] for property 'filterInvocationDefinitionSource'; nested exception is java.lang.IllegalArgumentException: Failed to parse a valid name/value pair from /xx= Caused by: java.lang.IllegalArgumentException: Failed to parse a valid name/value pair from /xx= at org.acegisecurity.intercept.web.FilterInvocationDefinitionSourceEditor.setAsText(FilterInvocationDefinitionSourceEditor.java:136) at org.springframework.beans.PropertyTypeConverter.convertValue(PropertyTypeConverter.java:250) at org.springframework.beans.PropertyTypeConverter.convertIfNecessary(PropertyTypeConverter.java:174) at org.springframework.beans.PropertyTypeConverter.convertIfNecessary(PropertyTypeConverter.java:108) at org.springframework.beans.BeanWrapperImpl.setPropertyValue(BeanWrapperImpl.java:723) at org.springframework.beans.BeanWrapperImpl.setPropertyValue(BeanWrapperImpl.java:575) at org.springframework.beans.AbstractPropertyAccessor.setPropertyValue(AbstractPropertyAccessor.java:49) at org.springframework.beans.AbstractPropertyAccessor.setPropertyValues(AbstractPropertyAccessor.java:68) at org.springframework.beans.AbstractPropertyAccessor.setPropertyValues(AbstractPropertyAccessor.java:57) Please advise. Also do you think that it is okay to avoid the filter chain as far as possible.

    Spring JIRA | 1 decade ago | Peter Thomas
    java.lang.IllegalArgumentException: Failed to parse a valid name/value pair from /xx=
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.IllegalArgumentException

      Failed to parse a valid name/value pair from /xx=

      at org.acegisecurity.intercept.web.FilterInvocationDefinitionSourceEditor.setAsText()
    2. Acegi Security Core
      FilterInvocationDefinitionSourceEditor.setAsText
      1. org.acegisecurity.intercept.web.FilterInvocationDefinitionSourceEditor.setAsText(FilterInvocationDefinitionSourceEditor.java:136)
      1 frame
    3. Spring Beans
      AbstractPropertyAccessor.setPropertyValues
      1. org.springframework.beans.PropertyTypeConverter.convertValue(PropertyTypeConverter.java:250)
      2. org.springframework.beans.PropertyTypeConverter.convertIfNecessary(PropertyTypeConverter.java:174)
      3. org.springframework.beans.PropertyTypeConverter.convertIfNecessary(PropertyTypeConverter.java:108)
      4. org.springframework.beans.BeanWrapperImpl.setPropertyValue(BeanWrapperImpl.java:723)
      5. org.springframework.beans.BeanWrapperImpl.setPropertyValue(BeanWrapperImpl.java:575)
      6. org.springframework.beans.AbstractPropertyAccessor.setPropertyValue(AbstractPropertyAccessor.java:49)
      7. org.springframework.beans.AbstractPropertyAccessor.setPropertyValues(AbstractPropertyAccessor.java:68)
      8. org.springframework.beans.AbstractPropertyAccessor.setPropertyValues(AbstractPropertyAccessor.java:57)
      8 frames