ansaurus

Question

Jetty 7 hightide distribution, JSP and JSTL support

Answer 1

A:

java.lang.AbstractMethodError: javax.servlet.jsp.PageContext.getELContext()Ljavax/el/ELContext;

This exception basically means that the mentioned method cannot be found in the runtime classpath, while it was available in the compiletime classpath of either the class or one of its dependencies.

This method is introduced in JSP 2.1 which gets hand in hand with Servlet 2.5. Since Jetty 7 is supposed to support Servlet 2.5 and thus isn't the suspect here, the only cause can be that the web.xml is declared as Servlet 2.4 or lower instead of Servlet 2.5. So, to fix this particular problem, you need to declare your web.xml as at least Servlet 2.5. The <web-app> tag should look like this:

<web-app 
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
    xmlns="http://java.sun.com/xml/ns/javaee"
    xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" 
    xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
    id="YourWebAppID"
    version="2.5">

If that doesn't solve the problem, then the other cause is that the /WEB-INF/lib or even worse the /JRE/lib or /JRE/lib/ext is cluttered with appserver-specific libraries containing an older Servlet API version. E.g. servlet-api.jar from Tomcat or j2ee.jar or javaee.jar from Glassfish, etcetera. You'll need to clean up those classpath folders from any libraries which doesn't belong there, because they get precedence in classloading and will override the appserver's own libraries. Appserver-specific libraries belongs to the appserver in question, not to the webapp or JRE.

That said and apart from the actual problem, the @page attributes language="java" contentType="text/html; charset=utf-8" are all superfluous. The language already defaults to Java and the contentType already defaults to text/html and the charset will already be set to UTF-8 if you set pageEncoding="UTF-8". So the following is already sufficient:

<%@page pageEncoding="UTF-8" %>

BalusC 2010-03-28 23:26:20

My web.xml already uses the 2.5 version as shown above. No go.

Lior Cohen 2010-03-28 23:32:35

I updated my answer to include another possible cause.

BalusC 2010-03-28 23:38:19

Modified my <%@page directive to match your suggestions. Thanks. Still struggling with the main issue tho.

Lior Cohen 2010-03-28 23:38:29

No jar files are bundles into the .war file exported by eclipse.

Lior Cohen 2010-03-28 23:40:04

Sorry, I don't see another causes. Good luck with the problem. I'd be curious to the root cause though.

BalusC 2010-03-28 23:41:36

Thanks for the effort. I'll update this question when I find a solution (hopefully).

Lior Cohen 2010-03-28 23:43:18

Accepting the answer, no solution was found. Moved to GlassFish3 instead.

Lior Cohen 2010-04-28 16:13:35

Answer 2

A:

With Jetty 8, the situation is a bit different, in case this helps anyone.

For JSTL 1.2, rather surprisingly, the taglib has to be:

<%@ taglib prefix="c" uri="http://java.sun.com/jstl/core" %>

with JSTL 1.2 from (mavenishly):

 <dependency>
    <groupId>javax.servlet</groupId>
    <artifactId>jstl</artifactId>
    <version>1.2</version>
 </dependency>

I can't really explain why the URL lacks 'jsp', but it works this way.

bmargulies 2010-07-02 14:59:17

ansaurus

tags:

views:

answers:

Jetty 7 hightide distribution, JSP and JSTL support

related questions