Inject ejb into class in war

[rkilcoyne.rkilcoyne.mac.com]

Having an issue with a null reference when injecting an EJB.

The following class is in a war file that depends upon a separate jar containing my DeviceService EJB:

@Path("/")
public class Rest {

     protected @Inject
     DeviceService deviceService;

     @Path("/test")
     @GET
     @Produces(MediaType.TEXT_PLAIN)
     public String getTestMessage() {
          return "Rest#getTestMessage()";
     }

     @Path("/test2")
     @GET
     @Produces(MediaType.TEXT_PLAIN)
     public String getTestMessage2() {
          return deviceService.getTestMessage();
     }
}

EJB Local interface:

@Local
public interface DeviceService {

     public String getTestMessage();

}

EJB Implementation:

public @Stateless
class DeviceServiceBean implements DeviceService {

     public DeviceServiceBean() {
     }

     @Override
     public String getTestMessage() {
          return "DeviceServiceBean#getTestMessage()";
     }

}

When executed via resteasy, the deviceService reference is null. My ejb jar contains the beans.xml file and properly registers my EJB. I'm not sure if this is a Weld or RESTeasy issue.

Suggestions are greatly appreciated!

Rick

[rkilcoyne.rkilcoyne.mac.com]

Moved the EJB into the war file -- made no difference.

I've tried many deployment combinations and even updated RESTeasy that comes with JBoss 6 M4 to 2.0.1.GA to no avail -- the Inject doesn't happen and I get a null reference.

WTF. Frustration now setting in.

[rkilcoyne.rkilcoyne.mac.com]

Does anyone have a working CDI/RESTeasy example?

[jharting]

Rick, are you using an empty web.xml? If so, can you provide a testcase for the issue?

Take a look at the resteasy-cdi testing application http://svn.jboss.org/repos/jbossas/trunk/resteasy-int/test/cdi-test-2 We test CDI injection with JAX-RS resources in the app.

[jharting]

Does your .war contain a beans.xml file?

[meetoblivion]

There's a few subtleties that the test case points out that aren't immediately clear to someone using rest.

1. Your rest resource needs to be scoped, most people just use @RequestScoped
2. EJB injection itself is a bit flakey right now.
3. I would probably throw out there that mileage varies based on your app server.  Above comments are based on GF v3.