关于Maven 使用Spring+Hibernate+JPA的问题

 最近将一个SSHJ项目，导入到Maven工程，以便以后更快捷的开发和移植，但却出现一个百思不得其解的异常：

NetBeans: Executing 'mvn.bat -Dnetbeans.execution=true clean jetty:run' NetBeans: JAVA_HOME=C:/Program Files/Java/jdk1.6.0_18 Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for cn.vicky:sshj:war:1.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 278, column 21 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] ------------------------------------------------------------------------ Building Struts1.3.8+Spring2.5.6+Hibernate3.4+Jpa1.0 1.0-SNAPSHOT ------------------------------------------------------------------------ --- maven-clean-plugin:2.4.1:clean (default-clean) @ sshj --- Deleting F:/workspace/netbeans03/sshj/target >>> jetty-maven-plugin:7.1.5.v20100705:run (default-cli) @ sshj >>> --- maven-resources-plugin:2.4.3:resources (default-resources) @ sshj --- [WARNING] File encoding has not been set, using platform encoding GBK, i.e. build is platform dependent! [WARNING] Using platform encoding (GBK actually) to copy filtered resources, i.e. build is platform dependent! Copying 2 resources --- maven-compiler-plugin:2.3.2:compile (default-compile) @ sshj --- Compiling 4 source files to F:/workspace/netbeans03/sshj/target/classes --- maven-resources-plugin:2.4.3:testResources (default-testResources) @ sshj --- [WARNING] Using platform encoding (GBK actually) to copy filtered resources, i.e. build is platform dependent! skip non existing resourceDirectory F:/workspace/netbeans03/sshj/src/test/resources --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ sshj --- Compiling 2 source files to F:/workspace/netbeans03/sshj/target/test-classes <<< jetty-maven-plugin:7.1.5.v20100705:run (default-cli) @ sshj <<< --- jetty-maven-plugin:7.1.5.v20100705:run (default-cli) @ sshj --- Configuring Jetty for project: Struts1.3.8+Spring2.5.6+Hibernate3.4+Jpa1.0 webAppSourceDirectory F:/workspace/netbeans03/sshj/src/main/webapp does not exist. Defaulting to F:/workspace/netbeans03/sshj/src/main/webapp Reload Mechanic: automatic Classes = F:/workspace/netbeans03/sshj/target/classes Context path = / Tmp directory = F:/workspace/netbeans03/sshj/target/tmp Web defaults = org/eclipse/jetty/webapp/webdefault.xml Web overrides = none web.xml file = file:/F:/workspace/netbeans03/sshj/src/main/webapp/WEB-INF/web.xml Webapp directory = F:/workspace/netbeans03/sshj/src/main/webapp Starting jetty 7.1.5.v20100705 ... 2011-05-03 00:44:42.046:INFO::jetty-7.1.5.v20100705 2011-05-03 00:44:43.718:INFO::No Transaction manager found - if your webapp requires one, please configure one. 2011-05-03 00:44:44.203:WARN::Skipping PostConstruct annotation on org.springframework.ejb.interceptor.SpringBeanAutowiringInterceptor.autowireBean: has parameters 2011-05-03 00:44:44.203:WARN::Skipping PreDestroy annotation on org.springframework.ejb.interceptor.SpringBeanAutowiringInterceptor.releaseBean: has parameters 2011-05-03 00:44:45.015:WARN::Skipping PostConstruct annotation on org.springframework.ejb.interceptor.SpringBeanAutowiringInterceptor.autowireBean: has parameters 2011-05-03 00:44:45.015:WARN::Skipping PreDestroy annotation on org.springframework.ejb.interceptor.SpringBeanAutowiringInterceptor.releaseBean: has parameters Lcn/vicky/sshj/UserService; 2011-05-03 00:44:51.187:WARN::EXCEPTION java.lang.IllegalStateException: No resource at cn.vicky.sshj.DAO/userService at org.eclipse.jetty.annotations.ResourceAnnotationHandler.handleField(ResourceAnnotationHandler.java:166) at org.eclipse.jetty.annotations.AnnotationParser$MyClassVisitor$3$1.visitEnd(AnnotationParser.java:375) at org.objectweb.asm.ClassReader.a(Unknown Source) at org.objectweb.asm.ClassReader.accept(Unknown Source) at org.objectweb.asm.ClassReader.accept(Unknown Source) at org.eclipse.jetty.annotations.AnnotationParser.scanClass(AnnotationParser.java:595) at org.eclipse.jetty.annotations.AnnotationParser.parse(AnnotationParser.java:485) at org.eclipse.jetty.annotations.AnnotationParser.parse(AnnotationParser.java:480) at org.eclipse.jetty.annotations.AnnotationParser.parse(AnnotationParser.java:480) at org.eclipse.jetty.annotations.AnnotationParser.parse(AnnotationParser.java:480) at org.mortbay.jetty.plugin.MavenAnnotationConfiguration.parseWebInfClasses(MavenAnnotationConfiguration.java:31) at org.eclipse.jetty.annotations.AnnotationConfiguration.configure(AnnotationConfiguration.java:70) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:991) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:588) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:380) at org.mortbay.jetty.plugin.JettyWebAppContext.doStart(JettyWebAppContext.java:114) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:165) at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:162) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:165) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:92) at org.eclipse.jetty.server.Server.doStart(Server.java:242) at org.mortbay.jetty.plugin.JettyServer.doStart(JettyServer.java:67) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55) at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:437) at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:377) at org.mortbay.jetty.plugin.JettyRunMojo.execute(JettyRunMojo.java:577) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:195) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:451) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:188) at org.apache.maven.cli.MavenCli.main(MavenCli.java:134) 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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) 2011-05-03 00:44:51.390:INFO:/:Initializing Spring root WebApplicationContext null null log4j:WARN No appenders could be found for logger (org.springframework.web.context.ContextLoader). log4j:WARN Please initialize the log4j system properly. 2011-05-03 00:44:53.390:INFO::Started SelectChannelConnector@0.0.0.0:8080 Started Jetty Server

这个错误很奇怪，因为Maven工程，使用Jetty Plugin或者Netbean自带Tomcat和GlassFish都无法运行，且jetty出现如下警告：

2011-05-03 00:44:44.203:WARN::Skipping PostConstruct annotation on org.springframework.ejb.interceptor.SpringBeanAutowiringInterceptor.autowireBean: has parameters
2011-05-03 00:44:44.203:WARN::Skipping PreDestroy annotation on org.springframework.ejb.interceptor.SpringBeanAutowiringInterceptor.releaseBean: has parameters
2011-05-03 00:44:45.015:WARN::Skipping PostConstruct annotation on org.springframework.ejb.interceptor.SpringBeanAutowiringInterceptor.autowireBean: has parameters
2011-05-03 00:44:45.015:WARN::Skipping PreDestroy annotation on org.springframework.ejb.interceptor.SpringBeanAutowiringInterceptor.releaseBean: has parameters

 

但是Maven打包的 工程名.war单独放入独立的Timcat下，执行却无任何异常，程序执行良好！让我一头雾水，甚至一度怀疑是Maven无法读取相对路径的persistence.xml或者无法读取Spring的xml配置文件，伤透脑筋，于是，采用junit4单独测试，但结果却否认了以上的猜想。但是为什么3种不同的的服务器都无法运行呢？为什么要跳过Spring的注解配置呢？ 

<aop:aspectj-autoproxy/>

<context:component-scan base-package="cn.vicky"/>

Spring自动扫描机制在Maven项目中究竟出了什么错？？？

 

 

 

终于在网上找到一篇与我出现相同问题的文章：

Answered my own question. Here's the solution for anyone else who might run into this. This has to do with Jetty's Annotation processor and the 2.5 servlet spec. You need to tell Jetty not to scan the application and process annotations by adding the metadata-complete attribute to the web-app element of your web.xml, as in: <web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" metadata-complete="true" version="2.5"> Without this attribute or if it's set to false, Jetty will attempt to process annotations and it will cause a lot of noise in your logs (unless of course you need it). Note that this does not apply or occur in servlet spec 2.4. More info at http://docs.codehaus.org/display/JETTY/Annotations -- View this message in context: http://old.nabble.com/java.lang.IllegalStateException%3A-No-resource-at-cxf-tp26852074p26855937.html Sent from the cxf-user mailing list archive at Nabble.com.

 

问题终于解决了！

metadata-complete="true" 编译元数据。