[jetty-users] Re: Jetty 7.0.0.pre5 Issue running from script missing met

[Doug Daniels <daniels.douglas@xxxxxxxxx>]

We do plan on upgrading to the latest Jetty release eventually (but we're heavily invested in the old Suspend Servlet COMETD implementation using the pre Servlet 3.0 API).

is there a way to configure the order of the JETTY server's classpath, other than what seems like them being included alphabetically from the jars in the JETTY_HOME/lib folder, what's the best approach to include external libraries (we have some custom JAAS classes and logging classes).


~ doug daniels

• From: Jan Bartel <janb@xxxxxxxxxxx>
• Date: Tue, 18 Aug 2009 14:23:31 +1000
• Delivered-to: jetty-users@xxxxxxxxxxx

Doug,

Jetty-7.0.0.pre5 is now a dead branch, so you might like to try some
of the newer pre-releases at Eclipse - the most recent is RC3, but
as we speak we're doing an RC4. Here's the download link:

http://www.eclipse.org/jetty/downloads.php

In your pre5 distro, your jsp-2.1 directory should look like:
|-- ant-1.6.5.jar
|-- core-3.1.1.jar
|-- jsp-2.1-glassfish-9.1.1.B51.p0.jar
|-- jsp-2.1-jetty-7.0.0.pre5.jar
`-- jsp-api-2.1-glassfish-9.1.1.B51.p0.jar

The jsp-2.1-jetty-7.0.0.pre5.jar contains a bridging class from commons
logging as used in the jsp engine to the jetty logger. 

Jan

On Mon, Aug 17, 2009 at 9:44 PM, Doug Daniels <daniels.douglas@xxxxxxxxx> wrote:

I'm trying to run Jetty 7.0.0.pre5 from the command line (with some copied JSP and other jars into the JETTY lib directory so that it will be picked up at startup), and I'm receiving an error:
2009-08-17 21:17:10.539::WARN:  EXCEPTION
java.lang.NoSuchMethodException: com.sun.org.apache.commons.logging.LogFactory.setLogImplClassName(java.lang.String)
    at java.lang.Class.getDeclaredMethod(Class.java:1937)
    at org.mortbay.jetty.webapp.WebXmlConfiguration.initServlet(WebXmlConfiguration.java:656)
    at org.mortbay.jetty.webapp.WebXmlConfiguration.initWebXmlElement(WebXmlConfiguration.java:458)
    at org.mortbay.jetty.plus.webapp.AbstractConfiguration.initWebXmlElement(AbstractConfiguration.java:187)
    at org.mortbay.jetty.webapp.WebXmlConfiguration.initialize(WebXmlConfiguration.java:413)
    at org.mortbay.jetty.plus.webapp.AbstractConfiguration.initialize(AbstractConfiguration.java:135)
    at org.mortbay.jetty.webapp.WebXmlConfiguration.configureDefaults(WebXmlConfiguration.java:207)
    at org.mortbay.jetty.plus.webapp.AbstractConfiguration.configureDefaults(AbstractConfiguration.java:92)
    at org.mortbay.jetty.plus.webapp.Configuration.configureDefaults(Configuration.java:142)
    at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1195)
    at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:548)
    at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:348)
    at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
    at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:151)
    at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
    at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
    at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:151)
    at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
    at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
    at org.mortbay.jetty.Server.doStart(Server.java:222)
    at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
    at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:982)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.mortbay.start.Main.invokeMain(Main.java:218)
    at org.mortbay.start.Main.start(Main.java:564)
    at org.mortbay.start.Main.main(Main.java:136)

Has anyone every configured their classpath incorrectly and received this error. What is the proper Jar that contains the correct LogFactory (I'm searching my maven and eclipse classpath and cannot find it).



~ doug daniels