從其他Maven模塊導入Spring bean

我目前有我的應用程序的以下Maven模塊：規則，持久性，服務器，其中每個都包含一個applicationContext.xml文件相互導入（即。導入導入persistenceAC的rulesAC ，所有AC文件都位於{對應模塊}/src/main/resources中）。雖然我的IDE（的IntelliJ），集成測試和Maven包中的所有構建，並通過精細在嘗試啓動我的服務器我笑臉相迎：從其他Maven模塊導入Spring bean

org.apache.maven.lifecycle.LifecycleExecutionException: An exception occured while executing the Java class. null 
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) 
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) 
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) 
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) 
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) 
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) 
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) 
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) 
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) 
    at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
    at java.lang.reflect.Method.invoke(Method.java:597) 
    at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) 
    at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) 
    at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) 
    at org.codehaus.classworlds.Launcher.main(Launcher.java:375) 
Caused by: org.apache.maven.plugin.MojoExecutionException: An exception occured while executing the Java class. null 
    at org.codehaus.mojo.exec.ExecJavaMojo.execute(ExecJavaMojo.java:338) 
    at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) 
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) 
    ... 17 more 
Caused by: java.lang.reflect.InvocationTargetException 
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
    at java.lang.reflect.Method.invoke(Method.java:597) 
    at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:283) 
    at java.lang.Thread.run(Thread.java:662) 
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'abService' defined in class path resource [applicationContext.xml]: Cannot resolve reference to bean 'foo' while setting constructor argument; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'foo' is defined 
    at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:328) 
    at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:106) 
    at org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:616) 
    at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:148) 
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1003) 
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:907) 
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485) 
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) 
    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:291) 
    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222) 
    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288) 
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:190) 
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:580) 
    at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895) 
    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425) 
    at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:139) 
    at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:83) 
    at com.boku.risk.service.server.Server.main(Server.java:30) 
    ... 6 more 
Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'foo' is defined 
     at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanDefinition(DefaultListableBeanFactory.java:527) 
    at org.springframework.beans.factory.support.AbstractBeanFactory.getMergedLocalBeanDefinition(AbstractBeanFactory.java:1083) 
    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:274) 
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:190) 
    at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:322) 
    ... 23 more

「富」無法找到bean是從persistenceAC.xml 。順便我導入每個孩子的AC的是：

<import resource="classpath*:rulesAC.xml"/>

我也tryed這種進口的每一個變化（「類路徑：rulesAC.xml」，「類路徑*：/ rulesAC.xml」，「類路徑：/rulesAC.xml「）認爲這是問題，但似乎並非如此。

雖然我認爲這是某種類路徑問題，但我已經嘗試瞭解我所知道的一切，並試圖尋找解決方案而沒有多少運氣。預先感謝您的幫助，如果還有其他任何幫助，請通知。

注意*服務器模塊包含規則模塊和持久性模塊上的依賴關係。

來源

2011-09-06 Conner McNamara

您列出的所有導入變體都應該有效。事實上，如果他們不這樣做，Spring在嘗試加載文件時會得到一個IOException。缺少這種情況表明文件存在並正在加載，或者包含導入的文件未加載。查找INFO級別的日誌，顯示Spring正在加載哪些XML文件以及每個ApplicationContext中加載了哪些singleton bean。這會引導您發現配置錯誤。日誌看起來像：

Loading XML bean definitions from <description of resource> 
Pre-instantiating singletons in <type of application context> <list of singleton beans>

來源

2011-09-06 02:17:02

感謝您的建議。當我在父類上運行mvn包時，它似乎預先實例化了持久性，規則和服務器中的所有bean，但是如果我進入規則，它只會將規則bean實例化爲與applicationContext從持久性AC導入的規則bean和bean相對的bean，在檢查規則堆時，它似乎對持久性有依賴性。我錯過了什麼嗎？ –

我不清楚什麼是開始運行的春天，甚至是你的應用程序的性質。這是一個Web應用程序或獨立的應用程序？您發佈的堆棧跟蹤來自正在運行的exec：java。你的每個模塊是否都有你正在運行的主類？你究竟在做什麼，你期望會發生什麼，以及它如何不能達到你的期望？（我建議更新你的問題，因爲這可能需要一些空間。） –

從其他Maven模塊導入Spring bean

回答

相關問題