You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2013/02/27 14:03:14 UTC
[jira] [Resolved] (FELIX-57) Determine proper use of javax.servlet
in HTTP Service
[ https://issues.apache.org/jira/browse/FELIX-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger resolved FELIX-57.
------------------------------------
Resolution: Won't Fix
Assignee: Felix Meschberger
This issue has been lying around all too long and now its probably time to just close it.
We keep the Servlet API 2.1 bundle around but development moved on to more recent API releases.
> Determine proper use of javax.servlet in HTTP Service
> -----------------------------------------------------
>
> Key: FELIX-57
> URL: https://issues.apache.org/jira/browse/FELIX-57
> Project: Felix
> Issue Type: Task
> Components: HTTP Service
> Reporter: Richard S. Hall
> Assignee: Felix Meschberger
> Priority: Minor
>
> Currently, we have javax.servlet 2.1 code in the Felix repository for the purposes of using it for the HTTP Service because it was thought that the HTTP Service was required to use javax.servlet 2.1. However, the conclusion of this thread seems to state otherwise:
> http://mail-archives.apache.org/mod_mbox/incubator-felix-dev/200511.mbox/%3c1042983247.20051121180750@aQute.se%3e
> As a result, the current HTTP Service implementation depends on Jetty 4.2.25 and javax.servlet 2.4, both of which are embedded inside the bundle JAR file. This is incorrect because Jetty 4.2.25 does not implement 2.4, so we actually need to use javax.servlet 2.3 for it, but I could not find it in ibiblio.
> So first, we need to find servlet 2.3 and add a dependency to it. If we decide to stick with javax.servlet 2.3, then we should remove 2.1 from the repo and just bundle-ize the javax.servlet 2.3 JAR from ibiblio or whereever. Then we can move the servlet API out of the HTTP Service bundle and import it as before.
--
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