This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
This does sound like something wrong with the schema you have defined to Hibernate. You said you app's database is empty. Does that mean that you are letting Hibernate create the scheme? Or do you already have a schema? If the former, post the source for the OLOLO (or class that represents this table) and com.trololo.pack.Class classes. If the latter, post the database schema for the OLOLO table.
Also, you might try running JBoss AS without your application deployed. This will ensure that you migration from Hypersonic to MySQL went OK for DefaultDS. After you have verified that that works, you can deploy your app and can work on its issues.
Of course I tried to run JBoss without applications deployed. It started well and 7 tables were created in MySql DB for JBoss (jbossdb).
Before I switched from Hypersonic to MySql I had well deploying and well running application. It's DB schema (myappdb in MySql) was generated by Hibernate and had no problem. After I switched to MySql I tried to make deploy both on the old schema in MySql (myappdb was filled with data) and with empty one. The result was the same:
org.hibernate.MappingException: An association from the table OLOLO refers to an unmapped class: com.trololo.pack.ClassInterface.
OLOLO class has a set of OneInstance objects and a single field of OneInstance . OneInstance entity inherits com.trololo.pack.ClassInterface interface.
Joined: Sep 27, 2011
Any ideas why switching to MySQL broke the hibernate's mapping?