resteasy-netty4-cdi

[martinofcourse]

Is resteasy-netty4-cdi meant to work with SeBootstrap? I wasn't able to able to get it to work, unfortunately, and was wondering if I might be missing dependecies?

This doesn't work with SeBootstrap (resteasy-netty4-cdi)

      <dependencies>
        <dependency>
          <groupId>org.jboss.resteasy</groupId>
          <artifactId>resteasy-netty4-cdi</artifactId>
          <version>6.2.3.Final</version>
        </dependency>

        <dependency>
          <groupId>org.jboss.resteasy</groupId>
          <artifactId>resteasy-json-binding-provider</artifactId>
          <version>6.2.3.Final</version>
        </dependency>
      </dependencies>

while this works with SeBootstrap (resteasy-undertow-cdi)

      <dependencies>
        <dependency>
          <groupId>org.jboss.resteasy</groupId>
          <artifactId>resteasy-undertow-cdi</artifactId>
          <version>6.2.3.Final</version>
        </dependency>

        <dependency>
          <groupId>org.jboss.resteasy</groupId>
          <artifactId>resteasy-json-binding-provider</artifactId>
          <version>6.2.3.Final</version>
        </dependency>
      </dependencies>

By "doesn't work", I mean that @Inject-ed members are null.

[jamezp]

I'll have to look as I would expect it to work, but I've never tested it. I don't have any CDI integration tests as not all the embedded servers implement CDI.

That said, since we're now using JUnit 5, this should be an easy thing to add some tests for CDI and use tags to filter them.

[jamezp]

Okay, I'm seeing the same thing locally and this looks like a bug to me. I've filed https://issues.redhat.com/browse/RESTEASY-3584 for this.

[jamezp]

There seems to be a couple issues with this. The first is that the org.jboss.resteasy.plugins.server.netty.NettyJaxrsServer is the chosen implementation. This is caused by two factors. One that org.jboss.resteasy:resteasy-netty4-cdi does not provide a service implementation for org.jboss.resteasy.plugins.server.embedded.EmbeddedServer. The other is, even if the service file is provided the wrong one may be chosen.

The other issue is a CDI container is not started. It's the responsibility of the user to start a CDI container.

I'm not sure if we should support starting a CDI container or not. We could, but that does break backwards compatibility. We might be able to add an option to activate CDI to control the lifecycle from the org.jboss.resteasy.plugins.server.netty.cdi.CdiNettyJaxrsServer.

The current tests work by using the Arquillian CDI adaptor.