title: getting 'Unable to locate Spring NamespaceHandler for XML schema namespace [http://www.springframework.org/schema/security]' with spring 4
body: <p>I am upgrading <code>spring</code> versions of our <code>OSGi</code> project to spring 4.2.x.</p>
  
  <p>I have removed Spring DM dependencies and add Gemini Blueprint dependencies (<code>org.eclipse.gemini.blueprint.core</code>,<code>org.eclipse.gemini.blueprint.extender</code>,<code>org.eclipse.gemini.blueprint.io</code>) and those are in ACTIVE state in Virgo RT server.<br>
  I have added <code>spring-security-config</code> dependency and it is also in ACTIVE state.</p>
  
  <p>But I am facing following issue</p>
  
  <blockquote>
    <p>org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Unable to locate Spring NamespaceHandler for XML schema namespace [<a href="http://www.springframework.org/schema/security]" rel="nofollow noreferrer">http://www.springframework.org/schema/security]</a> Offending resource: URL [bundleentry://157.fwk1212103909/META-INF/spring/applicationContext-security.xml]</p>
  </blockquote>
  
  <p>my applicationContext-security.xml file is like this</p>
  
  <pre><code>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
  &lt;beans xmlns="http://www.springframework.org/schema/beans"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xmlns:security="http://www.springframework.org/schema/security"
     xsi:schemaLocation="http://www.springframework.org/schema/beans
         http://www.springframework.org/schema/beans/spring-beans.xsd
         http://www.springframework.org/schema/security
         http://www.springframework.org/schema/security/spring-security.xsd"&gt;
  
    &lt;security:global-method-security pre-post-annotations="enabled" run-as-manager-ref="runAsManager"
  secured-annotations="enabled"&gt;
      &lt;security:expression-handler ref="expressionHandler" /&gt;
    &lt;/security:global-method-security&gt; 
  
    ... 
  
  &lt;/beans&gt;
  </code></pre>
  
  <p><em>I have used the <code>xsd</code> with versions. same result.</em><br><br>
  any idea what is causing this issue?</p>