Announcement Announcement Module
Collapse
No announcement yet.
Unexpected failure during bean definition parsing in STS 3.3.0 Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Unexpected failure during bean definition parsing in STS 3.3.0

    With STS 3.3.0, I recreive the following error in Psi-Probe projects spring-probe-security.xml files FilterSecurityInterceptor bean validation:

    Unexpected failure during bean definition parsing: org.springframework.beans.factory.support.BeanDefi nitionBuilder.addConstructorArg(Ljava/lang/ObjectLorg/springframework/beans/factory/support/BeanDefinitionBuilder; spring-probe-security.xml /web/src/main/webapp/WEB-INF line 83 Spring Beans Problem


    I cannot see any error there. This is Spring 2.5.6.SEC01 and Spring Security Core 2.0.7 based:

    Code:
        
    <bean id="fsi" class="org.springframework.security.intercept.web.FilterSecurityInterceptor">
            <property name="authenticationManager" ref="authenticationManager"/>
            <property name="accessDecisionManager" ref="httpRequestAccessDecisionManager"/>
            <property name="objectDefinitionSource">
                <sec:filter-invocation-definition-source>
                    <sec:intercept-url pattern="/adm/**"  access="ROLE_MANAGER,ROLE_MANAGER-GUI"/>
                    <sec:intercept-url pattern="/sql/**,/adm/restartvm.ajax" access="ROLE_POWERUSERPLUS,ROLE_MANAGER,ROLE_MANAGER-GUI"/>
                    <sec:intercept-url pattern="/app/**"  access="ROLE_POWERUSER,ROLE_POWERUSERPLUS,ROLE_MANAGER,ROLE_MANAGER-GUI"/>
                    <sec:intercept-url pattern="/**"      access="ROLE_PROBEUSER,ROLE_POWERUSER,ROLE_POWERUSERPLUS,ROLE_MANAGER,ROLE_MANAGER-GUI"/>
                </sec:filter-invocation-definition-source>
            </property>
        </bean>
    If I remove the <sec:filter-invocation-definition-source> element, the error disappears.

    Is this a bug in STS 3.3.0 spring bean validator?

  • #2
    Hey!

    I think this is related or maybe even exactly the same issue as this one:
    http://forum.springsource.org/showth...pring-Security

    Hope this explains the reasons, even though it is kind of unsatisfying situation... :-(
    -Martin

    Comment

    Working...
    X