[
https://issues.apache.org/jira/browse/FELIX-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582211#action_12582211
]
Felix Meschberger commented on FELIX-57:
----------------------------------------
Now that I implemented FELIX-55 and export the Servlet API 2.5 from the
http.jetty bundle, can we also close this issue. I think the resolution is
simple: We keep the servlet API 2.1 around for standards compliance reasonse
but we do not use it for http.jetty any more.
WDYT ?
> 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
> 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/[EMAIL
> PROTECTED]
> 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.
-
You can reply to this email to add a comment to the issue online.
