TransactionalInterceptor should be executed around other interceptors

[agori]

EJB interceptors of a transactional EJB bean should be executed inside the same transaction of the intercepted bean. In BeanTest this doesn't happen because it seems that the TransactionalInterceptor is executed before application specific interceptors.

If the application specific interceptor works with the EntityManager, you get

javax.persistence.TransactionRequiredException: no transaction is in progress

[carlosbarragan]

We need to take a look at this. Maybe we need global interceptors to achieve this functionality.

[bbq2100]

@carlosbarragan a word and a blow 😉 Please have a look in #10.

[agori]

This commit fixes the reported problem but opens another one: @ExcludeClassInterceptors is no more working and I suspect that per method EJB interceptors are not working as well.Thanks to the Murphy's Law, I have both ;)

[bbq2100]

Hi @agori, thx for your fast feedback :) I will asap fix my shortcomings.