Announcement Announcement Module
No announcement yet.
STS Spring Security 3.0.1 config compile error Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • eggsy84
    started a topic STS Spring Security 3.0.1 config compile error

    STS Spring Security 3.0.1 config compile error

    Hi all,

    I have recently downloaded and installed the SpringSource Tool suite.

    We have configured our project to use the latest version of Spring Security version 3.0.1.

    However we are getting a slight error in our config:

    In the security file we have the following namespace defintions:

    <beans:beans xmlns=""
    	xmlns:beans="" xmlns:xsi=""
    And the offending bean is:

    <beans:bean id="filterSecurityInterceptor" class="">
    		<beans:property name="authenticationManager" ref="authenticationManager" />
    		<beans:property name="accessDecisionManager" ref="accessDecisionManager" />
    		<beans:property name="securityMetadataSource">
    				<intercept-url pattern="/admin/**" access="ROLE_ADMIN" />
    				<intercept-url pattern="/rest/**" access="ROLE_WRITE_ACCESS" />
    				<intercept-url pattern="/**"
    But we get the following error:

    Cannot locate BeanDefinitionParser for element filter-security-metadata-source.

    The web application runs OK and everything seems to work as normal but we just have that unusual compile error?

    Is this something incorrect with our setup or a small error with STS?

    Many thanks all,

    Last edited by eggsy84; Jan 18th, 2010, 05:23 AM. Reason: highlight error clearly

  • eggsy84

    Hi Christian,

    Many thanks for the reply.

    I'll wait on the new release of STS

    Leave a comment:

  • Christian Dupuis
    Hi Eggsy,

    you are hitting a bug in Spring Security 3.0.0. See the following JIRA for details:

    SEC-1357: Use reader context classloader when checking for web classes in namespace handler

    Essentially this bug prevents Spring Security from registering the required namespace parsers in an OSGi runtime. Please note that this has been fixed with Spring Security 3.0.1 but you need to update to STS 2.3.1 (not released yet) to get this fix accessible for STS.

    For now, you can just ignore the warning or switch it off from the project preferences (Spring -> Beans Support -> Ignore Missing NamespaceHandler warnings).



    Leave a comment: