| commit | 6d95c936dfc7767f1cea23d1db98a8c7d7810378 | [log] [tgz] |
|---|---|---|
| author | Paul <paul@blueconic.com> | Thu Apr 18 14:27:47 2024 +0200 |
| committer | GitHub <noreply@github.com> | Thu Apr 18 14:27:47 2024 +0200 |
| tree | bb2788aa90975d0be8f983a1bc667e361f598760 | |
| parent | e7fdbb7774392b76bab23c44200fec654f565cf0 [diff] |
Add jetty websocket support to Jetty12 (#298)
* Update to latest Jetty 12.0.6 and add Jetty WebSocket bundles
This change makes it possible to use WebSockets via Felix HTTP Jetty 12 bundle.
There are still some strange things that need to be done to get it all to work, but that's for a separate change request/bug report.
* Update pom.xml
* Remove websocket client dependency
* Remove tag
* Update to jetty 12.0.7
* Update pom.xml
Update to 12.0.8
* Add example of how to register a servlet that can upgrade to a Jetty WebSocket
To try it out, deploy the whiteboard sample bundle to your OSGi environment and execute the following snippet in your Chrome console.
```
const websocket = new WebSocket("ws://localhost:8080/filtersample/websocket/example");
websocket.send("test");
```
* Send message for example as well
* Remove upgrade check, already done in super
* Extract abstract base class, which could be part of the Felix HTTP Jetty12 bundle.
This abstracts away all the ugly code currently required to make websockets work.The Apache Felix project is a collection of semi-related OSGi sub-projects that build and release individually.
The flagship project is the Apache Felix Framework which implements the OSGi Core R7 specification. The /framework directory contains the source and build tree for the OSGi-compliant framework implementation.
Directly related projects:
/main* - provides an executable jar that launches the Felix framework./log*/resolverSeveral sub-projects cover various OSGi Compendium specifications such as:
/configadmin/configurator/converter/coordinator/deploymentadmin/deviceaccess/scr*/eventadmin/http/http/io/metatype/prefs/upnp/useradmin/wireadminSeveral projects provide extra features to an OSGi runtime.
/bundlerepository - Bundle repository service./connect - A service registry that enables OSGi style service registry programs without using an OSGi framework./dependencymanager - A versatile java API, allowing to declaratively register, acquire, and manage dynamic OSGi services./fileinstall* - A utility to automatically install bundles from a directory./gogo - A command line shell, runtime and set of base commands for interacting with and introspecting an OSGi framework./healthcheck/* - An extensible framework to monitor the status of the OSGi container at runtime. (contains systemready)/inventory - Provides some mechanisms to get the current state of the system and therefore provides an inventory of the system./ipojo - A service component runtime aiming to simplify OSGi application development./jaas - Bundle to simplify JAAS usage within OSGi environment./logback - A simple integration of the OSGi R7 Log (1.4) service to Logback backend./metrics/osgi - Collecting and publishing metrics related to OSGi applications/rootcause - Finding the root cause of problems with OSGi declarative services components./utils - Utility classes for OSGi (intended for embedding within other bundles.)/webconsole* - Web Based Management Console for OSGi Frameworks.The /tools directory contains various build tools.
/tools/maven-bundle-plugin - A maven plugin for building OSGi bundles./tools/osgicheck-maven-plugin - Maven plugin for checking several OSGi aspects of your project.