felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sten Roger Sandvik (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-57) Determine proper use of javax.servlet in HTTP Service
Date Thu, 24 Sep 2009 20:52:16 GMT

    [ https://issues.apache.org/jira/browse/FELIX-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759249#action_12759249
] 

Sten Roger Sandvik commented on FELIX-57:
-----------------------------------------

The new http jetty bundle exports Servlet 2.5 API. Is this issue still valid? Can we close
it?

> 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/%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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message