You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by "F. Da Costa Gomez" <dc...@fixed.com> on 2003/11/09 17:26:50 UTC
[Jetty startup] ExceptionInInitializerError
Hi,
I was wondering whether anybody can shed some light on the following
error I get when I try to start up Jetty.
Worked perfectly fine on Jetty Launcher 1.03 (& Eclipse 2.1.1)
Current setup is Launcher 1.07 & Eclipse 2.1.2.
All libs used are those within Tap 3.b3 (both in the project as well as
in the WEB-INF/lib).
Any suggestions appreciated.
TIA
Fermin DCG
17:21:04.819 EVENT
[main]org.mortbay.http.HttpServer.start(HttpServer.java:639)03> Starting
Jetty/4.2.11
17:21:05.550 EVENT
[main]org.mortbay.util.FileResource.<clinit>(FileResource.java:46)07>
Checking Resource aliases
17:21:06.211 EVENT
[main]org.mortbay.http.HttpContext.start(HttpContext.java:1815)05>
Started WebApplicationContext[/,Standard Tapestry Setup]
java.lang.ExceptionInInitializerError
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:308)
at java.lang.Class.newInstance(Class.java:261)
at org.mortbay.jetty.servlet.Holder.newInstance(Holder.java:176)
at org.mortbay.jetty.servlet.ServletHolder.start(ServletHolder.java:215)
at
org.mortbay.jetty.servlet.ServletHandler.initializeServlets(ServletHandler.java:436)
at
org.mortbay.jetty.servlet.WebApplicationHandler.initializeServlets(WebApplicationHandler.java:150)
at
org.mortbay.jetty.servlet.WebApplicationContext.start(WebApplicationContext.java:449)
at org.mortbay.http.HttpServer.start(HttpServer.java:663)
at com.iw.plugins.jettyrunner.PluginRunner.launch(PluginRunner.java:177)
at com.iw.plugins.jettyrunner.PluginRunner.main(PluginRunner.java:126)
Caused by: org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException: Class
org.apache.commons.logging.impl.Log4JCategoryLog does not implement Log
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:555)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:289)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:259)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:390)
at
org.apache.tapestry.ApplicationServlet.<clinit>(ApplicationServlet.java:131)
... 14 more
Caused by: org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException: Class
org.apache.commons.logging.impl.Log4JCategoryLog does not implement Log
at
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:420)
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:548)
... 18 more
Caused by: org.apache.commons.logging.LogConfigurationException: Class
org.apache.commons.logging.impl.Log4JCategoryLog does not implement Log
at
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:416)
... 19 more
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: [Jetty startup] ExceptionInInitializerError (SOLVED)
Posted by "F. Da Costa Gomez" <dc...@fixed.com>.
No worries, just don't make it too cool (you might spoil the audience ;-) )
If and when I encounter a bug(gy feature) I'll do just that.
Fermin
Geoff Longman wrote:
>Sorry I didn't respond in a timely fashion. Deep into a cool new (secret)
>feature.
>
>Also, could you add bugs to sf for the issues in the messages following the
>one below?
>
>thx,
>
>Geoff
>----- Original Message -----
>From: "F. Da Costa Gomez" <dc...@fixed.com>
>To: "Tapestry users" <ta...@jakarta.apache.org>
>Sent: Monday, November 10, 2003 1:08 PM
>Subject: Re: [Jetty startup] ExceptionInInitializerError (SOLVED)
>
>
>
>
>>Wiped the complete Eclipse installation & did everything from scratch.
>>Obviously my installation was stuffed so I guess one should take a
>>little care.
>>
>>Cheers
>>
>>F. Da Costa Gomez wrote:
>>
>>
>>
>>>Hi,
>>>
>>>I was wondering whether anybody can shed some light on the following
>>>error I get when I try to start up Jetty.
>>>Worked perfectly fine on Jetty Launcher 1.03 (& Eclipse 2.1.1)
>>>Current setup is Launcher 1.07 & Eclipse 2.1.2.
>>>All libs used are those within Tap 3.b3 (both in the project as well
>>>as in the WEB-INF/lib).
>>>
>>>Any suggestions appreciated.
>>>
>>>TIA
>>>Fermin DCG
>>>
>>>17:21:04.819 EVENT
>>>[main]org.mortbay.http.HttpServer.start(HttpServer.java:639)03>
>>>Starting Jetty/4.2.11
>>>17:21:05.550 EVENT
>>>[main]org.mortbay.util.FileResource.<clinit>(FileResource.java:46)07>
>>>Checking Resource aliases
>>>17:21:06.211 EVENT
>>>[main]org.mortbay.http.HttpContext.start(HttpContext.java:1815)05>
>>>Started WebApplicationContext[/,Standard Tapestry Setup]
>>>java.lang.ExceptionInInitializerError
>>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>>>Method)
>>> at
>>>
>>>
>>>
>sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAcces
>sorImpl.java:39)
>
>
>>> at
>>>
>>>
>>>
>sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstruc
>torAccessorImpl.java:27)
>
>
>>> at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
>>> at java.lang.Class.newInstance0(Class.java:308)
>>> at java.lang.Class.newInstance(Class.java:261)
>>> at org.mortbay.jetty.servlet.Holder.newInstance(Holder.java:176)
>>> at
>>>org.mortbay.jetty.servlet.ServletHolder.start(ServletHolder.java:215)
>>> at
>>>
>>>
>>>
>org.mortbay.jetty.servlet.ServletHandler.initializeServlets(ServletHandler.j
>ava:436)
>
>
>>> at
>>>
>>>
>>>
>org.mortbay.jetty.servlet.WebApplicationHandler.initializeServlets(WebApplic
>ationHandler.java:150)
>
>
>>> at
>>>
>>>
>>>
>org.mortbay.jetty.servlet.WebApplicationContext.start(WebApplicationContext.
>java:449)
>
>
>>> at org.mortbay.http.HttpServer.start(HttpServer.java:663)
>>> at
>>>com.iw.plugins.jettyrunner.PluginRunner.launch(PluginRunner.java:177)
>>> at
>>>
>>>
>com.iw.plugins.jettyrunner.PluginRunner.main(PluginRunner.java:126)
>
>
>>>Caused by: org.apache.commons.logging.LogConfigurationException:
>>>org.apache.commons.logging.LogConfigurationException:
>>>org.apache.commons.logging.LogConfigurationException: Class
>>>org.apache.commons.logging.impl.Log4JCategoryLog does not implement Log
>>> at
>>>
>>>
>>>
>org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.ja
>va:555)
>
>
>>> at
>>>
>>>
>>>
>org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.ja
>va:289)
>
>
>>> at
>>>
>>>
>>>
>org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.ja
>va:259)
>
>
>>> at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:390)
>>> at
>>>
>>>
>>>
>org.apache.tapestry.ApplicationServlet.<clinit>(ApplicationServlet.java:131)
>
>
>>> ... 14 more
>>>Caused by: org.apache.commons.logging.LogConfigurationException:
>>>org.apache.commons.logging.LogConfigurationException: Class
>>>org.apache.commons.logging.impl.Log4JCategoryLog does not implement Log
>>> at
>>>
>>>
>>>
>org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryI
>mpl.java:420)
>
>
>>> at
>>>
>>>
>>>
>org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.ja
>va:548)
>
>
>>> ... 18 more
>>>Caused by: org.apache.commons.logging.LogConfigurationException: Class
>>>org.apache.commons.logging.impl.Log4JCategoryLog does not implement Log
>>> at
>>>
>>>
>>>
>org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryI
>mpl.java:416)
>
>
>>> ... 19 more
>>>
>>>
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>
>>
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: [Jetty startup] ExceptionInInitializerError (SOLVED)
Posted by Geoff Longman <gl...@intelligentworks.com>.
Sorry I didn't respond in a timely fashion. Deep into a cool new (secret)
feature.
Also, could you add bugs to sf for the issues in the messages following the
one below?
thx,
Geoff
----- Original Message -----
From: "F. Da Costa Gomez" <dc...@fixed.com>
To: "Tapestry users" <ta...@jakarta.apache.org>
Sent: Monday, November 10, 2003 1:08 PM
Subject: Re: [Jetty startup] ExceptionInInitializerError (SOLVED)
> Wiped the complete Eclipse installation & did everything from scratch.
> Obviously my installation was stuffed so I guess one should take a
> little care.
>
> Cheers
>
> F. Da Costa Gomez wrote:
>
> > Hi,
> >
> > I was wondering whether anybody can shed some light on the following
> > error I get when I try to start up Jetty.
> > Worked perfectly fine on Jetty Launcher 1.03 (& Eclipse 2.1.1)
> > Current setup is Launcher 1.07 & Eclipse 2.1.2.
> > All libs used are those within Tap 3.b3 (both in the project as well
> > as in the WEB-INF/lib).
> >
> > Any suggestions appreciated.
> >
> > TIA
> > Fermin DCG
> >
> > 17:21:04.819 EVENT
> > [main]org.mortbay.http.HttpServer.start(HttpServer.java:639)03>
> > Starting Jetty/4.2.11
> > 17:21:05.550 EVENT
> > [main]org.mortbay.util.FileResource.<clinit>(FileResource.java:46)07>
> > Checking Resource aliases
> > 17:21:06.211 EVENT
> > [main]org.mortbay.http.HttpContext.start(HttpContext.java:1815)05>
> > Started WebApplicationContext[/,Standard Tapestry Setup]
> > java.lang.ExceptionInInitializerError
> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> > Method)
> > at
> >
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAcces
sorImpl.java:39)
> >
> > at
> >
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstruc
torAccessorImpl.java:27)
> >
> > at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
> > at java.lang.Class.newInstance0(Class.java:308)
> > at java.lang.Class.newInstance(Class.java:261)
> > at org.mortbay.jetty.servlet.Holder.newInstance(Holder.java:176)
> > at
> > org.mortbay.jetty.servlet.ServletHolder.start(ServletHolder.java:215)
> > at
> >
org.mortbay.jetty.servlet.ServletHandler.initializeServlets(ServletHandler.j
ava:436)
> >
> > at
> >
org.mortbay.jetty.servlet.WebApplicationHandler.initializeServlets(WebApplic
ationHandler.java:150)
> >
> > at
> >
org.mortbay.jetty.servlet.WebApplicationContext.start(WebApplicationContext.
java:449)
> >
> > at org.mortbay.http.HttpServer.start(HttpServer.java:663)
> > at
> > com.iw.plugins.jettyrunner.PluginRunner.launch(PluginRunner.java:177)
> > at
com.iw.plugins.jettyrunner.PluginRunner.main(PluginRunner.java:126)
> > Caused by: org.apache.commons.logging.LogConfigurationException:
> > org.apache.commons.logging.LogConfigurationException:
> > org.apache.commons.logging.LogConfigurationException: Class
> > org.apache.commons.logging.impl.Log4JCategoryLog does not implement Log
> > at
> >
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.ja
va:555)
> >
> > at
> >
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.ja
va:289)
> >
> > at
> >
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.ja
va:259)
> >
> > at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:390)
> > at
> >
org.apache.tapestry.ApplicationServlet.<clinit>(ApplicationServlet.java:131)
> >
> > ... 14 more
> > Caused by: org.apache.commons.logging.LogConfigurationException:
> > org.apache.commons.logging.LogConfigurationException: Class
> > org.apache.commons.logging.impl.Log4JCategoryLog does not implement Log
> > at
> >
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryI
mpl.java:420)
> >
> > at
> >
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.ja
va:548)
> >
> > ... 18 more
> > Caused by: org.apache.commons.logging.LogConfigurationException: Class
> > org.apache.commons.logging.impl.Log4JCategoryLog does not implement Log
> > at
> >
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryI
mpl.java:416)
> >
> > ... 19 more
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> >
> >
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: [Jetty startup] ExceptionInInitializerError (SOLVED)
Posted by "F. Da Costa Gomez" <dc...@fixed.com>.
Wiped the complete Eclipse installation & did everything from scratch.
Obviously my installation was stuffed so I guess one should take a
little care.
Cheers
F. Da Costa Gomez wrote:
> Hi,
>
> I was wondering whether anybody can shed some light on the following
> error I get when I try to start up Jetty.
> Worked perfectly fine on Jetty Launcher 1.03 (& Eclipse 2.1.1)
> Current setup is Launcher 1.07 & Eclipse 2.1.2.
> All libs used are those within Tap 3.b3 (both in the project as well
> as in the WEB-INF/lib).
>
> Any suggestions appreciated.
>
> TIA
> Fermin DCG
>
> 17:21:04.819 EVENT
> [main]org.mortbay.http.HttpServer.start(HttpServer.java:639)03>
> Starting Jetty/4.2.11
> 17:21:05.550 EVENT
> [main]org.mortbay.util.FileResource.<clinit>(FileResource.java:46)07>
> Checking Resource aliases
> 17:21:06.211 EVENT
> [main]org.mortbay.http.HttpContext.start(HttpContext.java:1815)05>
> Started WebApplicationContext[/,Standard Tapestry Setup]
> java.lang.ExceptionInInitializerError
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
>
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
>
> at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
> at java.lang.Class.newInstance0(Class.java:308)
> at java.lang.Class.newInstance(Class.java:261)
> at org.mortbay.jetty.servlet.Holder.newInstance(Holder.java:176)
> at
> org.mortbay.jetty.servlet.ServletHolder.start(ServletHolder.java:215)
> at
> org.mortbay.jetty.servlet.ServletHandler.initializeServlets(ServletHandler.java:436)
>
> at
> org.mortbay.jetty.servlet.WebApplicationHandler.initializeServlets(WebApplicationHandler.java:150)
>
> at
> org.mortbay.jetty.servlet.WebApplicationContext.start(WebApplicationContext.java:449)
>
> at org.mortbay.http.HttpServer.start(HttpServer.java:663)
> at
> com.iw.plugins.jettyrunner.PluginRunner.launch(PluginRunner.java:177)
> at com.iw.plugins.jettyrunner.PluginRunner.main(PluginRunner.java:126)
> Caused by: org.apache.commons.logging.LogConfigurationException:
> org.apache.commons.logging.LogConfigurationException:
> org.apache.commons.logging.LogConfigurationException: Class
> org.apache.commons.logging.impl.Log4JCategoryLog does not implement Log
> at
> org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:555)
>
> at
> org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:289)
>
> at
> org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:259)
>
> at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:390)
> at
> org.apache.tapestry.ApplicationServlet.<clinit>(ApplicationServlet.java:131)
>
> ... 14 more
> Caused by: org.apache.commons.logging.LogConfigurationException:
> org.apache.commons.logging.LogConfigurationException: Class
> org.apache.commons.logging.impl.Log4JCategoryLog does not implement Log
> at
> org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:420)
>
> at
> org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:548)
>
> ... 18 more
> Caused by: org.apache.commons.logging.LogConfigurationException: Class
> org.apache.commons.logging.impl.Log4JCategoryLog does not implement Log
> at
> org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:416)
>
> ... 19 more
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: [Jetty startup] ExceptionInInitializerError
Posted by "F. Da Costa Gomez" <dc...@fixed.com>.
Probably for Geoff:
I noticed that the Laucher (Profiler) update entry stays on the page
with the <repair> button whilst the 'normal' launcher does not.
Small other detail concerns the eclipseColorer plugin that is required.
There are two links nowadays:
1. http://colorer.sourceforge.net/ and
2. http://eclipsecolorer.sourceforge.net/index_profiler.html (I'm
assuming this is the one, version 0.5.29 is the one i'm using)
I'll continue (but am starting to consider grabbing a sandwich instead :-\ )
TIA,
Fermin
F. Da Costa Gomez wrote:
> Hi,
>
> I was wondering whether anybody can shed some light on the following
> error I get when I try to start up Jetty.
> Worked perfectly fine on Jetty Launcher 1.03 (& Eclipse 2.1.1)
> Current setup is Launcher 1.07 & Eclipse 2.1.2.
> All libs used are those within Tap 3.b3 (both in the project as well
> as in the WEB-INF/lib).
>
> Any suggestions appreciated.
>
> TIA
> Fermin DCG
>
> 17:21:04.819 EVENT
> [main]org.mortbay.http.HttpServer.start(HttpServer.java:639)03>
> Starting Jetty/4.2.11
> 17:21:05.550 EVENT
> [main]org.mortbay.util.FileResource.<clinit>(FileResource.java:46)07>
> Checking Resource aliases
> 17:21:06.211 EVENT
> [main]org.mortbay.http.HttpContext.start(HttpContext.java:1815)05>
> Started WebApplicationContext[/,Standard Tapestry Setup]
> java.lang.ExceptionInInitializerError
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
>
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
>
> at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
> at java.lang.Class.newInstance0(Class.java:308)
> at java.lang.Class.newInstance(Class.java:261)
> at org.mortbay.jetty.servlet.Holder.newInstance(Holder.java:176)
> at
> org.mortbay.jetty.servlet.ServletHolder.start(ServletHolder.java:215)
> at
> org.mortbay.jetty.servlet.ServletHandler.initializeServlets(ServletHandler.java:436)
>
> at
> org.mortbay.jetty.servlet.WebApplicationHandler.initializeServlets(WebApplicationHandler.java:150)
>
> at
> org.mortbay.jetty.servlet.WebApplicationContext.start(WebApplicationContext.java:449)
>
> at org.mortbay.http.HttpServer.start(HttpServer.java:663)
> at
> com.iw.plugins.jettyrunner.PluginRunner.launch(PluginRunner.java:177)
> at com.iw.plugins.jettyrunner.PluginRunner.main(PluginRunner.java:126)
> Caused by: org.apache.commons.logging.LogConfigurationException:
> org.apache.commons.logging.LogConfigurationException:
> org.apache.commons.logging.LogConfigurationException: Class
> org.apache.commons.logging.impl.Log4JCategoryLog does not implement Log
> at
> org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:555)
>
> at
> org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:289)
>
> at
> org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:259)
>
> at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:390)
> at
> org.apache.tapestry.ApplicationServlet.<clinit>(ApplicationServlet.java:131)
>
> ... 14 more
> Caused by: org.apache.commons.logging.LogConfigurationException:
> org.apache.commons.logging.LogConfigurationException: Class
> org.apache.commons.logging.impl.Log4JCategoryLog does not implement Log
> at
> org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:420)
>
> at
> org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:548)
>
> ... 18 more
> Caused by: org.apache.commons.logging.LogConfigurationException: Class
> org.apache.commons.logging.impl.Log4JCategoryLog does not implement Log
> at
> org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:416)
>
> ... 19 more
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org