[ http://issues.apache.org/jira/browse/FELIX-57?page=comments#action_12375184 ]
Jeff McAffer commented on FELIX-57: ----------------------------------- yes, we are approaching this problem right now as people want ot have servlet 2.4 stuff around. We are leaning towards multiple versions of the same bundle symbolic name as this is most representative of what is going on. This does however cause various problems with different development infrastructures. For example, you have to start using CVS branches (not sure what the SVN setup would be) and PDE currently has some issues around support for multiple versions of the same plugin. We will seek to resolve those going forward and would like to establish the "norm" as this case will just keep coming up. > Determine proper use of javax.servlet in HTTP Service > ----------------------------------------------------- > > Key: FELIX-57 > URL: http://issues.apache.org/jira/browse/FELIX-57 > Project: Felix > 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. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
