Use different JPA.persistence.xml in Eclipse depending on production or test environment

Question

We are working with gradle and have the default project structure:

/src
   /main
     /java
     /resources
       /META-INF
         persistence.xml
   /test
     /java
     /resources
       /META-INF
         persistence.xml

While we run our junit tests with gradle, all is fine (we do not have any special gradle configuration concerning source paths or the like): the persistence.xml from 'test' is used.

But if we try to run our junit tests with eclipse, always the peristence.xml from 'main' is used.

How can we configure eclipse to use the persistence.xml from 'main' for one launch configuration, but the persistence.xml from 'test' for all junit tests?

while thinking about different possible solutions the following additional problem showed itself: The same problem exists for all kinds of resources where I'd like to separate test from production (e.g. .json files in 'resources'). — Markus Frauenfelder, Aug 10 '15 at 15:32
Perhpas you should consider dependency injection framework, issues like this are easily solvable wiht Spring for example. — John, Aug 10 '15 at 18:45

score 1 · Accepted Answer · answered Aug 10 '15 at 15:37

1

Another thing to try, if this is a general problem about resources loaded from your classpath:

In Eclipse's project properties, Java Build Path->Order and Export, put your test folder above your src folder.

Then under Deployment Assembly, exclude your test folder

That will ensure that when you launch tests directly from within Eclipse, you will search the test folder first for classpath resources. But when you launch as a webapp instead, the test folders would be excluded from WEB-INF/classes.

answered Aug 10 '15 at 15:37

wrschneider

17,913
16
96
176

I'll try that at work ;-) WEB-INF/classes sounds like JEE stuff. I'm in a J2SE environment. – Markus Frauenfelder Aug 10 '15 at 16:22
My suggestion probably won't work then if it's all J2SE, and Eclipse is launching both your main method and unit tests directly rather than assembling a webapp first. – wrschneider Aug 10 '15 at 16:25
I'll be working with classpath definitions and their orders. I can imagine that this will work. In the worst case I'll have to duplicate some classpath stuff for the execution of the main method so that the 'main' classpath gets loaded first. – Markus Frauenfelder Aug 10 '15 at 16:28

score 0 · Answer 2 · answered Aug 10 '15 at 15:11

I've solved this problem with a single persistence.xml and different persistence units.

<persistence-unit name="MAIN">
  ...
</persistence-unit>

<persistence-unit app="TEST">
  ...
</persistence-unit>

Then in your app, you would inject the main persistence unit with

@PersistenceContext(name="MAIN", unitName="MAIN")
private EntityManager entityManager;

And for unit tests, you would explicitly create an EntityManager using the TEST persistence unit, and inject it manually into the object under test:

EntityManager em = Persistence.createEntityManagerFactory("TEST").createEntityManager();
bean.setEntityManager(em);

That was one possible solution I thought of myself. I just don't want to clutter my productive code (including resources) with test code. — Markus Frauenfelder, Aug 10 '15 at 15:30

Use different JPA.persistence.xml in Eclipse depending on production or test environment

2 Answers2

Linked