Thanks!
I tried again, setting persistence to use JTA transactions, and
specifying the connection using openjpa properties, instead of a
DataSource, and the problem turns out to be the DataSource: Geronimo
prefers to use Geronimo names to identify resources, and has arcane
procedures to
Hi Doug,
By setting openjpa.jdbc.SynchronizeMappings property to the value
you've specified, the schema should be created for you. You could try
enabling OpenJPA trace to see if there are any messages in the log
that may show whether there was a problem during the the schema
creation process. Th
I created a small test project in Eclipse (v 3.4.1) which I attempt to
deploy to a Geronimo (v 2.1.3) server, with the default OpenJPA 1.0.3
installed, running under OS X 10.5.5. There's only one entity class,
learn.eclipse.Person.
Using the first persistence-unit definition in my persist
