Annotations do not work in Jetty

• Key: SHALE-317
• Type: Bug
• Status: Resolved
• Resolution: Fixed
• Priority: Minor
• Assignee: Craig McClanahan
• Reporter: sean schofield
• Component/s: Tiger
• Fix Version/s: 1.0.4

Description

Matthias was reporting problems with the Tiger annotations a while back and now I'm having problems with them when using the Jetty plugin. The managed beans are not available in EL expressions. Its most likely a problem on the Jetty side of things but if we can figure out what's going on here we could help users who are using Jetty.

Comments

[Craig McClanahan]

With commit r473877, I have committed enough hacks to get shale-test-tiger (including the tests that require the annotations to be recognized) with Jetty 6.0.1. However, there are enough weirdness left to look at (the only way to make it work so far is to replace Jetty's JSP compiler with one from Tomcat), and the fact that the usecases and sql-browser apps don't work yet, that I want to leave this issue open for a bit.

[Craig McClanahan]

At least part of the issue is that Jetty apparently does not recognize TLDs embedded in JAR files, contrary to the requirements of the JSP specification. Filed <http://jira.codehaus.org/browse/JETTY-170> against Jetty to track this.

Are we sure the TLD's aren't recognized? That supposedly was fixed in Jetty 6.x. I'm also not experiencing any problems using the MyFaces or RI implementations which both rely on listeners defined in the TLD.

[Craig McClanahan]

> Are we sure the TLD's aren't recognized? That supposedly was fixed in Jetty 6.x.

Try deploying any of our Shale examples with the Jetty 6.0.1 plugin, and you'll see the error message quoted in the message thread above, stating that the tag library with URI "http://java.sun.com/jsf/core" is not recognized (even though the myfaces-impl.jar file that contains it is present in WEB-INF/lib.

> I'm also not experiencing any problems using the MyFaces or RI implementations which both
> rely on listeners defined in the TLD.

So the actual problem is likely to be that TLD URIs are not recognized, rather than the TLDs not being scanned at all. That's still a bug, but its a different bug.

[Craig McClanahan]

As of Jetty 6.1.0rc1, the Jetty related problems appear to have been addressed. I was successfully able to run all the tests in shale-test-tiger, which includes extensive use of evaluating EL expressions and loading annotated managed beans (as well as regular ones). Therefore, I'm going to mark this issue as FIXED.