[
https://jira.jboss.org/browse/WELD-729?page=com.atlassian.jira.plugin.sys...
]
Dan Allen resolved WELD-729.
----------------------------
Assignee: Dan Allen
Fix Version/s: 1.1.0.Beta3
(was: 1.1.0.CR1)
Resolution: Done
Safer to check server info string. Loading Jetty classes via the classloader is disabled
in the Eclipse version of Jetty.
The user will be required to configure different classes in jetty-web.xml to support Jetty
6, Jetty 7 and Jetty 8.
https://github.com/weld/core/pull/46
Servlet / listener / filter injection support for Jetty 7 and above
-------------------------------------------------------------------
Key: WELD-729
URL:
https://jira.jboss.org/browse/WELD-729
Project: Weld
Issue Type: Feature Request
Components: Servlet Container Support
Affects Versions: 1.1.0.Beta1
Reporter: Dan Allen
Assignee: Dan Allen
Fix For: 1.1.0.Beta3
Jetty changed it's packaging in version 7 when it moved to the Eclipse runtimes
project. Therefore, the following required class check only works in earlier versions of
Jetty.
private static final String JETTY_REQUIRED_CLASS_NAME =
"org.mortbay.jetty.servlet.ServletHandler";
boolean jetty = true;
try
{
Reflections.classForName(JETTY_REQUIRED_CLASS_NAME);
}
catch (IllegalArgumentException e)
{
jetty = false;
}
A second check should be performed for the class
org.eclipse.jetty.servlet.ServletHandler.
But then we have the issue that the WeldServletHandler extends a class only in Jetty 6.
So we'll likely need a special classifier for weld-servlet that runs on jetty 7 and
above.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira