Details
-
Type:
Task
-
Status:
Closed
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: 2.0.0-RC2
-
Fix Version/s: 2.0.x Backlog
-
Component/s: Transport: HTTP(S) / Jetty
-
Labels:None
-
User impact:Medium
-
Similar Issues:
MULE-1821Upgrade Jetty versionMULE-1646Upgrade Jetty to 5.1.12MULE-3489Upgrade to Jetty 6.1.9MULE-3526Revert back to Jetty 5.1.9MULE-3525Move the servlet/jetty support to their own moduleMULE-4757Upgrade cometd libraries to 6.1.22MULE-3500Upgrade to CXF 2.1.1MULE-4454Upgrade Tanuki Wrapper for Mule 2.2.x and beyondMULE-1716Upgrade Woodstox to 3.2.1MULE-5326Upgrade the HTTP inbound endpoint server to use an NIO based server
Description
We should upgrade to Jetty 6 at some point. Not sure that this has to be done for Mule 2.0, but it definitely should be done by Mule 2.1. It shouldn't be that much work.
Issue Links
| Duplicate | |||
|---|---|---|---|
|
|||
Dan, please see the linked issue. Major hurdles were:
Note that we already successfully integrated Jetty into Mule (Mule acts as a web container then), though this is not a scenario we could apply to every user (override with newer libraries in lib/user). Take a look at http://www.mulesource.org/display/WEBCONTAINER/Home , maybe it helps.
- Java 5 dependency
- Servlet specification version conflicts
Note that we already successfully integrated Jetty into Mule (Mule acts as a web container then), though this is not a scenario we could apply to every user (override with newer libraries in lib/user). Take a look at http://www.mulesource.org/display/WEBCONTAINER/Home , maybe it helps.