Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 306910

Summary: Support Servlet 3.0 API
Product: [RT] RAP Reporter: Rüdiger Herrmann <ruediger.herrmann>
Component: RWTAssignee: Project Inbox <rap-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: P1 CC: b.muskalla
Version: 1.3   
Target Milestone: 1.4 RC1   
Hardware: All   
OS: All   
Whiteboard:

Description Rüdiger Herrmann CLA 2010-03-24 04:08:38 EDT 
RWT should be able to run on servlet engines that implement the Servlet API in version 3.0 (see http://jcp.org/en/jsr/detail?id=315)
Comment 1 Benjamin Muskalla CLA 2010-07-20 06:54:10 EDT 
As JSR 315 already has it's final release and other vendors like GlassFish or Tomcat 7 already provide Reference implementations for Servlet 3.0, I'd suggest to try it out and bump the version constrains. Rüdiger, any objections?
Comment 2 Benjamin Muskalla CLA 2010-07-22 09:16:39 EDT 
Tested with Tomcat 7 and Glassfish 3, works as expected.

Committed the new version ranges to CVS HEAD.
Comment 3 Ralf Sternberg CLA 2011-04-23 18:05:56 EDT 
Currently our version range includes 3.0.0 as highest version. Not sure if this was on purpose or an oversight, but the upper edge should be either 3.1.0 (exclusive) or 4.0.0 (exclusive) to include newer minor versions.
Comment 4 Ralf Sternberg CLA 2011-05-16 15:25:45 EDT 
After discussion with Rüdiger, we decided to remove the upper bound for javax.servlet imports. It's unlikely that a new version would break RWT code within the foreseeable future. And as the Servlet API does not follow OSGi's versioning scheme, any upper bound would be just guessing.