I downloaded Tomcat 6 this morning, and the QuickStart project runs in it without the logging conflict I had with Tomcat 5.5.9. Perhaps a newer release of Tomcat 5.5 would also work, but I'll just go to Tomcat 6. However, I have a couple of follow-up questions:
(*) My old Wicket 1.2 application, which ran in Tomcat 5.5.9, doesn't run in Tomcat 6! My guess is that Tomcat 6 removed the logging .jar that was interfering with the logging classes deployed with Wicket 1.3 applications, but now my Wicket 1.2 application on Tomcat 6 is lacking a logging implementation. Though I plan to upgrade all my Wicket 1.2 applications to Wicket 1.3, is there a recommended .jar I should add to the lib directory of my Wicket 1.2 application so it runs in Tomcat 6? (My Wicket 1.3 QuickStart adds log4j-1.2.14.jar, slf4j-api-1.4.2.jar, and slf4j-log4j12-1.4.2.jar to the application's lib directory; my Wicket 1.2 application does not add these.) (*) I really like the idea of debugging in Eclipse using in-process Jetty, even if I do deploy to Tomcat. Thanks to posts I found in the archive of this mailing list, I was able to modify the QuickStart configuration of Jetty to read the J2EE and Jetty configuration .xml files that configure my data source. However, I have another problem. My application uses images much as does in Wicket's "images" example. I have some image files (e.g. "image1.png") stored directly inside the "webapp" folder, and my application references the images by generating HTML like so: <html xmlns="http://www.w3.org/1999/xhtml"; xmlns:wicket="http://wicket.sourceforge.net/"; xml:lang="en" lang="en"> <head/> <body> < img wicket:id="picture" src="image1.png" alt="Picture"/ > </body> </html> The image appears when I run the application in Tomcat, but not when I run it in Eclipse with Jetty (following the process described in http://herebebeasties.com/2007-10-07/wicket-quickstart/). What do I need to change to the QuickStart's Jetty configuration so that this HTML will be able to access the image? -----Original Message----- From: Frank Silbermann [mailto:[EMAIL PROTECTED] Sent: Friday, June 06, 2008 3:08 PM To: users@wicket.apache.org Subject: RE: Tomcat 5.5.9 isn't running Quickstart I did a Windows search for files with names containing "log4j" and came up with nothing. I wonder whether it could be bundled into other Tomcat jars. I'm using Tomcat 5.5.9, so maybe I should try a fresh install of Tomcat, version 6, when I get back on Wednesday. -----Original Message----- From: Igor Vaynberg [mailto:[EMAIL PROTECTED] Sent: Friday, June 06, 2008 2:57 PM To: users@wicket.apache.org Subject: Re: Tomcat 5.5.9 isn't running Quickstart it doesnt sound right. tomcat itself is writing out logs and i dont think it uses jdk logging. so there must be at least a log4j jar somewhere in tomcat install.. we have deployed in 5.5 and 6.0 previously and everything works fine. -igor On Fri, Jun 6, 2008 at 9:31 AM, Frank Silbermann <[EMAIL PROTECTED]> wrote: > The lib directory in the QuickStart's WEB-INF contains: > > log4j-1.2.14.jar > slf4j-api-1.4.2.jar > slf4j-log4j12-1.4.2.jar > > -----Original Message----- > From: Igor Vaynberg [mailto:[EMAIL PROTECTED] > Sent: Friday, June 06, 2008 11:27 AM > To: users@wicket.apache.org > Subject: Re: Tomcat 5.5.9 isn't running Quickstart > > you have to at least also have log4j in there somewhere. > commons-logging is just the pipeline.. > > -igor > > On Fri, Jun 6, 2008 at 9:15 AM, 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] > > --------------------------------------------------------------------- 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]
