RESTEasy - Best practices to override service method to implement some generic logic across the different methods (like in servlet)

Question

Ex: I have some common logic across different resources

@Path("/rest")
public class AddUser {

   @GET
   @Path("/AddUser/{ext}/{userId}")
   @Produces(MediaType.APPLICATION_JSON)
    public String addUser(@PathParam("tenantId") String tenantId, @PathParam("userId") Integer userId) {

   //I have some common logic here

}


@Path("/newrest")
public class AddUser1 {   
    @GET
    @Path("/AddUser/{ext}/{userId}")
    @Produces(MediaType.APPLICATION_JSON)
        public String addDifferentUser(@PathParam("tenantId") String tenantId,              @PathParam("userId") Integer userId) {

      //I have same common logic here as well
  }

} 

Which class i can extend to overwrite common logic for bot the rest services?

Answer 1

Overriding Service method is not recommended Should I override service ?

Take a look @ ContainerRequestFilter An extension interface implemented by container request filters. You can handle your common logic here.

Answer 2

You should probably not have bussiness logic directly in the communication layer. Imagine adding soap interface using different technology it will be imposible to use any common entry point.

You'd rather write service class and call it wherever you need.