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 use JNDI names.
I gave up (for now) on trying to use JNDI names with Geronimo.
Unfortunately, this means I need a different persistence.xml file for
Geronimo. :-(
On Oct 27, 2008, at 1:19 PM, Jeremy Bauer wrote:
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. There also could be a schema mismatch or other
config issue. The trace may help determine that as well.
Full trace can typically be enabled with the following property,
unless Geronimo overrides the default trace facility/configuration.
<property name="openjpa.Log" value="DefaultLevel=TRACE"/>
-Jeremy
