Unable to start Jetty due to IS_SECURITY_ENABLED error

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Unsuccessful in starting up the plugin.

What is the expected output? What do you see instead?

008-02-03 22:28:41.864::WARN:  failed jsp
java.lang.NoSuchFieldError: IS_SECURITY_ENABLED
    at
org.apache.jasper.compiler.JspRuntimeContext.<init>(JspRuntimeContext.java:181)
    at org.apache.jasper.servlet.JspServlet.init(JspServlet.java:134)
    at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:433)
    at org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:256)
    at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
    at
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:612)
    at org.mortbay.jetty.servlet.Context.startContext(Context.java:139)
    at
org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1216)
    at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:509)
    at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:447)
    at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
    at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:117)
    at org.mortbay.jetty.Server.doStart(Server.java:222)
    at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
    at runjettyrun.Bootstrap.main(Bootstrap.java:76)

What version of the product are you using? On what operating system?

Eclipse 3.3.1.1
Mac OS X 10.5.1 
JDK 1.5.0_13

Please provide any additional information below.

FYI - Running my web application using mvn jetty6:run works fine.

Original issue reported on code.google.com by joe.c...@gmail.com on 4 Feb 2008 at 7:00

[GoogleCodeExporter]

I get the same error.
Searching google doesn't turn up anything but this page. :(

Original comment by michaelm...@gmail.com on 8 Apr 2008 at 7:25

[GoogleCodeExporter]

nothing? 
I have the same error... both in Ubuntu and Windows

Original comment by emore...@gmail.com on 25 Jun 2008 at 8:47

[GoogleCodeExporter]

What I ended up doing to get around this was to remove the jsp related jar 
files from
my classpath:

1) In Eclipse, go to Run menu->Open Run Dialog.
2) Click on your Jetty web application.
3) Click on the Classpath tab
4) Click on any jar files with jsp in the filename (i.e. jsp-2.1.jar or
jsp-api-2.1.jar) and click on the Remove button.

This allowed me to get up and going, and since my app doesn't use JSP, I was 
fine. 
If you're using JSP, then this workaround may not work.

Original comment by joe.c...@gmail.com on 25 Jun 2008 at 10:58

[GoogleCodeExporter]

I'm having this problem not within Eclipse but from the command line as well, 
using
the instructions provided by the Jetty people to use the Maven plugin and get 
JSP 2.0
compatibility.  It looks like there's still a 2.1/2.0 classpath conflict.

Original comment by mojo...@gmail.com on 27 Feb 2009 at 6:54

[GoogleCodeExporter]

Looks like a spec conflick , too.
As same , it's a old issue and still need more detail to verify it.

Original comment by tonylovejava on 11 Mar 2011 at 8:47

• Changed state: More-Info

[GoogleCodeExporter]

Original comment by tonylovejava on 1 Jul 2011 at 8:34

• Changed state: Invalid

[GoogleCodeExporter]

I also faced the same problem. Here is my solution. If you used Eclipse and 
faced this issue, try this. 
When you try to export your project into .jar runnable file, use the "Package 
required libraries into generated JAR" instead of "Extract required libraries 
into generated JAR". This worked for me and my jsp page runs well. 

By Haijie Wu

Original comment by bylikeha...@gmail.com on 10 Jul 2011 at 8:26

[GoogleCodeExporter]

Since the error class "org.apache.jasper.compiler.JspRuntimeContext" is a 
implemenation of Tomcat , 
it doesn't make sense when you run a Jetty webapp but using Tomcat lib.

It usually caused by using Server Runtime lib , 
by default we suggestion remove the server runtime lib and using Servlet API 
jar instead.

(We have documented this in GettingStarted wiki.)

Or not to use Run-Jetty-Run in this case if you really need Tomcat feature.

We will ignore all the runtime lib after next official build (1.3) , 
you could reference to Issue 54

Original comment by tonylovejava on 10 Jul 2011 at 9:01