Yes, there do seem to be classloading problems with Tomcat 5.5 that prevent it from finding the application's classes, but I haven't found a solution for it.
No, I haven't tried Tomcat 6. Has anyone tried running the Wicket 1.3 QuickStart program in Tomcat 6? -----Original Message----- From: Johan Compagner [mailto:[EMAIL PROTECTED] Sent: Friday, June 06, 2008 1:48 PM To: users@wicket.apache.org Subject: Re: Tomcat 5.5.9 isn't running Quickstart And if you use toimcat 6? It could be classloading problems one (commons) cant find the stuff in the web folder On 6/6/08, Frank Silbermann <[EMAIL PROTECTED]> wrote: > Well, aside from the logging-oriented jars that maven packs into the > QuickStart's lib folder, the only logging jar I can see in Tomcat is > in Tomcat's bin folder, named > > commons-logging-api.jar > > dated 3/26/2005. > > Do I need to replace that with a more recent version? Would you > recommend moving to the current version of Tomcat to avoid side-effects? > > > -----Original Message----- > From: Igor Vaynberg [mailto:[EMAIL PROTECTED] > Sent: Friday, June 06, 2008 11:07 AM > To: users@wicket.apache.org > Subject: Re: Tomcat 5.5.9 isn't running Quickstart > > well, there you go, something funky with your logger jars > > -igor > > On Fri, Jun 6, 2008 at 9:03 AM, Frank Silbermann > <[EMAIL PROTECTED]> wrote: >> Ah, yes, I thought I had checked those, but I must have missed the >> right log. The error messages are: >> >> The catalina.log file contains: >> >> INFO: Stopping service Catalina >> Jun 6, 2008 10:58:23 AM org.apache.catalina.loader.WebappClassLoader >> findResourceInternal >> INFO: Illegal access: this web application instance has been stopped >> already. Could not load commons-logging.properties. The eventual >> following stack trace is caused by an error thrown for debugging >> purposes as well as to attempt to terminate the thread which caused >> the illegal access, and has no functional impact. >> Jun 6, 2008 10:58:23 AM org.apache.catalina.loader.WebappClassLoader >> findResourceInternal >> INFO: Illegal access: this web application instance has been stopped >> already. Could not load >> META-INF/services/org.apache.commons.logging.LogFactory. The >> eventual > >> following stack trace is caused by an error thrown for debugging >> purposes as well as to attempt to terminate the thread which caused >> the illegal access, and has no functional impact. >> Jun 6, 2008 10:58:23 AM org.apache.catalina.loader.WebappClassLoader >> loadClass >> INFO: Illegal access: this web application instance has been stopped >> already. Could not load org.apache.log4j.Logger. The eventual >> following stack trace is caused by an error thrown for debugging >> purposes as well as to attempt to terminate the thread which caused >> the illegal access, and has no functional impact. >> Jun 6, 2008 10:58:23 AM org.apache.catalina.loader.WebappClassLoader >> loadClass >> INFO: Illegal access: this web application instance has been stopped >> already. Could not load java.util.logging.Logger. The eventual >> following stack trace is caused by an error thrown for debugging >> purposes as well as to attempt to terminate the thread which caused >> the illegal access, and has no functional impact. >> Jun 6, 2008 10:58:23 AM org.apache.catalina.loader.WebappClassLoader >> loadClass >> INFO: Illegal access: this web application instance has been stopped >> already. Could not load org.apache.log4j.Logger. The eventual >> following stack trace is caused by an error thrown for debugging >> purposes as well as to attempt to terminate the thread which caused >> the illegal access, and has no functional impact. >> Jun 6, 2008 10:58:23 AM org.apache.catalina.loader.WebappClassLoader >> loadClass >> INFO: Illegal access: this web application instance has been stopped >> already. Could not load java.util.logging.Logger. The eventual >> following stack trace is caused by an error thrown for debugging >> purposes as well as to attempt to terminate the thread which caused >> the illegal access, and has no functional impact. >> Jun 6, 2008 10:58:23 AM org.apache.catalina.loader.WebappClassLoader >> loadClass >> INFO: Illegal access: this web application instance has been stopped >> already. Could not load java.util.logging.Logger. The eventual >> following stack trace is caused by an error thrown for debugging >> purposes as well as to attempt to terminate the thread which caused >> the illegal access, and has no functional impact. >> Jun 6, 2008 10:58:23 AM org.apache.catalina.loader.WebappClassLoader >> loadClass >> INFO: Illegal access: this web application instance has been stopped >> already. Could not load org.apache.commons.logging.impl.SimpleLog. >> The eventual following stack trace is caused by an error thrown for >> debugging purposes as well as to attempt to terminate the thread >> which > >> caused the illegal access, and has no functional impact. >> Jun 6, 2008 10:58:23 AM org.apache.catalina.loader.WebappClassLoader >> loadClass >> INFO: Illegal access: this web application instance has been stopped >> already. Could not load org.apache.commons.logging.impl.SimpleLog. >> The eventual following stack trace is caused by an error thrown for >> debugging purposes as well as to attempt to terminate the thread >> which > >> caused the illegal access, and has no functional impact. >> Jun 6, 2008 10:58:23 AM org.apache.coyote.http11.Http11Protocol >> destroy >> INFO: Stopping Coyote HTTP/1.1 on http-8080 >> >> -----Original Message----- >> From: Igor Vaynberg [mailto:[EMAIL PROTECTED] >> Sent: Friday, June 06, 2008 10:50 AM >> To: users@wicket.apache.org >> Subject: Re: Tomcat 5.5.9 isn't running Quickstart >> >> how about the tomcat log... >> >> -igor >> >> On Fri, Jun 6, 2008 at 8:49 AM, Frank Silbermann >> <[EMAIL PROTECTED]> wrote: >>> Any suggestions as to where I should look for clues? >>> >>> -----Original Message----- >>> From: Igor Vaynberg [mailto:[EMAIL PROTECTED] >>> Sent: Friday, June 06, 2008 10:46 AM >>> To: users@wicket.apache.org >>> Subject: Re: Tomcat 5.5.9 isn't running Quickstart >>> >>> correct course of action is to figure out why its not running in >>> tomcat >>> >>> -igor >>> >>> On Fri, Jun 6, 2008 at 8:39 AM, Frank Silbermann >>> <[EMAIL PROTECTED]> wrote: >>>> I have the quickstart program and have been able to run it in >>>> Eclipse >> >>>> following the directions in >>>> http://herebebeasties.com/2007-10-07/wicket-quickstart/ >>>> >>>> Also, I used "mvn package" to build the web application and .war >>>> >>>> I tried copying the myproject-1.0-SNAPSHOT folder (and I also tried >>>> the .war file) into the webapps folder to Tomcat 5.5.9 and started >>>> up >> >>>> Tomcat. When I entered http://127.0.0.1:8080/myproject/ (or >>>> http://localhost:8080/myproject/) it failed to serve the quickstart >>>> project. Do I need a more recent version of Tomcat for running >>>> Wicket >>> >>>> 1.3, or is there something else I need to do to configure it for >>> Tomcat? >>>> This is what it told me: >>>> >>>> HTTP Status 404 - /myproject/ >>>> >>>> ------------------------------------------------------------------- >>>> - >>>> - >>>> - >>>> -- >>>> -------- >>>> >>>> type Status report >>>> >>>> message /myproject/ >>>> >>>> description The requested resource (/myproject/) is not available. >>>> >>>> >>>> ------------------------------------------------------------------- >>>> - >>>> - >>>> - >>>> -- >>>> -------- >>>> >>>> Apache Tomcat/5.5.9 >>>> >>>> >>>> >>>> ------------------------------------------------------------------- >>>> - >>>> - To unsubscribe, e-mail: [EMAIL PROTECTED] >>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>> >>>> >>> >>> -------------------------------------------------------------------- >>> - To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >>> -------------------------------------------------------------------- >>> - To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
