Configure Hibernate transactions only with Jersey API Annotations

Question

I want to use something similar to org.springframework.transaction.annotation.Transactional Spring that configures a Transaction only using only the Jersey API. Something similar to the code that follows below:

@Resource
private SessionFactory factory;

private Class<E> entity;

private String tableName;

public DataProvider(Class e) {
    this.entity = e;
    this.tableName = entity.getAnnotation(Table.class).name();
}

@Transactional(readOnly = true)
public E get(final Long ID) {
    return (E)factory.getCurrentSession().get(entity, ID);
}

@Transactional(readOnly = true)
public List<E> getAll() {
    Session s = factory.getCurrentSession();
    return s.createQuery("FROM " + tableName ).list();
}

It is possible?

Answer 1

No, it is not possible to do with Jersey control Hibernate transactions.

Understand that Jersey is made for REST communication and has nothing to do with Hibernate transaction.

You could use CDI to perform transaction control, but it has nothing to do with Jersey.

With CDI you need to create an Interceptor:

@Target({METHOD, TYPE})
@Retention(RetentionPolicy.RUNTIME)
@InterceptorBinding
public @interface Transaction {
    boolean readOnly() default true;
}

And then you would create your developer as:

@Interceptor @Transaction(readOnly = false)
public class MethodWithTransaction {

    @Inject
    private EntityManager entityManager;

    @AroundInvoke
    public Object manageTransaction(InvocationContext context) throws Exception{
        EntityTransaction transaction = null;
        try{
            transaction = entityManager.getTransaction();
            transaction.begin();
            Object methodResult = context.proceed();
            transaction.commit();
            return methodResult;
        } catch (Exception ex){
            if(transaction != null && transaction.isActive()){
                transaction.rollback();
            }

            throw ex;
        }finally {
            entityManager.close();
        }
    }
}

To use you would apply as:

@Transaction(readOnly = false)
public void fazAlgo(){
    //
}

The only difference is that you will need to create an Interceptor for when readonly is true.

Answer 2

If you’re using an application server like Wildfly, you can make your service also an EJB Stateless (add @Stateless at the top of the class), and all REST methods will automatically be involved in a transaction.

If not, why not? By who and looks, you will end up doing a manual integration that is already ready for use on Java EE servers "complete"...