[
https://issues.apache.org/jira/browse/FELIX-3631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved FELIX-3631.
--------------------------------------
Resolution: Won't Fix
I don't think it is worth it doing it. We are embedding the Jetty Server in the
Http Service bundle; so to use a separate Servlet API bundle the Jetty Servlet
API bundle can as well be used.
This would be (in Maven Speak):
<dependency>
<groupId>org.eclipse.jetty.orbit</groupId>
<artifactId>javax.servlet</artifactId>
<version>2.5.0.v201103041518</version>
</dependency>
So I think we can resolve this as wontfix
> Create separate Servlet API Bundle
> ----------------------------------
>
> Key: FELIX-3631
> URL: https://issues.apache.org/jira/browse/FELIX-3631
> Project: Felix
> Issue Type: Task
> Components: HTTP Service
> Affects Versions: http-2.2.0
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
>
> The Serlvet API is currently exported from the Jetty bundle. This creates a
> problematic wiring to the servlet API implementation putting unneeded load on
> the system in case of Jetty update.
> Consider a Web Application server like Apache Sling where almost all bundles
> directly or indirectly import the Servlet API. In this case the bundle
> exporting the Servlet API becomes like a bottleneck. Rewiring the Servlet API
> exporter causes all direct and indirect consumers to be rewired. This is
> detrimental to the overall system.
> The solution is:
> (a) not export Servlet API from the Jetty bundle
> (b) create a separate bundle exporting Servlet API
> The Servlet API must not be exported by the Http Service API bundle because
> the Servlet API bundle is not needed in a bridged deployment (using the Http
> Service bridge) but the Http Service API is.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
