Comments on: AOP – Spring – Hibernate Sessions for background threads / jobs

By: Alberto

Alberto — Sat, 19 May 2012 00:47:00 +0000

Thanks a lot!

By: Raul Raja

Raul Raja — Sat, 19 May 2012 20:34:00 +0000

@Alberto, AFAIK the TransactionInterceptor is used to declaratively configure pointcuts that will be surrounded by a transaction. For example methods of a given service. As far as the HibernateInterceptor in this post is mostly to open and close the session automatically in background threads. You should be able to use the TransactionInterceptor to provide a transaction when you think is necessary or @Transactional if you’d rather configure it with annotations.

By: Alberto

Alberto — Sat, 19 May 2012 02:20:00 +0000

Do you know the difference between HibernateInterceptor and TransactionInterceptor? I am trying to take over some code that is using TransactionInterceptor with the same purpose.

By: Raul Raja

Raul Raja — Sat, 19 May 2012 08:44:00 +0000

Nicolás, la parte importante del tutorial es que el contenedor de Spring es capaz de crear un proxy para tus servicios el cual abre y cierra el contexto de persistencia alreadedor de invocaciones en los metodos. En tu caso puedes obetner un proxy de “RequestJob” programaticamente de forma que la invocación del metodo a tu elección ya estaría dentro de las sessión de hibernate por ejemplo:

java.lang.Runnable

hibernateInterceptor

y lo obtienes:

applicationContext.getBean(“testBackgroundJobProxy”);

Buena suerte y ya me cuentas

By: Nicolás

Nicolás — Sat, 19 May 2012 08:19:00 +0000

Hola Raúl,

En mi caso estoy tratando de utilizar un pool de hilos para ejecutar tareas. java.util.concurrent). En mi caso quiero que se vayan resolviendo a medida que van llegando las tareas, no cada cierto período de tiempo.

Como puedo proveer mis workers su correspondiente sesión de Hibernate?

un pseudo-código de lo que quiero hacer sería el siguiente:

ExecutorService servicePool = Executors.newFixedThreadPool(10);

public void processJob(CustomJob job) {
…
servicePool.execute(new RequestJob(job.getId());
…
}

donde Request implementa la interfaz Runnable.

Desde ya, muchas gracias!
saludos

By: Raul Raja

Raul Raja — Sat, 19 May 2012 10:18:00 +0000

Lucas aslo if you’re using JPA you should be able to just inject the persistence context with:

@PersistenceContext
private EntityManager entityManager;

…

entityManager.createQuery(…).setParameter(“…”, …).getResultList();

By: Raul Raja

Raul Raja — Sat, 19 May 2012 10:12:00 +0000

Lucas, glad you found the answer and you found the post useful!

By: Lucas

Lucas — Sat, 19 May 2012 07:14:00 +0000

Hi Raul,
I found the answer to my own question, I should use autowiring which is what I was using before in my app:
@Autowired
private ObjectService object_service;
public void run() {
List objects = object_service.findAllObject();
}

Thank you for this useful post, seriously, I spent a lot of time trying to figure this out.
I’m sorry for clustering your page with questions.
Thanks once more,
Lucas

By: Lucas

Lucas — Sat, 19 May 2012 05:58:00 +0000

I am aware you posted this last year and I’m not as proficient with persistence as I would like to be.
On question I have is:
If you want to retrieve all the the rows from table A. How would you do that in TestBackgroundJobImpl.run()?

I really don’t know which way to go to get the session and to create a Criteria object.
Thanks in advance,
Lucas

By: Francesco Chicchiricco

Francesco Chicchiricco — Sat, 19 May 2012 07:12:00 +0000

Thanks for your post!

I’ve updated your source code to work with JPA 2.0: read at http://chicchiricco.blogspot.com/2011/07/aop-spring-jpa-for-background-threads.html.