How can I use derby in memory with jpa2?

I'm using Derby in memory for testing and my configuration is very close to yours Here is my persistence. Xml :? Xml version="1.0" encoding="UTF-8"?

> org.eclipse.persistence.jpa. PersistenceProvider com.acme. Foo com.acme.

Bar true Xml you think you are.

I'm using Derby in memory for testing and my configuration is very close to yours. Here is my persistence. Xml: org.eclipse.persistence.jpa.

PersistenceProvider com.acme. Foo com.acme. Bar true Where org.apache.

Derby:derby:jar:10.6.2.1 is on the classpath. Now two questions/suggestions: How do you know the database is persisted on disk? If it really does, make sure you're using the persistence.

Xml you think you are.

Add the following to your maven configuration org. Bernate hibernate-entitymanager 3.3.2. GA test org.apache.

Derby derby 10.5.3.0 test The following persistance. Xml works pretty well with hibernate. Org.hibernate.ejb.

BernatePersistence myapp.model.entities. Group myapp.model.entities. User true.

– simpatico Nov 6 '10 at 22:41 It definitely is possible, nothing forces you to switch to hibernate. The persistence provider has nothing to do with your issue IMO. – Pascal Thivent Nov 6 '10 at 22:58.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.