Jetty 7.2+ container incorrectly identified as Jetty 7 container
----------------------------------------------------------------
Key: WELD-906
URL: https://issues.jboss.org/browse/WELD-906
Project: Weld
Issue Type: Bug
Components: Servlet Container Support
Affects Versions: 1.1.1.Final
Reporter: Ben Sommerville
Priority: Minor
Weld-servlet can identify a jetty 7.3 or 7.4 environment as a Jetty 7.0
environment
(similar problem to WELD-879 but for Jetty not tomcat)
In Listener.java it checks for a Jetty 7 container before checking for a Jetty
7.2+ container. The version 7 check looks for the presence of
org.eclipse.jetty.servlet.ServletHandler which is present (but not necessarily
visible) in all jetty 7.x environments. By default this class won't be found
in Jetty 7.2+, but in this case Weld won't actually work. To run Weld under
Jetty 7.2+ you need to expose some of the server classes that are normally
hidden, and if you don't explicitly exclude the ServletHandler class the
environment is detected as Jetty 7 not 7.2+
The suggested fix would be to reverse the order in which containers are checked
and check for JettyPost72Container before checking for JettyContainer
You can work around this issue by using META-INF/services to specify container
or setting the ServletHandler class as a server class so that the web app can't
see it
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
weld-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/weld-issues
