SEC-1397: NoSuchMethodError: org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.getLocalName(Lorg/w3c/dom/Node;)Ljava/lang/String; #1640

spring-issuemaster opened this Issue Feb 1, 2010 · 8 comments


None yet
1 participant

Dennis Kieselhorst (Migrated from SEC-1397) said:

I'm unable to use Spring Security 3.0.1:

Caused by: java.lang.NoSuchMethodError: org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.getLocalName(Lorg/w3c/dom/Node;)Ljava/lang/String;
at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(
at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(
at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(
at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(
... 37 more

Dennis Kieselhorst said:

Please mark this issue as invalid. There was an old spring 2.5.6 jar on classpath.

Steppe jens said:

We have the same issue at the moment, can you explain how you solved this?

We work with spring 2.5.6 and spring security 3.0.0 RELEASE

Thank you

Dennis Kieselhorst said:

Spring 2.5.6 is not compatible with Spring Security 3. You must use Spring 3.

pinot noir said:

Just a note for people having the same problem: you must use Spring 3 RELEASE, with Spring 3 M4 you will also have the problem.

Nilesh Bharambe said:

I am getting the same error using Spring 3.0.2 and while deploying on Weblogic server as well as but when i deploy my application on weblogic server its running fine.
Is it bug??

hari said:

Hi I see the exact error Deploying t0 Oracle 11g weblogic 10.3.3 with spring 3.0, spring security 3.0 , letem know if you have a fix for this

Connor Barry said:

I see the same error using Spring Security 3.0.5.RELEASE, WebLogic 10.2, with no instances of any earlier version of Spring on the classpath. Should be reopened?

Luke Taylor said:

The method exists in Spring 3.0. If you get this exception then you have an incompatible version of Spring, either in your app or inadvertently provided by the app server.

spring-issuemaster added this to the 3.0.2 milestone Feb 5, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment