You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Richard S. Hall (JIRA)" <ji...@apache.org> on 2008/01/08 16:57:34 UTC

[jira] Commented: (FELIX-55) Look at migration to more recent Jetty version

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

Richard S. Hall commented on FELIX-55:
--------------------------------------

One issue we had with upgrading to newer versions of Jetty was support for earlier JVMs. Currently, we use a version of Jetty compiled for JDK 1.2 so that our HTTP Service can run on older JVMs. I guess this is not a hard constraint, but it is nice.

I did commit to my sandbox a simple file-based HTTP Service that we could think about using as a foundation for a lightweight HTTP Service implementation if we cannot maintain backwards compatibility.

> Look at migration to more recent Jetty version
> ----------------------------------------------
>
>                 Key: FELIX-55
>                 URL: https://issues.apache.org/jira/browse/FELIX-55
>             Project: Felix
>          Issue Type: Improvement
>          Components: HTTP Service
>            Reporter: Rob Walker
>            Assignee: Rob Walker
>         Attachments: FELIX-55.patch
>
>
> - Look at the issues and effort involved in migrating to a more recent version of Jetty. Most likely the latest Jetty6 would be considered, since this has architectural changes over Jetty5 and hence we'd be upgrading to the latest greatest Jetty internals and APIs
> - Check backwards compatibility against existing (limited) set of cases in test bundle
> - enlist help from others with bundles using HttpService for more extensive testing

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.