[
https://issues.apache.org/jira/browse/FELIX-783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Walker reopened FELIX-783:
------------------------------
Just tried a 1.4 Felix build and it seems unfortunately the Jetty SSL engine
still needs 1.5 or above:
mpile]
[exec] [INFO] Compiling 8 source files to
E:\MiscProjs\felix\http.jetty\target\classes
[exec] [INFO]
------------------------------------------------------------------------
[exec] [ERROR] BUILD FAILURE
[exec] [INFO]
------------------------------------------------------------------------
[exec] [INFO] Compilation failure
[exec]
E:\MiscProjs\felix\http.jetty\src\main\java\org\apache\felix\http\jetty\Activator.java:[29,-1]
cannot access org.mortbay
.jetty.security.SslSelectChannelConnector
[exec] bad class file: C:\Documents and
Settings\robw\.m2\repository\org\mortbay\jetty\jetty-sslengine\6.1.14\jetty-sslengine-6
.1.14.jar(org/mortbay/jetty/security/SslSelectChannelConnector.class)
[exec] class file has wrong version 49.0, should be 48.0
I think we should re-open this issue and call a vote whether creating a JDK
1.5+ dependency is acceptable.
> Migrate HTTPS support to new Jetty NIO classes
> ----------------------------------------------
>
> Key: FELIX-783
> URL: https://issues.apache.org/jira/browse/FELIX-783
> Project: Felix
> Issue Type: Improvement
> Components: HTTP Service
> Reporter: Rob Walker
> Assignee: Marcel Offermans
> Priority: Minor
>
> The Jetty6 migration takes advantage of the new Jetty NIO socket classes but
> only for the HTTP port. There are also new NIO classes in Jetty for SSL
> sockets, which presumably will offer similar scalability and performance
> benefits.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
