Re: [ANN] 1.2.9 of Keel build system/Maven plugin - bug fix for .war generating
Michael Nash <[email protected]>
| Newsgroups | gmane.comp.java.keel.devel |
|---|---|
| Organization | JGlobal Limited |
| Message-ID | <[email protected]> |
Raoul: This looks like the war file is not loading the uberjar, which was a bug I saw happen at one point when the manifest was being build incorrectly. It was actually an error in the utility class we use to build the uberjar. If you look in the tomcat log for a message about "not loaded" or something similar, you may see it saying that it's not in fact loading the uberjar file. With the latest plugin a "maven clean; maven war" *should* sort this out, as Morten found. If not, then I'll need to dig deeper. Mike On Thu, 2005-03-03 at 11:26, Raoul Pierre wrote: > Morten, > > In the Tomcat log file, there is: > > 2005-03-03 17:23:37 StandardWrapperValve[action]: "Servlet.service()" > pour la servlet action a généré une exception > java.lang.NoClassDefFoundError: org/keel/servers/KeelAbstractServer > at java.lang.ClassLoader.defineClass0(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:537) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123) > at > org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1634) > at > org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:860) > at > org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1307) > at > org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1189) > at > org.keel.clients.KeelStarter.CreateAndStartKeelDirectServerThread(KeelStarter.java:188) > at > org.keel.clients.KeelStarter.createKeelDirectServer(KeelStarter.java:101) > at org.keel.clients.KeelStarter.execute(KeelStarter.java:221) > at > org.keel.clients.direct.KeelClientDirect.execute(KeelClientDirect.java:70) > at > org.keel.clients.DefaultClientConnector.execute(DefaultClientConnector.java:49) > at > org.keel.clients.webapp.AbstractWebappClientConnector.execute(AbstractWebappClientConnector.java:73) > at > org.keel.clients.struts.StrutsClientConnector.execute(StrutsClientConnector.java:105) > at org.keel.clients.struts.ModelAction.execute(ModelAction.java:70) > at > org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:421) > at > org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:226) > at > org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164) > at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) > at > org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) > at > org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705) > at > org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577) > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) > at java.lang.Thread.run(Thread.java:534) > > > Pierre > > > Morten Norby Larsen a écrit : > > > I just want to say that I had a similar problem with 1.2.7, but it > > went away after I re-built with 1.2.9. > > > > Whether it's due to the re-build or the new plugin is another question. > > > > Raoul, there is probably a nested Exception further down the page > > which says exactly which class is causing the problem. That could be > > useful info. > > > > Cheers, > > > > Morten > > > > > > http://keelframework.org/documentation.shtml > Keelgroup mailing list > [email protected] > http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com http://keelframework.org/documentation.shtml Keelgroup mailing list [email protected] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com