You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Robo <gr...@post.sk> on 2007/09/06 10:52:46 UTC

Re: Re: Wicket libraries stack trace

Hello Gwyn,

So after I put wicket-velocity jar in my build path, I`m getting following errors. (I`m using nothing from it and the prove is when I remove it it deploys OK.)
---6.9.2007 11:37:21 org.apache.catalina.core.StandardContext filterStart
SEVERE: Exception starting filter HelloWorldApplication
java.lang.NoClassDefFoundError: org/apache/velocity/app/Velocity
        at org.apache.wicket.velocity.Initializer.init(Initializer.java:64)
        at org.apache.wicket.Application.callInitializers(Application.java:808)
        at org.apache.wicket.Application.initializeComponents(Application.java:638)
        at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:423)
        at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
        at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:397)
        at org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilterConfig.java:108)
        at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3693)
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:4340)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
        at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:626)
        at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:553)
        at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:488)
        at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138)
        at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
        at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
        at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
        at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
        at org.apache.catalina.core.StandardService.start(StandardService.java:516)
        at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:566)
        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.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
6.9.2007 11:37:25 org.apache.catalina.core.StandardContext filterStart
SEVERE: Exception starting filter HelloWorldApplication
java.lang.NoClassDefFoundError: org/apache/velocity/app/Velocity
        at org.apache.wicket.velocity.Initializer.init(Initializer.java:64)
        at org.apache.wicket.Application.callInitializers(Application.java:808)
        at org.apache.wicket.Application.initializeComponents(Application.java:638)
        at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:423)
        at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
        at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:397)
        at org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilterConfig.java:108)
        at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3693)
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:4340)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
        at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:626)
        at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:511)
        at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1220)
        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.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
        at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
        at org.apache.catalina.manager.ManagerServlet.check(ManagerServlet.java:1458)
        at org.apache.catalina.manager.ManagerServlet.deploy(ManagerServlet.java:820)
        at org.apache.catalina.manager.ManagerServlet.doGet(ManagerServlet.java:348)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:174)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
        at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:581)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
        at java.lang.Thread.run(Thread.java:619)
6.9.2007 11:37:25 org.apache.catalina.core.StandardContext filterStart
SEVERE: Exception starting filter HelloWorldApplication
java.lang.NoClassDefFoundError: org/apache/velocity/app/Velocity
        at org.apache.wicket.velocity.Initializer.init(Initializer.java:64)
        at org.apache.wicket.Application.callInitializers(Application.java:808)
        at org.apache.wicket.Application.initializeComponents(Application.java:638)
        at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:423)
        at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
        at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:397)
        at org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilterConfig.java:108)
        at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3693)
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:4340)
        at org.apache.catalina.manager.ManagerServlet.start(ManagerServlet.java:1237)
        at org.apache.catalina.manager.ManagerServlet.doGet(ManagerServlet.java:373)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:174)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
        at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:581)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
        at java.lang.Thread.run(Thread.java:619)
---
web.xml

<!DOCTYPE web-app
      PUBLIC \"-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN\"
      \"http://java.sun.com/dtd/web-app_2_3.dtd\">


  Wicket Examples
  
    HelloWorldApplication
    org.apache.wicket.protocol.http.WicketFilter
    
      applicationClassName
      wicket.examples.helloworld.HelloWorldApplication
    
  

  
    HelloWorldApplication
    /app/*
  

---
So please explain me why Tomcat is complaining at deployment time about velocity just including it in the build path?

Regards
Robo.

----- Originálna Správa -----
Od: Gwyn Evans  
Komu: Robo  
Poslaná: 06.09.2007 10:34 
Predmet: Re: Wicket libraries

> On Thursday, September 6, 2007, 5:57:53 AM, Robo  wrote:
> 
> > Ok, seems removing \\\"wicket-velocity-1.3.0-beta3.jar\\\" from build
> > path solved problem with velocity problem. But please explain me why
> > removing package from build path solves the problem if nowhere in my
> > Hello World code i call for any of the velocity packages. Is there
> > some duplicities in packages or what?
> 
> Well, without seeing your code or the full stacktrace, we can\'t be
> sure.  There\'s always a chance that you\'ve left a  that uses
> Velocity in the web.xml, for instance.
> 
> > As to Maven2. It seems that like you in some way force developers to Maven2. :-)
> 
> In one sense, we do. If users who have problems are able to provide
> examples of their issues as QuickStart apps, then we\'re able to
> investigate and fix a lot easier. By using Maven and sticking to the
> standard project layout, we provide a layout familiar to a significant
> number of Java developers, thus minimising obstacles to getting them
> going.
> 
> > In wicket inAction EA there is just mentioned that when using Ant
> > you need to do some work about libraries ant Maven manages it for
> > you. This is too little for serious docs. Please do look into
> > Icefaces free docs. There is steb by step mentioned what libs one
> > need to enable which feature and the libs are added as demo app more
> > feature ritch. Developer needs to understand core functionalities
> > and dependencies. Just After understandig this developer is able to
> > set up Ant project, make project, Eclipse or Netbeans based project
> > and if you want also Maven. :-) But many of the advices about libs
> > was \\\"Use Maven2\\\" like. If you use it, so use it but do not force
> > me to use it.
> 
> We don\'t force you to use it, but if you do choose to swim upstream,
> you must expect to have to put in some extra work yourself. The
> information\'s there in easily accessible form and most users seem to
> manage find & use it, even those who wish to use build systems other
> than Maven. The main issue that would occur with having a separate
> document detailing dependances is that it needs keeping in sync, which
> is why the one that I know of (and has been referenced recently) is
> one generated from the Maven build files.
> 
> Frankly, any Java developer worth the name should be at least aware of
> how to read Maven pom.xml files in order to determine things such as
> dependances, in the same way that in the past, a basic familiarity
> with Makefiles and build.xml files would have been expected.
> 
> > Explain in some part od book or docs what do I need to
> > run which part of wicket to save my time to go into jars and solve
> > dependencies troubles. Yes Maven solves you some problems with
> > dependecies and also si suitable for small pr oject but at big
> > projects it definitely fails. :-/
> 
> Does the phrase \"When in a hole, stop digging\" mean anything to you?
> While \'big\' is subjective, there are many projects that I\'d consider
> \'big\' that are quite happily using Maven - maybe the problem\'s not
> with the tool?
> 
> > So please. I know you have lot of work with wicket, and as users can
> > see you have a good aproach. But please do spend some time to at
> > least write one chapter about libraries, neede dependencies and so
> > on. If you have licensing problems just make one clear site with
> > core libs link, dep libs link and explanation what feature they are
> > enabling and so on.
> 
> The point is, this is all documented in the pom.xml, where you can be
> sure that it\'s up-to-date & correct, as else the builds would fail -
> if extracted into a document, you\'d never be 100% sure it wasn\'t
> out-of-date...
> 
> > And make some quick start page in which you
> > explainn dependecies on simple sample app :-)
> 
> $ mvn archetype:create -DarchetypeGroupId=org.apache.wicket
>       -DarchetypeArtifactId=wicket-archetype-quickstart
>       -DarchetypeVersion=1.3.0-beta3
>       -DgroupId=com.mycompany
>       -DartifactId=myproject
> $ cd myproject
> $ more pom.xml
> 
> > one Joke. Americans was looking for some pen, which could be used in
> > space without troubles, They invested 1 000 000 $ in research and
> > finally had one. Russians in the meantime used pencils. :-)
> 
> Yes, that one\'s false too -
> http://www.snopes.com/business/genius/spacepen.asp.
> 
> Lead pencils were used on all Mercury and Gemini space flights and all
> Russian space flights prior to 1968. Fisher Space Pens are more
> dependable than lead pencils and cannot create the hazard of a broken
> piece of lead floating through the gravity-less atmosphere. Both
> American and Soviet space missions initially used pencils, NASA did
> not seek out Fisher and ask them to develop a \"space pen,\" Fisher did
> not charge NASA for the cost of developing the pen, and the Fisher pen
> was eventually used by both American and Soviet astronauts.
> 
> /Gwyn
> 
> 


__________
Najoriginalnejsie technologicke hracky - http://pocitace.sme.sk/



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Wicket libraries stack trace

Posted by Gwyn Evans <gw...@gmail.com>.
On Thursday, September 6, 2007, 9:52:46 AM, Robo <gr...@post.sk> wrote:

> So after I put wicket-velocity jar in my build path, I`m getting
> following errors. (I`m using nothing from it and the prove is
> when I remove it it deploys OK.)
...
> So please explain me why Tomcat is complaining at deployment time
> about velocity just including it in the build path?

What's happening is that the Wicket Application instance has searched
the classpath to read all the wicket.properties files provided. The
one in the wicket-velocity jar says
"initializer=org.apache.wicket.velocity.Initializer", so it's trying
to run that initializer instance, but you're missing the dependances.

If using Maven, you'd have them, but if not, you can go to
MvnRepository (http://mvnrepository.com/) and search which would take
you to http://mvnrepository.com/artifact/velocity/velocity/1.4 where
it shows that you need velocity-dep-1.4.jar too.

That's a useful site to bookmark, whether using Maven or not (probably
even more if not!)

/Gwyn


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org