expression language bean properties stop working

Can you try with a recent snapshot version of the plugin? There was a bug I found in Jasper (which is the JSP engine that Jetty uses) related to the bean expression language and I fixed it in the Jetty repository. Try it and see if that does the trick.

If not, please post the details of the exception or failure that you get. I tested with your example and could not induce a failure even after many repeated invocations.

I switched to the snapshot and the problem went away.

When it occurs, it throws no exceptions nor does jetty generate any log information pertaining to it.

Spoke too soon. Using the snapshot makes the submitted example work in my environment but my app under development continues to exhibit the problem. I can't create a simple example that demonstrates.

Switching back to beta12 makes the problem go away.

The difference between beta12 and beta14 is that beta12 always used the jsp2.0 implementation from Jasper (which is from Tomcat). In beta14 if you are are running with jdk1.5, we use the jsp2.1 implementation instead (which is actually the correct version of jsp for servlet 2.5 spec). It seems there is a bug in the jsp2.1 code from Jasper. If you can manage to come up with a small webapp that clearly demonstrates the problem, it would be best to raise it on the appropriate Tomcat issue tracker.

Can you explicitly delete the 2.1 JSP jars from lib. If this fixes your problem, then we know it is definitely an issue with the 2.1 jasper implementation from apache.

I removed jsp-2.1.jar and jsp-api-2.1.jar and the problem went away in beta 14

I have a similar issue and was suspicious the problem was related to JSP 2.1.
But rather then removing the jars, it would be better to set Jetty to explicitely use JSP 2.0 (even if being run on JDK 5.0).

So, I've opened another Jira (JETTY-73) for this issue.

Can you confirm if this is still a problem?

I tried to reproduce this with the JSP/Tag in the original report, but after hitting the JSP 1000 times, it's still evaluating the EL.

If anyone has a test app that fails on RC0, please attach it, or send it to me and I'll try and track down the issue.

Is there Mmaven 2 repository where I could try RC0 or the last snapshot (I'm facing this a similar problem by using the maven2-jetty6-plugin)?

Hi Greg,

In which Jetty version has it been fixed? Is there a new beta available at ibiblio?

– Felipe

Felipe,

The plugin jars are available from ibiblio. The version is 6.0.0rc0. Please also note that the plugin has changed it's prefix to just "jetty". You need to update your pom to use the new <artifactId>maven-jetty-plugin.

Hi again,

Ok, I've changed my POM and the problem persisted, so I decided to create a test-case: it's a simple jsp page that shows the request headers, using a tag file to change the CSS style of each line. As I didn't find a way to upload it here, I made it available on my ASF page:

http://people.apache.org/~felipeal/jetty52-test-case.zip

To test the issue, run 'mvn jetty:run' and try to access the site (http://localhost:8080/jetty52-test-case/); it should give you an error like this:

HTTP ERROR: 500

INTERNAL_SERVER_ERROR

RequestURI=/jetty52-test-case/index.jsp

Powered by Jetty://

If you run 'mvn install' and deploy it on Tomcat 5.x, it works fine...

You can also add the following profile in the POM (instead of deploying on Tomcat), and it will work:

<profile>
<id>jdk1.5</id>
<activation>
<jdk>!1.4</jdk>
</activation>
<dependencies>
<dependency>
<groupId>org.mortbay.jetty</groupId>
<artifactId>jsp-2.0</artifactId>
<version>6.0.0rc0</version>
<type>pom</type>
</dependency>
</dependencies>
</profile>
</profiles>