Hi Jeremy, thanks for your post.
Jeremy Bauer wrote: > > According to the OpenJPA doc (section 1.3), "In order to enable > automatic runtime mapping, you must first list all your persistent > classes as described in Section 1, " Persistent Class List "." > But what about http://openjpa.apache.org/builds/1.2.0/apache-openjpa-1.2.0/docs/manual/ref_guide_pc.html#ref_guide_pc_pcclasses chapter 5, section 1 : "Unlike many ORM products, OpenJPA does not need to know about all of your persistent classes at startup." ? Maybe I don't understand it right, but doesn't that means, that at startup-time (= creating an entity manager) it is not necessary to have knowing about the entities? > props.put("openjpa.MetaDataFactory", > "jpa(Types=\"com.dvelop.esb.esbruntime.service.persistenceservice.impl.openjpa.domain.Statement\")"); > That sounds good, it is an option. But not yet what we want ;) Right now I'm trying get things to work with an orm.xml. With such a file you don't need "openjpa.MetaDataFactory"-property, do you? Cheers, Kevin -- View this message in context: http://n2.nabble.com/OpenJPA-doesn%27t-create-table-in-embedded-DerbyDB-tp1082390p1084359.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
