You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Frank Silbermann <fr...@fedex.com> on 2008/06/06 17:39:43 UTC
Tomcat 5.5.9 isn't running Quickstart
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: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Tomcat 5.5.9 isn't running Quickstart
Posted by Alastair Maw <me...@almaw.com>.
Argh. Commons logging classloader interactions are legendarily hard to
debug. :-(
IIRC, this fixes it.
In your tomcat directories:
bin/commons-logging-api.jar
common/lib/log4j.jar
common/lib/commons-logging.jar
In your web-app directories:
Whatever you like.
It's also possible to embed Tomcat in a similar manner to Jetty if you wish
to have something closer to your production environment. If anyone is
interested in how to do that, I can post you some basic code.
Good luck!
Alastair
2008/6/11 Frank Silbermann <fr...@fedex.com>:
> 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:frank.silbermann@fedex.com]
> 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:igor.vaynberg@gmail.com]
> 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
> <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
> > 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
> > <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
> >> 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
> >> <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
> >>> 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
> >>> <fr...@fedex.com> wrote:
> >>>> Any suggestions as to where I should look for clues?
> >>>>
> >>>> -----Original Message-----
> >>>> From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
> >>>> 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
> >>>> <fr...@fedex.com> 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: users-unsubscribe@wicket.apache.org
> >>>>> For additional commands, e-mail: users-help@wicket.apache.org
> >>>>>
> >>>>>
> >>>>
> >>>> -------------------------------------------------------------------
> >>>> -
> >>>> - To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >>>> For additional commands, e-mail: users-help@wicket.apache.org
> >>>>
> >>>>
> >>>> -------------------------------------------------------------------
> >>>> -
> >>>> - To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >>>> For additional commands, e-mail: users-help@wicket.apache.org
> >>>>
> >>>>
> >>>
> >>> --------------------------------------------------------------------
> >>> - To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >>> For additional commands, e-mail: users-help@wicket.apache.org
> >>>
> >>>
> >>> --------------------------------------------------------------------
> >>> - To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >>> For additional commands, e-mail: users-help@wicket.apache.org
> >>>
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >> For additional commands, e-mail: users-help@wicket.apache.org
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >> For additional commands, e-mail: users-help@wicket.apache.org
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Modifying QuickStart to serve static content in embedded Jetty (was: RE: Tomcat 5.5.9 isn't running Quickstart)
Posted by Maurice Marrink <ma...@gmail.com>.
On Fri, Jun 13, 2008 at 3:56 PM, Frank Silbermann
<fr...@fedex.com> wrote:
> OK, I did some experiments starting with a clean quicksort project. The
> images did appear. However, when I modified the web.xml to change from:
>
> <filter-mapping>
> <filter-name>wicket.myproject</filter-name>
> <url-pattern>/*</url-pattern>
> </filter-mapping>
>
> to this:
>
> <filter-mapping>
> <filter-name>wicket.myproject</filter-name>
> <url-pattern>/test/*</url-pattern>
> </filter-mapping>
>
> then the image no longer appeared.
>
> In Wicket 1.2 I could define to Wicket applications in the same .war
> file, giving them different URLs. I assumed that in Wicket 1.3 I could
> simply define two filters in my web.xml, using different filter mappings
> to distinguish the URLs, but changing the URL like this is clearly not
> appropriate.
>
> What, then, is the proper way in Wicket 1.3 to define multiple Wicket
> applications -- i.e., different home-pages?
You should define a filter and a filter-mapping for each application instance.
The wicket security examples do this, to give you an example.
Maurice
>
> Or was my original plan sound, provided I add something (what?) to my
> web.xml for the default URL that is used when linking static resources?
>
> -----Original Message-----
> From: Martijn Dashorst [mailto:martijn.dashorst@gmail.com]
> Sent: Thursday, June 12, 2008 9:11 AM
> To: users@wicket.apache.org
> Subject: Re: Modifying QuickStart to serve static content in embedded
> Jetty (was: RE: Tomcat 5.5.9 isn't running Quickstart)
>
> No, because the JSP servlet is needed to compile JSPs into servlet code.
> An unmodified configuration generated by the Wicket quickstart on our
> website serves static images perfectly well. You really are doing
> something funky.
>
> Martijn
>
> On Thu, Jun 12, 2008 at 4:07 PM, Frank Silbermann
> <fr...@fedex.com> wrote:
>> Yes, the QuickStart itself works. As for your ability to serve
>> images, it might depend whether these are images stored with the .html
>
>> and .java files for Wicket to pick up, versus images that are stored
>> as static objects. I googled the INFO - log warning " - NO JSP
>> Support for /, did not find org.apache.jasper.servlet.JspServlet"
>>
>> and found http://code.google.com/p/run-jetty-run/wiki/GettingStarted
>> about running Wicket projects with Jetty in Eclipse. It contains the
>> following comments:
>>
>> Comment by angelo.mariano, Jan 02, 2008
>> When I try to launch it, I get the following error: 2008-01-02
>> 10:11:55.191::INFO: Logging to STDERR
>> via org.mortbay.log.StdErrLog? 2008-01-02 10:11:55.300::INFO:
>> jetty-6.1.6 2008-01-02
>> 10:11:55.441::INFO: NO JSP Support for /, did not find
>> org.apache.jasper.servlet.JspServlet?
>> 2008-01-02 10:11:55.659:/:INFO: default: init 2008-01-02
>> 10:11:55.659:/:INFO: jsp: init 2008-01-02
>> 10:11:55.691::INFO: Started SelectChannelConnector?@0.0.0.0:8080
>>
>> and then I am not able to compile jsp. Do you know how to solve this
>
>> problem? Thank you
>>
>> Comment by eelco.hillenius, Jan 02, 2008
>> Ah, I probably have to include the appropriate libs to turn JSP
>> support on. Could you please file a
>> ticket? I'll get to it shortly.
>>
>>
>>
>> Eelco, could that discussion have anything to do with my problem?
>>
>> -----Original Message-----
>> From: Martijn Dashorst [mailto:martijn.dashorst@gmail.com]
>> Sent: Thursday, June 12, 2008 1:23 AM
>> To: users@wicket.apache.org
>> Subject: Re: Tomcat 5.5.9 isn't running Quickstart
>>
>> The quickstart works for me without modifications. It serves images,
>> etc. out of the box, every time.
>>
>> Martijn
>>
>> On Thu, Jun 12, 2008 at 12:54 AM, Frank Silbermann
>> <fr...@fedex.com> wrote:
>>> Searching for some clue as to why my modification of the QuickStart
>>> application is serving images when run in Tomcat but not when running
>
>>> in embedded Jetty via Eclipse, I found:
>>>
>>> http://osdir.com/ml/java.jetty.support/2003-03/msg00045.html --
>>> titled
>>> "Re: Re: jetty can't find images: msg#00045"
>>>
>>> It says, "You need the webdefaults file because it sets up the
>>> Default
>>
>>> servlet which is what serves static resources like images. You can
>>> also manually add the Default servlet if you want to avoid a
>>> webdefaults.xml file."
>>>
>>> I think this is a clue. Looking at the console log when running
>>> Jetty
>>
>>> in Eclipse I see:
>>>
>>> INFO - log - NO JSP Support for /, did not
>> find
>>> org.apache.jasper.servlet.JspServlet
>>>
>>> So what do I need to do to make it set up the Default servlet? Is
>>> there a line I need to insert into Start.java to make it read the
>>> webdefaults.xml file? I don't even have a webdefaults.xml file --
>>> unless it's buried somewhere inside one of the Jetty jars.
>>>
>>> Here's the complete console log when debugging Start.java to bring up
>
>>> Jetty (as demonstrated in
>>> http://herebebeasties.com/2007-10-07/wicket-quickstart/).
>>>
>>> INFO - log - Logging to
>>> org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via
>>> org.mortbay.log.Slf4jLog
>>>>>> STARTING EMBEDDED JETTY SERVER, PRESS ANY KEY TO STOP
>>> INFO - log - jetty-6.1.4
>>> INFO - log - NO JSP Support for /, did not
>> find
>>> org.apache.jasper.servlet.JspServlet
>>> INFO - log - No Transaction manager found -
> if
>>> your webapp requires one, please configure one.
>>> INFO - Application - [TestApplication] init: Wicket
>> core
>>> library initializer
>>> INFO - RequestListenerInterface - registered listener interface
>>> [RequestListenerInterface name=IBehaviorListener, method=public
>>> abstract void
>> org.apache.wicket.behavior.IBehaviorListener.onRequest()]
>>> INFO - RequestListenerInterface - registered listener interface
>>> [RequestListenerInterface name=IBehaviorListener, method=public
>>> abstract void
>> org.apache.wicket.behavior.IBehaviorListener.onRequest()]
>>> INFO - RequestListenerInterface - registered listener interface
>>> [RequestListenerInterface name=IFormSubmitListener, method=public
>>> abstract void
>>> org.apache.wicket.markup.html.form.IFormSubmitListener.onFormSubmitte
>>> d
>>> ()
>>> ]
>>> INFO - RequestListenerInterface - registered listener interface
>>> [RequestListenerInterface name=IFormSubmitListener, method=public
>>> abstract void
>>> org.apache.wicket.markup.html.form.IFormSubmitListener.onFormSubmitte
>>> d
>>> ()
>>> ]
>>> INFO - RequestListenerInterface - registered listener interface
>>> [RequestListenerInterface name=ILinkListener, method=public abstract
>>> void
> org.apache.wicket.markup.html.link.ILinkListener.onLinkClicked()]
>>> INFO - RequestListenerInterface - registered listener interface
>>> [RequestListenerInterface name=ILinkListener, method=public abstract
>>> void
> org.apache.wicket.markup.html.link.ILinkListener.onLinkClicked()]
>>> INFO - RequestListenerInterface - registered listener interface
>>> [RequestListenerInterface name=IOnChangeListener, method=public
>>> abstract void
>>> org.apache.wicket.markup.html.form.IOnChangeListener.onSelectionChang
>>> e
>>> d(
>>> )]
>>> INFO - RequestListenerInterface - registered listener interface
>>> [RequestListenerInterface name=IOnChangeListener, method=public
>>> abstract void
>>> org.apache.wicket.markup.html.form.IOnChangeListener.onSelectionChang
>>> e
>>> d(
>>> )]
>>> INFO - RequestListenerInterface - registered listener interface
>>> [RequestListenerInterface name=IRedirectListener, method=public
>>> abstract void org.apache.wicket.IRedirectListener.onRedirect()]
>>> INFO - RequestListenerInterface - registered listener interface
>>> [RequestListenerInterface name=IRedirectListener, method=public
>>> abstract void org.apache.wicket.IRedirectListener.onRedirect()]
>>> INFO - RequestListenerInterface - registered listener interface
>>> [RequestListenerInterface name=IResourceListener, method=public
>>> abstract void
>> org.apache.wicket.IResourceListener.onResourceRequested()]
>>> INFO - RequestListenerInterface - registered listener interface
>>> [RequestListenerInterface name=IResourceListener, method=public
>>> abstract void
>> org.apache.wicket.IResourceListener.onResourceRequested()]
>>> INFO - Application - [TestApplication] init: Wicket
>>> extensions initializer
>>> INFO - WebApplication - [TestApplication] Started Wicket
>>> version 1.3.3 in development mode
>>> ********************************************************************
>>> *** WARNING: Wicket is running in DEVELOPMENT mode. ***
>>> *** ^^^^^^^^^^^ ***
>>> *** Do NOT deploy to your live server(s) without changing this. ***
>>> *** See Application#getConfigurationType() for more information. ***
>>> ********************************************************************
>>> INFO - log - Started
>>> SocketConnector@0.0.0.0:8080
>>>
>>>
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: Frank Silbermann [mailto:frank.silbermann@fedex.com]
>>> Sent: Wednesday, June 11, 2008 4:41 PM
>>> To: users@wicket.apache.org
>>> Subject: RE: Tomcat 5.5.9 isn't running Quickstart
>>>
>>> It's the identical .war file which shows the images when run in
>>> Tomcat
>>
>>> 6 but not when run in Jetty configured as per the QuickStart
>> application.
>>> The actual HTML in the rendered pages is exactly what I showed you --
>
>>> Wicket generated it using AttributeModifier, and I copied the
>>> generated HTML by doing "show source" in my browser.
>>>
>>> I'm guessing the Jetty has some default security not done in Tomcat
>>> that is "protecting" my image files, which I need to override
> somehow.
>>
>>> Or maybe it is not automatically recognizing .png files as a
>>> MIME-type. Or maybe there's something else that must be configured
>>> in
>>
>>> Jetty to tell it to look in the webapp folder for static content. I
>>> posted about this on the jetty-support mailing list last week
>>> (http://www.nabble.com/-Jetty-support--Embedded-jetty-td8400457.html#
>>> a
>>> 17
>>> 679320), but no one answered it.
>>>
>>> -----Original Message-----
>>> From: Gwyn Evans [mailto:gwyn.evans@gmail.com]
>>> Sent: Wednesday, June 11, 2008 3:51 PM
>>> To: users@wicket.apache.org
>>> Subject: Re: Tomcat 5.5.9 isn't running Quickstart
>>>
>>> On Wed, Jun 11, 2008 at 9:00 PM, Frank Silbermann <
>>> frank.silbermann@fedex.com> wrote:
>>>
>>>
>>>> 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:
>>>>
>>> ...
>>>
>>>> < img wicket:id="picture" src="image1.png" alt="Picture"/ >
>>>>
>>>> The image appears when I run the application in Tomcat, but not when
>
>>>> I
>>>
>>>> run it in Eclipse with Jetty
>>>
>>> ...
>>>
>>> That seems odd to me - the same web-app? I'm probably way off base,
>>> but I'd be double-checking where it's actually serving it from & the
>>> HTML in the rendered pages...
>>>
>>> /Gwyn
>>>
>>>
>>>> ...
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>>
>>
>> --
>> Become a Wicket expert, learn from the best: http://wicketinaction.com
>
>> Apache Wicket 1.3.3 is released Get it now:
>> http://www.apache.org/dyn/closer.cgi/wicket/1.3.3
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> Apache Wicket 1.3.3 is released Get it now:
> http://www.apache.org/dyn/closer.cgi/wicket/1.3.3
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: Modifying QuickStart to serve static content in embedded Jetty (was: RE: Tomcat 5.5.9 isn't running Quickstart)
Posted by Frank Silbermann <fr...@fedex.com>.
OK, I did some experiments starting with a clean quicksort project. The
images did appear. However, when I modified the web.xml to change from:
<filter-mapping>
<filter-name>wicket.myproject</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>
to this:
<filter-mapping>
<filter-name>wicket.myproject</filter-name>
<url-pattern>/test/*</url-pattern>
</filter-mapping>
then the image no longer appeared.
In Wicket 1.2 I could define to Wicket applications in the same .war
file, giving them different URLs. I assumed that in Wicket 1.3 I could
simply define two filters in my web.xml, using different filter mappings
to distinguish the URLs, but changing the URL like this is clearly not
appropriate.
What, then, is the proper way in Wicket 1.3 to define multiple Wicket
applications -- i.e., different home-pages?
Or was my original plan sound, provided I add something (what?) to my
web.xml for the default URL that is used when linking static resources?
-----Original Message-----
From: Martijn Dashorst [mailto:martijn.dashorst@gmail.com]
Sent: Thursday, June 12, 2008 9:11 AM
To: users@wicket.apache.org
Subject: Re: Modifying QuickStart to serve static content in embedded
Jetty (was: RE: Tomcat 5.5.9 isn't running Quickstart)
No, because the JSP servlet is needed to compile JSPs into servlet code.
An unmodified configuration generated by the Wicket quickstart on our
website serves static images perfectly well. You really are doing
something funky.
Martijn
On Thu, Jun 12, 2008 at 4:07 PM, Frank Silbermann
<fr...@fedex.com> wrote:
> Yes, the QuickStart itself works. As for your ability to serve
> images, it might depend whether these are images stored with the .html
> and .java files for Wicket to pick up, versus images that are stored
> as static objects. I googled the INFO - log warning " - NO JSP
> Support for /, did not find org.apache.jasper.servlet.JspServlet"
>
> and found http://code.google.com/p/run-jetty-run/wiki/GettingStarted
> about running Wicket projects with Jetty in Eclipse. It contains the
> following comments:
>
> Comment by angelo.mariano, Jan 02, 2008
> When I try to launch it, I get the following error: 2008-01-02
> 10:11:55.191::INFO: Logging to STDERR
> via org.mortbay.log.StdErrLog? 2008-01-02 10:11:55.300::INFO:
> jetty-6.1.6 2008-01-02
> 10:11:55.441::INFO: NO JSP Support for /, did not find
> org.apache.jasper.servlet.JspServlet?
> 2008-01-02 10:11:55.659:/:INFO: default: init 2008-01-02
> 10:11:55.659:/:INFO: jsp: init 2008-01-02
> 10:11:55.691::INFO: Started SelectChannelConnector?@0.0.0.0:8080
>
> and then I am not able to compile jsp. Do you know how to solve this
> problem? Thank you
>
> Comment by eelco.hillenius, Jan 02, 2008
> Ah, I probably have to include the appropriate libs to turn JSP
> support on. Could you please file a
> ticket? I'll get to it shortly.
>
>
>
> Eelco, could that discussion have anything to do with my problem?
>
> -----Original Message-----
> From: Martijn Dashorst [mailto:martijn.dashorst@gmail.com]
> Sent: Thursday, June 12, 2008 1:23 AM
> To: users@wicket.apache.org
> Subject: Re: Tomcat 5.5.9 isn't running Quickstart
>
> The quickstart works for me without modifications. It serves images,
> etc. out of the box, every time.
>
> Martijn
>
> On Thu, Jun 12, 2008 at 12:54 AM, Frank Silbermann
> <fr...@fedex.com> wrote:
>> Searching for some clue as to why my modification of the QuickStart
>> application is serving images when run in Tomcat but not when running
>> in embedded Jetty via Eclipse, I found:
>>
>> http://osdir.com/ml/java.jetty.support/2003-03/msg00045.html --
>> titled
>> "Re: Re: jetty can't find images: msg#00045"
>>
>> It says, "You need the webdefaults file because it sets up the
>> Default
>
>> servlet which is what serves static resources like images. You can
>> also manually add the Default servlet if you want to avoid a
>> webdefaults.xml file."
>>
>> I think this is a clue. Looking at the console log when running
>> Jetty
>
>> in Eclipse I see:
>>
>> INFO - log - NO JSP Support for /, did not
> find
>> org.apache.jasper.servlet.JspServlet
>>
>> So what do I need to do to make it set up the Default servlet? Is
>> there a line I need to insert into Start.java to make it read the
>> webdefaults.xml file? I don't even have a webdefaults.xml file --
>> unless it's buried somewhere inside one of the Jetty jars.
>>
>> Here's the complete console log when debugging Start.java to bring up
>> Jetty (as demonstrated in
>> http://herebebeasties.com/2007-10-07/wicket-quickstart/).
>>
>> INFO - log - Logging to
>> org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via
>> org.mortbay.log.Slf4jLog
>>>>> STARTING EMBEDDED JETTY SERVER, PRESS ANY KEY TO STOP
>> INFO - log - jetty-6.1.4
>> INFO - log - NO JSP Support for /, did not
> find
>> org.apache.jasper.servlet.JspServlet
>> INFO - log - No Transaction manager found -
if
>> your webapp requires one, please configure one.
>> INFO - Application - [TestApplication] init: Wicket
> core
>> library initializer
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IBehaviorListener, method=public
>> abstract void
> org.apache.wicket.behavior.IBehaviorListener.onRequest()]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IBehaviorListener, method=public
>> abstract void
> org.apache.wicket.behavior.IBehaviorListener.onRequest()]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IFormSubmitListener, method=public
>> abstract void
>> org.apache.wicket.markup.html.form.IFormSubmitListener.onFormSubmitte
>> d
>> ()
>> ]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IFormSubmitListener, method=public
>> abstract void
>> org.apache.wicket.markup.html.form.IFormSubmitListener.onFormSubmitte
>> d
>> ()
>> ]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=ILinkListener, method=public abstract
>> void
org.apache.wicket.markup.html.link.ILinkListener.onLinkClicked()]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=ILinkListener, method=public abstract
>> void
org.apache.wicket.markup.html.link.ILinkListener.onLinkClicked()]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IOnChangeListener, method=public
>> abstract void
>> org.apache.wicket.markup.html.form.IOnChangeListener.onSelectionChang
>> e
>> d(
>> )]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IOnChangeListener, method=public
>> abstract void
>> org.apache.wicket.markup.html.form.IOnChangeListener.onSelectionChang
>> e
>> d(
>> )]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IRedirectListener, method=public
>> abstract void org.apache.wicket.IRedirectListener.onRedirect()]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IRedirectListener, method=public
>> abstract void org.apache.wicket.IRedirectListener.onRedirect()]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IResourceListener, method=public
>> abstract void
> org.apache.wicket.IResourceListener.onResourceRequested()]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IResourceListener, method=public
>> abstract void
> org.apache.wicket.IResourceListener.onResourceRequested()]
>> INFO - Application - [TestApplication] init: Wicket
>> extensions initializer
>> INFO - WebApplication - [TestApplication] Started Wicket
>> version 1.3.3 in development mode
>> ********************************************************************
>> *** WARNING: Wicket is running in DEVELOPMENT mode. ***
>> *** ^^^^^^^^^^^ ***
>> *** Do NOT deploy to your live server(s) without changing this. ***
>> *** See Application#getConfigurationType() for more information. ***
>> ********************************************************************
>> INFO - log - Started
>> SocketConnector@0.0.0.0:8080
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: Frank Silbermann [mailto:frank.silbermann@fedex.com]
>> Sent: Wednesday, June 11, 2008 4:41 PM
>> To: users@wicket.apache.org
>> Subject: RE: Tomcat 5.5.9 isn't running Quickstart
>>
>> It's the identical .war file which shows the images when run in
>> Tomcat
>
>> 6 but not when run in Jetty configured as per the QuickStart
> application.
>> The actual HTML in the rendered pages is exactly what I showed you --
>> Wicket generated it using AttributeModifier, and I copied the
>> generated HTML by doing "show source" in my browser.
>>
>> I'm guessing the Jetty has some default security not done in Tomcat
>> that is "protecting" my image files, which I need to override
somehow.
>
>> Or maybe it is not automatically recognizing .png files as a
>> MIME-type. Or maybe there's something else that must be configured
>> in
>
>> Jetty to tell it to look in the webapp folder for static content. I
>> posted about this on the jetty-support mailing list last week
>> (http://www.nabble.com/-Jetty-support--Embedded-jetty-td8400457.html#
>> a
>> 17
>> 679320), but no one answered it.
>>
>> -----Original Message-----
>> From: Gwyn Evans [mailto:gwyn.evans@gmail.com]
>> Sent: Wednesday, June 11, 2008 3:51 PM
>> To: users@wicket.apache.org
>> Subject: Re: Tomcat 5.5.9 isn't running Quickstart
>>
>> On Wed, Jun 11, 2008 at 9:00 PM, Frank Silbermann <
>> frank.silbermann@fedex.com> wrote:
>>
>>
>>> 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:
>>>
>> ...
>>
>>> < img wicket:id="picture" src="image1.png" alt="Picture"/ >
>>>
>>> The image appears when I run the application in Tomcat, but not when
>>> I
>>
>>> run it in Eclipse with Jetty
>>
>> ...
>>
>> That seems odd to me - the same web-app? I'm probably way off base,
>> but I'd be double-checking where it's actually serving it from & the
>> HTML in the rendered pages...
>>
>> /Gwyn
>>
>>
>>> ...
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> Apache Wicket 1.3.3 is released Get it now:
> http://www.apache.org/dyn/closer.cgi/wicket/1.3.3
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.3 is released Get it now:
http://www.apache.org/dyn/closer.cgi/wicket/1.3.3
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Modifying QuickStart to serve static content in embedded Jetty (was: RE: Tomcat 5.5.9 isn't running Quickstart)
Posted by Gwyn Evans <gw...@gmail.com>.
JIRA issue & mvn clean, I'd say...
/Gwyn
On Thu, Jun 12, 2008 at 5:28 PM, Frank Silbermann <
frank.silbermann@fedex.com> wrote:
> Well, I guess the only thing to do is try and minimally modify the
> QuickStart project with code that exhibits the problem and let others
> try it. Should I submit it as a JIRA issue (to be closed when it is
> determined what I'm doing wrong), or should I attach the .zip to a
> mailing list message? Should I "mvn clean" it before zipping it to save
> space?
>
> -----Original Message-----
> From: Martijn Dashorst [mailto:martijn.dashorst@gmail.com]
> Sent: Thursday, June 12, 2008 9:11 AM
> To: users@wicket.apache.org
> Subject: Re: Modifying QuickStart to serve static content in embedded
> Jetty (was: RE: Tomcat 5.5.9 isn't running Quickstart)
>
> No, because the JSP servlet is needed to compile JSPs into servlet code.
> An unmodified configuration generated by the Wicket quickstart on our
> website serves static images perfectly well. You really are doing
> something funky.
>
> Martijn
>
> On Thu, Jun 12, 2008 at 4:07 PM, Frank Silbermann
> <fr...@fedex.com> wrote:
> > Yes, the QuickStart itself works. As for your ability to serve
> > images, it might depend whether these are images stored with the .html
>
> > and .java files for Wicket to pick up, versus images that are stored
> > as static objects. I googled the INFO - log warning " - NO JSP
> > Support for /, did not find org.apache.jasper.servlet.JspServlet"
> >
> > and found http://code.google.com/p/run-jetty-run/wiki/GettingStarted
> > about running Wicket projects with Jetty in Eclipse. It contains the
> > following comments:
> >
> > Comment by angelo.mariano, Jan 02, 2008
> > When I try to launch it, I get the following error: 2008-01-02
> > 10:11:55.191::INFO: Logging to STDERR
> > via org.mortbay.log.StdErrLog? 2008-01-02 10:11:55.300::INFO:
> > jetty-6.1.6 2008-01-02
> > 10:11:55.441::INFO: NO JSP Support for /, did not find
> > org.apache.jasper.servlet.JspServlet?
> > 2008-01-02 10:11:55.659:/:INFO: default: init 2008-01-02
> > 10:11:55.659:/:INFO: jsp: init 2008-01-02
> > 10:11:55.691::INFO: Started SelectChannelConnector?@0.0.0.0:8080
> >
> > and then I am not able to compile jsp. Do you know how to solve this
>
> > problem? Thank you
> >
> > Comment by eelco.hillenius, Jan 02, 2008
> > Ah, I probably have to include the appropriate libs to turn JSP
> > support on. Could you please file a
> > ticket? I'll get to it shortly.
> >
> >
> >
> > Eelco, could that discussion have anything to do with my problem?
> >
> > -----Original Message-----
> > From: Martijn Dashorst [mailto:martijn.dashorst@gmail.com]
> > Sent: Thursday, June 12, 2008 1:23 AM
> > To: users@wicket.apache.org
> > Subject: Re: Tomcat 5.5.9 isn't running Quickstart
> >
> > The quickstart works for me without modifications. It serves images,
> > etc. out of the box, every time.
> >
> > Martijn
> >
> > On Thu, Jun 12, 2008 at 12:54 AM, Frank Silbermann
> > <fr...@fedex.com> wrote:
> >> Searching for some clue as to why my modification of the QuickStart
> >> application is serving images when run in Tomcat but not when running
>
> >> in embedded Jetty via Eclipse, I found:
> >>
> >> http://osdir.com/ml/java.jetty.support/2003-03/msg00045.html --
> >> titled
> >> "Re: Re: jetty can't find images: msg#00045"
> >>
> >> It says, "You need the webdefaults file because it sets up the
> >> Default
> >
> >> servlet which is what serves static resources like images. You can
> >> also manually add the Default servlet if you want to avoid a
> >> webdefaults.xml file."
> >>
> >> I think this is a clue. Looking at the console log when running
> >> Jetty
> >
> >> in Eclipse I see:
> >>
> >> INFO - log - NO JSP Support for /, did not
> > find
> >> org.apache.jasper.servlet.JspServlet
> >>
> >> So what do I need to do to make it set up the Default servlet? Is
> >> there a line I need to insert into Start.java to make it read the
> >> webdefaults.xml file? I don't even have a webdefaults.xml file --
> >> unless it's buried somewhere inside one of the Jetty jars.
> >>
> >> Here's the complete console log when debugging Start.java to bring up
>
> >> Jetty (as demonstrated in
> >> http://herebebeasties.com/2007-10-07/wicket-quickstart/).
> >>
> >> INFO - log - Logging to
> >> org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via
> >> org.mortbay.log.Slf4jLog
> >>>>> STARTING EMBEDDED JETTY SERVER, PRESS ANY KEY TO STOP
> >> INFO - log - jetty-6.1.4
> >> INFO - log - NO JSP Support for /, did not
> > find
> >> org.apache.jasper.servlet.JspServlet
> >> INFO - log - No Transaction manager found -
> if
> >> your webapp requires one, please configure one.
> >> INFO - Application - [TestApplication] init: Wicket
> > core
> >> library initializer
> >> INFO - RequestListenerInterface - registered listener interface
> >> [RequestListenerInterface name=IBehaviorListener, method=public
> >> abstract void
> > org.apache.wicket.behavior.IBehaviorListener.onRequest()]
> >> INFO - RequestListenerInterface - registered listener interface
> >> [RequestListenerInterface name=IBehaviorListener, method=public
> >> abstract void
> > org.apache.wicket.behavior.IBehaviorListener.onRequest()]
> >> INFO - RequestListenerInterface - registered listener interface
> >> [RequestListenerInterface name=IFormSubmitListener, method=public
> >> abstract void
> >> org.apache.wicket.markup.html.form.IFormSubmitListener.onFormSubmitte
> >> d
> >> ()
> >> ]
> >> INFO - RequestListenerInterface - registered listener interface
> >> [RequestListenerInterface name=IFormSubmitListener, method=public
> >> abstract void
> >> org.apache.wicket.markup.html.form.IFormSubmitListener.onFormSubmitte
> >> d
> >> ()
> >> ]
> >> INFO - RequestListenerInterface - registered listener interface
> >> [RequestListenerInterface name=ILinkListener, method=public abstract
> >> void
> org.apache.wicket.markup.html.link.ILinkListener.onLinkClicked()]
> >> INFO - RequestListenerInterface - registered listener interface
> >> [RequestListenerInterface name=ILinkListener, method=public abstract
> >> void
> org.apache.wicket.markup.html.link.ILinkListener.onLinkClicked()]
> >> INFO - RequestListenerInterface - registered listener interface
> >> [RequestListenerInterface name=IOnChangeListener, method=public
> >> abstract void
> >> org.apache.wicket.markup.html.form.IOnChangeListener.onSelectionChang
> >> e
> >> d(
> >> )]
> >> INFO - RequestListenerInterface - registered listener interface
> >> [RequestListenerInterface name=IOnChangeListener, method=public
> >> abstract void
> >> org.apache.wicket.markup.html.form.IOnChangeListener.onSelectionChang
> >> e
> >> d(
> >> )]
> >> INFO - RequestListenerInterface - registered listener interface
> >> [RequestListenerInterface name=IRedirectListener, method=public
> >> abstract void org.apache.wicket.IRedirectListener.onRedirect()]
> >> INFO - RequestListenerInterface - registered listener interface
> >> [RequestListenerInterface name=IRedirectListener, method=public
> >> abstract void org.apache.wicket.IRedirectListener.onRedirect()]
> >> INFO - RequestListenerInterface - registered listener interface
> >> [RequestListenerInterface name=IResourceListener, method=public
> >> abstract void
> > org.apache.wicket.IResourceListener.onResourceRequested()]
> >> INFO - RequestListenerInterface - registered listener interface
> >> [RequestListenerInterface name=IResourceListener, method=public
> >> abstract void
> > org.apache.wicket.IResourceListener.onResourceRequested()]
> >> INFO - Application - [TestApplication] init: Wicket
> >> extensions initializer
> >> INFO - WebApplication - [TestApplication] Started Wicket
> >> version 1.3.3 in development mode
> >> ********************************************************************
> >> *** WARNING: Wicket is running in DEVELOPMENT mode. ***
> >> *** ^^^^^^^^^^^ ***
> >> *** Do NOT deploy to your live server(s) without changing this. ***
> >> *** See Application#getConfigurationType() for more information. ***
> >> ********************************************************************
> >> INFO - log - Started
> >> SocketConnector@0.0.0.0:8080
> >>
> >>
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: Frank Silbermann [mailto:frank.silbermann@fedex.com]
> >> Sent: Wednesday, June 11, 2008 4:41 PM
> >> To: users@wicket.apache.org
> >> Subject: RE: Tomcat 5.5.9 isn't running Quickstart
> >>
> >> It's the identical .war file which shows the images when run in
> >> Tomcat
> >
> >> 6 but not when run in Jetty configured as per the QuickStart
> > application.
> >> The actual HTML in the rendered pages is exactly what I showed you --
>
> >> Wicket generated it using AttributeModifier, and I copied the
> >> generated HTML by doing "show source" in my browser.
> >>
> >> I'm guessing the Jetty has some default security not done in Tomcat
> >> that is "protecting" my image files, which I need to override
> somehow.
> >
> >> Or maybe it is not automatically recognizing .png files as a
> >> MIME-type. Or maybe there's something else that must be configured
> >> in
> >
> >> Jetty to tell it to look in the webapp folder for static content. I
> >> posted about this on the jetty-support mailing list last week
> >> (http://www.nabble.com/-Jetty-support--Embedded-jetty-td8400457.html#
> >> a
> >> 17
> >> 679320), but no one answered it.
> >>
> >> -----Original Message-----
> >> From: Gwyn Evans [mailto:gwyn.evans@gmail.com]
> >> Sent: Wednesday, June 11, 2008 3:51 PM
> >> To: users@wicket.apache.org
> >> Subject: Re: Tomcat 5.5.9 isn't running Quickstart
> >>
> >> On Wed, Jun 11, 2008 at 9:00 PM, Frank Silbermann <
> >> frank.silbermann@fedex.com> wrote:
> >>
> >>
> >>> 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:
> >>>
> >> ...
> >>
> >>> < img wicket:id="picture" src="image1.png" alt="Picture"/ >
> >>>
> >>> The image appears when I run the application in Tomcat, but not when
>
> >>> I
> >>
> >>> run it in Eclipse with Jetty
> >>
> >> ...
> >>
> >> That seems odd to me - the same web-app? I'm probably way off base,
> >> but I'd be double-checking where it's actually serving it from & the
> >> HTML in the rendered pages...
> >>
> >> /Gwyn
> >>
> >>
> >>> ...
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >> For additional commands, e-mail: users-help@wicket.apache.org
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >> For additional commands, e-mail: users-help@wicket.apache.org
> >>
> >>
> >
> >
> >
> > --
> > Become a Wicket expert, learn from the best: http://wicketinaction.com
>
> > Apache Wicket 1.3.3 is released Get it now:
> > http://www.apache.org/dyn/closer.cgi/wicket/1.3.3
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> Apache Wicket 1.3.3 is released Get it now:
> http://www.apache.org/dyn/closer.cgi/wicket/1.3.3
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
RE: Modifying QuickStart to serve static content in embedded Jetty (was: RE: Tomcat 5.5.9 isn't running Quickstart)
Posted by Frank Silbermann <fr...@fedex.com>.
Well, I guess the only thing to do is try and minimally modify the
QuickStart project with code that exhibits the problem and let others
try it. Should I submit it as a JIRA issue (to be closed when it is
determined what I'm doing wrong), or should I attach the .zip to a
mailing list message? Should I "mvn clean" it before zipping it to save
space?
-----Original Message-----
From: Martijn Dashorst [mailto:martijn.dashorst@gmail.com]
Sent: Thursday, June 12, 2008 9:11 AM
To: users@wicket.apache.org
Subject: Re: Modifying QuickStart to serve static content in embedded
Jetty (was: RE: Tomcat 5.5.9 isn't running Quickstart)
No, because the JSP servlet is needed to compile JSPs into servlet code.
An unmodified configuration generated by the Wicket quickstart on our
website serves static images perfectly well. You really are doing
something funky.
Martijn
On Thu, Jun 12, 2008 at 4:07 PM, Frank Silbermann
<fr...@fedex.com> wrote:
> Yes, the QuickStart itself works. As for your ability to serve
> images, it might depend whether these are images stored with the .html
> and .java files for Wicket to pick up, versus images that are stored
> as static objects. I googled the INFO - log warning " - NO JSP
> Support for /, did not find org.apache.jasper.servlet.JspServlet"
>
> and found http://code.google.com/p/run-jetty-run/wiki/GettingStarted
> about running Wicket projects with Jetty in Eclipse. It contains the
> following comments:
>
> Comment by angelo.mariano, Jan 02, 2008
> When I try to launch it, I get the following error: 2008-01-02
> 10:11:55.191::INFO: Logging to STDERR
> via org.mortbay.log.StdErrLog? 2008-01-02 10:11:55.300::INFO:
> jetty-6.1.6 2008-01-02
> 10:11:55.441::INFO: NO JSP Support for /, did not find
> org.apache.jasper.servlet.JspServlet?
> 2008-01-02 10:11:55.659:/:INFO: default: init 2008-01-02
> 10:11:55.659:/:INFO: jsp: init 2008-01-02
> 10:11:55.691::INFO: Started SelectChannelConnector?@0.0.0.0:8080
>
> and then I am not able to compile jsp. Do you know how to solve this
> problem? Thank you
>
> Comment by eelco.hillenius, Jan 02, 2008
> Ah, I probably have to include the appropriate libs to turn JSP
> support on. Could you please file a
> ticket? I'll get to it shortly.
>
>
>
> Eelco, could that discussion have anything to do with my problem?
>
> -----Original Message-----
> From: Martijn Dashorst [mailto:martijn.dashorst@gmail.com]
> Sent: Thursday, June 12, 2008 1:23 AM
> To: users@wicket.apache.org
> Subject: Re: Tomcat 5.5.9 isn't running Quickstart
>
> The quickstart works for me without modifications. It serves images,
> etc. out of the box, every time.
>
> Martijn
>
> On Thu, Jun 12, 2008 at 12:54 AM, Frank Silbermann
> <fr...@fedex.com> wrote:
>> Searching for some clue as to why my modification of the QuickStart
>> application is serving images when run in Tomcat but not when running
>> in embedded Jetty via Eclipse, I found:
>>
>> http://osdir.com/ml/java.jetty.support/2003-03/msg00045.html --
>> titled
>> "Re: Re: jetty can't find images: msg#00045"
>>
>> It says, "You need the webdefaults file because it sets up the
>> Default
>
>> servlet which is what serves static resources like images. You can
>> also manually add the Default servlet if you want to avoid a
>> webdefaults.xml file."
>>
>> I think this is a clue. Looking at the console log when running
>> Jetty
>
>> in Eclipse I see:
>>
>> INFO - log - NO JSP Support for /, did not
> find
>> org.apache.jasper.servlet.JspServlet
>>
>> So what do I need to do to make it set up the Default servlet? Is
>> there a line I need to insert into Start.java to make it read the
>> webdefaults.xml file? I don't even have a webdefaults.xml file --
>> unless it's buried somewhere inside one of the Jetty jars.
>>
>> Here's the complete console log when debugging Start.java to bring up
>> Jetty (as demonstrated in
>> http://herebebeasties.com/2007-10-07/wicket-quickstart/).
>>
>> INFO - log - Logging to
>> org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via
>> org.mortbay.log.Slf4jLog
>>>>> STARTING EMBEDDED JETTY SERVER, PRESS ANY KEY TO STOP
>> INFO - log - jetty-6.1.4
>> INFO - log - NO JSP Support for /, did not
> find
>> org.apache.jasper.servlet.JspServlet
>> INFO - log - No Transaction manager found -
if
>> your webapp requires one, please configure one.
>> INFO - Application - [TestApplication] init: Wicket
> core
>> library initializer
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IBehaviorListener, method=public
>> abstract void
> org.apache.wicket.behavior.IBehaviorListener.onRequest()]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IBehaviorListener, method=public
>> abstract void
> org.apache.wicket.behavior.IBehaviorListener.onRequest()]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IFormSubmitListener, method=public
>> abstract void
>> org.apache.wicket.markup.html.form.IFormSubmitListener.onFormSubmitte
>> d
>> ()
>> ]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IFormSubmitListener, method=public
>> abstract void
>> org.apache.wicket.markup.html.form.IFormSubmitListener.onFormSubmitte
>> d
>> ()
>> ]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=ILinkListener, method=public abstract
>> void
org.apache.wicket.markup.html.link.ILinkListener.onLinkClicked()]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=ILinkListener, method=public abstract
>> void
org.apache.wicket.markup.html.link.ILinkListener.onLinkClicked()]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IOnChangeListener, method=public
>> abstract void
>> org.apache.wicket.markup.html.form.IOnChangeListener.onSelectionChang
>> e
>> d(
>> )]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IOnChangeListener, method=public
>> abstract void
>> org.apache.wicket.markup.html.form.IOnChangeListener.onSelectionChang
>> e
>> d(
>> )]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IRedirectListener, method=public
>> abstract void org.apache.wicket.IRedirectListener.onRedirect()]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IRedirectListener, method=public
>> abstract void org.apache.wicket.IRedirectListener.onRedirect()]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IResourceListener, method=public
>> abstract void
> org.apache.wicket.IResourceListener.onResourceRequested()]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IResourceListener, method=public
>> abstract void
> org.apache.wicket.IResourceListener.onResourceRequested()]
>> INFO - Application - [TestApplication] init: Wicket
>> extensions initializer
>> INFO - WebApplication - [TestApplication] Started Wicket
>> version 1.3.3 in development mode
>> ********************************************************************
>> *** WARNING: Wicket is running in DEVELOPMENT mode. ***
>> *** ^^^^^^^^^^^ ***
>> *** Do NOT deploy to your live server(s) without changing this. ***
>> *** See Application#getConfigurationType() for more information. ***
>> ********************************************************************
>> INFO - log - Started
>> SocketConnector@0.0.0.0:8080
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: Frank Silbermann [mailto:frank.silbermann@fedex.com]
>> Sent: Wednesday, June 11, 2008 4:41 PM
>> To: users@wicket.apache.org
>> Subject: RE: Tomcat 5.5.9 isn't running Quickstart
>>
>> It's the identical .war file which shows the images when run in
>> Tomcat
>
>> 6 but not when run in Jetty configured as per the QuickStart
> application.
>> The actual HTML in the rendered pages is exactly what I showed you --
>> Wicket generated it using AttributeModifier, and I copied the
>> generated HTML by doing "show source" in my browser.
>>
>> I'm guessing the Jetty has some default security not done in Tomcat
>> that is "protecting" my image files, which I need to override
somehow.
>
>> Or maybe it is not automatically recognizing .png files as a
>> MIME-type. Or maybe there's something else that must be configured
>> in
>
>> Jetty to tell it to look in the webapp folder for static content. I
>> posted about this on the jetty-support mailing list last week
>> (http://www.nabble.com/-Jetty-support--Embedded-jetty-td8400457.html#
>> a
>> 17
>> 679320), but no one answered it.
>>
>> -----Original Message-----
>> From: Gwyn Evans [mailto:gwyn.evans@gmail.com]
>> Sent: Wednesday, June 11, 2008 3:51 PM
>> To: users@wicket.apache.org
>> Subject: Re: Tomcat 5.5.9 isn't running Quickstart
>>
>> On Wed, Jun 11, 2008 at 9:00 PM, Frank Silbermann <
>> frank.silbermann@fedex.com> wrote:
>>
>>
>>> 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:
>>>
>> ...
>>
>>> < img wicket:id="picture" src="image1.png" alt="Picture"/ >
>>>
>>> The image appears when I run the application in Tomcat, but not when
>>> I
>>
>>> run it in Eclipse with Jetty
>>
>> ...
>>
>> That seems odd to me - the same web-app? I'm probably way off base,
>> but I'd be double-checking where it's actually serving it from & the
>> HTML in the rendered pages...
>>
>> /Gwyn
>>
>>
>>> ...
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> Apache Wicket 1.3.3 is released Get it now:
> http://www.apache.org/dyn/closer.cgi/wicket/1.3.3
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.3 is released Get it now:
http://www.apache.org/dyn/closer.cgi/wicket/1.3.3
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Modifying QuickStart to serve static content in embedded Jetty (was: RE: Tomcat 5.5.9 isn't running Quickstart)
Posted by Martijn Dashorst <ma...@gmail.com>.
No, because the JSP servlet is needed to compile JSPs into servlet
code. An unmodified configuration generated by the Wicket quickstart
on our website serves static images perfectly well. You really are
doing something funky.
Martijn
On Thu, Jun 12, 2008 at 4:07 PM, Frank Silbermann
<fr...@fedex.com> wrote:
> Yes, the QuickStart itself works. As for your ability to serve images,
> it might depend whether these are images stored with the .html and .java
> files for Wicket to pick up, versus images that are stored as static
> objects. I googled the INFO - log warning " - NO JSP Support for /, did
> not find org.apache.jasper.servlet.JspServlet"
>
> and found http://code.google.com/p/run-jetty-run/wiki/GettingStarted
> about running Wicket projects with Jetty in Eclipse. It contains the
> following comments:
>
> Comment by angelo.mariano, Jan 02, 2008
> When I try to launch it, I get the following error: 2008-01-02
> 10:11:55.191::INFO: Logging to STDERR
> via org.mortbay.log.StdErrLog? 2008-01-02 10:11:55.300::INFO:
> jetty-6.1.6 2008-01-02
> 10:11:55.441::INFO: NO JSP Support for /, did not find
> org.apache.jasper.servlet.JspServlet?
> 2008-01-02 10:11:55.659:/:INFO: default: init 2008-01-02
> 10:11:55.659:/:INFO: jsp: init 2008-01-02
> 10:11:55.691::INFO: Started SelectChannelConnector?@0.0.0.0:8080
>
> and then I am not able to compile jsp. Do you know how to solve this
> problem? Thank you
>
> Comment by eelco.hillenius, Jan 02, 2008
> Ah, I probably have to include the appropriate libs to turn JSP
> support on. Could you please file a
> ticket? I'll get to it shortly.
>
>
>
> Eelco, could that discussion have anything to do with my problem?
>
> -----Original Message-----
> From: Martijn Dashorst [mailto:martijn.dashorst@gmail.com]
> Sent: Thursday, June 12, 2008 1:23 AM
> To: users@wicket.apache.org
> Subject: Re: Tomcat 5.5.9 isn't running Quickstart
>
> The quickstart works for me without modifications. It serves images,
> etc. out of the box, every time.
>
> Martijn
>
> On Thu, Jun 12, 2008 at 12:54 AM, Frank Silbermann
> <fr...@fedex.com> wrote:
>> Searching for some clue as to why my modification of the QuickStart
>> application is serving images when run in Tomcat but not when running
>> in embedded Jetty via Eclipse, I found:
>>
>> http://osdir.com/ml/java.jetty.support/2003-03/msg00045.html -- titled
>> "Re: Re: jetty can't find images: msg#00045"
>>
>> It says, "You need the webdefaults file because it sets up the Default
>
>> servlet which is what serves static resources like images. You can
>> also manually add the Default servlet if you want to avoid a
>> webdefaults.xml file."
>>
>> I think this is a clue. Looking at the console log when running Jetty
>
>> in Eclipse I see:
>>
>> INFO - log - NO JSP Support for /, did not
> find
>> org.apache.jasper.servlet.JspServlet
>>
>> So what do I need to do to make it set up the Default servlet? Is
>> there a line I need to insert into Start.java to make it read the
>> webdefaults.xml file? I don't even have a webdefaults.xml file --
>> unless it's buried somewhere inside one of the Jetty jars.
>>
>> Here's the complete console log when debugging Start.java to bring up
>> Jetty (as demonstrated in
>> http://herebebeasties.com/2007-10-07/wicket-quickstart/).
>>
>> INFO - log - Logging to
>> org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via
>> org.mortbay.log.Slf4jLog
>>>>> STARTING EMBEDDED JETTY SERVER, PRESS ANY KEY TO STOP
>> INFO - log - jetty-6.1.4
>> INFO - log - NO JSP Support for /, did not
> find
>> org.apache.jasper.servlet.JspServlet
>> INFO - log - No Transaction manager found - if
>> your webapp requires one, please configure one.
>> INFO - Application - [TestApplication] init: Wicket
> core
>> library initializer
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IBehaviorListener, method=public
>> abstract void
> org.apache.wicket.behavior.IBehaviorListener.onRequest()]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IBehaviorListener, method=public
>> abstract void
> org.apache.wicket.behavior.IBehaviorListener.onRequest()]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IFormSubmitListener, method=public
>> abstract void
>> org.apache.wicket.markup.html.form.IFormSubmitListener.onFormSubmitted
>> ()
>> ]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IFormSubmitListener, method=public
>> abstract void
>> org.apache.wicket.markup.html.form.IFormSubmitListener.onFormSubmitted
>> ()
>> ]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=ILinkListener, method=public abstract
>> void org.apache.wicket.markup.html.link.ILinkListener.onLinkClicked()]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=ILinkListener, method=public abstract
>> void org.apache.wicket.markup.html.link.ILinkListener.onLinkClicked()]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IOnChangeListener, method=public
>> abstract void
>> org.apache.wicket.markup.html.form.IOnChangeListener.onSelectionChange
>> d(
>> )]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IOnChangeListener, method=public
>> abstract void
>> org.apache.wicket.markup.html.form.IOnChangeListener.onSelectionChange
>> d(
>> )]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IRedirectListener, method=public
>> abstract void org.apache.wicket.IRedirectListener.onRedirect()]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IRedirectListener, method=public
>> abstract void org.apache.wicket.IRedirectListener.onRedirect()]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IResourceListener, method=public
>> abstract void
> org.apache.wicket.IResourceListener.onResourceRequested()]
>> INFO - RequestListenerInterface - registered listener interface
>> [RequestListenerInterface name=IResourceListener, method=public
>> abstract void
> org.apache.wicket.IResourceListener.onResourceRequested()]
>> INFO - Application - [TestApplication] init: Wicket
>> extensions initializer
>> INFO - WebApplication - [TestApplication] Started Wicket
>> version 1.3.3 in development mode
>> ********************************************************************
>> *** WARNING: Wicket is running in DEVELOPMENT mode. ***
>> *** ^^^^^^^^^^^ ***
>> *** Do NOT deploy to your live server(s) without changing this. ***
>> *** See Application#getConfigurationType() for more information. ***
>> ********************************************************************
>> INFO - log - Started
>> SocketConnector@0.0.0.0:8080
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: Frank Silbermann [mailto:frank.silbermann@fedex.com]
>> Sent: Wednesday, June 11, 2008 4:41 PM
>> To: users@wicket.apache.org
>> Subject: RE: Tomcat 5.5.9 isn't running Quickstart
>>
>> It's the identical .war file which shows the images when run in Tomcat
>
>> 6 but not when run in Jetty configured as per the QuickStart
> application.
>> The actual HTML in the rendered pages is exactly what I showed you --
>> Wicket generated it using AttributeModifier, and I copied the
>> generated HTML by doing "show source" in my browser.
>>
>> I'm guessing the Jetty has some default security not done in Tomcat
>> that is "protecting" my image files, which I need to override somehow.
>
>> Or maybe it is not automatically recognizing .png files as a
>> MIME-type. Or maybe there's something else that must be configured in
>
>> Jetty to tell it to look in the webapp folder for static content. I
>> posted about this on the jetty-support mailing list last week
>> (http://www.nabble.com/-Jetty-support--Embedded-jetty-td8400457.html#a
>> 17
>> 679320), but no one answered it.
>>
>> -----Original Message-----
>> From: Gwyn Evans [mailto:gwyn.evans@gmail.com]
>> Sent: Wednesday, June 11, 2008 3:51 PM
>> To: users@wicket.apache.org
>> Subject: Re: Tomcat 5.5.9 isn't running Quickstart
>>
>> On Wed, Jun 11, 2008 at 9:00 PM, Frank Silbermann <
>> frank.silbermann@fedex.com> wrote:
>>
>>
>>> 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:
>>>
>> ...
>>
>>> < img wicket:id="picture" src="image1.png" alt="Picture"/ >
>>>
>>> The image appears when I run the application in Tomcat, but not when
>>> I
>>
>>> run it in Eclipse with Jetty
>>
>> ...
>>
>> That seems odd to me - the same web-app? I'm probably way off base,
>> but I'd be double-checking where it's actually serving it from & the
>> HTML in the rendered pages...
>>
>> /Gwyn
>>
>>
>>> ...
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> Apache Wicket 1.3.3 is released Get it now:
> http://www.apache.org/dyn/closer.cgi/wicket/1.3.3
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.3 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.3
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Modifying QuickStart to serve static content in embedded Jetty (was: RE: Tomcat 5.5.9 isn't running Quickstart)
Posted by Frank Silbermann <fr...@fedex.com>.
Yes, the QuickStart itself works. As for your ability to serve images,
it might depend whether these are images stored with the .html and .java
files for Wicket to pick up, versus images that are stored as static
objects. I googled the INFO - log warning " - NO JSP Support for /, did
not find org.apache.jasper.servlet.JspServlet"
and found http://code.google.com/p/run-jetty-run/wiki/GettingStarted
about running Wicket projects with Jetty in Eclipse. It contains the
following comments:
Comment by angelo.mariano, Jan 02, 2008
When I try to launch it, I get the following error: 2008-01-02
10:11:55.191::INFO: Logging to STDERR
via org.mortbay.log.StdErrLog? 2008-01-02 10:11:55.300::INFO:
jetty-6.1.6 2008-01-02
10:11:55.441::INFO: NO JSP Support for /, did not find
org.apache.jasper.servlet.JspServlet?
2008-01-02 10:11:55.659:/:INFO: default: init 2008-01-02
10:11:55.659:/:INFO: jsp: init 2008-01-02
10:11:55.691::INFO: Started SelectChannelConnector?@0.0.0.0:8080
and then I am not able to compile jsp. Do you know how to solve this
problem? Thank you
Comment by eelco.hillenius, Jan 02, 2008
Ah, I probably have to include the appropriate libs to turn JSP
support on. Could you please file a
ticket? I'll get to it shortly.
Eelco, could that discussion have anything to do with my problem?
-----Original Message-----
From: Martijn Dashorst [mailto:martijn.dashorst@gmail.com]
Sent: Thursday, June 12, 2008 1:23 AM
To: users@wicket.apache.org
Subject: Re: Tomcat 5.5.9 isn't running Quickstart
The quickstart works for me without modifications. It serves images,
etc. out of the box, every time.
Martijn
On Thu, Jun 12, 2008 at 12:54 AM, Frank Silbermann
<fr...@fedex.com> wrote:
> Searching for some clue as to why my modification of the QuickStart
> application is serving images when run in Tomcat but not when running
> in embedded Jetty via Eclipse, I found:
>
> http://osdir.com/ml/java.jetty.support/2003-03/msg00045.html -- titled
> "Re: Re: jetty can't find images: msg#00045"
>
> It says, "You need the webdefaults file because it sets up the Default
> servlet which is what serves static resources like images. You can
> also manually add the Default servlet if you want to avoid a
> webdefaults.xml file."
>
> I think this is a clue. Looking at the console log when running Jetty
> in Eclipse I see:
>
> INFO - log - NO JSP Support for /, did not
find
> org.apache.jasper.servlet.JspServlet
>
> So what do I need to do to make it set up the Default servlet? Is
> there a line I need to insert into Start.java to make it read the
> webdefaults.xml file? I don't even have a webdefaults.xml file --
> unless it's buried somewhere inside one of the Jetty jars.
>
> Here's the complete console log when debugging Start.java to bring up
> Jetty (as demonstrated in
> http://herebebeasties.com/2007-10-07/wicket-quickstart/).
>
> INFO - log - Logging to
> org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via
> org.mortbay.log.Slf4jLog
>>>> STARTING EMBEDDED JETTY SERVER, PRESS ANY KEY TO STOP
> INFO - log - jetty-6.1.4
> INFO - log - NO JSP Support for /, did not
find
> org.apache.jasper.servlet.JspServlet
> INFO - log - No Transaction manager found - if
> your webapp requires one, please configure one.
> INFO - Application - [TestApplication] init: Wicket
core
> library initializer
> INFO - RequestListenerInterface - registered listener interface
> [RequestListenerInterface name=IBehaviorListener, method=public
> abstract void
org.apache.wicket.behavior.IBehaviorListener.onRequest()]
> INFO - RequestListenerInterface - registered listener interface
> [RequestListenerInterface name=IBehaviorListener, method=public
> abstract void
org.apache.wicket.behavior.IBehaviorListener.onRequest()]
> INFO - RequestListenerInterface - registered listener interface
> [RequestListenerInterface name=IFormSubmitListener, method=public
> abstract void
> org.apache.wicket.markup.html.form.IFormSubmitListener.onFormSubmitted
> ()
> ]
> INFO - RequestListenerInterface - registered listener interface
> [RequestListenerInterface name=IFormSubmitListener, method=public
> abstract void
> org.apache.wicket.markup.html.form.IFormSubmitListener.onFormSubmitted
> ()
> ]
> INFO - RequestListenerInterface - registered listener interface
> [RequestListenerInterface name=ILinkListener, method=public abstract
> void org.apache.wicket.markup.html.link.ILinkListener.onLinkClicked()]
> INFO - RequestListenerInterface - registered listener interface
> [RequestListenerInterface name=ILinkListener, method=public abstract
> void org.apache.wicket.markup.html.link.ILinkListener.onLinkClicked()]
> INFO - RequestListenerInterface - registered listener interface
> [RequestListenerInterface name=IOnChangeListener, method=public
> abstract void
> org.apache.wicket.markup.html.form.IOnChangeListener.onSelectionChange
> d(
> )]
> INFO - RequestListenerInterface - registered listener interface
> [RequestListenerInterface name=IOnChangeListener, method=public
> abstract void
> org.apache.wicket.markup.html.form.IOnChangeListener.onSelectionChange
> d(
> )]
> INFO - RequestListenerInterface - registered listener interface
> [RequestListenerInterface name=IRedirectListener, method=public
> abstract void org.apache.wicket.IRedirectListener.onRedirect()]
> INFO - RequestListenerInterface - registered listener interface
> [RequestListenerInterface name=IRedirectListener, method=public
> abstract void org.apache.wicket.IRedirectListener.onRedirect()]
> INFO - RequestListenerInterface - registered listener interface
> [RequestListenerInterface name=IResourceListener, method=public
> abstract void
org.apache.wicket.IResourceListener.onResourceRequested()]
> INFO - RequestListenerInterface - registered listener interface
> [RequestListenerInterface name=IResourceListener, method=public
> abstract void
org.apache.wicket.IResourceListener.onResourceRequested()]
> INFO - Application - [TestApplication] init: Wicket
> extensions initializer
> INFO - WebApplication - [TestApplication] Started Wicket
> version 1.3.3 in development mode
> ********************************************************************
> *** WARNING: Wicket is running in DEVELOPMENT mode. ***
> *** ^^^^^^^^^^^ ***
> *** Do NOT deploy to your live server(s) without changing this. ***
> *** See Application#getConfigurationType() for more information. ***
> ********************************************************************
> INFO - log - Started
> SocketConnector@0.0.0.0:8080
>
>
>
>
>
> -----Original Message-----
> From: Frank Silbermann [mailto:frank.silbermann@fedex.com]
> Sent: Wednesday, June 11, 2008 4:41 PM
> To: users@wicket.apache.org
> Subject: RE: Tomcat 5.5.9 isn't running Quickstart
>
> It's the identical .war file which shows the images when run in Tomcat
> 6 but not when run in Jetty configured as per the QuickStart
application.
> The actual HTML in the rendered pages is exactly what I showed you --
> Wicket generated it using AttributeModifier, and I copied the
> generated HTML by doing "show source" in my browser.
>
> I'm guessing the Jetty has some default security not done in Tomcat
> that is "protecting" my image files, which I need to override somehow.
> Or maybe it is not automatically recognizing .png files as a
> MIME-type. Or maybe there's something else that must be configured in
> Jetty to tell it to look in the webapp folder for static content. I
> posted about this on the jetty-support mailing list last week
> (http://www.nabble.com/-Jetty-support--Embedded-jetty-td8400457.html#a
> 17
> 679320), but no one answered it.
>
> -----Original Message-----
> From: Gwyn Evans [mailto:gwyn.evans@gmail.com]
> Sent: Wednesday, June 11, 2008 3:51 PM
> To: users@wicket.apache.org
> Subject: Re: Tomcat 5.5.9 isn't running Quickstart
>
> On Wed, Jun 11, 2008 at 9:00 PM, Frank Silbermann <
> frank.silbermann@fedex.com> wrote:
>
>
>> 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:
>>
> ...
>
>> < img wicket:id="picture" src="image1.png" alt="Picture"/ >
>>
>> The image appears when I run the application in Tomcat, but not when
>> I
>
>> run it in Eclipse with Jetty
>
> ...
>
> That seems odd to me - the same web-app? I'm probably way off base,
> but I'd be double-checking where it's actually serving it from & the
> HTML in the rendered pages...
>
> /Gwyn
>
>
>> ...
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.3 is released Get it now:
http://www.apache.org/dyn/closer.cgi/wicket/1.3.3
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Tomcat 5.5.9 isn't running Quickstart
Posted by Martijn Dashorst <ma...@gmail.com>.
The quickstart works for me without modifications. It serves images,
etc. out of the box, every time.
Martijn
On Thu, Jun 12, 2008 at 12:54 AM, Frank Silbermann
<fr...@fedex.com> wrote:
> Searching for some clue as to why my modification of the QuickStart
> application is serving images when run in Tomcat but not when running in
> embedded Jetty via Eclipse, I found:
>
> http://osdir.com/ml/java.jetty.support/2003-03/msg00045.html -- titled
> "Re: Re: jetty can't find images: msg#00045"
>
> It says, "You need the webdefaults file because it sets up the Default
> servlet which is what serves static resources like images. You can also
> manually add the Default servlet if you want to avoid
> a webdefaults.xml file."
>
> I think this is a clue. Looking at the console log when running Jetty
> in Eclipse I see:
>
> INFO - log - NO JSP Support for /, did not find
> org.apache.jasper.servlet.JspServlet
>
> So what do I need to do to make it set up the Default servlet? Is there
> a line I need to insert into Start.java to make it read the
> webdefaults.xml file? I don't even have a webdefaults.xml file --
> unless it's buried somewhere inside one of the Jetty jars.
>
> Here's the complete console log when debugging Start.java to bring up
> Jetty (as demonstrated in
> http://herebebeasties.com/2007-10-07/wicket-quickstart/).
>
> INFO - log - Logging to
> org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via
> org.mortbay.log.Slf4jLog
>>>> STARTING EMBEDDED JETTY SERVER, PRESS ANY KEY TO STOP
> INFO - log - jetty-6.1.4
> INFO - log - NO JSP Support for /, did not find
> org.apache.jasper.servlet.JspServlet
> INFO - log - No Transaction manager found - if
> your webapp requires one, please configure one.
> INFO - Application - [TestApplication] init: Wicket core
> library initializer
> INFO - RequestListenerInterface - registered listener interface
> [RequestListenerInterface name=IBehaviorListener, method=public abstract
> void org.apache.wicket.behavior.IBehaviorListener.onRequest()]
> INFO - RequestListenerInterface - registered listener interface
> [RequestListenerInterface name=IBehaviorListener, method=public abstract
> void org.apache.wicket.behavior.IBehaviorListener.onRequest()]
> INFO - RequestListenerInterface - registered listener interface
> [RequestListenerInterface name=IFormSubmitListener, method=public
> abstract void
> org.apache.wicket.markup.html.form.IFormSubmitListener.onFormSubmitted()
> ]
> INFO - RequestListenerInterface - registered listener interface
> [RequestListenerInterface name=IFormSubmitListener, method=public
> abstract void
> org.apache.wicket.markup.html.form.IFormSubmitListener.onFormSubmitted()
> ]
> INFO - RequestListenerInterface - registered listener interface
> [RequestListenerInterface name=ILinkListener, method=public abstract
> void org.apache.wicket.markup.html.link.ILinkListener.onLinkClicked()]
> INFO - RequestListenerInterface - registered listener interface
> [RequestListenerInterface name=ILinkListener, method=public abstract
> void org.apache.wicket.markup.html.link.ILinkListener.onLinkClicked()]
> INFO - RequestListenerInterface - registered listener interface
> [RequestListenerInterface name=IOnChangeListener, method=public abstract
> void
> org.apache.wicket.markup.html.form.IOnChangeListener.onSelectionChanged(
> )]
> INFO - RequestListenerInterface - registered listener interface
> [RequestListenerInterface name=IOnChangeListener, method=public abstract
> void
> org.apache.wicket.markup.html.form.IOnChangeListener.onSelectionChanged(
> )]
> INFO - RequestListenerInterface - registered listener interface
> [RequestListenerInterface name=IRedirectListener, method=public abstract
> void org.apache.wicket.IRedirectListener.onRedirect()]
> INFO - RequestListenerInterface - registered listener interface
> [RequestListenerInterface name=IRedirectListener, method=public abstract
> void org.apache.wicket.IRedirectListener.onRedirect()]
> INFO - RequestListenerInterface - registered listener interface
> [RequestListenerInterface name=IResourceListener, method=public abstract
> void org.apache.wicket.IResourceListener.onResourceRequested()]
> INFO - RequestListenerInterface - registered listener interface
> [RequestListenerInterface name=IResourceListener, method=public abstract
> void org.apache.wicket.IResourceListener.onResourceRequested()]
> INFO - Application - [TestApplication] init: Wicket
> extensions initializer
> INFO - WebApplication - [TestApplication] Started Wicket
> version 1.3.3 in development mode
> ********************************************************************
> *** WARNING: Wicket is running in DEVELOPMENT mode. ***
> *** ^^^^^^^^^^^ ***
> *** Do NOT deploy to your live server(s) without changing this. ***
> *** See Application#getConfigurationType() for more information. ***
> ********************************************************************
> INFO - log - Started
> SocketConnector@0.0.0.0:8080
>
>
>
>
>
> -----Original Message-----
> From: Frank Silbermann [mailto:frank.silbermann@fedex.com]
> Sent: Wednesday, June 11, 2008 4:41 PM
> To: users@wicket.apache.org
> Subject: RE: Tomcat 5.5.9 isn't running Quickstart
>
> It's the identical .war file which shows the images when run in Tomcat 6
> but not when run in Jetty configured as per the QuickStart application.
> The actual HTML in the rendered pages is exactly what I showed you --
> Wicket generated it using AttributeModifier, and I copied the generated
> HTML by doing "show source" in my browser.
>
> I'm guessing the Jetty has some default security not done in Tomcat that
> is "protecting" my image files, which I need to override somehow. Or
> maybe it is not automatically recognizing .png files as a MIME-type. Or
> maybe there's something else that must be configured in Jetty to tell it
> to look in the webapp folder for static content. I posted about this on
> the jetty-support mailing list last week
> (http://www.nabble.com/-Jetty-support--Embedded-jetty-td8400457.html#a17
> 679320), but no one answered it.
>
> -----Original Message-----
> From: Gwyn Evans [mailto:gwyn.evans@gmail.com]
> Sent: Wednesday, June 11, 2008 3:51 PM
> To: users@wicket.apache.org
> Subject: Re: Tomcat 5.5.9 isn't running Quickstart
>
> On Wed, Jun 11, 2008 at 9:00 PM, Frank Silbermann <
> frank.silbermann@fedex.com> wrote:
>
>
>> 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:
>>
> ...
>
>> < img wicket:id="picture" src="image1.png" alt="Picture"/ >
>>
>> The image appears when I run the application in Tomcat, but not when I
>
>> run it in Eclipse with Jetty
>
> ...
>
> That seems odd to me - the same web-app? I'm probably way off base, but
> I'd be double-checking where it's actually serving it from & the HTML in
> the rendered pages...
>
> /Gwyn
>
>
>> ...
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.3 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.3
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: Tomcat 5.5.9 isn't running Quickstart
Posted by Frank Silbermann <fr...@fedex.com>.
Searching for some clue as to why my modification of the QuickStart
application is serving images when run in Tomcat but not when running in
embedded Jetty via Eclipse, I found:
http://osdir.com/ml/java.jetty.support/2003-03/msg00045.html -- titled
"Re: Re: jetty can't find images: msg#00045"
It says, "You need the webdefaults file because it sets up the Default
servlet which is what serves static resources like images. You can also
manually add the Default servlet if you want to avoid
a webdefaults.xml file."
I think this is a clue. Looking at the console log when running Jetty
in Eclipse I see:
INFO - log - NO JSP Support for /, did not find
org.apache.jasper.servlet.JspServlet
So what do I need to do to make it set up the Default servlet? Is there
a line I need to insert into Start.java to make it read the
webdefaults.xml file? I don't even have a webdefaults.xml file --
unless it's buried somewhere inside one of the Jetty jars.
Here's the complete console log when debugging Start.java to bring up
Jetty (as demonstrated in
http://herebebeasties.com/2007-10-07/wicket-quickstart/).
INFO - log - Logging to
org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via
org.mortbay.log.Slf4jLog
>>> STARTING EMBEDDED JETTY SERVER, PRESS ANY KEY TO STOP
INFO - log - jetty-6.1.4
INFO - log - NO JSP Support for /, did not find
org.apache.jasper.servlet.JspServlet
INFO - log - No Transaction manager found - if
your webapp requires one, please configure one.
INFO - Application - [TestApplication] init: Wicket core
library initializer
INFO - RequestListenerInterface - registered listener interface
[RequestListenerInterface name=IBehaviorListener, method=public abstract
void org.apache.wicket.behavior.IBehaviorListener.onRequest()]
INFO - RequestListenerInterface - registered listener interface
[RequestListenerInterface name=IBehaviorListener, method=public abstract
void org.apache.wicket.behavior.IBehaviorListener.onRequest()]
INFO - RequestListenerInterface - registered listener interface
[RequestListenerInterface name=IFormSubmitListener, method=public
abstract void
org.apache.wicket.markup.html.form.IFormSubmitListener.onFormSubmitted()
]
INFO - RequestListenerInterface - registered listener interface
[RequestListenerInterface name=IFormSubmitListener, method=public
abstract void
org.apache.wicket.markup.html.form.IFormSubmitListener.onFormSubmitted()
]
INFO - RequestListenerInterface - registered listener interface
[RequestListenerInterface name=ILinkListener, method=public abstract
void org.apache.wicket.markup.html.link.ILinkListener.onLinkClicked()]
INFO - RequestListenerInterface - registered listener interface
[RequestListenerInterface name=ILinkListener, method=public abstract
void org.apache.wicket.markup.html.link.ILinkListener.onLinkClicked()]
INFO - RequestListenerInterface - registered listener interface
[RequestListenerInterface name=IOnChangeListener, method=public abstract
void
org.apache.wicket.markup.html.form.IOnChangeListener.onSelectionChanged(
)]
INFO - RequestListenerInterface - registered listener interface
[RequestListenerInterface name=IOnChangeListener, method=public abstract
void
org.apache.wicket.markup.html.form.IOnChangeListener.onSelectionChanged(
)]
INFO - RequestListenerInterface - registered listener interface
[RequestListenerInterface name=IRedirectListener, method=public abstract
void org.apache.wicket.IRedirectListener.onRedirect()]
INFO - RequestListenerInterface - registered listener interface
[RequestListenerInterface name=IRedirectListener, method=public abstract
void org.apache.wicket.IRedirectListener.onRedirect()]
INFO - RequestListenerInterface - registered listener interface
[RequestListenerInterface name=IResourceListener, method=public abstract
void org.apache.wicket.IResourceListener.onResourceRequested()]
INFO - RequestListenerInterface - registered listener interface
[RequestListenerInterface name=IResourceListener, method=public abstract
void org.apache.wicket.IResourceListener.onResourceRequested()]
INFO - Application - [TestApplication] init: Wicket
extensions initializer
INFO - WebApplication - [TestApplication] Started Wicket
version 1.3.3 in development mode
********************************************************************
*** WARNING: Wicket is running in DEVELOPMENT mode. ***
*** ^^^^^^^^^^^ ***
*** Do NOT deploy to your live server(s) without changing this. ***
*** See Application#getConfigurationType() for more information. ***
********************************************************************
INFO - log - Started
SocketConnector@0.0.0.0:8080
-----Original Message-----
From: Frank Silbermann [mailto:frank.silbermann@fedex.com]
Sent: Wednesday, June 11, 2008 4:41 PM
To: users@wicket.apache.org
Subject: RE: Tomcat 5.5.9 isn't running Quickstart
It's the identical .war file which shows the images when run in Tomcat 6
but not when run in Jetty configured as per the QuickStart application.
The actual HTML in the rendered pages is exactly what I showed you --
Wicket generated it using AttributeModifier, and I copied the generated
HTML by doing "show source" in my browser.
I'm guessing the Jetty has some default security not done in Tomcat that
is "protecting" my image files, which I need to override somehow. Or
maybe it is not automatically recognizing .png files as a MIME-type. Or
maybe there's something else that must be configured in Jetty to tell it
to look in the webapp folder for static content. I posted about this on
the jetty-support mailing list last week
(http://www.nabble.com/-Jetty-support--Embedded-jetty-td8400457.html#a17
679320), but no one answered it.
-----Original Message-----
From: Gwyn Evans [mailto:gwyn.evans@gmail.com]
Sent: Wednesday, June 11, 2008 3:51 PM
To: users@wicket.apache.org
Subject: Re: Tomcat 5.5.9 isn't running Quickstart
On Wed, Jun 11, 2008 at 9:00 PM, Frank Silbermann <
frank.silbermann@fedex.com> wrote:
> 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:
>
...
> < img wicket:id="picture" src="image1.png" alt="Picture"/ >
>
> The image appears when I run the application in Tomcat, but not when I
> run it in Eclipse with Jetty
...
That seems odd to me - the same web-app? I'm probably way off base, but
I'd be double-checking where it's actually serving it from & the HTML in
the rendered pages...
/Gwyn
> ...
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: Tomcat 5.5.9 isn't running Quickstart
Posted by Frank Silbermann <fr...@fedex.com>.
It's the identical .war file which shows the images when run in Tomcat 6
but not when run in Jetty configured as per the QuickStart application.
The actual HTML in the rendered pages is exactly what I showed you --
Wicket generated it using AttributeModifier, and I copied the generated
HTML by doing "show source" in my browser.
I'm guessing the Jetty has some default security not done in Tomcat that
is "protecting" my image files, which I need to override somehow. Or
maybe it is not automatically recognizing .png files as a MIME-type. Or
maybe there's something else that must be configured in Jetty to tell it
to look in the webapp folder for static content. I posted about this on
the jetty-support mailing list last week
(http://www.nabble.com/-Jetty-support--Embedded-jetty-td8400457.html#a17
679320), but no one answered it.
-----Original Message-----
From: Gwyn Evans [mailto:gwyn.evans@gmail.com]
Sent: Wednesday, June 11, 2008 3:51 PM
To: users@wicket.apache.org
Subject: Re: Tomcat 5.5.9 isn't running Quickstart
On Wed, Jun 11, 2008 at 9:00 PM, Frank Silbermann <
frank.silbermann@fedex.com> wrote:
> 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:
>
...
> < img wicket:id="picture" src="image1.png" alt="Picture"/ >
>
> The image appears when I run the application in Tomcat, but not when I
> run it in Eclipse with Jetty
...
That seems odd to me - the same web-app? I'm probably way off base, but
I'd be double-checking where it's actually serving it from & the HTML in
the rendered pages...
/Gwyn
> ...
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Tomcat 5.5.9 isn't running Quickstart
Posted by Gwyn Evans <gw...@gmail.com>.
On Wed, Jun 11, 2008 at 9:00 PM, Frank Silbermann <
frank.silbermann@fedex.com> wrote:
> (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.)
If I recall, 1.2 would have been common-logging based, hence the appearance
of the slf4j jars with 1.3...
> 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:
>
...
> < img wicket:id="picture" src="image1.png" alt="Picture"/ >
>
> The image appears when I run the application in Tomcat, but not when I
> run it in Eclipse with Jetty
...
That seems odd to me - the same web-app? I'm probably way off base, but I'd
be double-checking where it's actually serving it from & the HTML in the
rendered pages...
/Gwyn
> ...
RE: Tomcat 5.5.9 isn't running Quickstart
Posted by Frank Silbermann <fr...@fedex.com>.
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:frank.silbermann@fedex.com]
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:igor.vaynberg@gmail.com]
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
<fr...@fedex.com> 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:igor.vaynberg@gmail.com]
> 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
> <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
>> 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
>> <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
>>> 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
>>> <fr...@fedex.com> wrote:
>>>> Any suggestions as to where I should look for clues?
>>>>
>>>> -----Original Message-----
>>>> From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
>>>> 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
>>>> <fr...@fedex.com> 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: users-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>
>>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> -
>>>> - To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> -
>>>> - To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: Tomcat 5.5.9 isn't running Quickstart
Posted by Frank Silbermann <fr...@fedex.com>.
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:igor.vaynberg@gmail.com]
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
<fr...@fedex.com> 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:igor.vaynberg@gmail.com]
> 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
> <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
>> 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
>> <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
>>> 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
>>> <fr...@fedex.com> wrote:
>>>> Any suggestions as to where I should look for clues?
>>>>
>>>> -----Original Message-----
>>>> From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
>>>> 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
>>>> <fr...@fedex.com> 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: users-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>
>>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> -
>>>> - To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> -
>>>> - To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Tomcat 5.5.9 isn't running Quickstart
Posted by Igor Vaynberg <ig...@gmail.com>.
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
<fr...@fedex.com> 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:igor.vaynberg@gmail.com]
> 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
> <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
>> 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
>> <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
>>> 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
>>> <fr...@fedex.com> wrote:
>>>> Any suggestions as to where I should look for clues?
>>>>
>>>> -----Original Message-----
>>>> From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
>>>> 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
>>>> <fr...@fedex.com> 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: users-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>
>>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> - To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> - To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: Tomcat 5.5.9 isn't running Quickstart
Posted by Frank Silbermann <fr...@fedex.com>.
Well, it suggests I should replace commons-logging-api.jar with
commons-logging-1.1-api.jar, but when I tried that Tomcat failed to
start up. Is there something else I need to do at the same time?
------------------------------
At the current date, Tomcat 5.5.16 is the current release. All releases
from version 4.1.x through 5.5.16 have a startup process that places
jarfile ${tomcat.home}/bin/commons-logging-api.jar in the system
classpath and then prevents any webapp from overriding the classes in
that jarfile. Effectively, all webapps behave as if "parent-first"
classloading were enabled for those classes.
This has some benefits; in particular it means that there are no
problems in these Tomcat versions with having multiple copies of the
commons-logging Log interface in the classpath (which avoids the "Log
does not implement Log" problem described elsewhere).
However it also means that no webapp can override the core
commons-logging classes by including an updated commons-logging jarfile
in WEB-INF/lib; any class already loaded via the container takes
priority. In particular, as Tomcat bundles logging 1.0.4 only, the new
diagnostics and memory-leak-prevention features of the 1.1 release will
not be available unless the container's library version is updated.
Because the commons-logging-api.jar in the container does not contain
any log-library-adapter classes, updated behaviour for these will be
seen when logging 1.1 is bundled in WEB-INF/lib. In particular, the
support for log4j's TRACE level will take effect without having to
update the container.
If you do wish to update Tomcat's version of commons-logging, then you
must use the commons-logging-1.1-api jar only, not the full jar. Classes
in the webapp cannot override classes loaded from the system classpath
set up during Tomcat's startup process, and logging adapters can only
see their matching concrete logging library if that library is available
in the same classpath. Bundling the full commons-logging jarfile (with
adapters) into the system classpath therefore means that logging
libraries (eg log4j) within WEB-INF/lib are not accessable.
Note that the behaviour described here only applies if the standard
Tomcat startup process is run. When Tomcat is embedded in a larger
framework (eg run embedded within an IDE) this may not apply.
-----Original Message-----
From: jcarman@carmanconsulting.com [mailto:jcarman@carmanconsulting.com]
On Behalf Of James Carman
Sent: Friday, June 06, 2008 2:50 PM
To: users@wicket.apache.org
Subject: Re: Tomcat 5.5.9 isn't running Quickstart
Our test/production servers are running Tomcat just fine. Check this
out and I think it'll help you:
http://commons.apache.org/logging/troubleshooting.html#Apache%20Tomcat
On Fri, Jun 6, 2008 at 3:44 PM, Frank Silbermann
<fr...@fedex.com> wrote:
>
>
> Documentation for the jcl-over-slf4j.jar () says it replaces
> commons-logging.jar -- which I cannot find anywhere in my Tomcat
> installation. All I've found is commons-logging-api.jar in the
> {Tomcat installation}/bin directory. When I do the replacement,
> Tomcat fails to start.
>
> I'm having trouble finding any documentation that specifically speaks
> of configuring Tomcat for this purpose. Hasn't _anyone_ made the
> Wicket
> 1.3 QuickStart project run in Tomcat? Yes, I plan to use Jetty for
> development, but I don't think my company's architecture committee has
> approved Jetty for deployment. It seems to me that I ought to be able
> to run a Java web application in any J2EE-compliant webserver.
>
> So, does this so
>
> -----Original Message-----
> From: jcarman@carmanconsulting.com
> [mailto:jcarman@carmanconsulting.com] On Behalf Of James Carman
> Sent: Friday, June 06, 2008 1:01 PM
> To: users@wicket.apache.org
> Subject: Re: Tomcat 5.5.9 isn't running Quickstart
>
> I would also check the tomcat/JCL documentation. I seem to
> remember there being some very specific instructions on one of their
> sites about this issue.
>
> On Fri, Jun 6, 2008 at 1:54 PM, Gwyn Evans
> <gw...@gmail.com> wrote:
> > That's a bit odd then... One thing you could try is adding
> in SLF4J's
> > jcl-over-slf4j.jar instead of any commons-logging jars. That
> would
> > redirect any Commons-Logging logging to SLF4J.
> >
> > (Personally I'd also be looking to go with James' suggestion
> of
> > switching to Jetty, as I find that to be both clearer to
> debug and
> > more forgiving in terms of class-loading issues, but that may
> not be
> > possible...)
> >
> > /Gwyn
> >
> > On Fri, Jun 6, 2008 at 5:31 PM, Frank Silbermann
> > <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
> >> 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
> >> <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
> >>> 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
> >>> <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
> >>>> 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
> >>>> <fr...@fedex.com> wrote:
> >>>>> Any suggestions as to where I should look for clues?
> >>>>>
> >>>>> -----Original Message-----
> >>>>> From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
> >>>>> 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
> >>>>> <fr...@fedex.com> 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:
> users-unsubscribe@wicket.apache.org
> >>>>>> For additional commands, e-mail:
> users-help@wicket.apache.org
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> ------------------------------------------------------------------
> >>>>> --
> >>>>> - To unsubscribe, e-mail:
> users-unsubscribe@wicket.apache.org
> >>>>> For additional commands, e-mail:
> users-help@wicket.apache.org
> >>>>>
> >>>>>
> >>>>>
> ------------------------------------------------------------------
> >>>>> --
> >>>>> - To unsubscribe, e-mail:
> users-unsubscribe@wicket.apache.org
> >>>>> For additional commands, e-mail:
> users-help@wicket.apache.org
> >>>>>
> >>>>>
> >>>>
> >>>>
> -------------------------------------------------------------------
> >>>> -- To unsubscribe, e-mail:
> users-unsubscribe@wicket.apache.org
> >>>> For additional commands, e-mail:
> users-help@wicket.apache.org
> >>>>
> >>>>
> >>>>
> -------------------------------------------------------------------
> >>>> -- To unsubscribe, e-mail:
> users-unsubscribe@wicket.apache.org
> >>>> For additional commands, e-mail:
> users-help@wicket.apache.org
> >>>>
> >>>>
> >>>
> >>>
> --------------------------------------------------------------------
> >>> - To unsubscribe, e-mail:
> users-unsubscribe@wicket.apache.org
> >>> For additional commands, e-mail:
> users-help@wicket.apache.org
> >>>
> >>>
> >>>
> --------------------------------------------------------------------
> >>> - To unsubscribe, e-mail:
> users-unsubscribe@wicket.apache.org
> >>> For additional commands, e-mail:
> users-help@wicket.apache.org
> >>>
> >>>
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >> For additional commands, e-mail:
users-help@wicket.apache.org
> >>
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >> For additional commands, e-mail:
users-help@wicket.apache.org
> >>
> >>
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Tomcat 5.5.9 isn't running Quickstart
Posted by James Carman <ja...@carmanconsulting.com>.
Our test/production servers are running Tomcat just fine. Check this
out and I think it'll help you:
http://commons.apache.org/logging/troubleshooting.html#Apache%20Tomcat
On Fri, Jun 6, 2008 at 3:44 PM, Frank Silbermann
<fr...@fedex.com> wrote:
>
>
> Documentation for the jcl-over-slf4j.jar () says it replaces
> commons-logging.jar -- which I cannot find anywhere in my Tomcat
> installation. All I've found is commons-logging-api.jar in the {Tomcat
> installation}/bin directory. When I do the replacement, Tomcat fails to
> start.
>
> I'm having trouble finding any documentation that specifically speaks of
> configuring Tomcat for this purpose. Hasn't _anyone_ made the Wicket
> 1.3 QuickStart project run in Tomcat? Yes, I plan to use Jetty for
> development, but I don't think my company's architecture committee has
> approved Jetty for deployment. It seems to me that I ought to be able
> to run a Java web application in any J2EE-compliant webserver.
>
> So, does this so
>
> -----Original Message-----
> From: jcarman@carmanconsulting.com
> [mailto:jcarman@carmanconsulting.com] On Behalf Of James Carman
> Sent: Friday, June 06, 2008 1:01 PM
> To: users@wicket.apache.org
> Subject: Re: Tomcat 5.5.9 isn't running Quickstart
>
> I would also check the tomcat/JCL documentation. I seem to
> remember there being some very specific instructions on one of their
> sites about this issue.
>
> On Fri, Jun 6, 2008 at 1:54 PM, Gwyn Evans
> <gw...@gmail.com> wrote:
> > That's a bit odd then... One thing you could try is adding in
> SLF4J's
> > jcl-over-slf4j.jar instead of any commons-logging jars. That
> would
> > redirect any Commons-Logging logging to SLF4J.
> >
> > (Personally I'd also be looking to go with James' suggestion
> of
> > switching to Jetty, as I find that to be both clearer to debug
> and
> > more forgiving in terms of class-loading issues, but that may
> not be
> > possible...)
> >
> > /Gwyn
> >
> > On Fri, Jun 6, 2008 at 5:31 PM, Frank Silbermann
> > <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
> >> 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
> >> <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
> >>> 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
> >>> <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
> >>>> 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
> >>>> <fr...@fedex.com> wrote:
> >>>>> Any suggestions as to where I should look for clues?
> >>>>>
> >>>>> -----Original Message-----
> >>>>> From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
> >>>>> 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
> >>>>> <fr...@fedex.com> 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:
> users-unsubscribe@wicket.apache.org
> >>>>>> For additional commands, e-mail:
> users-help@wicket.apache.org
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> ------------------------------------------------------------------
> >>>>> --
> >>>>> - To unsubscribe, e-mail:
> users-unsubscribe@wicket.apache.org
> >>>>> For additional commands, e-mail:
> users-help@wicket.apache.org
> >>>>>
> >>>>>
> >>>>>
> ------------------------------------------------------------------
> >>>>> --
> >>>>> - To unsubscribe, e-mail:
> users-unsubscribe@wicket.apache.org
> >>>>> For additional commands, e-mail:
> users-help@wicket.apache.org
> >>>>>
> >>>>>
> >>>>
> >>>>
> -------------------------------------------------------------------
> >>>> -- To unsubscribe, e-mail:
> users-unsubscribe@wicket.apache.org
> >>>> For additional commands, e-mail:
> users-help@wicket.apache.org
> >>>>
> >>>>
> >>>>
> -------------------------------------------------------------------
> >>>> -- To unsubscribe, e-mail:
> users-unsubscribe@wicket.apache.org
> >>>> For additional commands, e-mail:
> users-help@wicket.apache.org
> >>>>
> >>>>
> >>>
> >>>
> --------------------------------------------------------------------
> >>> - To unsubscribe, e-mail:
> users-unsubscribe@wicket.apache.org
> >>> For additional commands, e-mail:
> users-help@wicket.apache.org
> >>>
> >>>
> >>>
> --------------------------------------------------------------------
> >>> - To unsubscribe, e-mail:
> users-unsubscribe@wicket.apache.org
> >>> For additional commands, e-mail:
> users-help@wicket.apache.org
> >>>
> >>>
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >> For additional commands, e-mail: users-help@wicket.apache.org
> >>
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >> For additional commands, e-mail: users-help@wicket.apache.org
> >>
> >>
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: Tomcat 5.5.9 isn't running Quickstart
Posted by Frank Silbermann <fr...@fedex.com>.
Documentation for the jcl-over-slf4j.jar () says it replaces
commons-logging.jar -- which I cannot find anywhere in my Tomcat
installation. All I've found is commons-logging-api.jar in the {Tomcat
installation}/bin directory. When I do the replacement, Tomcat fails to
start.
I'm having trouble finding any documentation that specifically speaks of
configuring Tomcat for this purpose. Hasn't _anyone_ made the Wicket
1.3 QuickStart project run in Tomcat? Yes, I plan to use Jetty for
development, but I don't think my company's architecture committee has
approved Jetty for deployment. It seems to me that I ought to be able
to run a Java web application in any J2EE-compliant webserver.
So, does this so
-----Original Message-----
From: jcarman@carmanconsulting.com
[mailto:jcarman@carmanconsulting.com] On Behalf Of James Carman
Sent: Friday, June 06, 2008 1:01 PM
To: users@wicket.apache.org
Subject: Re: Tomcat 5.5.9 isn't running Quickstart
I would also check the tomcat/JCL documentation. I seem to
remember there being some very specific instructions on one of their
sites about this issue.
On Fri, Jun 6, 2008 at 1:54 PM, Gwyn Evans
<gw...@gmail.com> wrote:
> That's a bit odd then... One thing you could try is adding in
SLF4J's
> jcl-over-slf4j.jar instead of any commons-logging jars. That
would
> redirect any Commons-Logging logging to SLF4J.
>
> (Personally I'd also be looking to go with James' suggestion
of
> switching to Jetty, as I find that to be both clearer to debug
and
> more forgiving in terms of class-loading issues, but that may
not be
> possible...)
>
> /Gwyn
>
> On Fri, Jun 6, 2008 at 5:31 PM, Frank Silbermann
> <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
>> 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
>> <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
>>> 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
>>> <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
>>>> 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
>>>> <fr...@fedex.com> wrote:
>>>>> Any suggestions as to where I should look for clues?
>>>>>
>>>>> -----Original Message-----
>>>>> From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
>>>>> 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
>>>>> <fr...@fedex.com> 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:
users-unsubscribe@wicket.apache.org
>>>>>> For additional commands, e-mail:
users-help@wicket.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>>
------------------------------------------------------------------
>>>>> --
>>>>> - To unsubscribe, e-mail:
users-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail:
users-help@wicket.apache.org
>>>>>
>>>>>
>>>>>
------------------------------------------------------------------
>>>>> --
>>>>> - To unsubscribe, e-mail:
users-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail:
users-help@wicket.apache.org
>>>>>
>>>>>
>>>>
>>>>
-------------------------------------------------------------------
>>>> -- To unsubscribe, e-mail:
users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail:
users-help@wicket.apache.org
>>>>
>>>>
>>>>
-------------------------------------------------------------------
>>>> -- To unsubscribe, e-mail:
users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail:
users-help@wicket.apache.org
>>>>
>>>>
>>>
>>>
--------------------------------------------------------------------
>>> - To unsubscribe, e-mail:
users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail:
users-help@wicket.apache.org
>>>
>>>
>>>
--------------------------------------------------------------------
>>> - To unsubscribe, e-mail:
users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail:
users-help@wicket.apache.org
>>>
>>>
>>
>>
---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>>
---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Tomcat 5.5.9 isn't running Quickstart
Posted by James Carman <ja...@carmanconsulting.com>.
I would also check the tomcat/JCL documentation. I seem to remember
there being some very specific instructions on one of their sites
about this issue.
On Fri, Jun 6, 2008 at 1:54 PM, Gwyn Evans <gw...@gmail.com> wrote:
> That's a bit odd then... One thing you could try is adding in SLF4J's
> jcl-over-slf4j.jar instead of any commons-logging jars. That would
> redirect any Commons-Logging logging to SLF4J.
>
> (Personally I'd also be looking to go with James' suggestion of
> switching to Jetty, as I find that to be both clearer to debug and
> more forgiving in terms of class-loading issues, but that may not be
> possible...)
>
> /Gwyn
>
> On Fri, Jun 6, 2008 at 5:31 PM, Frank Silbermann
> <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
>> 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
>> <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
>>> 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
>>> <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
>>>> 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
>>>> <fr...@fedex.com> wrote:
>>>>> Any suggestions as to where I should look for clues?
>>>>>
>>>>> -----Original Message-----
>>>>> From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
>>>>> 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
>>>>> <fr...@fedex.com> 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: users-unsubscribe@wicket.apache.org
>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>> --------------------------------------------------------------------
>>>>> - To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>
>>>>>
>>>>> --------------------------------------------------------------------
>>>>> - To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Tomcat 5.5.9 isn't running Quickstart
Posted by Gwyn Evans <gw...@gmail.com>.
That's a bit odd then... One thing you could try is adding in SLF4J's
jcl-over-slf4j.jar instead of any commons-logging jars. That would
redirect any Commons-Logging logging to SLF4J.
(Personally I'd also be looking to go with James' suggestion of
switching to Jetty, as I find that to be both clearer to debug and
more forgiving in terms of class-loading issues, but that may not be
possible...)
/Gwyn
On Fri, Jun 6, 2008 at 5:31 PM, Frank Silbermann
<fr...@fedex.com> 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:igor.vaynberg@gmail.com]
> 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
> <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
>> 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
>> <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
>>> 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
>>> <fr...@fedex.com> wrote:
>>>> Any suggestions as to where I should look for clues?
>>>>
>>>> -----Original Message-----
>>>> From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
>>>> 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
>>>> <fr...@fedex.com> 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: users-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>
>>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> - To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> - To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: Tomcat 5.5.9 isn't running Quickstart
Posted by Frank Silbermann <fr...@fedex.com>.
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:igor.vaynberg@gmail.com]
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
<fr...@fedex.com> 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:igor.vaynberg@gmail.com]
> 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
> <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
>> 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
>> <fr...@fedex.com> wrote:
>>> Any suggestions as to where I should look for clues?
>>>
>>> -----Original Message-----
>>> From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
>>> 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
>>> <fr...@fedex.com> 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: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Tomcat 5.5.9 isn't running Quickstart
Posted by Igor Vaynberg <ig...@gmail.com>.
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
<fr...@fedex.com> 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:igor.vaynberg@gmail.com]
> 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
> <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
>> 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
>> <fr...@fedex.com> wrote:
>>> Any suggestions as to where I should look for clues?
>>>
>>> -----Original Message-----
>>> From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
>>> 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
>>> <fr...@fedex.com> 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: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: Tomcat 5.5.9 isn't running Quickstart
Posted by Frank Silbermann <fr...@fedex.com>.
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:jcompagner@gmail.com]
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 <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
> 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
> <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
>> 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
>> <fr...@fedex.com> wrote:
>>> Any suggestions as to where I should look for clues?
>>>
>>> -----Original Message-----
>>> From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
>>> 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
>>> <fr...@fedex.com> 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: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Tomcat 5.5.9 isn't running Quickstart
Posted by Johan Compagner <jc...@gmail.com>.
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 <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
> 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
> <fr...@fedex.com> 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:igor.vaynberg@gmail.com]
>> 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
>> <fr...@fedex.com> wrote:
>>> Any suggestions as to where I should look for clues?
>>>
>>> -----Original Message-----
>>> From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
>>> 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
>>> <fr...@fedex.com> 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: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: Tomcat 5.5.9 isn't running Quickstart
Posted by Frank Silbermann <fr...@fedex.com>.
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:igor.vaynberg@gmail.com]
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
<fr...@fedex.com> 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:igor.vaynberg@gmail.com]
> 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
> <fr...@fedex.com> wrote:
>> Any suggestions as to where I should look for clues?
>>
>> -----Original Message-----
>> From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
>> 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
>> <fr...@fedex.com> 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: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Tomcat 5.5.9 isn't running Quickstart
Posted by Igor Vaynberg <ig...@gmail.com>.
well, there you go, something funky with your logger jars
-igor
On Fri, Jun 6, 2008 at 9:03 AM, Frank Silbermann
<fr...@fedex.com> 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:igor.vaynberg@gmail.com]
> 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
> <fr...@fedex.com> wrote:
>> Any suggestions as to where I should look for clues?
>>
>> -----Original Message-----
>> From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
>> 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
>> <fr...@fedex.com> 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: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Tomcat 5.5.9 isn't running Quickstart
Posted by James Carman <ja...@carmanconsulting.com>.
Have you tried running it using Jetty? For development, this is
really nice, and it's setup "out of the box"
On Fri, Jun 6, 2008 at 11:39 AM, Frank Silbermann
<fr...@fedex.com> 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: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: Tomcat 5.5.9 isn't running Quickstart
Posted by Frank Silbermann <fr...@fedex.com>.
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:igor.vaynberg@gmail.com]
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
<fr...@fedex.com> wrote:
> Any suggestions as to where I should look for clues?
>
> -----Original Message-----
> From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
> 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
> <fr...@fedex.com> 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: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Tomcat 5.5.9 isn't running Quickstart
Posted by Igor Vaynberg <ig...@gmail.com>.
how about the tomcat log...
-igor
On Fri, Jun 6, 2008 at 8:49 AM, Frank Silbermann
<fr...@fedex.com> wrote:
> Any suggestions as to where I should look for clues?
>
> -----Original Message-----
> From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
> 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
> <fr...@fedex.com> 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: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: Tomcat 5.5.9 isn't running Quickstart
Posted by Frank Silbermann <fr...@fedex.com>.
Any suggestions as to where I should look for clues?
-----Original Message-----
From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
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
<fr...@fedex.com> 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: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Tomcat 5.5.9 isn't running Quickstart
Posted by Igor Vaynberg <ig...@gmail.com>.
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
<fr...@fedex.com> 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: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org