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