Especially since it prints out the valid class name in the log message.

I suppose you can't post the WAR somewhere so I can have a poke?

-Ross

On Oct 12, 2009, at 8:41 PM, Timothy Perrett wrote:

>
> Nope, I've certainly only got 1 javax.servlet in my CP.
>
> Looking at the Jetty source:
>
> http://jetty.mortbay.com/xref/org/mortbay/jetty/servlet/FilterHolder.html#86
>
> It appears its using isAssignableFrom - the question is, that how can
> it find the filter class usually, and be fine, but not when its being
> called by the wrapper?
>
> Cheers, Tim
>
> On Oct 13, 1:26 am, Timothy Perrett <[email protected]> wrote:
>> Hey Ross,
>>
>> Thanks for the response - I'll just take a look; im using maven-shade
>> but thought id been careful about making sure i only had one
>> javax.servlet.... I'll just double check now.
>>
>> Cheers, Tim
>>
>> On Oct 13, 1:22 am, Ross Mellgren <[email protected]> wrote:
>>
>>
>>
>>> My top-of-the-brain guess would be that you have two servlet JARs in
>>> your classpath, and jetty is using one but your WAR is using  
>>> another.
>>
>>> Really weird error though, for sure.
>>
>>> -Ross
>>
>>> On Oct 12, 2009, at 8:14 PM, Timothy Perrett wrote:
>>
>>>> Hey guys,
>>
>>>> I've been having a crazy problem all day (and now into the  
>>>> extremely
>>>> late night). Basically, Jetty is throwing this error:
>>
>>>> jvm 1    | java.lang.IllegalStateException: class
>>>> net.liftweb.http.LiftFilter is not a javax.servlet.Filter
>>>> jvm 1    |      at org.mortbay.jetty.servlet.FilterHolder.doStart
>>>> (FilterHolder.java:88)
>>>> jvm 1    |      at org.mortbay.component.AbstractLifeCycle.start
>>>> (AbstractLifeCycle.java:50)
>>>> jvm 1    |      at  
>>>> org.mortbay.jetty.servlet.ServletHandler.initialize
>>>> (ServletHandler.java:662)
>>>> jvm 1    |      at org.mortbay.jetty.servlet.Context.startContext
>>>> (Context.java:140)
>>>> jvm 1    |      at  
>>>> org.mortbay.jetty.webapp.WebAppContext.startContext
>>>> (WebAppContext.java:1250)
>>>> jvm 1    |      at org.mortbay.jetty.handler.ContextHandler.doStart
>>>> (ContextHandler.java:517)
>>>> jvm 1    |      at org.mortbay.jetty.webapp.WebAppContext.doStart
>>>> (WebAppContext.java:467)
>>>> jvm 1    |      at org.mortbay.component.AbstractLifeCycle.start
>>>> (AbstractLifeCycle.java:50)
>>>> jvm 1    |      at org.mortbay.jetty.handler.HandlerWrapper.doStart
>>>> (HandlerWrapper.java:130)
>>>> jvm 1    |      at org.mortbay.jetty.Server.doStart(Server.java: 
>>>> 224)
>>>> jvm 1    |      at org.mortbay.component.AbstractLifeCycle.start
>>>> (AbstractLifeCycle.java:50)
>>>> jvm 1    |      at Launcher.main(Launcher.java:53)
>>>> jvm 1    |      at sun.reflect.NativeMethodAccessorImpl.invoke0 
>>>> (Native
>>>> Method)
>>>> jvm 1    |      at sun.reflect.NativeMethodAccessorImpl.invoke 
>>>> (Unknown
>>>> Source)
>>>> jvm 1    |      at sun.reflect.DelegatingMethodAccessorImpl.invoke
>>>> (Unknown Source)
>>>> jvm 1    |      at java.lang.reflect.Method.invoke(Unknown Source)
>>>> jvm 1    |      at org.tanukisoftware.wrapper.WrapperJarApp.run
>>>> (WrapperJarApp.java:358)
>>>> jvm 1    |      at java.lang.Thread.run(Unknown Source)
>>>> jvm 1    | 2009-10-13 01:10:12.781::INFO:  Started
>>>> [email protected]:9090
>>
>>>> I must confess, Im running a fairly specific config. Essentially I
>>>> have an executable WAR file that has a jetty launcher class  
>>>> inside -
>>>> its pretty sweet, and it works from the command line doing:
>>
>>>> java -jar myapp.war
>>
>>>> However, when I go to implement it with JWS I get this error.
>>
>>>> Any help would be really, really welcome
>>
>>>> Cheers, Tim
> >


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to