Hey, For each persistence unit you have an implementation backing it. This implementation is initialized by a PersistenceProvider implementation, which then creates the EntityManagerFactory, and so forth.
My question is, whether, in this process there are separate steps? If I were to, for example, use Hibernate, where would the schema generation occur? The reason I'm asking is to find out if there is a way, whether in each app on it's own, or collaborating, I can the schema DROPs happen first, and then the schema CREATEs, when using multiple persistence units. I understand that drop/create is not part of the spec, but this is purely out of curiosity. I modified Hibernate to do a DROP CASCADE to drop the tables, and this leaves a semi empty database after the tests were run. It's not a problem because it's only a test database and made from clean everytime the tests run. This just inspired some curiosity if such a thing would be at all possible. Quintin Beukes
