Here is an example of hibernate configuration file that operates in embedded more:
Are you setting the Hibernate 'hbm2ddl.auto' config property at all?
Once your schema is created and if you had 'hbm2ddl.auto=create-drop', you should set Hibernate 'hbm2ddl.auto' config property to 'create' and issue a connection using 'IJ' like in the example above.
Note that once the database has been created with its schemas, etc, you can remove the ';create=true' on Hibernate's JDBC connection URL (hibernate.connection.url)....
Hope this helps.
Hello, I am attempting to use an embedded Derby instance wrapped with
Hibernate and Hibernate Annotations. However, after the tables are
initialized by Hibernate, the first time that I attempt to access the
tables Derby throws exceptions that claims the tables and views do not
exist. When I restart the application everything works fine (because
the tables already exist in the database on load). How can I possibly
alleviate this problem (without pulling Derby out into server mode)?