Home/ Questions/Q 8013797
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-04T19:43:52+00:00

I have an JEE5 app using EJB3 with JPA. E.g I have some beans

  • 0

I have an JEE5 app using EJB3 with JPA. E.g I have some beans with 

@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)

I’d like to write some tests for those services. I know I can use embeddable container like OpenEJB, but as JPA is available in Java SE, I wonder if I can use it in testing?
Certainly I won’t have all the

@PersistenceContext, @PersistenceUnit, @TransactionAttribute

features available. So my question is if this is worth trying (hand-made transaction management and so on)? Or should I go with embedded container? I’m talking about integration tests (with real, but in-memory database), not about mocking all stuff around.

EDIT:

One more thing as I’m quite new to testing in embedded container. Is it possible to inject e.g. Mockito’s mock as an @EJB dependency to my bean under test? Or maybe it doesn’t make sense in this setup?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You can test a lot of things with Java SE / JPA. But there is a major part of what we call Integration Testing that will require massive amount of effort to mock up things, and some that just won’t be doable without Arquillian or similar help. Do you want your EJB transactional functionality/etc to be included among the things you test? If so you have to implement tests that lives in a transactional environment as close to production as possible. I strongly suggest using a ejb-testing-framework.

    • 0