Correct way to integrate JAX-RS with CDI?

I used to integrate services and DAO beans in Jersey REST resources, annotating them with @Path

following Java EE tutorial

In general, for JAX-RS to work with beans corporation, you need to annotate the bean class with @Path to convert it to the root resource class. You can use @Path annotation with stateless session beans and singleton POJO beans.

So my code was something like this:

@Path("/")
public class ServiceResource {
   @Inject
   private AccountService accountService;

   @GET
   @Path("/account/get")
   public Account getAccount(@QueryParam("id") String id) {
     return accountService.get(id);
   }
}

@javax.inject.Singleton
@Path("")
public class AccountService {
   public Account get(String id){...}
}

      

        
        
        
      

    

Now I started integrating Quartz Job into my application and I wanted to find a way to insert mine AccountService

inside jobs like this

public class AccountJob implements Job {
  @Inject
  private AccountService accountService;

  @Override
  public void execute(JobExecutionContext jec) throws JobExecutionException {
    accountService.updateAllAccounts();
  }
}

      

        
        
        
      

    

I found this answer that says to use DeltaSpike

to get the job done, so I added the following dependencies to mine pom.xml

and don't add more line of code for any class, i.e. invalidation AccountService

for mine Job

works fine

<dependency>
    <groupId>org.apache.deltaspike.modules</groupId>
    <artifactId>deltaspike-scheduler-module-api</artifactId>
    <version>1.7.2</version>
    <scope>compile</scope>
</dependency>
<dependency>
    <groupId>org.apache.deltaspike.modules</groupId>
    <artifactId>deltaspike-scheduler-module-impl</artifactId>
    <version>1.7.2</version>
    <scope>runtime</scope>
</dependency>
<dependency>
    <groupId>org.apache.deltaspike.cdictrl</groupId>
    <artifactId>deltaspike-cdictrl-api</artifactId>
    <version>1.7.2</version>
    <scope>compile</scope>
</dependency>
<dependency>
    <groupId>org.apache.deltaspike.cdictrl</groupId>
    <artifactId>deltaspike-cdictrl-weld</artifactId>
    <version>1.7.2</version>
    <scope>runtime</scope>
</dependency>

      

        
        
        
      

    

However , I realized that when I remove @Path("")

from AccountService

, its instance is still injected within within ServiceResource

, so I ask the following questions:

• Why did adding dependencies DeltaSpike
  
  allow injecting my beans without being used @Path
  
  on them?
• Looking for more, I figured out what is DeltaSpike
  
  using Weld
  
  for internal injection, and since I already use GlassFish 4.0
  
  , I know that it Weld
  
  already exists, so why doesn't injection work by default in the class Job
  
  and in the class ServiceResource
  
  without adding @Path
  
  to my beans? In fact, why is the addition @Path
  
  even suggested in the Java tutorial?
• Are there any bad side effects that I don't see in my code because I think I am mixing several DI methods here without understanding how they work?

Update: . After more searching, I realize that it Jersey

does not use Weld

for dependency injection, instead it uses HK2

, another structure which also turns out to be part of GlassFish

, when I try to inject AccountService

without using @Path

it shows the following exception

org.glassfish.hk2.api.UnsatisfiedDependencyException: There was no object to inject in SystemInjecteeImpl (requiredType = AccountService , parent = ServiceResource , qualifiers = {} ...

So this updates the questions to the following:

• How to do injections HK2
  
  ? // Without using @Path
  
  as pointed out in the Java EE tutorial
• If I was able to do DI
  
  with using HK2
  
  , can I use Quartz DeltaSpike
  
  to execute DI
  
  for the job? Can I mix two CDI fluids together to scan classes and inject?

I have put my source code on pastebin; pom.xml

here and Java

here