Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 546010 - Servlet Bridge cannot be used in a servlet 3.1 container
Summary: Servlet Bridge cannot be used in a servlet 3.1 container
Status: CLOSED DUPLICATE of bug 545682
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Server-Side (show other bugs)
Version: 4.11   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: equinox.server-side-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-01 10:25 EDT by Arnaud MERGEY CLA
Modified: 2019-04-04 09:37 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Arnaud MERGEY CLA 2019-04-01 10:25:41 EDT 
Deploying a servlet bridge war application on a servlet 3.1 container like tomcat 8.5, the application cannot start and complains about missing requirement:

Could not resolve module: org.eclipse.equinox.http.servlet [191]
Unresolved requirement: Import-Package: javax.servlet; version="[3.1.0,5.0.0)"  

For a 3.1 servlet container org.eclipse.equinox.servletbridge.FrameworkLauncher export javax.servlet with 2.7 version.

It used to work in 2018-12 because org.eclipse.equinox.http.servlet required javax.servlet 2.3, but since 2019-03, org.eclipse.equinox.http.servlet requires javax.servlet 3.1. 

I am not sure where the bug is really located, I mean  org.eclipse.equinox.http.servlet could required 2.7, but it seems strange. 
org.eclipse.equinox.servletbridge.FrameworkLauncher should export the real servlet version of the container.
Comment 1 Thomas Watson CLA 2019-04-04 09:37:17 EDT 
See discussion in bug 545682.

*** This bug has been marked as a duplicate of bug 545682 ***