Hey Ross,
Just to close up this thread - you were exactly right. As it turns
out, the dependency tree was pulling in a special jetty servlet
implementation that I didn't know about.
After some dependency management everything worked perfectly!
Cheers, Tim
On 13 Oct 2009, at 15:25, Ross
Hooray! Three cheers for working code!
-Ross
On Oct 15, 2009, at 4:45 AM, Timothy Perrett wrote:
Hey Ross,
Just to close up this thread - you were exactly right. As it turns
out, the dependency tree was pulling in a special jetty servlet
implementation that I didn't know about.
After
Sorry Ross, I meant Java Service Wrapper! It was late and I must have
typed it wrong :-(
Any thoughts? Would it help if put together a rough sample?
Cheers
Tim
Sent from my iPhone
On 13 Oct 2009, at 02:21, Ross Mellgren dri...@gmail.com wrote:
Before I go barking up the wrong tree, by
Hey Naftoli,
I posted a link to the code that's throwing the error - seems to being
caused from isAssignableFrom.
I'm wondering if it's got anything to do with the servlet abstraction
stuff?
Cheers, Tim
Sent from my iPhone
On 13 Oct 2009, at 02:06, Naftoli Gugenheim naftoli...@gmail.com
Hey Ross,
Yeah i've used JSW before also and its been pretty good. However, i
got annoyed with it and found this:
http://yajsw.sourceforge.net/
Its really, really good - a lot more comprehensive that JSW and its
still free. yajsw FTW!
Cheers, Tim
On 13 Oct 2009, at 15:25, Ross Mellgren
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
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 dri...@gmail.com wrote:
My top-of-the-brain guess would be
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
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:
I cant really post the war im afraid, as its calling all manner of
services on some internal systems.
The strange thing with all of this is that it works when you execute:
java -jar myapp.war
Here's what you should need to just make a similar demo project:
Wouldn't know, but have you tried looking up the source code that
throws the exception? Is Jetty trying to do anything unusual?
On Mon, Oct 12, 2009 at 8:14 PM, Timothy Perrett
timo...@getintheloop.eu wrote:
Hey guys,
I've been having a crazy problem all day (and now into the extremely
late
Before I go barking up the wrong tree, by JWS you mean Java Web Start
or Java Web Services?
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:
12 matches
Mail list logo
