Seam (EJB3/JSF) App Deploys - but tables are not created, populated

Question

Please let me know if you've run across this or have an inkling of an idea of what is going on here.
Description: I have created the JDBC Data Source and this deploys successfully. The JNDI Name for this data source is: "seam-jee5-ds".
I am using this JDNI name as the data source in my persistence.xml for the application. This data source is found when the application deploys. The data source itself is an embedded HSQLDB database, but I have also tried this with H2 and the result is the same.
The application works, I can open the page...but anytime there is a transaction with the database, the transaction fails. The error is that it can't find the table to query from, and fails w/ this exception:
javax.el.ELException: javax.ejb.EJBTransactionRolledbackException: EJB Exception: ; nested exception is: javax.persistence.PersistenceException: org.h
ibernate.exception.SQLGrammarException: could not execute query; nested exception is: javax.persistence.PersistenceException: org.hibernate.exception.
SQLGrammarException: could not execute query
+Caused by: java.sql.SQLException: Table not found in statement [select user0_.username as username2_, user0_.name as name2_, user0_.password as passwo+
+rd2_ from Customer user0_ where user0_.username=? and user0_.password=?]+
at org.hsqldb.jdbc.Util.throwError(Unknown Source)
The EJBs are recognized/discovered; example:
Aug 15, 2009 7:35:29 PM org.hibernate.cfg.annotations.EntityBinder bindTable
INFO: Bind entity org.jboss.seam.example.booking.Booking on table Booking
The persistence unit is configured:
Aug 15, 2009 7:35:29 PM org.hibernate.ejb.Ejb3Configuration configure
+INFO: Processing PersistenceUnitInfo [+
name: bookingDatabase
+...]+
Problem: When I then check the database (HSQLDB or H2), none of the tables that should be created and populated as a result of the EJBs are there.
The only two issues/warnings that I see are:
Aug 15, 2009 7:35:29 PM org.hibernate.impl.SessionFactoryObjectFactory addInstance
INFO: Not binding factory to JNDI, no JNDI name configured+
Aug 15, 2009 7:35:29 PM org.hibernate.util.NamingHelper getInitialContext+
INFO: JNDI InitialContext properties:{}+
Aug 15, 2009 7:35:32 PM com.sun.faces.config.ConfigureListener contextInitialized
INFO: Initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/seam-jee5-booking'
Aug 15, 2009 7:35:34 PM org.jboss.seam.servlet.SeamListener contextInitialized
INFO: Welcome to Seam 2.1.2
Aug 15, 2009 7:35:34 PM org.jboss.seam.util.Resources getRealFile
WARNING: Unable to determine real path from servlet context for "/WEB-INF/classes" path does not exist.
Aug 15, 2009 7:35:34 PM org.jboss.seam.util.Resources getRealFile
WARNING: Unable to determine real path from servlet context for "/WEB-INF/dev" path does not exist.
Stack: JDK 1.6_011; WebLogic 10.3.1 (11g); Seam 2.1.2; Windows XP; HSQLDB 1.8
Any help you can provide would be much appreciated.
The app's persistence.xml:
<?xml version="1.0" encoding="UTF-8"?>
<persistence xmlns="http://java.sun.com/xml/ns/persistence"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
version="1.0">
<persistence-unit name="bookingDatabase">
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<jta-data-source>seam-jee5-ds</jta-data-source>
<properties>
     <!--<property name="hibernate.dialect" value="org.hibernate.dialect.Oracle10gDialect"/>-->
     <property name="hibernate.dialect" value="org.hibernate.dialect.HSQLDialect"/>
     <property name="hibernate.transaction.manager_lookup_class"
          value="org.hibernate.transaction.WeblogicTransactionManagerLookup"/>
</properties>
</persistence-unit>
</persistence>
Edited by: user447661 on Aug 17, 2009 9:41 AM
Edited by: user447661 on Aug 17, 2009 9:45 AM
Edited by: user447661 on Aug 17, 2009 9:47 AM

Answer 1

Nevermind, the issue was that my persistence.xml did not contain the following property:
<property name="hibernate.hbm2ddl.auto" value="create-drop"/>
Therefore, the tables were not being created upon deployment.
Still, I would expect to see entity beans listed in the WebLogic console.