[
https://issues.apache.org/jira/browse/FELIX-6851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18099386#comment-18099386
]
Paul Rütter commented on FELIX-6851:
------------------------------------
[[email protected]] did you review the WebSocket examples for
both
[https://github.com/apache/felix-dev/blob/master/http/jetty/src/test/java/org/apache/felix/http/jetty/it/JakartaSpecificWebsocketIT.java]
and
[https://github.com/apache/felix-dev/blob/master/http/jetty/src/test/java/org/apache/felix/http/jetty/it/JettySpecificWebsocketIT.java?]
Those should work without having to expose anything.
> Adding a connector to the HTTP service
> --------------------------------------
>
> Key: FELIX-6851
> URL: https://issues.apache.org/jira/browse/FELIX-6851
> Project: Felix
> Issue Type: New Feature
> Components: HTTP Service
> Reporter: André Freyssinet
> Priority: Major
>
> We are using Felix and the Felix-http bundle (5.2.0) with various servlets
> and Jolokia. We also want to set up a WebSocket server; currently, we are
> forced to create a new `Server` instance to add the corresponding connector.
> This approach consumes significant resources, particularly by requiring a
> separate thread pool.
> Would it be possible to expose the `http-jetty` `Server` object as an OSGi
> service so that we can add our connector to the existing server?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
