https://github.com/microbean/microbean-jersey-netty-cdi
Puts Jersey running on Netty inside a CDI 2.0 SE container.
https://github.com/microbean/microbean-jersey-netty-cdi
cdi java jersey microbean netty
Last synced: about 2 months ago
JSON representation
Puts Jersey running on Netty inside a CDI 2.0 SE container.
- Host: GitHub
- URL: https://github.com/microbean/microbean-jersey-netty-cdi
- Owner: microbean
- License: apache-2.0
- Created: 2019-06-15T18:40:24.000Z (almost 7 years ago)
- Default Branch: master
- Last Pushed: 2020-02-17T05:27:49.000Z (over 6 years ago)
- Last Synced: 2025-09-05T17:54:55.661Z (9 months ago)
- Topics: cdi, java, jersey, microbean, netty
- Language: Java
- Homepage: https://microbean.github.io/microbean-jersey-netty-cdi/
- Size: 1.22 MB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# microBean™ Jersey Netty CDI Integration
[](https://travis-ci.com/microbean/microbean-jersey-netty-cdi)
[](https://maven-badges.herokuapp.com/maven-central/org.microbean/microbean-jersey-netty-cdi)
The microBean™ Jersey Netty CDI Integration project integrates
[Jersey](https://jersey.github.io/) and [Netty](https://netty.io) into
[CDI 2.0](http://cdi-spec.org/) environments in an idiomatic way.
## Installation and Usage
Add this project as a `runtime`-scoped dependency in your CDI 2.0-based Maven project:
```
org.microbean
microbean-jersey-netty-cdi
0.4.0
runtime
```
Then [start a CDI SE
container](https://docs.jboss.org/cdi/api/2.0/javax/enterprise/inject/se/SeContainerInitializer.html).
Any [JAX-RS
applications](https://jax-rs.github.io/apidocs/2.1/javax/ws/rs/core/Application.html)
or resource classes found on the classpath will be served up by [Eclipse Jersey](https://projects.eclipse.org/projects/ee4j.jersey) and [Netty](https://netty.io/) on
`0.0.0.0` port `8080` by default, or port `443` by default if there is
an
[`SslContext`](https://netty.io/4.1/api/io/netty/handler/ssl/SslContext.html)
available to your CDI container. You can pass `host` and `port`
System properties (or source them from any other [microBean™
Configuration](https://microbean.github.io/microbean-configuration/)
[`Configuration`](https://microbean.github.io/microbean-configuration/apidocs/org/microbean/configuration/spi/Configuration.html)
instances) to change your application's endpoint.
HTTP 1.1 and HTTP/2 requests, including upgrades via [HTTP's upgrade
header](https://svn.tools.ietf.org/svn/wg/httpbis/specs/rfc7230.html#header.upgrade),
[ALPN](https://www.rfc-editor.org/rfc/rfc7301#page-2) or [prior
knowledge](https://http2.github.io/http2-spec/#known-http), are fully
supported.
## Related Projects
* [microBean™ Jersey Netty Integration](https://microbean.github.io/microbean-jersey-netty/)
* [microBean™ Jakarta RESTful Web Services CDI Integration](https://microbean.github.io/microbean-jaxrs-cdi/)
* [microBean™ Configuration API](https://microbean.github.io/microbean-configuration-api/)
* [microBean™ Configuration](https://microbean.github.io/microbean-configuration/)
* [microBean™ Configuration CDI](https://microbean.github.io/microbean-configuration-cdi/)