Hello! i've realized initialization of jpa provider is not a part of the deploy process in tomEE (unlike glassfish, or jobss). Openjpa creates database schema at the first entitymanager call. I can reproduce this in a simple web-application too, but my main issue is integration testing.
I try to populate the database with test data before the test method. For example in arquillian i can do it at @before, but at this point the schema does not exist. Tried arquillian-persistence, and failed too. Is a switch somewhere to turn off this extra-lazy behaviour? -- View this message in context: http://openejb.979440.n4.nabble.com/jpa-extra-lazy-initialization-tp4663443.html Sent from the OpenEJB User mailing list archive at Nabble.com.
