Spring + mule ESB 프로젝트의 Junit에서 java.lang.NoSuchMethodError를 해결하는 방법

Question

ESB + Spring 프로젝트의 단위 테스트를해야하고 다음과 같은 마개를 찾을 때까지 잘 진행되고 있습니다. 내가 가지고 java.lang.NoSuchMethodError : org.springframework.core.type.classreading.CachingMetadataReaderFactory.clearCache() V 나는 시험 실행할 때 :

:

가 난 단지 다음과 같이 단위 테스트를 호출을

//annotations @TransactionConfiguration(defaultRollback = true) @RunWith(SpringJUnit4ClassRunner.class) @ContextConfiguration(locations = { "classpath:/platform-context-test.xml" }) public class AbstractExceptionUnitTest { private static final Logger LOG = Logger.getLogger(AbstractExceptionUnitTest.class); @BeforeClass public static void setUpClass() throws Exception { LOG.info("Testing " + AbstractExceptionUnitTest.class); JndiSetup.doSetup(); } /** * Method testApp. */ @Test public void test() { LOG.info("Testing!!"); } } 

스프링 컨텍스트 :

INFO 17-10 20 : 09 : 33,155 - @TestExecutionListeners가 [class com.tesing.AbstractExceptionUnitTest] : 기본값 사용시 존재하지 않습니다. INFO 17-10 20 : 09 : 33,181 - 테스트 클래스 com.tesing.AbstractExceptionUnitTest INFO 17-10 20 : 09 : 33,248 - 데이터 소스 MySQL -> myDataSourceDS가 결합되었습니다. INFO 17-10 20 : 09 : 33,356 - 클래스 경로 자원 [platform-context-test.xml]에서 XML bean 정의로드 정보 17-10 20 : 09 : 33,689 - 새로 고침 org.springframework.context.support.GenericApplicationContext @ 7af485b : 시작일 [Thu Oct 17 20:09:33 COT 2013];

java.lang.NoSuchMethodError: org.springframework.core.type.classreading.CachingMetadataReaderFactory.clearCache()V 
    at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:325) 
    at org.springframework.context.annotation.ConfigurationClassPostProcessor.postProcessBeanDefinitionRegistry(ConfigurationClassPostProcessor.java:223) 
    at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:630) 
    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:461) 
    at org.springframework.test.context.support.AbstractGenericContextLoader.loadContext(AbstractGenericContextLoader.java:103) 
    at org.springframework.test.context.support.AbstractGenericContextLoader.loadContext(AbstractGenericContextLoader.java:1) 
    at org.springframework.test.context.support.DelegatingSmartContextLoader.loadContext(DelegatingSmartContextLoader.java:228) 
    at org.springframework.test.context.TestContext.loadApplicationContext(TestContext.java:124) 
    at org.springframework.test.context.TestContext.getApplicationContext(TestContext.java:148) 
    at org.springframework.test.context.support.DependencyInjectionTestExecutionListener.injectDependencies(DependencyInjectionTestExecutionListener.java:109) 
    at org.springframework.test.context.support.DependencyInjectionTestExecutionListener.prepareTestInstance(DependencyInjectionTestExecutionListener.java:75) 
    at org.springframework.test.context.TestContextManager.prepareTestInstance(TestContextManager.java:321) 
    at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.createTest(SpringJUnit4ClassRunner.java:211) 
    at org.springframework.test.context.junit4.SpringJUnit4ClassRunner$1.runReflectiveCall(SpringJUnit4ClassRunner.java:288) 
    at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) 
    at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.methodBlock(SpringJUnit4ClassRunner.java:290) 
    at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:231) 
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) 
    at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) 
    at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) 
    at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) 
    at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) 
    at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) 
    at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) 
    at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61) 
    at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:71) 
    at org.junit.runners.ParentRunner.run(ParentRunner.java:300) 
    at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:174) 
    at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) 
    at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) 
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) 
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) 
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) 
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) 

그리고 여기에 프로젝트의 관련 종속의 부분 :

<dependency> 
     <groupId>pentaho-kettle</groupId> 
     <artifactId>kettle-core</artifactId> 
     <version>4.4.0-stable</version> 
     <scope>compile</scope> 
    </dependency> 
    <dependency> 
     <groupId>pentaho-kettle</groupId> 
     <artifactId>kettle-db</artifactId> 
     <version>4.4.0-stable</version> 
     <scope>compile</scope> 
    </dependency> 
    <dependency> 
     <groupId>pentaho-kettle</groupId> 
     <artifactId>kettle-engine</artifactId> 
     <version>4.4.0-stable</version> 
     <scope>compile</scope> 
    </dependency> 
    <dependency> 
     <groupId>directory-naming</groupId> 
     <artifactId>naming-java</artifactId> 
     <version>0.8</version> 
     <scope>test</scope> 
    </dependency> 
    <dependency> 
     <groupId>joda-time</groupId> 
     <artifactId>joda-time</artifactId> 
     <version>2.1</version> 
     <scope>compile</scope> 
    </dependency> 
    </dependencies> 
    <repositories> 
    <repository> 
     <id>central-mule.repository</id> 
     <name>Mule Plugins</name> 
     <url>https://repository.mulesoft.org/releases/</url> 
    </repository> 
    <repository> 
     <releases> 
     <enabled>true</enabled> 
     <updatePolicy>never</updatePolicy> 
     <checksumPolicy>warn</checksumPolicy> 
     </releases> 
     <id>PentahoRepo</id> 
     <name>Pentaho repository</name> 
     <url>http://repository.pentaho.org/artifactory/repo</url> 
    </repository> 
    <repository> 
    <repository> 
     <snapshots> 
     <enabled>false</enabled> 
     </snapshots> 
     <id>central</id> 
     <name>Central Repository</name> 
     <url>http://repo.maven.apache.org/maven2</url> 
    </repository> 
    </repositories> 
    <pluginRepositories> 
    <pluginRepository> 
     <snapshots> 
     <enabled>false</enabled> 
     </snapshots> 
     <id>mulesoft-release</id> 
     <name>mulesoft release repository</name> 
     <url>https://repository.mulesoft.org/releases/</url> 
    </pluginRepository> 
    <pluginRepository> 
     <releases> 
     <updatePolicy>never</updatePolicy> 
     </releases> 
     <snapshots> 
     <enabled>false</enabled> 
     </snapshots> 

시도하는 어떤 아이디어하시기 바랍니다 컨텍스트 계층 구조의 루트는

그 후

테스트는 오류를 보여줍니다 이 NoShuchMethodError 해결하시오 ??

Answer 1

TestExecutionListeners anotation을 사용해보십시오.

@TestExecutionListeners({ DependencyInjectionTestExecutionListener.class }) 
@TransactionConfiguration(defaultRollback = true) 
@RunWith(SpringJUnit4ClassRunner.class) 
@ContextConfiguration(locations = { "classpath:/platform-context-test.xml" }) 

Answer 2

가능한 모든 스프링 의존성을 3.4.0 스프링 버전으로 업그레이드하여이 문제를 해결했습니다.