Em Thu, 24 Jul 2008 18:14:32 -0300, Chris Lewis
<[EMAIL PROTECTED]> escreveu:
This is occurring in a development environment on a fresh and small app
with a schema with a total of 6 mapped entities, 7 tables, 3 records in
the abstract entity's table, one user (me), and all queries working
completely normally in the context of pages. I can't say it's impossible
for this to be a data issue, but the odds of that are miniscule.
I don't think so. When you have an inheritence mapping, yes, you can have
an interface or abstract class on the top. When you query for your Listing
class, Hibernate will create a query (typically a join with many tables)
that will load all possible Listing instances. For each row in the
returned ResultSet, Hibernate will try to figure out what is its
corresponding class. When it doesn't find it, it assumes the row is from
the searched type. In this case, Listing, an abstract class, thus you see
that error message. So it really looks to me like an inheritence mapping
problem or some Listing table row that doesn't have a matching one in the
subclasses tables (JOINED_TABLE inheritence mapping).
Please post your mappings and the generated SQL query here so we can check
them. :)
Thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
